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
Proceedings ArticleDOI
Service Security Analysis Based on i*: An Approach from the Attacker Viewpoint
TL;DR: A service security modeling approach based on the agent-oriented requirement modeling framework, i*.
Book ChapterDOI
Conceptual Modeling to Support the “Larger Goal” Pivot – An Example from Netflix
TL;DR: In this article, the authors present conceptual models of the larger goal pivot based on a historic example from Netflix, a movie streaming service, which is essential when lower-level options for achieving a higher-level organizational goal are either unavailable or insufficient.
Using Models at Run Time to Detect Incomplete and Inconsistent Requirements.
Byron DeVries,Betty H. C. Cheng +1 more
TL;DR: This paper introduces Lykus, an approach for using models at run time to detect incomplete and inconsistent requirements decompositions atRun time, and illustrates the approach by applying Lykus to a requirements model of an adaptive cruise control system from industrial collaborators.
Quality-aware agent-oriented information-system development
TL;DR: This thesis addresses issues about improving the treatment of quality concerns in the context of multi-agent systems and of goal-based requirements engineering by extending the Tropos methodology into Quality-aware Tropos and proposing a catalogue of design patterns for quality control.
Book ChapterDOI
User Perception of Numeric Contribution Semantics for Goal Models: An Exploratory Experiment
TL;DR: This work experimentally explores how users interpret numeric contribution labels in goal models and finds that users tend to prefer specific aggregation rules over others, depending on specific factors.
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.