Goal-Oriented Requirements Engineering and Enterprise Architecture: Two case studies and some lessons learned

W. Engelsman, Roelf J. Wieringa

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

31 Citations (Scopus)
106 Downloads (Pure)

Abstract

An enterprise-architecture (EA) is a high-level representation of the enterprise, used for managing the relation between business and IT. [Problem] Ideally, all elements of an enterprise architecture can be traced to business goals ad vice versa, but in practice, this is not the case. In this paper we explore the use of goal-oriented requirements engineering (GORE) techniques to improve this bidirectional traceability. [Principal ideas/results] We collected GORE techniques from KAOS, i*, Tropos, BMM and TOGAF and integrated them in a language called ARMOR. This was used by enterprise architects in case study. It turned out that the language was too complex for the architects to understand as intended. Based on this we redefined ARMOR to contain only a minimum number of goal-oriented concepts, and this was tested in a second case study. This second case study suggests that the minimal version is still useful for traceability management in practice. [Contribution] We have identified a core set of concepts of goal-oriented requirements engineering, that can be used in the practice of enterprise architecture. Our analysis provides generalizable insights into GORE that will be tested in future case studies.
Original languageUndefined
Title of host publicationRequirements Engineering: Foundation for Software Quality (REFSQ 2012)
EditorsBjörn Regnell, Daniela Damian
Place of PublicationLondon
PublisherSpringer
Pages306-320
Number of pages15
ISBN (Print)978-3-642-28713-8
DOIs
Publication statusPublished - Mar 2012
Event18th International Working Conference on Requirements Engineering: Foundation for Software Quality 2012 - ATLANTIC Congress Hotel, Essen, Germany
Duration: 19 Mar 201222 Mar 2012
Conference number: 18
https://refsq.org/2012/

Publication series

NameLecture notes in computer science
PublisherSpringer Verlag
Volume7195
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349

Conference

Conference18th International Working Conference on Requirements Engineering: Foundation for Software Quality 2012
Abbreviated titleREFSQ 2012
CountryGermany
CityEssen
Period19/03/1222/03/12
Internet address

Keywords

  • METIS-286330
  • SCS-Services
  • EWI-21773
  • IR-80258

Cite this

Engelsman, W., & Wieringa, R. J. (2012). Goal-Oriented Requirements Engineering and Enterprise Architecture: Two case studies and some lessons learned. In B. Regnell, & D. Damian (Eds.), Requirements Engineering: Foundation for Software Quality (REFSQ 2012) (pp. 306-320). (Lecture notes in computer science; Vol. 7195). London: Springer. https://doi.org/10.1007/978-3-642-28714-5_27
Engelsman, W. ; Wieringa, Roelf J. / Goal-Oriented Requirements Engineering and Enterprise Architecture: Two case studies and some lessons learned. Requirements Engineering: Foundation for Software Quality (REFSQ 2012). editor / Björn Regnell ; Daniela Damian. London : Springer, 2012. pp. 306-320 (Lecture notes in computer science).
@inproceedings{a3200cedc5ce401daddd5013c2374ed0,
title = "Goal-Oriented Requirements Engineering and Enterprise Architecture: Two case studies and some lessons learned",
abstract = "An enterprise-architecture (EA) is a high-level representation of the enterprise, used for managing the relation between business and IT. [Problem] Ideally, all elements of an enterprise architecture can be traced to business goals ad vice versa, but in practice, this is not the case. In this paper we explore the use of goal-oriented requirements engineering (GORE) techniques to improve this bidirectional traceability. [Principal ideas/results] We collected GORE techniques from KAOS, i*, Tropos, BMM and TOGAF and integrated them in a language called ARMOR. This was used by enterprise architects in case study. It turned out that the language was too complex for the architects to understand as intended. Based on this we redefined ARMOR to contain only a minimum number of goal-oriented concepts, and this was tested in a second case study. This second case study suggests that the minimal version is still useful for traceability management in practice. [Contribution] We have identified a core set of concepts of goal-oriented requirements engineering, that can be used in the practice of enterprise architecture. Our analysis provides generalizable insights into GORE that will be tested in future case studies.",
keywords = "METIS-286330, SCS-Services, EWI-21773, IR-80258",
author = "W. Engelsman and Wieringa, {Roelf J.}",
note = "10.1007/978-3-642-28714-5_27",
year = "2012",
month = "3",
doi = "10.1007/978-3-642-28714-5_27",
language = "Undefined",
isbn = "978-3-642-28713-8",
series = "Lecture notes in computer science",
publisher = "Springer",
pages = "306--320",
editor = "Bj{\"o}rn Regnell and Daniela Damian",
booktitle = "Requirements Engineering: Foundation for Software Quality (REFSQ 2012)",

}

