Phases Of Software Development Research Articles

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points

Abstract The Use Case Points (UCP) has been a method that often used as a reference to calculate effort estimation, the amount of worker and time required in software development project. In Reality, software project planning has not been only effort estimation, but also cost estimation to estimate how much cost of resource allocation spent in software development. Result of the effort estimation using UCP is the number of effort required to develop the software as a whole. In fact, the determination of the cost of software development is based on the cost per activity of pay rate different in each phase of software development. Therefore it requires the distribution of effort per activity to get the cost of software development. To produce cost estimation in the software development project, we need to know the percentage of each phase of software development, in this case called the effort distribution. The percentage of effort distribution was obtained through the collection of empirical data of governance's software development in small to medium scale. In this study, it was used 15 small and medium-sized projects of software development in Indonesia that was completed. The findings of this study was the value of the percentage of effort to the three categories of phases of the software development, namely: the percentage of the phase of software development at 72.6%, the percentage of the phase of the on-going life-cycle activities amounted to 17.5%, and a phase of quality control and testing amounted to 9.9%. While the percentage of detail presented in this paper. Another result of this study was the steps to determine the estimated costs for software development with UCP method.

Industrial Perspectives on the Impact of Object-Oriented Programming for SoftwareDevelopment

This study assessed the impact of object-oriented programming on the quality and reusability of software development. The degree to which object-oriented programming is prevalent over structured and other traditional programming in the software development phase at business organizations was investigated. This research examined the extent to which business organizations use object-oriented approach in software development. A number of professionals from the industries were surveyed to ascertain the relevance of advocating the incorporation of the object-oriented approach into computer science and information technology curriculums.

A novel effort estimation approach for requirement changes during software development phase

Managing software changes and achieving an effective change acceptance decision is one of the crucial factors in ensuring the software project success. Accepting too many changes will cause expense and delay and rejecting the changes may cause customer dissatisfaction. One of the inputs that help in achieving an effective change acceptance decision is by having reliable estimation on the change effort. From software development perspective, the estimation has to take into account the inconsistent states of software artifacts across project lifecycle i.e., fully developed or partially developed. These inconsistent states require different ways of estimation such as the fully developed artifacts may have different calculation compared to the partially developed artifacts. Many change effort estimation approaches have been developed and one of them is using impact analysis. One main challenge of this technique from software development perspective is that this technique is specifically used for software maintenance phase in which all software artifacts have been completely developed. This research introduces a new change effort estimation approach that is able to use different estimation techniques for different states of software artifacts. The outcome of this research is a new change effort estimation approach for software development phase using the extended version of the static and dynamic analysis techniques from our previous works.

An advanced training environment for vessels' last mile navigation

This article presents the design, development and prototyping of an advanced training environment for vessels' operations in the last mile of navigation. The main idea is to recreate the typical conditions in which operators are usually involved, including manoeuvres of large ships within the harbour area, tugboat operations to support ship manoeuvres and traffic. The system architecture includes three interoperable simulators, and this article focuses on one of the simulators, the tugboat simulator, presenting the system general architecture, the software design and development phase and the hardware integration. In particular, the 3D geometric models and the virtual environments (based on the port of Livorno, Italy) are introduced and described, the tugboat motion equations at sea (based on a 6 Degree of Freedom model) and the equations ruling the ship-tugboat interactions are presented and discussed; finally, specific information about the hardware integration (recreation of a tugboat bridge replica) is given.

Approximating the Evolution History of Software from Source Code

SUMMARY Once a software product has been released, a large number of software products may be derived from an original single product. Management and maintenance of product variants are important, but those are hardly cared because developers do not make efforts for the further maintainability in the initial phase of software development. However, history of products would be lost in typical cases and developers have only source code of products in the worst case. In this paper, we approximate the evolution history of software products using source code of them. Our key idea is that two successive products are the most similar pair of products in evolution history, and have many similar source files. We did an experiment to compare the analysis result with actual evolution history. The result shows 78% (on average) of edges in the extracted trees are consistent with the actual evolution history of the products.

Modelling and Evaluating Software Project Risks with Quantitative Analysis Techniques in Planning Software Development

