Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Using non-functional requirements to systematically support change
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Defining goals in a COTS-aware requirements engineering approach: Regular Paper
Systems Engineering
Analysing the impact of change in COTS-Based systems
ICCBSS'05 Proceedings of the 4th international conference on COTS-Based Software Systems
Visualization and comparison of architecture rationale with semantic web technologies
Journal of Systems and Software
"integrare", a collaborative environment for behavior-oriented design
CDVE'07 Proceedings of the 4th international conference on Cooperative design, visualization, and engineering
| Hi-index | 0.00 |
Rapid changes in a component-based application (CBA), or the capabilities available in off-the-shelf (OTS) components, have significant impact on the specification and evolution of requirements in an OTS-aware requirements engineering paradigm. A well-disciplined, systematic methodology that explicitly supports the use of OTS components needs a clearly defined process for effectively managing the inevitable changes and determining the impact of such changes on the system. In this paper, we present a Non-functional Requirement (NFR) Framework based approach that supports representing changes either to an OTS component or a CBA, the associations from components to the requirements using positive and negative contributions, reasoning about the impact of change, and (re-)evaluating the degree of meeting requirements as a result of these change.