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
Dissertation
Architectural Knowledge Management: Supporting Architects and Auditors
Rik Farenhorst,R.C. de Boer +1 more
TL;DR: To illustrate the effect of LSA on the document vector-space model, LSA was applied to the 8 documents from the audit that were still available, and both auditors seem to agree that there are two large document clusters.
Business and IT Alignment with SEAM
TL;DR: This work presents some of the traditional techniques used for the development of an enterprise model (value system, BPMN, UML) and compares them with a systemic method (SEAM), showing that the concepts of goals, strategies and needs correspond to interpretations of the stakeholders of the enterprise model.
Journal ArticleDOI
A DSS Design Model for complex problems: Lessons from mission critical infrastructure
Robb Klashner,Sameh A. Sabet +1 more
TL;DR: The new DSS Design Model was derived from conceptual design research and through a deep qualitative field research study at an electric power utility control center-a typical arena for ''wicked'' problems.
Journal ArticleDOI
Requirement progression in problem frames: deriving specifications from requirements
TL;DR: A technique is presented for obtaining a specification from a requirement through a series of incremental steps, involving a decomposition of the environment into interconnected domains and a formal requirement on phenomena of those domains.
Book ChapterDOI
Rescue an integrated method for specifying requirements for complex sociotechnical systems
Sara Jones,Neil Maiden Maiden +1 more
TL;DR: Examples are presented showing how the RESCUE method can be applied in the context of a case study involving the specification of requirements for Countdown, a system to provide bus passengers with information about expected bus arrival times.
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.