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
Applying a security requirements engineering process
TL;DR: In this paper, a case study is presented demonstrating how the security requirements for a security critical IS can be obtained in a guided and systematic way by applying SREP (Security Requirements Engineering Process), which is a standard-centred process and a reuse-based approach which deals with the security requirement at the earlier stages of software development in a systematic and intuitive way by providing a security resources repository and by integrating the Common Criteria into the software development lifecycle.
Book ChapterDOI
Modeling Goals and Reasoning with Them
Colette Rolland,Camille Salinesi +1 more
TL;DR: This chapter presents a particular goal model, the goal/strategy map, and shows that maps can help with facing the challenge of new emerging multi-purposes systems, i.e. systems imposing variability in requirements elaboration and customization in the requirements engineering process.
Book ChapterDOI
A goal-oriented software testing methodology
TL;DR: A testing framework for the AOSE methodology Tropos specifies a testing process model that complements the agent-oriented requirements and design models and strengthens the mutualrelationship between goal analysis and testing.
Journal ArticleDOI
The Unified Enterprise Modelling Language—Overview and further work
Víctor Anaya,Giuseppe Berio,Mounira Harzallah,Patrick Heymans,Raimundas Matulevičius,Andreas L. Opdahl,Hervé Panetto,María-José Verdecho +7 more
TL;DR: This paper motivates and presents the most central parts of the UEML approach: a structured path to describing enterprise and IS modelling constructs; a common ontology to interrelate construct descriptions at the semantic level; a correspondence analysis approach to estimate semantic construct similarity.
Book ChapterDOI
Aligning IS to organization's strategy: the INSTAL method
TL;DR: The proposed method, called INSTAL (Intentional Strategic Alignment), reuses organization documents as a basis to formalize strategic alignment and describes organizations' strategic objectives and its IS, in order to document and analyze strategic alignment.
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.