Other Agile Methods

Author(s):  
Barbara Russo ◽  
Marco Scotto ◽  
Alberto Sillitti ◽  
Giancarlo Succi

In the early ‘90s, the IBM Consulting Group hired Alistair Cockburn to build a methodology for object-oriented development. Cockburn investigated a large number of software projects and asked to each team to identify the main reasons for their own success. Cockburn has defined Crystal (Cockburn, 2004) as a family of AMs, because he believed that different kinds of projects require different development methodologies.

Author(s):  
Patrick A Gray ◽  
Bo Sandén ◽  
Phillip Laplante

A way to measure the complexity of object-oriented software involves topological features of the code's hierarchical organization at the method, class, package, and component levels. Sangwan et al (2008) suggested that as certain software products evolve, this complexity shifts from lower to higher structural levels, or vice-versa. They studied three widely used open source software programs and showed that these structural shifts called “epochs” were present and suspected that this phenomenon was pervasive. To support or refute this assertion, 30 open source programs were studied and structural shifts in complexity were found significantly in 27 of them. In those projects where no complexity shift was evident, no refactoring had occurred. These findings further suggest that in large, open source software projects, when refactoring occurs a shifting in complexity from one level to another will occur.


Author(s):  
Boris Roussev

Agile methods are lightweight, iterative software development frameworks used predominantly on small and mid-sized software development projects. This chapter introduces a project structure and management practices creating agile conditions for large software projects outsourced either offshore or onshore. Agility is achieved by slicing a large project into a number of small projects working in agile settings. Development is divided into research and development activities that are located on-site, and production activities located off-site. The proposed approach makes agile methods applicable to the stressed conditions of outsourcing without compromising the quality or pace of the software development effort. Creating an agile environment in an outsourcing project relies on maintaining a balance between the functions and sizes of on-site and off-site teams, on redefining the developers’ roles, and on reorganizing the information flow between the different development activities to compensate for the lack of customers on-site, team colocation, and tacit project knowledge.


2014 ◽  
Vol 2014 ◽  
pp. 1-10 ◽  
Author(s):  
Rongcun Wang ◽  
Rubing Huang ◽  
Binbin Qu

The object-oriented software systems frequently evolve to meet new change requirements. Understanding the characteristics of changes aids testers and system designers to improve the quality of softwares. Identifying important modules becomes a key issue in the process of evolution. In this context, a novel network-based approach is proposed to comprehensively investigate change distributions and the correlation between centrality measures and the scope of change propagation. First, software dependency networks are constructed at class level. And then, the number of times of cochanges among classes is minded from software repositories. According to the dependency relationships and the number of times of cochanges among classes, the scope of change propagation is calculated. Using Spearman rank correlation analyzes the correlation between centrality measures and the scope of change propagation. Three case studies on java open source software projects Findbugs, Hibernate, and Spring are conducted to research the characteristics of change propagation. Experimental results show that (i) change distribution is very uneven; (ii) PageRank, Degree, and CIRank are significantly correlated to the scope of change propagation. Particularly, CIRank shows higher correlation coefficient, which suggests it can be a more useful indicator for measuring the scope of change propagation of classes in object-oriented software system.


2012 ◽  
Vol 52 (No. 4) ◽  
pp. 165-172
Author(s):  
V. Merunka

The development of business information systems has the communication gap that exists between business and software experts, because they live in their own well-defined and complex cultures. One place where this gap manifests itself is in the constant failure of software developers to fully capture the system requirements. Second example is the inability to exactly analyze and store business knowledge. In our experience, gathered during the last ten years, working on major software projects, not all system requirements are known at the start of the project and the customers expect that their discovery and refinement will form part of the project. Our solution of this dilemma is in the new methodology called BORM (Business and Object Relationship Modeling), which reuses the object-oriented approach known from the area of software engineering into the area of business process modeling. CraftCASE is the original Czech software tool supporting BORM. CraftCASE is developed to capture and analyze knowledge of process-based business systems. The integral part of the analysis using CraftCASE is object-oriented process diagram and process simulator. 


Author(s):  
Boris Roussev

Agile methods are lightweight, iterative software development frameworks used predominantly on small and mid-sized software development projects. This chapter introduces a project structure and management practices creating agile conditions for large software projects outsourced either offshore or onshore. Agility is achieved by slicing a large project into a number of small projects working in agile settings. Development is divided into research and development activities that are located on-site, and production activities located off-site. The proposed approach makes agile methods applicable to the stressed conditions of outsourcing without compromising the quality or pace of the software development effort. Creating an agile environment in an outsourcing project relies on maintaining a balance between the functions and sizes of on-site and off-site teams, on redefining the developers’ roles, and on reorganizing the information flow between the different development activities to compensate for the lack of customers on-site, team colocation, and tacit project knowledge.


