Proceedings ArticleDOI
Towards modelling and reasoning support for early-phase requirements engineering
Reads0
Chats0
TLDR
This paper argues that a different kind of modelling and reasoning support is needed for the early phase of requirements engineering, which aims to model and analyze stakeholder interests and how they might be addressed, or compromised, by various system-and-environment alternatives.Abstract:
Requirements are usually understood as stating what a system is supposed to do, as apposed to how it should do it. However, understanding the organizational context and rationales (the "Whys") that lead up to systems requirements can be just as important for the ongoing success of the system. Requirements modelling techniques can be used to help deal with the knowledge and reasoning needed in this earlier phase of requirements engineering. However most existing requirements techniques are intended more for the later phase of requirements engineering, which focuses on completeness, consistency, and automated verification of requirements. In contrast, the early phase aims to model and analyze stakeholder interests and how they might be addressed, or compromised, by various system-and-environment alternatives. This paper argues, therefore, that a different kind of modelling and reasoning support is needed for the early phase. An outline of the i* framework is given as an example of a step in this direction. Meeting scheduling is used as a domain example.read more
Citations
More filters
Book ChapterDOI
On Non-Functional Requirements in Software Engineering
TL;DR: This chapter reviews the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.
Proceedings ArticleDOI
Requirements engineering: a roadmap
TL;DR: An overview of the field of software systems requirements engineering (RE) is presented, describing the main areas of RE practice, and highlights some key open research issues for the future.
Proceedings ArticleDOI
Goal-oriented requirements engineering: a guided tour
TL;DR: The paper compares the main approaches to goal modeling, goal specification and goal-based reasoning in the many activities of the requirements engineering process and suggests what a goal-oriented requirements engineering method may look like.
Journal ArticleDOI
The “Physics” of Notations: Toward a Scientific Basis for Constructing Visual Notations in Software Engineering
TL;DR: A set of principles for designing cognitively effective visual notations: ones that are optimized for human communication and problem solving are defined, which form a design theory, called the Physics of Notations, which focuses on the physical properties of notations rather than their logical properties.
Book ChapterDOI
Software Engineering for Self-Adaptive Systems: A Research Roadmap
Betty H. C. Cheng,Rogério de Lemos,Holger Giese,Paola Inverardi,Jeff Magee,Jesper Andersson,Basil Becker,Nelly Bencomo,Yuriy Brun,Bojan Cukic,Giovanna Di Marzo Serugendo,Schahram Dustdar,Anthony Finkelstein,Cristina Gacek,Kurt Geihs,Vincenzo Grassi,Gabor Karsai,Holger M. Kienle,Jeff Kramer,Marin Litoiu,Sam Malek,Raffaela Mirandola,Hausi A. Müller,Sooyong Park,Mary Shaw,Matthias Tichy,Massimo Tivoli,Danny Weyns,Jon Whittle +28 more
TL;DR: The goal of this roadmap paper is to summarize the state-of-the-art and to identify critical challenges for the systematic software engineering of self-adaptive systems.
References
More filters
Journal ArticleDOI
Al models for business process reengineering
TL;DR: The authors describe their I* framework, which views organizations as collections of actors with strategic interests, and interdependencies involving goals, tasks, and resources, which supports reasoning about the dynamics of processes under incomplete knowledge.
Journal ArticleDOI
Knowledge representation and reasoning in the design of composite systems
Stephen Fickas,B.R. Helm +1 more
TL;DR: The goal is an interactive model of composite system design incorporating deficiency-driven design, formal analysis, incremental design and rationalization, and design reuse that is used to reconstruct the design of two existing composite systems rationally.
Proceedings ArticleDOI
Using non-functional requirements to systematically support change
TL;DR: It is shown how a historical record of the treatment of NFRs during the development process can also serve to systematically support evolution of the software system.
Proceedings ArticleDOI
Challenges in requirements engineering
TL;DR: A number of essential problems of software requirements engineering, related to management, organisations, users, stakeholders, methodology, tools, and education are discussed.