A Controlled Expeniment on the Impact of Software Structure on Maintainability
IEEE Transactions on Software Engineering
Object-oriented modeling and design
Object-oriented modeling and design
Software requirements & specifications: a lexicon of practice, principles and prejudices
Software requirements & specifications: a lexicon of practice, principles and prejudices
How well do experienced software developers predict software change?
Journal of Systems and Software
The unified software development process
The unified software development process
Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Software Change Impact Analysis
Software Change Impact Analysis
An Object-Oriented Tool for Tracing Requirements
IEEE Software
Supporting impact analysis: a semi-automated technique and associated tool
ICSM '95 Proceedings of the International Conference on Software Maintenance
A Weakly Constrained Approach to Software Change Coordination
Proceedings of the 26th International Conference on Software Engineering
Reconstructing requirements coverage views from design and test using traceability recovery via LSI
TEFSE '05 Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering
An industrial case study in reconstructing requirements views
Empirical Software Engineering
Lightweight query-based analysis of workflow process dependencies
Journal of Systems and Software
Semantic Management of Heterogeneous Documents
MICAI '09 Proceedings of the 8th Mexican International Conference on Artificial Intelligence
The emergence of requirements networks: the case for requirements inter-dependencies
International Journal of Computer Applications in Technology
| Hi-index | 0.00 |
ABSTRACT Technical systems play an important role in our daily lives. Most systems have to be changed during their lifetime, but cost estimates of changes are often inaccurate and implementation of changes is time consuming and cost intensive. Planning and performing changes can be supported by precise impact analysis. Traditionally, impact analysis has been something that software professionals do intuitively, after some cursory examination of code and documentation. But, empirical investigation shows that even experienced software professionals predict incomplete sets of change impacts. This paper introduces an approach that focuses on impact analysis of system requirements changes and that is suited for embedded control systems. The approach is based on a fine-grained trace model. Empirical studies show that the approach allows a more effective impact analysis of changes on embedded systems.