Corpus ID: 6570742

An Empirical Study of Requirements-Driven Impact Analysis in Object-Oriented Software Evolution

@inproceedings{Lindvall1997AnES,
  title={An Empirical Study of Requirements-Driven Impact Analysis in Object-Oriented Software Evolution},
  author={M. Lindvall},
  year={1997}
}
Requirements-driven impact analysis (RDIA) identifies the set of software entities that need to be changed to implement a new requirement in an existing system. RDIA thus involves a transition from requirements to software entities or to a representative model of the implemented system. RDIA is performed during the release planning phase. Input is a set of requirements and the existing system. Output is, for each requirement, a set of software entities that have to be changed. The output is… Expand

Figures, Tables, and Topics from this paper

How well do experienced software developers predict software change?
TLDR
This paper quantifies how well experienced software developers predict change by conducting rdia, where rdian is the general activity of predicting changes based on change request and finds that project developers are unaware of their own positive and negative capabilities in predicting change. Expand
Impact Analysis in Software Evolution
Abstract Project planning relies on accurate estimates of the work at hand. In software development, the work at hand is represented by the requirements. In software evolution, when new requirementsExpand
Impact Analysis : Organisational Views and Support Techniques
Change is unavoidable in software development. During the entire lifecycle of a product, from concept to retirement, the environment changes; the needs of customers or the market change and grow, andExpand
Design properties and object-oriented software changeability
TLDR
This research defined a model of software changes and change impacts, and implemented it for the C++ language, and identified a set of nine object-oriented (OO) design metrics, four of which are specifically geared towards changeability detection. Expand
EXPLORING PROCESS ASPECTS OF CHANGE IMPACT ANALYSIS
Change is inevitable in software development. During the entire lifecycle of a software system, from conception to retirement, things happen that require the system to be changed: the hardware andExpand
Market-Driven Requirements Engineering Process Model – MDREPM
Research findings in requirements engineering (RE) report that software organizations still struggle in establishing processes that lead to proper requirements handling. This leads to theExpand
Software change impact analysis: an approach to differentiate type of change to minimise regression test selection
TLDR
A new approach of estimating impact analysis by allocating tokens to the changes encountered in the two versions of the software system is proposed and an algorithm is proposed for token allocation and for determining matches which take into account a minimum threshold value to predict the matched results. Expand
An Empirically-Based Process for Software Architecture Evaluation
TLDR
This paper defines and uses a set of architectural metrics and outlines a process for analyzing architecture to support such an argument, and reports on a case study where the architecture of an existing client-server system was restructured while adding new functionality. Expand
X Design Properties and Evolvability of Object-Oriented Systems
Over the years, cumulative data have shown that maintenance is a major cost concern, as a matter of fact, a growing cost concern (Pigosky, 1997). The maintainability of a system seems to have muchExpand
The visibility of maintenance in object models: an empirical study
  • M. Lindvall, Magnus Runesson
  • Computer Science
  • Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272)
  • 1998
TLDR
The major finding is that even though many of the classes are changed, the majority of these changes turn out to be invisible in the object model, which means that changes made on the source code level are of a finer granularity than available in common object modeling concepts. Expand
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 50 REFERENCES
Traceability aspects of impact analysis in object-oriented systems
TLDR
A promising potential is seen for using traceability, together with the use of existing object models, to achieve a more structured impact analysis process and accurate prediction in an industrial object-oriented system. Expand
The impact analysis task in software maintenance: a model and a case study
TLDR
A general model of software impacts is presented that uses flexible declarative propagation rules to describe the way software objects affect each other and distinguishes between impact analysis and program understanding. Expand
An early impact analysis technique for software maintenance
TLDR
This paper surveys existing ripple analysis techniques and presents a new technique for the early detection of ripple effects based on a simple graph-theoretic model of documentation and the themes within the documentation. Expand
A framework for software maintenance metrics
TLDR
The authors introduce a software maintenance process model that emphasizes impact analysis and forms a framework for software maintenance metrics support, as well as new impact analysis metrics that address software work-product traceability and inter-work-product dependencies. Expand
Why is Software Late? An Empirical Study of Reasons For Delay in Software Development
TLDR
It is recommended that every department should gain an insight into its reasons for delay in order to be able to take adequate actions for improvement. Expand
Characteristics of application software maintenance
TLDR
The results of the analysis indicate that maintenance and enhancement do consume much of the total resources of systems and programming groups and user demands for enhancements and extension constitute the most important management problem area. Expand
Object-oriented metrics that predict maintainability
TLDR
This research concentrates on several object-oriented software metrics and the validation of these metrics with maintenance effort in two commercial systems. Expand
Mechanisms of modifiability in large software systems
TLDR
The mechanisms behind the exhibited modifiability and lack of modifiable in a large commercial software system during a part of its evolution are investigated, and a dichotomy of software modularizations is proposed. Expand
Object-oriented software engineering - a use case driven approach
TLDR
This chapter discusses object-oriented software engineering as a process of change, management and reuse, and some of the methods used to develop and implement object- oriented software. Expand
Some Stability Measures for Software Maintenance
TLDR
In this paper, measures for estimating the stability of a program and the modules of which the program is composed are presented, and an algorithm for computing these stability measures is given. Expand
...
1
2
3
4
5
...