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
Analysis of techniques for documenting user requirements
TL;DR: The purpose of this paper is to propose a critical view on a number of chosen techniques that might be useful for practitioners when choosing which technique to use on a specific project.
Book ChapterDOI
Exploiting Tag Clouds for Database Browsing and Querying
TL;DR: This work shows how tag clouds can be used alongside more traditional query languages and data visualisation techniques as a means for browsing and querying databases by both experts and non-expert users.
Book
Engineering Self-Organizing Dynamics in Distributed Systems:: A Systemic Approach
TL;DR: Diese Dissertation beschaftigt sich mit der Nutzbarmachung von Prinzipien der Selbstorganisation fur die Entwicklung verteilter Softwaresysteme, wenn grose verteilte Systeme dezentral koordiniert werden sollen.
Requirements Reengineering from Legacy Information Systems Using Semiotic Techniques
TL;DR: AMBOLS as mentioned in this paper is a semiotic approach to requirements reengineering, which considers recovering the requirements of an existing (legacy) system under the restriction that only the operational system and its current stakeholders are accessible, while the original system documentation may be inaccurate or unavailable.
Journal ArticleDOI
Hazard Relation Diagrams: a diagrammatic representation to increase validation objectivity of requirements-based hazard mitigations
TL;DR: The ontology of Hazard Relation Diagrams is extended, its application to visualize complex relationships between hazards and mitigations is elaborate, and an automated approach is presented to generate Hazardrelation Di diagrams.
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.