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
Journal ArticleDOI
From modeling to implementing the perception loop in self-conscious systems
TL;DR: The externalist point of view is used for developing a complete process for the design and implementation of a conscious robotic system that is able to interact with a dynamic environment in a human-like fashion without possessing detailed knowledge about the environment and pre-programmed tasks and algorithms.
Dissertation
Managing mismatches in COTS-based development
TL;DR: It is argued that the successful selection of a suitable COTS product depends on the effective analysis of mismatches and management of risks, and a novel method, called TAOS (Tradeoff Analysis for COTS-based Systems), is proposed to guide the selection of COTS products.
Journal ArticleDOI
Extracting finite state models from i* models
TL;DR: In this paper, the authors proposed the Semantic Implosion Algorithm (SIA) to reduce the model space growth from O(1020) to O(103 by exploiting the temporal information embedded within the i* model of an enterprise.
Journal Article
An i*-based approach for modeling and testing web requirements
TL;DR: This paper presents an approach for using thei* framework for modeling users' goals with mockups and WebSpec diagrams for detailing the specification of Web requirements in such a way that the process of evaluating i*models for Web applications can be automated thus improving users' feedback during the development process.
Proceedings ArticleDOI
Mining and analysing security goal models in health information systems
TL;DR: A key value proposition of the approach is that requirements are mined “in-place”, i.e., the structured model is tightly integrated with the NL text, which results in better traceability and enables an iterative rather than waterfall-like requirements extraction and analysis process.
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.