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
A Comparison of Goal-Oriented Approaches to Model Software Product Lines Variability
Clarissa Borba,Carla Silva +1 more
TL;DR: A comparison among existing goal-oriented techniques and then, a new extension to the i* framework to capture common and variable requirements in software product lines is proposed.
Book ChapterDOI
A repository of agile method fragments
TL;DR: A repository of agile method fragments is introduced, which organizes the evidential knowledge according to their objectives and requisites, and proposes a modeling paradigm for visualizing the stored knowledge of method fragments, to facilitate the subsequent assembly task.
Specification and Analysis of Requirements Negotiation Strategy in Software Ecosystems.
TL;DR: A model based on negotiation and network theory for analyzing and designing flow of requirements through a software ecosystem supports requirements engineering process engineers and managers in taking strategic decisions for resolving communication bottlenecks, increasing overall requirements engineering productivity, and consciously assigning power to stakeholders.
Journal ArticleDOI
Intention-oriented programming support for runtime adaptive autonomic cloud-based applications
TL;DR: A requirements model for the runtime execution and control of an intention-oriented Cloud-Based Application and an associated framework are defined and developed where a given system's non/functional requirements are modelled in terms of intentions and encoded in a standard open mark-up language.
Proceedings ArticleDOI
Self-Explanation in Adaptive Systems
TL;DR: It is argued a self-adaptive system's behaviour needs to be explained in terms of satisfaction of its requirements, and the use of goal-based models during runtime to offer self-explanation of how a system is meeting its requirements.
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.