A Scenario-Driven Approach to Trace Dependency Analysis

Software development artifacts-such as model descriptions, diagrammatic languages, abstract (formal) specifications, and source code-are highly interrelated where changes in some of them affect others. Trace dependencies characterize such relationships abstractly. This paper presents an automated approach to generating and validating trace dependencies. It addresses the severe problem that the absence of trace information or the uncertainty of its correctness limits the usefulness of software models during software development. It also automates what is normally a time consuming and costly activity due to the quadratic explosion of potential trace dependencies between development artifacts.

[1]  J. Jackson.  A keyphrase based traceability scheme , 1991 .

[2]  Siobhán Clarke,et al.  Subject-oriented design: towards improved alignment of requirements, design, and code , 1999, OOPSLA '99.

[3]  Barry Boehm,et al.  Heterogeneous view integration and its automation , 2000 .

[4]  Joseph A. Goguen,et al.  An Object-Oriented Tool for Tracing Requirements , 1996, IEEE Softw..

[5]  NotkinDavid,et al.  Software reflexion models , 1995 .

[6]  Sean McDonald,et al.  Software Test Automation , 1999 .

[7]  Frank Tip,et al.  Reengineering class hierarchies using concept analysis , 1998, SIGSOFT '98/FSE-6.

[8]  Barry W. Boehm,et al.  Using the WinWin Spiral Model: A Case Study , 1998, Computer.

[9]  Kai Koskimies,et al.  Automated Support for Modeling OO Software , 1998, IEEE Softw..

[10]  Matthias Jarke,et al.  Improving reviews by extended traceability , 1999, Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Full Papers.

[11]  Stanley M. Sutton,et al.  N degrees of separation: multi-dimensional separation of concerns , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[12]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[13]  Ivar Jacobson,et al.  The unified modeling language reference manual , 2010 .

[14]  강문설.  [서평]「The Unified Modeling Language User Guide」 , 1999 .

[15]  C. Martin,et al.  Design traceability of complex systems , 1998, Proceedings Fourth Annual Symposium on Human Interaction with Complex Systems.

[16]  David Notkin,et al.  Software reflexion models: bridging the gap between source and high-level models , 1995, SIGSOFT FSE.

[17]  Alexander Egyed,et al.  Automating requirements traceability: Beyond the record & replay paradigm , 2002, Proceedings 17th IEEE International Conference on Automated Software Engineering,.

[18]  Danny B. Lange,et al.  Object-Oriented Program Tracing and Visualization , 1997, Computer.

[19]  Ismaïl Khriss,et al.  Automating the Synthesis of UML StateChart Diagrams from Multiple Collaboration Diagrams , 1998, UML.

[20]  Ellis Horowitz,et al.  Software Cost Estimation with COCOMO II , 2000 .

[21]  Giuliano Antoniol,et al.  Maintaining traceability during object-oriented software evolution: a case study , 1999, Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360).

[22]  Mark Neal,et al.  Why and how of requirements tracing , 1994, IEEE Software.