Requirements traceability to support evolution of access control
SESS '05 Proceedings of the 2005 workshop on Software engineering for secure systems—building trustworthy applications
Tracing software product line variability: from problem to solution space
SAICSIT '05 Proceedings of the 2005 annual research conference of the South African institute of computer scientists and information technologists on IT research in developing countries
Extracting traceability information from C# projects
ICCOMP'05 Proceedings of the 9th WSEAS International Conference on Computers
TQL: A query language to support traceability
TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
Customizing traceability links for the unified process
QoSA'07 Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications
A model-driven traceability framework for software product lines
Software and Systems Modeling (SoSyM)
Linking feature models to code artifacts using executable acceptance tests
SPLC'10 Proceedings of the 14th international conference on Software product lines: going beyond
Squid: an extensible infrastructure for analyzing software product line implementations
Proceedings of the 16th International Software Product Line Conference - Volume 2
| Hi-index | 0.00 |
During their usage, software systems have to be changedconstantly. If such changes are implemented in an incompleteor inconsistent way a loss of architectural qualitywill occur, i.e. in terms of maintainability and understandability.The lack of traceability of the impact of changedrequirements in the software enhances this effect. Traceabilitylinks have been proposed as a link between therequirements and the different parts of a solution. In practicaluse, these links are difficult to establish and maintain.Currently, tools cannot effectively support these links dueto human-required decisions. This paper introduces featuremodels as an intermediate element for linking requirementsto design models. They enable a more appropriatebridging of the different levels of abstraction. Featuremodels group sets of requirements to a feature andenable a modeling of the variability of requirements. Thefeature models structure traceability links between requirements,design elements and implementation parts.This leads to lower efforts of establishing and maintainingthe links. Furthermore, descriptions of design decisionscan be attached to the links. Industrial experience with thisapproach shows its support for the evolutionary developmentof large software systems, especially in the improvedcomprehension of the changes by the developers.