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
Modelling Strategic Actor Relationships to Support Intellectual Property Management
TL;DR: This paper outlines the use of the i* strategic actor relationships modelling framework to support IP management and suggests an ontology that captures the social and intentional dimensions of knowledge management.
Understanding Software Ecosystems: A Strategic Modeling Approach
Eric Yu,Stephanie Deng +1 more
TL;DR: This paper compares the buyer-supplier relationships in the traditional software supply chain to the open ecosystem format from a mobile platform vendor's perspective.
Proceedings ArticleDOI
Software development risk management model: a goal driven approach
TL;DR: This thesis contributes for a goal-drivenSoftware development risk management model to assess and manage software development risk within requirement engineering phase.
Book ChapterDOI
A Systematic Literature Review of Requirements Modeling and Analysis for Self-adaptive Systems
TL;DR: This paper provides an updated review of the research literature, enabling researchers and practitioners to better understand the research trends in these areas and identify research gaps which need to be further studied.
Book ChapterDOI
Enterprise Modeling for Business Intelligence
TL;DR: A vision for BI that is driven by enterprise modeling is presented, which draws upon well-established business practices such as Balanced Scorecard and Strategy Maps as well as requirements and conceptual modeling techniques such as goal modeling.
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.