Author(s):  
Tülin Erçelebi Ayyildiz ◽  
Altan Koçyiğit

This paper analyzes the correlations between the problem domain measures such as the number of distinct nouns and distinct verbs in the requirements artifacts and the solution domain measures such as the number of software classes and methods in the corresponding object-oriented software. For this purpose, 14 completed software development projects of a CMMI Level-3 certified defense industry company have been analyzed. The observed strong correlation is taken as the indication of linear relationship between the measures and a size estimation model based on linear regression analysis is proposed. Prediction performance of the method is analyzed on the 14 software projects. Moreover, it has been observed that there is a high correlation between the problem domain measures and the development effort. Therefore, the linear regression analysis is also used to estimate the effort in terms of the problem domain measures. The effort estimations are also evaluated and compared with the efforts predicted using the size measured by the COSMIC Function Point (CFP) method. The results show that the proposed method provides more accurate effort estimates compared to the effort estimated by using CFP size measurement.


2022 ◽  
pp. 929-946
Author(s):  
Kalle Rindell ◽  
Sami Hyrynsalmi ◽  
Ville Leppänen

Agile software development was introduced in the beginning of the 2000s to increase the visibility and efficiency software projects. Since then it has become as an industry standard. However, fitting sequential security engineering development models into iterative and incremental development practices in agile methods has caused difficulties in defining, implementing, and verifying the security properties of software. In addition, agile methods have also been criticized for decreased quality of documentation, resulting in decreased security assurance necessary for regulative purposes and security measurement. As a consequence, lack of security assurance can complicate security incident management, thus increasing the software's potential lifetime cost. This chapter clarifies the requirements for software security assurance by using an evaluation framework to analyze the compatibility of established agile security development methods: XP, Scrum, and Kanban. The results show that the agile methods are not inherently incompatible with security engineering requirements.


Author(s):  
Ruchika Malhotra ◽  
Juhi Jain

Development without any defect is unsubstantial. Timely detection of software defects favors the proper resource utilization saving time, effort and money. With the increasing size and complexity of software, demand for accurate and efficient prediction models is increasing. Recently, search-based techniques (SBTs) have fascinated many researchers for Software Defect Prediction (SDP). The goal of this study is to conduct an empirical evaluation to assess the applicability of SBTs for predicting software defects in object-oriented (OO) softwares. In this study, 16 SBTs are exploited to build defect prediction models for 13 OO software projects. Stable performance measures — GMean, Balance and Receiver Operating Characteristic-Area Under Curve (ROC-AUC) are employed to probe into the predictive capability of developed models, taking into consideration the imbalanced nature of software datasets. Proper measures are taken to handle the stochastic behavior of SBTs. The significance of results is statistically validated using the Friedman test complied with Wilcoxon post hoc analysis. The results confirm that software defects can be detected in the early phases of software development with help of SBTs. This paper identifies the effective subset of SBTs that will aid software practitioners to timely detect the probable software defects, therefore, saving resources and bringing up good quality softwares. Eight SBTs — sUpervised Classification System (UCS), Bioinformatics-oriented hierarchical evolutionary learning (BIOHEL), CHC, Genetic Algorithm-based Classifier System with Adaptive Discretization Intervals (GA_ADI), Genetic Algorithm-based Classifier System with Intervalar Rule (GA_INT), Memetic Pittsburgh Learning Classifier System (MPLCS), Population-Based Incremental Learning (PBIL) and Steady-State Genetic Algorithm for Instance Selection (SGA) are found to be statistically good defect predictors.


A lot of Size Estimation technique has been previously proposed for estimation of the effort of object oriented software projects. After reviewing several object oriented metrics we found that FFP is most excellent right metrics for real occasion application. We took FFP metric for estimating the size. There control functions will helps to calculate those complex, scientific or real time process that were not easily estimated by FP or any other metrics. This research job mostly focus on formative the functional_size of Real-time application at early stage. We define the rules to identify logical files from UML diagrams on different models of OMT. This proposed model is completely base on OOD Methodology owing to the version of the Function_Point Analysis to Object_Point Analysis .We also presented the result obtained by applying the model in a Case study. The result has proven that discovered OOFFA metric and Effort estimation model (OOFFMM) is the best model and metric suite for object oriented MIS applications as well as real time applications


Sign in / Sign up

Export Citation Format

Share Document