Use Case Maps as Architectural Entities for Complex Systems
IEEE Transactions on Software Engineering
Scenario-Based Analysis of Software Architecture
IEEE Software
Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
Towards Method-Driven Trace Capture
CAiSE '97 Proceedings of the 9th International Conference on Advanced Information Systems Engineering
Recovering documentation-to-source-code traceability links using latent semantic indexing
Proceedings of the 25th International Conference on Software Engineering
Nonfunctional Requirements: From Elicitation to Conceptual Models
IEEE Transactions on Software Engineering
A Heterogeneous Solution for Improving the Return on Investment of Requirements Traceability
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Helping Analysts Trace Requirements: An Objective Look
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Goal-centric traceability for managing non-functional requirements
Proceedings of the 27th international conference on Software engineering
Hidden Implementation Dependencies in High Assurance and Critical Computing Systems
IEEE Transactions on Software Engineering
TQL: A query language to support traceability
TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
The emergence of requirements networks: the case for requirements inter-dependencies
International Journal of Computer Applications in Technology
A fuzzy traceability vector model for requirements validation
International Journal of Computer Applications in Technology
| Hi-index | 0.00 |
This position paper examines current practices and challenges for tracing non-functional requirements (NFRs). Anecdotal evidence suggests that many organizations do not effectively trace NFRs and that functional changes are often implemented with very little understanding as to how system qualities such as safety, security, and performance will be impacted. The tendency for NFRs to have broad ranging impact upon a software system, and the strong interdependencies and tradeoffs that exist between NFRs and the software architecture leave typical existing traceability methods insufficient for tracing NFRs. This paper focuses on post-requirements traceability of NFRs. It first identifies three critical areas in which NFRs require traceability support, it then evaluates existing traceability methods, and finally proposes a more holistic traceability environment named Goal Centric Traceability that supports impact analysis of NFRs within the context of the software architecture in which they are deployed.