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
Dissertation
A Human-Centred Framework for Eliciting Users' Embedded Knowledge Requirements during Information Systems Development
TL;DR: This research has expanded the literature on knowledge transfer by illustrating that knowledge transfer processes do not transpire as a sequential orderly progression but are complex and occur simultaneously.
Journal ArticleDOI
A service-oriented framework to the design of information system service
TL;DR: A good design discipline based on SOMF (Service Oriented Model Framework) is proposed, which supports elicitation, modeling and requirements analysis supported by semi-formal methods (SOMF and UML) and formal methods (by using SysML and Petri Nets).
Problem Reduction: a systematic technique for deriving Specifications from Requirements
TL;DR: This paper introduces problem reduction, a systematic transformation from requirements to specifications by which a software problem with requirements deep in the world becomes a simplerSoftware problem with the same solution.
Journal ArticleDOI
Closing the GAP between organizational requirements and object oriented modeling
TL;DR: In this article, the authors present guidelines for the integration of early and late requirements specifications using the i* framework, which focuses on the description of organizational relationships among various organizational actors, and an understanding of the rationale for the alternatives chosen.
Proceedings ArticleDOI
Requirements engineering for COTS-based software systems
TL;DR: The RECSS method is proposed, aimed at supporting requirements elicitation and analysis in the context of COTS-based software systems, which builds a goal model of the system environment which identifies the external elements that interact with it.
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.