Abstract

Understanding software-based systems is a task essential not only for engineering new applications but also for evolving existing ones. For complex systems, the graphical representation of various attributes and projections con- tributes to such understanding. Also, scenarios have proven to greatly accelerate software understanding by capturing abstract system behavior. For existing software, abstraction based on architectural concepts is required to address the overflow of information generated by static code and dynamic executions. This paper explores a tool-supported technique for the extraction of abstract Use Case Map (UCMs) scenarios from code, and reports on work in progress through an example. UCMs, as part of the upcoming User Requirements Nota- tion, help visualizing behavior combined with structure at the architecture level, above the level of message exchanges and component behavior. The unusual application of UCMs proposed here promises interesting visualization and ab- straction benefits over conventional approaches to the reverse engineering of scenarios while maintaining traceability to the code.

Discussion

  • Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.

FormForVirtualLibrary edit

Title Understanding Existing Software with Use Case Map Scenarios
Authors Daniel Amyot, Nikolai Mansurov, and Gunter Mussbacher
Type Conference
Conference/Journal Title 3rd SDL and MSC Workshop (SAM02)
Volume/Number LNCS 2599
Editors
Publisher Springer
Month June
Year 2002
Pages 124-140
DOI 10.1007/3-540-36573-7_9
Keywords
Topic attachments
I Attachment Action Size Date Who Comment
sam02-KLOCwork.pdfpdf sam02-KLOCwork.pdf manage 570 K 04 Nov 2005 - 18:10 JacquesSincennes  
sam02-KLOCwork.zipzip sam02-KLOCwork.zip manage 543 K 05 Aug 2006 - 15:56 DanielAmyot Presentation
Topic revision: r4 - 07 Nov 2009, HannaFarah
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback