Use Case Maps as a Feature Description Notation

Abstract

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.

Feature-Guided Architecture Development for Embedded System Families

“…To capture this information in a completely architecture independent way, we employ the Use Case Maps (UCM) path notation [7][8]. Our feature modeling tool allows UCM paths to be attached to features where this is appropriate.…”

“…The understanding gained is captured using UCM path representations linked to features. We exploit the UCM concepts of stubs and plug-ins [7][8] to capture behavioral variability. Thus a feature at one level with alternative child features can have a dynamic stub within its path.…”

“…Our scheme of feature modeling does this. It is inspired by earlier approaches to feature modeling, including FODA [2] and FORM [3] [4], and incorporates concepts from other work [5] [7]. Construction of such models is only justified if they can be used as a significant aid to the architecture development stage.…”

Weaving Behavior into Feature Models for Embedded System Families

“…Its focus is on the capture of behavior at a reasonable level of detail. The founding concepts of the notation were introduced by Buhr [10] and have subsequently been extensively developed by Amyot and others [12]. Whereas feature modeling is inherently a notation targeted at product-line requirements, UCM was developed as a general purpose requirements modeling notation, aimed at providing an abstract, path-centric view of system functionality.…”

“…Section 3 discusses the selection of a suitable notation for capturing feature behavior and explains the choice of the UCM path notation. The basic features of this notation are briefly described, although fuller details are available in other publications [10,11,12,13], and online via [14]. In section 4 we then describe how we compose these notations.…”