Systematic software development using VDM (2nd ed.)
Systematic software development using VDM (2nd ed.)
Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
Inquiry-Based Requirements Analysis
IEEE Software
Deriving specifications from requirements: an example
Proceedings of the 17th international conference on Software engineering
Software engineering: theory and practice
Software engineering: theory and practice
Use Case Maps as Architectural Entities for Complex Systems
IEEE Transactions on Software Engineering
Mastering the requirements process
Mastering the requirements process
Applied software architecture
Linguistic Instruments in Requirements Engineering
Linguistic Instruments in Requirements Engineering
Requirements Engineering: A Good Practice Guide
Requirements Engineering: A Good Practice Guide
Requirements Engineering: Processes and Techniques
Requirements Engineering: Processes and Techniques
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
Information-Knowledge-Systems Management
Requirements Engineering
A Process Module to Pre-Process Requirements for Architecting
ECBS '07 Proceedings of the 14th Annual IEEE International Conference and Workshops on the Engineering of Computer-Based Systems
| Hi-index | 0.00 |
Atomic requirements are one way of specifying software requirements. In this paper, we describe how atomic requirements can be of particular interest in the context of software architectures. We describe the way how to specify atomic requirements and their impact on the requirements engineering process, with an emphasis on architectural issues. In this work, we combine the theoretical concept of atomic requirements with ideas from Volere, a requirements engineering process used by various industrial consultants.