Supporting use case based requirements engineering

Abstract

Use cases that describe possible interactions involving a system and its environment are increasingly being accepted as effective means for functional requirements elicitation and analysis. In the current practice, informal definitions of use cases are used and the analysis process is manual. In this paper, we present an approach supported by a tool for use cases based requirements engineering. Our approach includes use cases formalization, a restricted form of natural language for use cases description, and the derivation of an executable specification as well as a simulation environment from use cases. q

Enhancement of a use cases based requirements engineering approach with scenarios

“…It is an enhancement of an approach presented in [11]. The process is supported by a tool called Use Case Editor (UCEd) [13].…”

“…The process is supported by a tool called Use Case Editor (UCEd) [13]. The following activities are included in the approach reported in [11]: domain model capture, use cases capture, use cases composition and use cases simulation. These activities are reviewed and illustrated with a case study in the remainder of this section.…”

“…The The previous example is a snapshot of our approach for use cases elaboration in conjunction with the domain model. A detailed presentation can be found in [11]. The approach involves several iterations of use cases and domain specification followed by simulation.…”

“…We are developing an approach where use cases are used to capture requirements [11]. A use case is the specification of a sequence of actions, including variants, that a system can perform, interacting with actors of the system [10].…”

An Aspect-Oriented Approach for Use Case Based Modeling of Software Product Lines

“…In our previous work [6], we proposed an approach to support use cased based requirements engineering. This approach is supported by a tool called Use Case Editor, (UCEd) [7].…”