Software maintenance: an approach to impact analysis of objects change
Software—Practice & Experience
Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Modeling of software concerns in Cosmos
AOSD '02 Proceedings of the 1st international conference on Aspect-oriented software development
Tracing All Around in Reengineering
IEEE Software
A Scenario-Driven Approach to Trace Dependency Analysis
IEEE Transactions on Software Engineering
Modularisation and composition of aspectual requirements
Proceedings of the 2nd international conference on Aspect-oriented software development
A Model for Change Propagation Based on Graph Rewriting
ICSM '97 Proceedings of the International Conference on Software Maintenance
Recovering documentation-to-source-code traceability links using latent semantic indexing
Proceedings of the 25th International Conference on Software Engineering
A concern-oriented requirements engineering model
CAiSE'05 Proceedings of the 17th international conference on Advanced Information Systems Engineering
ACM SIGSOFT Software Engineering Notes
On the relationship of concern metrics and requirements maintainability
Information and Software Technology
Investigating dependencies in software requirements for change propagation analysis
Information and Software Technology
| Hi-index | 0.00 |
A few AO Requirement Engineering approaches support traceability by providing mapping and influence of requirements-level concerns on subsequent phase artefacts. This is not sufficient to ensure that the architecture actually meets the specified requirements (as some requirements lead to architectural decisions, establish trade-offs, etc). Equally, without knowledge of such traceability relationships it becomes very difficult to predict change impact and thus understand the causes of system instability. In order to improve this situation, we have developed a concern-oriented dependency taxonomy that enables us to capture the dependency relationships between requirements-level concerns and their manifestation at the architectural level. We have applied the dependency taxonomy on a real-world case study to explore and identify unstable architectural components, which are most likely to be impacted by change.