Risk is not always avoidable, but it is controllable. The aim of this paper is to present new techniques which use the stepwise regression analysis tomodel and evaluate the risks in planning software development and reducing risk with software process improvement. Top ten software risk factors in planning software development phase and thirty control factors were presented to respondents. This study incorporates risk management approach and planning software development to mitigate software project failure. Performed techniques used stepwise regression analysis models to compare the controls to each of the risk planning software development factors, in order to determine and evaluate if they are effective in mitigating the occurrence of each risk planning factor and, finally, to select the optimal model. Also, top ten risk planning software development factors were mitigated by using control factors. The study has been conducted on a group of software project managers. Successful project risk management will greatly improve the probability of project success.

Soft competency requirements in requirements engineering, software design, implementation, and testing

Global software development changes the requirements in terms of soft competency and increases the complexity of social interaction by including intercultural aspects. While soft competency is often seen as crucial for the success of global software development projects, the concrete competence requirements remain unknown. Internationalization competency represents one of the first attempts to structure and describe the soft competence requirements for global software developers. Based on the diversity of tasks, competence requirements will differ among the various phases of software development. By conducting a survey on the importance of internationalization competences for the different phases of global software development, we identified differences in terms of competence importance and requirements in the phases. “Adaptability” (of one's working style) and “Cultural Awareness” were the main differences. “Cultural Awareness” distinguishes requirements engineering and software design from testing and implementation while “Adaptability” distinguishes implementation and software design from requirements engineering and testing.

Resolving Aspect Dependencies for Composition of Aspects

A new modularization technique is used in Aspect-oriented software development for the separation of widely used functions such as logging, caching, synchronization, and exception handling from the core business logic functions. Aspects are identified using the mathematical modeling tool, Colored Petri nets. During the software development process, dependencies may arise as a result of using operators such as Before, After, Around, and Replace; such dependencies are consumed by our framework. Using the specification of aspects, we generate a composition rule for every match point, which directs the composition process at the initial requirements phase of software development. The proposed FTS approach, incorporating a feedback edge set, topological ordering, and second valid ordering, is efficient in resolving conflicts and dependencies among the aspects. To analyze the second valid ordering, grey relational analysis is used to rank the aspects, while analysis of variance method is used for the verification thereof. The proposed approach is illustrated by a case study.

The effect of onsite-offshore work division on project cost, schedule, and quality for re-engineering projects in Indian outsourcing software industry

Purpose – The aim of this paper is to make an attempt to find good values of onsite–offshore team strength; number of hours of communication between business users and onsite team and between onsite and offshore team to reduce cost and improve schedule for re-engineering projects in global software development environment. Design/methodology/approach – The system dynamics technique is used for simulation model construction and policy run experimentation. The experts from Indian software outsourcing industry were consulted for model construction, validation and analysis of policy run results in both co-located and distributed software development environment. Findings – The study results show that there is a drop in the overall team productivity in outsourcing environment by considering the offshore options. But the project cost can be reduced by employing the offshore team for coding and testing work only with minimal training for imparting business knowledge. The research results show that there is a potential to save project cost by being flexible in project schedule. Research limitations/implications – The study found that there could be substantial cost saving for re-engineering projects with a loss of project schedule when an appropriate onsite–offshore combination is used. The quality and productivity drop, however, were rather small for such combinations. The cost savings are high when re-engineering work is sent to offshore location entirely after completion of requirement analysis work at onsite location and providing training to offshore team in business knowledge The research findings show that there is potential to make large cost savings by being flexible in project schedule for re-engineering projects. Practical implications – The software project manager can use the model results to divide the software team between onsite and offshore location during various phases of software development in distributed environment. Originality/value – The study is novel as there is little attempt at finding the team distribution between onsite and offshore location in global software development environment.

Empirical analysis of factors affecting confirmation bias levels of software engineers

Confirmation bias is defined as the tendency of people to seek evidence that verifies a hypothesis rather than seeking evidence to falsify it. Due to the confirmation bias, defects may be introduced in a software product during requirements analysis, design, implementation and/or testing phases. For instance, testers may exhibit confirmatory behavior in the form of a tendency to make the code run rather than employing a strategic approach to make it fail. As a result, most of the defects that have been introduced in the earlier phases of software development may be overlooked leading to an increase in software defect density. In this paper, we quantify confirmation bias levels in terms of a single derived metric. However, the main focus of this paper is the analysis of factors affecting confirmation bias levels of software engineers. Identification of these factors can guide project managers to circumvent negative effects of confirmation bias, as well as providing guidance for the recruitment and effective allocation of software engineers. In this empirical study, we observed low confirmation bias levels among participants with logical reasoning and hypothesis testing skills.

Improved Security Evaluation of the Software by using PSSS based Security Analyzer

After analyse the three security processes (CLASP, SDL AND PSSS) it has been selected that the PSSS as security approach to develop a secure project since of its advantages over the other two security processes. The most important objective of PSSS security process is to improve the effectiveness of software security projects. The overall objective of this paper is to evaluate the security analysis of the given software and return a security report which allows programmers to take certain action based upon the outcomes. The main objective of this dissertation is to develop a secure application using PSSS process and the other objectives areTo integrate the each activity of each phase of PSSS in each phase of software development. This paper initiated security process by establishment of a security Engineering approach consisting of security activities forming a process to support the development of more secure software. The validation of the security model has been done by approach by developing a security report through analysis. Thus, one can make its product more secured by rewrite and replacing some security threats in secure manner.

Proposing an Effective Artificial Neural Network Architecture to Improve the Precision of Software Cost Estimation Model

Software companies have to manage different software projects based on different time, cost, and manpower requirement, which is a very complex task in software project management. Accurate software estimates at the early phase of software development is one of the crucial objectives and a great challenge in software project management, in the last decades. Since software development attributes are vague and uncertain at the early phase of development, software estimates tend to a certain degree of estimation error. A software development cost estimation model incorporates soft computing techniques provides a solution to fit the vagueness and uncertainty of software attributes. In this paper, an adaptive artificial neural network (ANN) architecture for Constructive Cost Model (COCOMO) is proposed in order to produce accurate software estimates. The ANN is utilized to determine the importance of calibration of the software attributes using past project data in order to produce accurate software estimates. Software project data from the COCOMO I and NASA'93 data sets were used in the evaluation of the proposed model. The result shows an improvement in estimation accuracy of 8.36% of the ANN-COCOMO II when compared with the original COCOMO II.

Comparative analysis of statistical and machine learning methods for predicting faulty modules

The demand for development of good quality software has seen rapid growth in the last few years. This is leading to increase in the use of the machine learning methods for analyzing and assessing public domain data sets. These methods can be used in developing models for estimating software quality attributes such as fault proneness, maintenance effort, testing effort. Software fault prediction in the early phases of software development can help and guide software practitioners to focus the available testing resources on the weaker areas during the software development. This paper analyses and compares the statistical and six machine learning methods for fault prediction. These methods (Decision Tree, Artificial Neural Network, Cascade Correlation Network, Support Vector Machine, Group Method of Data Handling Method, and Gene Expression Programming) are empirically validated to find the relationship between the static code metrics and the fault proneness of a module. In order to assess and compare the models predicted using the regression and the machine learning methods we used two publicly available data sets AR1 and AR6. We compared the predictive capability of the models using the Area Under the Curve (measured from the Receiver Operating Characteristic (ROC) analysis). The study confirms the predictive capability of the machine learning methods for software fault prediction. The results show that the Area Under the Curve of model predicted using the Decision Tree method is 0.8 and 0.9 (for AR1 and AR6 data sets, respectively) and is a better model than the model predicted using the logistic regression and other machine learning methods.

Optimal cost: a criterion to release multiple versions of software

With successful multi up gradations of software as an indispensable part of any Information Technology company, the challenge before them is to decide when to stop testing these multiple versions. Too much of testing delays the software system’s entry into the market and also costs more. Releasing the software system too soon without adequate testing may cause customers’ dissatisfaction and may lead to failure of the software system in the market. In this paper we introduce cost model for each release of software based on debugging costs at different phases of software development viz-a-viz, testing and operational phase. Our model incorporates three new features that are not included in the literature. First, to the total cost incurred during the testing phase of new release, we add the debugging cost associated with remaining number of reported faults from previous release. Second, we consider that some of the remaining faults of previous release are partly removed during the testing phase and partly during the operational phase of new release. Third, we calculate the optimal testing time for each release of software in the presence of debugging costs associated from the previous releases. An Algorithm for finding optimal testing time for each version is developed. We estimate the parameters of the model using Statistical Package for Social Sciences on real data set and obtain optimum stopping time for each version of software using Maple software.

A Systematic Method for Identification of Anti-patterns in Service Oriented System Development

Service-Oriented Architecture is one of the popular software architecture's patterns used for developing lots of modern systems. However, it has been involved in many failures. Anti-patterns are solutions which have good view, but in fact they are wrong solutions that cause failure of systems. There are a lot of anti-patterns for SOA and new anti-patterns are revealed every day. Anti-patterns have their own reasons for being formed and also they are appeared in special area of the problem. As human's mind is restricted and it can process a limited number of states (piece of information) therefore identification of anti-patterns will be difficult for architects. In this paper, we propose a systematic method based on repository of anti-patterns along with a check list to identify anti-patterns of SOA. This method will assist architects to easily detect and avoid anti-patterns in development process and so escape from risks which related to anti-patterns. Furthermore, in this paper, we present a repository of forty five general anti-patterns in SOA. Reviewing these anti-patterns will help developers to work with clear understanding of patterns in phases of software development and so avoid from many potential problems. Also, our method is evaluated in action. DOI: http://dx.doi.org/10.11591/ijece.v4i1.4097 Normal 0 false false false EN-US X-NONE AR-SA /* Style Definitions */ table.MsoNormalTable {mso-style-name:Table Normal; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Times New Roman,serif;}

Considering Partially Developed Artifacts in Change Impact Analysis Implementation

It is important to manage the changes in the software to meet the evolving needs of the customer and hence, satisfy them. Accepting too many changes causes delay in the completion and it incurs additional cost. One type of information that helps to make the decision is the prediction of the number of classes affected by the changes or change impact analysis. Current impact analysis approaches assume that all classes in the class artifact are completely developed and the class artifact is used as a source of analysis since it represents the final user requirements. However, these assumptions are impractical for impact analysis in the software development phase as some classes in the class artifact are still under development or partially developed that leads to inaccuracy. This paper presents a novel impact analysis approach to be used in the software development phase. The significant achievements of the approach are demonstrated through an extensive experimental validation using several case studies. The experimental analysis shows improvement in the accuracy over current impact analysis results.

Risk Impact Analysis across the Phases of Software Development

success factors of any project will surface as risks if overlooked. This paper therefore focuses on analyzing the impact of these risks across all the phases of software development which are categorized in terms of short term and long term projects. This mode of analysis enables the developer to comprehend and thereby manage the risks more effectively.

Perceived Risks and Ict Use

The objective of this research is to investigate the types of problems and their associated perceived risks as well as the effects of risks perceived on frequently used information communication technologies (ICTs) by globally distributed software development teams. We focused on perceived risk in reception, understanding and action and studied two global software teams that were at different software development phases (i.e. requirements analysis versus development and maintenance). Data for this research was collected from a leading global IT consulting company and we found that instant messaging, email and teleconferencing system were frequently used by the two teams. Our results indicate that perceived risks in reception and action were encountered by members in the systems development and maintenance phase. Additionally, we also found differences on the effects of perceived risks on the use of instant messaging, email and teleconferencing system between the teams.

A Survey on Factors Affecting Testing Techniques in Object Oriented Software

The focus of this research paper is on the analysis of factors which affect software testing techniques in Object Oriented Software with the opinion of people who are engage in software development phases. The study uses a survey instrument to analyze the factors and identify factors that have significant impact on software testing techniques. The research focuses on the perspective of the primary participants, managers, programmers, testers and other people involved in software research or development teams. The original contribution of this research is to provide a general guide to the important aspects to consider in the whole software development process.

An approach to creating concretized test scenarios within test automation technology for industrial software projects

The paper describes an approach for creation of effective test automation technology for industrial software projects based on a formal model of the system under test, performing its automatic symbolic verification of the model and generation of symbolic traces, then their automatic concretization, generation and execution of test suites. The technology includes means for test results analysis and tests correction and update. High quality of software products is ensured by a balance between static (verification) and dynamic (testing) analysis techniques starting from the earlier development phases and through automation of all phases of software development. Special emphasis is made on presentation of the algorithm of concretization and configuring test scenarios.