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
Proceedings ArticleDOI
Creativity and Goal Modeling for Software Requirements Engineering
TL;DR: This work reports initial progress on a project aiming to combine goal modeling and creativity techniques for enhanced software Requirements Engineering (RE), and applies its methods to a historical case in air traffic control, providing example outcomes, illustrating the benefits of a creativity- and goal-oriented approach to early software development.
Book ChapterDOI
Aspects across Software Life Cycle: A Goal-Driven Approach
Nan Niu,Yijun Yu,Bruno González-Baixauli,Neil A. Ernst,Julio Cesar Sampaio do Prado Leite,John Mylopoulos +5 more
TL;DR: This paper proposes a model-driven framework for tracing aspects from requirements to implementation and testing, where goal models become engineering assets and straightforward model-to-code transformation bridges the gap between domain concepts and implementation technologies.
Journal ArticleDOI
An empirical investigation of the influence of persona with personality traits on conceptual design
Farshid Anvari,Deborah Richards,Michael Hitchens,Muhammad Ali Babar,Hien Minh Thi Tran,Peter Busch +5 more
TL;DR: The proposition that personas with personality traits can aid software engineers to produce conceptual designs tailored to the needs of specific personalities is supported.
Book ChapterDOI
Defining a Quality Model for Mail Servers
TL;DR: This paper presents an ISO/IEC-based quality model for the mail servers COTS domain, which is built by applying a precise methodology and its application to the domain is detailed.
Proceedings ArticleDOI
Integrating organizational requirements and object oriented modeling
TL;DR: This work presents a set of guidelines for the integration of early and late requirements specifications, and relies on the i* framework for early (organizational) modeling, whereas for late (functional) requirements specification, it relies on a precise subset of UML.
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.