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
A goal-oriented, ontology-based methodology to support the design of AAL environments
TL;DR: A goal-oriented approach of the methodology is presented, which involves the elicitation and analysis of AAL requirements and their formal representation in an ontology, where high-level goals are described in terms of subgoals and tasks, that are then linked to corresponding measures and devices.
Proceedings ArticleDOI
Dependability Arguments with Trusted Bases
Eunsuk Kang,Daniel Jackson +1 more
TL;DR: In this article, an approach for arguing that a system is dependable is proposed, where critical requirements are localized in small, reliable subsets of the system's components called trusted bases.
Proceedings ArticleDOI
Ensuring Consistency among Business Goals and Business Process Models
TL;DR: A pattern-based approach for the automated generation of verifiable business process quality constraints from business goal models is presented and how these constraints can be used to check the consistency between business goals and business processes is described.
Proceedings ArticleDOI
Business Metadata for the DataWarehouse
Veronika Stefanov,Beate List +1 more
TL;DR: This paper introduces a weaving model between enterprise goals and DWH data, and describes metamodels for both aspects as well as the weaving links between them, which allows to show the aspects separately but also in combination.
Proceedings ArticleDOI
Evolution: a more practical approach than refinement for software development
TL;DR: It is shown that refinement is indeed a special case of evolution and evolution is transitive, and it is proposed that using evolution rather than refinement as the discipline for software development is a more practical approach.
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.