Engelsman, W & Wieringa, RJ 2012, Goal-Oriented Requirements Engineering and Enterprise Architecture: Two case studies and some lessons learned. in B Regnell & D Damian (eds), Requirements Engineering: Foundation for Software Quality (REFSQ 2012). Lecture notes in computer science, vol. 7195, Springer, London, pp. 306-320, 18th International Working Conference on Requirements Engineering: Foundation for Software Quality 2012, Essen, Germany, 19/03/12. https://doi.org/10.1007/978-3-642-28714-5_27

Goal-Oriented Requirements Engineering and Enterprise Architecture: Two case studies and some lessons learned. / Engelsman, W.; Wieringa, Roelf J.

Requirements Engineering: Foundation for Software Quality (REFSQ 2012). ed. / Björn Regnell; Daniela Damian. London : Springer, 2012. p. 306-320 (Lecture notes in computer science; Vol. 7195).

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

TY - GEN

T1 - Goal-Oriented Requirements Engineering and Enterprise Architecture: Two case studies and some lessons learned

AU - Engelsman, W.

AU - Wieringa, Roelf J.

N1 - 10.1007/978-3-642-28714-5_27

PY - 2012/3

Y1 - 2012/3

N2 - An enterprise-architecture (EA) is a high-level representation of the enterprise, used for managing the relation between business and IT. [Problem] Ideally, all elements of an enterprise architecture can be traced to business goals ad vice versa, but in practice, this is not the case. In this paper we explore the use of goal-oriented requirements engineering (GORE) techniques to improve this bidirectional traceability. [Principal ideas/results] We collected GORE techniques from KAOS, i*, Tropos, BMM and TOGAF and integrated them in a language called ARMOR. This was used by enterprise architects in case study. It turned out that the language was too complex for the architects to understand as intended. Based on this we redefined ARMOR to contain only a minimum number of goal-oriented concepts, and this was tested in a second case study. This second case study suggests that the minimal version is still useful for traceability management in practice. [Contribution] We have identified a core set of concepts of goal-oriented requirements engineering, that can be used in the practice of enterprise architecture. Our analysis provides generalizable insights into GORE that will be tested in future case studies.

AB - An enterprise-architecture (EA) is a high-level representation of the enterprise, used for managing the relation between business and IT. [Problem] Ideally, all elements of an enterprise architecture can be traced to business goals ad vice versa, but in practice, this is not the case. In this paper we explore the use of goal-oriented requirements engineering (GORE) techniques to improve this bidirectional traceability. [Principal ideas/results] We collected GORE techniques from KAOS, i*, Tropos, BMM and TOGAF and integrated them in a language called ARMOR. This was used by enterprise architects in case study. It turned out that the language was too complex for the architects to understand as intended. Based on this we redefined ARMOR to contain only a minimum number of goal-oriented concepts, and this was tested in a second case study. This second case study suggests that the minimal version is still useful for traceability management in practice. [Contribution] We have identified a core set of concepts of goal-oriented requirements engineering, that can be used in the practice of enterprise architecture. Our analysis provides generalizable insights into GORE that will be tested in future case studies.

KW - METIS-286330

KW - SCS-Services

KW - EWI-21773

KW - IR-80258

U2 - 10.1007/978-3-642-28714-5_27

DO - 10.1007/978-3-642-28714-5_27

M3 - Conference contribution

SN - 978-3-642-28713-8

T3 - Lecture notes in computer science

SP - 306

EP - 320

BT - Requirements Engineering: Foundation for Software Quality (REFSQ 2012)

A2 - Regnell, Björn

A2 - Damian, Daniela

PB - Springer

CY - London

ER -

Engelsman W, Wieringa RJ. Goal-Oriented Requirements Engineering and Enterprise Architecture: Two case studies and some lessons learned. In Regnell B, Damian D, editors, Requirements Engineering: Foundation for Software Quality (REFSQ 2012). London: Springer. 2012. p. 306-320. (Lecture notes in computer science). https://doi.org/10.1007/978-3-642-28714-5_27