Exploring Views for Goal-Oriented Requirements Comprehension

Lyrene Silva, Ana Moreira, João Araújo, Catarina Gralha, Miguel Goulão, Vasco Amaral

Research output: Chapter in Book/Report/Conference proceedingOther chapter contributionpeer-review

6 Citations (Scopus)
17 Downloads (Pure)


Requirements documents and models need to be used by many stakeholders with different technological proficiency during software development. Each stakeholder may need to understand the entire (or simply part of the) requirements artifacts. To empower these stakeholders, views of the requirements should be configurable to their particular needs. This paper uses information visualization techniques to help in this process. It proposes different views aiming at highlighting information that is relevant for a particular stakeholder, helping him to query requirements artifacts. We offer three kinds of visualizations capturing language and domain elements, while providing a gradual model overview: the big picture view, the syntax-based view, and the concern-based view. We instantiate these views with i* models and introduce an implementation prototype in the iStarLab tool.
Original languageEnglish
Title of host publicationCONCEPTUAL MODELING, ER 2016
EditorsI. ComynWattiau, K. Tanaka, I. Y. Song, S. Yamamoto, M. Saeki
Place of PublicationCham
PublisherSpringer International Publishing AG
ISBN (Print)978-331946396-4
Publication statusPublished - 2016
Event35th International Conference on Conceptual Modeling - Gifu, Japan
Duration: 14 Nov 201617 Nov 2016
Conference number: 35

Publication series

NameConceptual Modeling
PublisherSpringer International Publishing A. G.
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349


Conference35th International Conference on Conceptual Modeling
Abbreviated titleER 2016
Internet address


  • Comprehension
  • Requirements exploration
  • Views
  • Visualization


Dive into the research topics of 'Exploring Views for Goal-Oriented Requirements Comprehension'. Together they form a unique fingerprint.

Cite this