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
Journal ArticleDOI
Unified Process for Domain Analysis integrating Quality, Aspects and Goals
TL;DR: A Unified Process for Domain Analysis (UPDA) is proposed, based on Aspect and Goal orientations to deal with NFR, specified by quality standards to enhance communication.
Proceedings ArticleDOI
Mining Associations Between Quality Concerns and Functional Requirements
TL;DR: This paper proposes and evaluates a new technique for discovering and specifying quality concerns related to specific functional components, and shows that it significantly outperforms a basic information retrieval approach.
Proceedings ArticleDOI
Next generation enterprise modelling the role of Organizational Theory and multi-agent systems
TL;DR: This position paper proposes that the current enterprise modeling approaches are overly reliant on the know how or tacit knowledge of enterprise architects for addressing organizational challenges such as business-IT alignment and proposes implementation requirements for a next generation enterprise modeling language that supports agent based simulation.
Book
Arguing Security: A Framework for Analyzing Security Requirements
TL;DR: This book presents a framework for security requirements elicitation and analysis based on constructing a context for the system, representing security requirements as constraints, and developing satisfaction arguments for the security requirements.
Book ChapterDOI
Systemic Service Design: Aligning Value and Implementation
TL;DR: This work proposes to use a systemic method where whole and composite reasoning are interleaved on both the organizational and functional dimensions to describe how customer value is delivered by a set of actors and the responsibility of each actor.
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.