Goal Modeling in Requirements Engineering

Kavakli, Evangelia; Loucopoulos, Pericles

doi:10.4018/978-1-59140-375-3.ch006

Cited by 62 publications

(14 citation statements)

References 46 publications

(51 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Kavakli has provided an overview of existing goal-oriented frameworks as per 2002, classifying approaches in terms of RE Activities: elicitation, specification, and validation. She proposes a meta-model based framework for unifying goal-oriented approaches, bearing similarities with method engineering approaches (Brinkkemper, 1996), Kavakli & Loucopoulos (2004) further extend their review of existing goal-oriented techniques, arguing, as we do, that research in the area is fragmented. Specifically, they argue that each goal-oriented approach focuses on only a subset of RE issues, without looking at the entire RE process, from elicitation to validation.…”

Section: Related Workmentioning

confidence: 90%

Using Goal Models Downstream

Horkoff

et al. 2015

International Journal of Information System Modeling and Design

View full text Add to dashboard Cite

Goal models have proven useful for capturing, understanding, and communicating requirements during early stages of software development. However, the utility of goal models is greatly enhanced when they can be exploited during downstream stages of the requirements analysis process (e.g. requirements elaboration, validation, planning), and can be used as part of the entire system life cycle (e.g., architectural and behavioral process design, coding, testing, monitoring, adaptation, and evolution). In order to better understand the progress that has been made in integrating goal models with downstream system development, the authors ask: what approaches exist that map/integrate/transform goal models to later stage software artifacts? To answer this question, they conduct a systematic survey, producing a roadmap of work summarizing 243 publications. Results include a categorization of the “why?” and “how?” for each approach. Furthermore, they select the 50 most prominent publications, based on citation numbers, in order to perform an in-depth literature review. Findings show that there is a wide variety of proposals with a variety of proposed goal models and targets, covering multiple paradigms, motivated by a variety of purposes. The authors conclude that although much work has been done in this area, the work is fragmented, following multiple separate strands of goal-orientation, and is often still in early stages of maturity.

show abstract

Section: Related Workmentioning

confidence: 90%

Using Goal Models Downstream

Horkoff

et al. 2015

International Journal of Information System Modeling and Design

View full text Add to dashboard Cite

show abstract

“…i* (Yu 1997), KAOS (Dardenne, Lamsweerde, and Fickas 1993), or the textual notation GBRAM (Goal-Based Requirement Analysis Method) (Subhani and Ravikumar 2019). According to Kavakli and Loucopoulos (2005), i* language encourages focusing on understanding the current business organization situations, while KAOS allows for concentrating on relating business goals to system components.…”

Section: Continued On the Next Pagementioning

confidence: 99%

Goal-Oriented Metropolis Ecosystem Development

Pańkowska

2024

MGT

View full text Add to dashboard Cite

Enterprise architecture (EA) modelling is understood as a system of architecture defined in ISO42010 and EA is intended to ensure a holistic view of business organization. This study analyses the goal-oriented approach to EA development. Justification of selection of this topic results from studies on EA modelling methods. Enterprise architects mainly focus on process modelling as well as on the application of UML language. There is still an open question of what the goals of EA modelling are. This paper presents an application of ArchiMate language and i* notation for goal-oriented EA modelling. The paper methodology covers a literature survey as well as a case study presenting ArchiMate and i* models for goal-oriented EA development by example of metropolis system architecture modelling. In this paper, a metropolis is defined as a consortium of cooperative communities and it is considered as a business organization for which the system architecture is modelled. The paper aims to develop the metropolis architecture model consisting of system components, i.e. business issues, data, software and hardware. The metropolis architecture models are provided to support development of a metropolis strategy. The main findings include the identification of business goals and EA goals, goal mapping, and specification of the key performance indicators (KPIs) to control the achievement of the goals.

show abstract

“…i*, KAOS, AOURN, AOGRL. RML, GCT [1][2][3][4][5][6]11,14,[33][34][35] are similar attempts of NFR refinement with vertical and horizontal extension of NFR framework as compared and contrasted in [14] Figure 1 below shows the example of Goal based refinement of "SIG" ("Soft goal Interdependence Graph") for problem refinement and its related "NFR Framework" has its own share of limitations [2,3,7]. As the no.…”

Section: Exploration and Evaluation Of Goal Oriented Requirement Engimentioning

confidence: 99%

Treating NFR as First Grade for Its Testability

Singh¹,

Tripathi²

2012

JSEA

View full text Add to dashboard Cite

Practitioners and researchers in the field of software engineering have realized that Non Functional requirement have not received due attention and second grade (or no) treatment has been meted out to Non Functional Requirements. Many software products/systems are finally not acceptable because of such an approach. This casual approach of treating NFR has moved on to Testing also. Testing of NFR has never been taken seriously. Here in this work, we attempt to under- stand what needs to be done for proper consideration of NFR, so that they are treated as seriously as the Functional Requirements. In an attempt to treat NFR as seriously as FR we work on the testability of NFR by refining an abstract quality concern into concrete NFR statements. We show that quality concerns needs to be analyzed, for identifying and finally converting them into appropriate and unambiguous NFR. Once a high quality of NFR is ensured then the consequent testing of these NFRs will become as effective as that of Functional Requirement. We finally propose a revised model of Problem Analysis and Requirement Specification. A step wise refinement model for quality concern into test- able Non Functional Requirement is also proposed.

show abstract

Goal Modeling in Requirements Engineering

Cited by 62 publications

References 46 publications

Using Goal Models Downstream

Using Goal Models Downstream

Goal-Oriented Metropolis Ecosystem Development

Treating NFR as First Grade for Its Testability

Contact Info

Product

Resources

About