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
Picking battles: The impact of trust assumptions on the elaboration of security requirements
TL;DR: It is shown how trust assumptions can affect the scope of the analysis, derivation of security requirements, and in some cases how functionality is realized.
Journal ArticleDOI
Specifying the requirements for requirements specification: the case for Work Domain and Worker Competencies Analyses
TL;DR: An argument for the applicability of Cognitive Work Analysis (CWA), particularly Work Domain and Worker Competencies Analyses, in supporting the requirements specification process for the acquisition of bespoke, socio-technical systems is presented.
Dissertation
Exploiting requirements variability for software customization and adaptation
TL;DR: The thesis presents an approach for systematically designing monitoring, analysis/diagnosis, and compensation components of a feedback controller, given a set of awareness requirements, in a requirements-driven approach for developing adaptive and customizable systems.
Book ChapterDOI
A comparative study of proposals for establishing security requirements for the development of secure information systems
TL;DR: In this paper, a comparative analysis of eight relevant technical proposals, which place great importance on the establishing of security requirements in the development of IS, is carried out, and they provide some significant contributions in aspects related to security.
Book ChapterDOI
Negotiation Constellations --- Method Selection Framework for Requirements Negotiation
TL;DR: A framework for selecting tactics and methods for various negotiation constellations that can be encountered in a software organization is described, opening perspectives that are essential for understanding the behavior of people involved in development projects.
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.