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
The Formal Semantics of the Domain Specific Modeling Language for Multiagent Systems
Christian Hahn,Klaus Fischer +1 more
TL;DR: This paper discusses an approach to formalize the semantics of Dsml4mas --a modeling language for multiagent systems--to support the system designer in validating and verifying the generated design.
Proceedings ArticleDOI
Problem frame transformations: deriving specifications from requirements
Robert Seater,Daniel Jackson +1 more
TL;DR: This work suggests a more systematic method for transforming an end-to-end system requirement into a machine specification plus a set of domain properties.
Journal ArticleDOI
Modeling Trust Relationships for Developing Trustworthy Information Systems
TL;DR: This paper introduces a process that allows developers to capture possible trust relationships and to reason about them and is supported by a modeling language based on a set of concepts relating to trust and control and a CASE tool.
Proceedings ArticleDOI
The thing itself speaks: Accountability as a foundation for requirements in sociotechnical systems
Amit K. Chopra,Munindar P. Singh +1 more
TL;DR: It is claimed that to model an STS means to precisely capture the accountability requirements between its principals to address the shortcoming in established requirements engineering methods.
Proceedings ArticleDOI
Visualizations to support interactive goal model analysis
Jennifer Horkoff,Eric Yu +1 more
TL;DR: In this paper, roots and leaves in the model are automatically detected and highlighted as suggested starting points for analysis, and goals within a conflicting path are highlighted during analysis, while the results suggest several further visualization mechanisms which could support analysis.
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.