• Corpus ID: 12465847

Traceability Framework : From Requirements Through Architecture and Design

@inproceedings{Pinto2008TraceabilityF,
  title={Traceability Framework : From Requirements Through Architecture and Design},
  author={M{\'o}nica Pinto and Lidia Fuentes and Ruzanna Chitchyan and Awais Rashid and Lancaster and Andrew Jackson and Siobh{\'a}n Clarke and B. Shishkov and Bedir Tekinerdogan and Mehmet Aksit and Uni and Phil Greenwood and Raffi Khatchadourian},
  year={2008}
}
The ability to follow and examine (i.e., trace) the life of a artifact throughout software evolution can greatly improve overall system comprehension. In this deliverable, we present material directed towards a traceability framework for tracing between software engineering-related artifacts, such as software requirements, software architecture, and software design. This work relies on previous efforts documented in D36, D37, D38 and D63, and has as its primary aim of providing traceability… 
1 Citations

References

SHOWING 1-10 OF 25 REFERENCES
An analysis of the requirements traceability problem
  • O. Gotel, A. Finkelstein
  • Computer Science
    Proceedings of IEEE International Conference on Requirements Engineering
  • 1994
TLDR
The distinction between pre-requirements specification (pre-RS) traceability and post-RS traceability is introduced to demonstrate why an all-encompassing solution to the problem is unlikely, and to provide a framework to understand its multifaceted nature.
Implementing requirements traceability: a case study
TLDR
A case study of a systems development organization employing a comprehensive view of traceability, a model describing the traceability practice in the organization, perceived benefits of such a scheme and lessons learnt from implementing it are presented.
Analysis of crosscutting across software development phases based on traceability
TLDR
This work uses trace relations to define crosscutting, and formalizes the definition in terms of linear algebra, and represented with matrices and matrix operations, so that crosscutting can be clearly distinguished from scattering and tangling.
On the Impact of Aspectual Decompositions on Design Stability: An Empirical Study
TLDR
A quantitative case study that evolves a real-life application to assess various facets of design stability of OO and AO implementations and includes an analysis of the application in terms of modularity, change propagation, concern interaction, identification of ripple-effects and adherence to well-known design principles.
Approach for Change Impact Analysis of Aspectual Requirements
TLDR
The change impact analysis model is a multidimensional concern-slicing approach that facilitates understanding of requirements dependencies and impact of requirements change.
TITAN: a Framework for Aspect Oriented System Evolution
TLDR
Titan is a framework that supports system evolution through aspect oriented techniques, allowing to verify whether the added behaviour produces the expected results, and generates a CCS algebraic description of the system.
Aspect-Based Introspection and Change Analysis for Evolving Programs
TLDR
This work contributes a tool that assists with the deployment of new code to evolving software that gives insight as to precisely the behavioral changes between the new code and the code it is replacing within the running system.
Quantifying the Effects of Aspect-Oriented Programming: A Maintenance Study
TLDR
It is found that the aspect-oriented design has exhibited superior stability and reusability through the changes, as it has resulted in fewer lines of code, improved separation of concerns, weaker coupling, and lower intra-component complexity.
Change impact analysis to support architectural evolution
TLDR
The main feature of this approach is to assess the effect of changes in a software architecture by analyzing its formal architectural specification, and, therefore, the process of change impact analysis can be automated completely.
Celadon: a change impact analysis tool for aspect-oriented programs
TLDR
Celadon helps facilitate fault localization by isolating failure-inducing changes for one specific affected test from other irrelevant changes, and decomposes their differences into a set of atomic changes together with their dependence relationships.
...
1
2
3
...