Analyzing user requirements by use cases: a goal-driven approach

Abstract

B ecause there is no systematic way in existing use-case approaches to handle nonfunctional requirements, the authors propose an approach to analyze and evaluate use cases with goals and to structure use-case models. se-case approaches are increasingly attracting attention in requirements engineering because the user-centered concept is valuable in eliciting, analyzing, and documenting requirements. 1-5 One of the main goals of the requirements engineering process is to get agreement on the views of the involved users, 6 and use cases are a good way to elicit requirements from a user's point of view. An important advantage of use-case-driven analysis is that it helps manage complexity, since it focuses on one specific usage aspect at a time. Use cases start from the very simple viewpoint that a system is built first and foremost for its users. The approach looks at the interactions of a single category of users at a time, considerably reducing the complexity of requirements determination. 7 However, current use-case approaches are somewhat limited in supporting use-case formalization, 4 and in structuring and managing large use-case models. 8

Aspect-enhanced goal-driven sequence diagram

“…Consequently, it is important to specify not only how system objects interact to achieve the goal of each base use case, but also how these objects interact to implement the crosscutting concerns of each aspectual use case as well as where the effects take places with respect to the aspectual use case's corresponding base use cases. As a continuation of our previous research, [8][9][10]24 we augment the use case speciÞcation with aspectual property to document the responsibility of an aspectual use case. Through the speciÞcation of aspectual property, aspectual behavior can be modeled within the proposed aspectual sequence diagrams together with three types of aspectual interaction operators to perform on the base use cases.…”

Issues in Testing of Software with Nfr

“…At requirement Engineering phase several Goal Oriented Approaches to handle NFR have been suggested such as i*, framework and GRL (Goal -Oriented Requirement Language), SIG (Soft goal interdependence graph) [21,25,35,34]. All these goal oriented approaches are based on identifying NFR as soft goal which needs to be satisfied (within an acceptable limit, or goals merely met) or "not satisfied" at all.…”

A Domain Ontology Based Approach to Identify Effect Types of Security Requirements upon Functional Requirements

“…Reviewing the literature, we found that several studies [6]- [9] applied different approaches to identify cooperative, conflicting, and irrelevant relationships among software requirements.…”

“…Lee and Xue [9] used a goal based approach to explore cooperative, conflicting, and irrelevant relationships between user requirements. They represented the user requirements by building the use case models with the associated goals.…”