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
A Lightweight GRL Profile for i* Modeling
TL;DR: This paper presents a lightweight GRL profile for i* that takes advantage of GRL's extensibility features to capture missing i* concepts and presents formal constraints on the use of the GRL and its extensions to restrict it to an i* style.
Survey of Aspect-Oriented Analysis and Design Approaches
Ruzanna Chitchyan,Awais Rashid,Pete Sawyer,Alessandro Garcia,M. P. Alarcon,J. Bakker,Bedir Tekinerdogan,Siobhán Clarke,A Jackson +8 more
TL;DR: This report provides some initial insights into processes for AO requirements engineering, analysis and design which may serve as basis for integration of the work of the AOSDEUROPE project partners and outlines some issues relevant to such integration.
Proceedings ArticleDOI
Alignment of Misuse Cases with Security Risk Management
TL;DR: This paper examines misuse cases in the light of a reference model for information system security risk management (ISSRM) using the well-known meeting scheduler example and suggests improvements for the conceptual appropriateness of misuse cases for the security risk domain.
Proceedings ArticleDOI
Visual notation design 2.0: Towards user comprehensible requirements engineering notations
TL;DR: A novel approach to designing RE visual notations that actively involves naïve users in the process and harnesses the collective intelligence of end users and actively involves them in the notation design process as “prosumers” rather than passive consumers is proposed.
Journal ArticleDOI
Emotion-led modelling for people-oriented requirements engineering
TL;DR: It is argued that emotional desires of people should be treated as first-class citizens in software engineering methodology, and preliminary work on including emotions in requirements models using emotional goals is presented.
References
More filters
Book
The Sciences of the Artificial
TL;DR: A new edition of Simon's classic work on artificial intelligence as mentioned in this paper adds a chapter that sorts out the current themes and tools for analyzing complexity and complex systems, taking into account important advances in cognitive psychology and the science of design while confirming and extending Simon's basic thesis that a physical symbol system has the necessary and sufficient means for intelligent action.
Book
Reengineering the corporation: a manifesto for business revolution
Michael Hammer,James Champy +1 more
TL;DR: In this paper, the authors set aside much of the received wisdom of the last 200 years of industrial management and in its place presented a new set of organizing principles by which managers can rebuild their businesses.
Journal ArticleDOI
A field study of the software design process for large systems
TL;DR: A layered behavioral model is used to analyze how three of these problems—the thin spread of application domain knowledge, fluctuating and conflicting requirements, and communication bottlenecks and breakdowns—affected software productivity and quality through their impact on cognitive, social, and organizational processes.
Journal ArticleDOI
Goal-directed requirements acquisition
TL;DR: An approach to requirements acquisition is presented which is driven by higher-level concepts that are currently not supported by existing formal specification languages, such as goals to be achieved, agents to be assigned, alternatives to be negotiated, etc.