Enhanced Use Case Map Traversal Semantics

Kealey, Jason; Amyot, Daniel

doi:10.1007/978-3-540-74984-4_9

Cited by 14 publications

(6 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We assume in this process the use of one of the existing UCM traversal techniques [6] to scan a UCM as input to identify individual map elements. For reasons of space we consider only some UCM elements (see Sec.…”

Section: Ucm Traversal Techniquementioning

confidence: 99%

“…They combine in a single view the behavioral and architectural structure of a system. UCMs also have the potential to serve as input to other speci¯cation and design languages, given a suitable transformation or adaptation process [5,6]. Although formal methods may be used during most stages of the software development process [7], the lack of a precise technique in Z to set up the boundaries of a system during the early stages of development makes it hard to grasp a system from scratch.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Addressing the Construction of Z and Object-Z with Use Case Maps (UCMs)

Dongmo

Poll

2014

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

A Use Case Map (UCM) is a scenario-based visual notation facilitating the requirements definition of complex systems. A UCM may be generated either from a set of informal requirements, or from a set of use cases normally expressed in natural language. Natural languages are, however, inherently ambiguous and as a semi-formal notation, UCMs have the potential to bring more clarity into the functional description of a system. It may furthermore eliminate possible errors in the user requirements. The semi-formal notation of UCMs aims to show how things work generally, but is not suitable to reason formally about system behavior. It is plausible, therefore, that the use of a UCM as an intermediate step may facilitate the construction of a formal speci¯cation. To this end this paper proposes a mechanism whereby a UCM may be translated into Object-Z. Int. J. Soft. Eng. Knowl. Eng. 2014.24:285-327. Downloaded from www.worldscientific.com by MONASH UNIVERSITY on 02/03/15. For personal use only. UCM Model of the Case StudyThis section presents an overview of Use Case Maps followed by the UCM model of the case study where UCM elements used are further explained. Brief overview of UCMsThe UCM notation, originally developed by Buhr and Casselman [11, 12] embodies a semi-formal notation showing related and interacting use cases in a map-like diagram. The progression of scenarios along use cases is captured by paths shown as wiggle lines. UCM models describe service functionalities with causal relationships between responsibilities, superimposed on organisational structures of abstract components. The strength of a UCM is in utilising a simple graphical notation to describe complex systems. A responsibility represents generic processing, e.g. an operation, a task, an action, a function and so forth. The case study UCMSince the¯rst expectation of stakeholders is that the speci¯cation describes the functionalities of the envisioned system, we may consider a scenario composed of the following activities:(1) A company (say Helper) to whom a customer returns a purchased item receives the item and temporarily keeps it, waiting to forward it to the provider. (2) The Helper forwards the returned item to the provider.(3) The provider collects the returned item. Figure 1 represents a UCM model of our case study in Sec. 2. The diagram is constructed with UCMs elements that may be grouped into the categories Paths, Path elements, Path connectors, and abstract components.A UCM path indicates the progression route of one or more scenarios in execution. It is a wiggly line that begins with a Start point and ends at an End point (see Fig. 1). The start point is a place where an event occurs to trigger (precondition) the execution of the scenario and the end point is where the resulting events are accumulated (postcondition). Elements encountered along a path segment are: Responsibility points, Path connectors, Timers, etc.A Responsibility point is graphically represented by a cross with a label (e.g. returnItem). It indicates a point along the...

show abstract

Section: Ucm Traversal Techniquementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Addressing the Construction of Z and Object-Z with Use Case Maps (UCMs)

Dongmo

Poll

2014

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

show abstract

“…He also provided goal-scenario traceability management (via URN links) and support for GRL catalogues. Kealey, in his thesis [114], implemented a flexible UCM traversal mechanism with color highlight (see Figure 2), together with an MSC export feature [115]. Kealey developed a mechanism where GRL evaluation results can influence the traversal of UCM paths, and vice-versa.…”

Section: N Urn Toolsmentioning

confidence: 99%

User Requirements Notation: The First Ten Years, The Next Ten Years (Invited Paper)

Amyot¹,

Mussbacher²

2011

JSW

Self Cite

115

View full text Add to dashboard Cite

The User Requirements Notation (URN), standardized by the International Telecommunication Union in 2008, is used to model and analyze requirements with goals and scenarios. This paper describes the first ten years of development of URN, and discusses ongoing efforts targeting the next ten years. We did a study inspired by the systematic literature review approach, querying five major search engines and using the existing URN Virtual Library. Based on the 281 scientific publications related to URN we collected and analyzed, we observe a shift from a more conventional use of URN for telecommunications and reactive systems to business process management and aspect-oriented modeling, with relevant extensions to the language being proposed. URN also benefits from a global and active research community, although industrial contributions are still sparse. URN is now a leading language for goal-driven and scenario-oriented modeling with a promising future for many application domains.

show abstract

“…One of the jUCMNav tool's features is a traversal mechanism which, besides improving the usability of the tool and allowing for a smoother transition to downstream modeling activities, defines more precisely the semantics of UCM. As no standard traversal mechanism existed for UCM before November 2008, the jUCMNav tool's traversal mechanism [62] [64] [66] was based on a simple but intuitive interpretation of the notational elements for sequences, alternatives, and concurrency in UCM. An OR-fork is an exclusive or, there is no synchronization on an OR-join, an AND-fork denotes strict concurrency, an AND-join requires all incoming branches to arrive before continuation, and the selection policy of a dynamic stub is also an exclusive or.…”

Section: Use Case Mapsmentioning

confidence: 99%

“…The UCM notation has also changed very little since its beginnings in the early 1990s, but some UCM modeling elements such as constructs for alternatives, concurrency, and hierarchical structuring are interpreted in different ways. The introduction of a UCM traversal mechanism [64] [66] capable of highlighting a particular scenario in the UCM model and transforming the scenario into a message sequence chart (MSC) [58] represented the first step toward a standardized semantic interpretation of UCM models. The semantics of UCM has also been defined based on LOTOS [52], abstract state machines (ASM) [54][56], as well as Clocked Transition Systems (CTS) and Timed Automata (TA) [56].…”

Section: Motivating the Need For Use Case Maps 20mentioning

confidence: 99%

The aspect-oriented user requirements notation

Mussbacher

2011

Proceedings of the Tenth International Conference on Aspect-Oriented Software Development Companion

View full text Add to dashboard Cite

Enhanced Use Case Map Traversal Semantics

Cited by 14 publications

References 8 publications

Addressing the Construction of Z and Object-Z with Use Case Maps (UCMs)

Addressing the Construction of Z and Object-Z with Use Case Maps (UCMs)

User Requirements Notation: The First Ten Years, The Next Ten Years (Invited Paper)

The aspect-oriented user requirements notation

Contact Info

Product

Resources

About