Metrics and laws of software evolution the nineties view

The distribution of class size and complexity retains its shape over time. Relatively little code is modified over time. Classes that tend to be modified, however, are also the more popular ones, that is, those with greater Fan-In. Measuring Software Flexibility by Amnon H. Eden, Tom Mens. Flexibility has been recognized as a desirable quality of software since the earliest days of software engineering.

Classic and contemporary software design litera-ture suggest that particular implementations are more flexible than others but stop short of suggesting objective criteria for Classic and contemporary software design litera-ture suggest that particular implementations are more flexible than others but stop short of suggesting objective criteria for quantifying such claims.

To measure software flexibility in precise terms, we introduce the notion of evolution complexity and dem-onstrate how it can be used to measure and compare the flexibility of— 1. We conclude with experimental results corroborating our claims. Refactoring is a hot and controversial issue. Supporters claim that it helps increasing the quality of the code, making it easier to understand, modify and maintain.

Moreover, there are also claims that refactoring yields higher development productivity — however, there is only limited emp Moreover, there are also claims that refactoring yields higher development productivity — however, there is only limited empirical evidence of such assumption.

A case study has been conducted to assess the impact of refactoring in a close-to industrial environment. Results indicate that refactoring not only increases aspects of software quality, but also improves productivity. Our findings are applicable to small teams working in similar, highly volatile domains ours is application development for mobile devices.

However, additional research is needed to ensure that this is indeed true and to generalize it to other contexts. Based on Source-Forge, most studies have concluded that the vast majority of projects are failures.

Abstract - Cited by 6 4 self - Add to MetaCart has often been evaluated through the number of commits made to its configuration management system, number of developers and number of users. This paper argues that the relative success of a FLOSS project can depend also on the chosen forge and distribution. Given a random sample of 50 projects contained within a popular FLOSS forge Debian, which is the basis of the successful Debian distribution , we compare these with a similar sample from SourceForge, using product and process metrics, such as size achieved and number of developers involved.

Secondly, the projects included in the Debian distribution benefit, on average, from more evolutionary activity and more developers than the comparable projects on SourceForge. Finally, the Debian projects start to benefit from more activity and more developers from the point at which they join this distribution.

Abstract-Background: Software systems must evolve in order to adapt in a timely fashion to the rapid changes of stakeholder needs, technologies, business environment and society regulations. Numerous studies have shown that cost, schedule or defect density of a software project may escalate as the Abstract - Cited by 4 0 self - Add to MetaCart Abstract-Background: Software systems must evolve in order to adapt in a timely fashion to the rapid changes of stakeholder needs, technologies, business environment and society regulations.

Numerous studies have shown that cost, schedule or defect density of a software project may escalate as the requirements evolve. Requirements evolution management has become one important topic in requirements engineering research. Aim: To depict a holistic state-of-the-art of requirement evolution management. Method: We undertook a systematic review on requirements evolution management.

Results: relevant studies were identified and reviewed. This paper reports the preliminary results from this review: 1 the terminology and definition of requirements evolution; 2 fourteen key activities in requirements evolution management; 3 twenty-eight metrics of requirements evolution for three measurement goals.

Conclusions: Requirements evolution is a process of continuous change of requirements in a certain direction. Perry , W. Citations: - 3 self. Abstract The process of E-type software development and evolution has proven most difficult to improve, possibly due to the fact that the process is a multi-input, multi-output system involving feedback at many levels. Keyphrases software evolution ninety view feast hypothesis software evolution process financial transaction system new analysis support new path preliminary conclusion on-going twoyear project e-type software development many level multi-output system feedback aspect relevant today process modelling extended study metric analysis.

Powered by:. Software evolution and software evolvability. Highly Influenced. View 4 excerpts, cites background and methods.

Feedback in the software evolution process. Engineering, Computer Science. Laws of Software Evolution Revisited. Programs, life cycles, and laws of software evolution. Proceedings of the IEEE. By classifying programs according to their relationship to the environment in which they are executed, the paper identifies the sources of evolutionary pressure on computer applications and programs … Expand.

System dynamics modeling of an inspection-based process. Principles of software engineering management. Computer Science, Engineering. A discipline for software engineering. Series in software engineering. On understanding laws, evolution, and conservation in the large-program life cycle.

The paper presents interpretations of some recently discovered laws of evolution and conservation in the largeprogram life cycle. Program development and maintenance processes are managed and … Expand.