Abstract

We propose Use Case Maps (UCMs) as a notation for describing features. UCMs capture functional requirements in terms of causal scenarios bound to underlying abstract components. This particular view proved very useful in the description of a wide range of reactive and telecommunications systems. This paper presents some of the most interesting constructs and benefits of the notation in relation to a question on a User Requirements Notation recently approved by ITU-T Study Group 10, which will lead to a new Recommendation by 2003. Tool support, current research on UCMs, and related notations are also discussed.

Discussion

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

FormForVirtualLibrary edit

Title Use Case Maps as a Feature Description Notation
Authors D. Amyot
Type Conference
Conference/Journal Title FIREworks Feature Constructs Workshop
Volume/Number
Editors S. Gilmore and M. Ryan
Publisher Springer-Verlag
Month May
Year 2000
Pages 27-44
Keywords Features, Notation, Use Case Maps
Topic attachments
I Attachment Action Size Date Who Comment
fireworks2000.pdfpdf fireworks2000.pdf manage 275 K 21 Oct 2005 - 15:55 UnknownUser Paper
fireworks2000pres.pdfpdf fireworks2000pres.pdf manage 199 K 21 Oct 2005 - 16:23 UnknownUser Presentation
Topic revision: r2 - 09 Aug 2006, DanielAmyot
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