See this document in CiteSeerX!

A Scenario-Driven Approach to Traceability (2001)  (Make Corrections)  (6 citations)
Alexander Egyed
International Conference on Software Engineering



  Home/Search   Context   Related

 
View or download:
usc.edu/~aegyed/pu...o_Traceability.pdf
alexanderegyed.co...o_Traceability.pdf
Cached:  PS.gz  PS  PDF   Image  Update  Help

From:  usc.edu/~aegyed/publications/ (more)
(Enter author homepages)

Rate this article: (best)
  Comment on this article  
(Enter summary)

Abstract: Design traceability has been widely recognized as being an integral aspect of software development. In the past years this fact has been amplified due to the increased use of legacy systems and COTS (commercial-off-the-shelf) components mixed with the growing use of elaborate "upstream" software modeling techniques such as the Unified Modeling Language (UML). The more intensive emphasis on upstream (non-programming) software development issues has, however, widened the gap between software... (Update)

Similar documents based on text:   More   All
0.4:   An Externalized Infrastructure for Self-Healing Systems - Wile, Egyed   (Correct)
0.4:   Reasoning about Trace Dependencies in a Multi-Dimensional Space - Egyed (2002)   (Correct)
0.3:   Dynamic Deployment of Executing and Simulating Software Components - Egyed (2004)   (Correct)

BibTeX entry:   (Update)

Egyed, A., A Scenario-Driven Approach to Traceability, Proceedings of the 23rd International Conference on Software Engineering (ICSE), Toronto, Canada, May 2001, pp. 123-132. http://citeseer.ist.psu.edu/egyed01scenariodriven.html   More

@inproceedings{ egyed01scenariodriven,
    author = "Alexander Egyed",
    title = "A Scenario-Driven Approach to Traceability",
    booktitle = "International Conference on Software Engineering",
    pages = "123-132",
    year = "2001",
    url = "citeseer.ist.psu.edu/egyed01scenariodriven.html" }
Citations (may not include all citations):
372   The Unified Modeling Language Reference Manual (context) - Rumbaugh, Jacobson et al. - 1999
117   Software Reflexion Models: Bridging the Gap Between Source a.. - Murphy, Notkin et al. - 1995
73   An Analysis of the Requirements Traceability Problem - Gotel, Finkelstein - 1994
51   and Sutton, S. M. Jr.: "N Degrees of Separation: Multi-Dimen.. - Tarr, Osher et al. - 1999
40   the Inevitable Intertwining of Specification and Implementat.. (context) - Swartout, Balzer - 1982
25   An ObjectOriented Tool for Tracing Requirements (context) - Goguen - 1996
22   Subject -Oriented Design: Towards Improved Alignment of Requ.. - Clarke, Harrison et al. - 1998
11   Object-Oriented Program Tracing and Visualization (context) - Lange, Nakamura - 1997
9   Heterogeneous View Integration and its Automation - Egyed - 2000
9   Why and How of Requirements Tracing (context) - Watkins, Neal - 1994
6   Inter-Library Loan Management System: Revised Life-Cycle Arc.. (context) - Abi-Antoun, Ho et al.
4   A Keyphrase Based Traceability Scheme (context) - Jackson - 1991
3   Traceability for Integration (context) - Gieszl - 1992
3   Maintaining Traceability During Object-Oriented Software Evo.. - Antoniol, Canfora et al. - 1998
2   Reengineering Class Hierachies Using Concept Analysis (context) - Snelting, Tip - 1998

[Article contains additional citations not shown here]

Documents on the same site (http://sunset.usc.edu/~aegyed/publications/):   More
Refinement and Evolution Issues in Bridging.. - Egyed, Grünbacher.. (2001)   (Correct)
Consistent Architectural Refinement and Evolution using the.. - Egyed, Medvidovic (2001)   (Correct)
Validating Consistency between Architecture and Design Descriptions - Egyed   (Correct)

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC