Defining Non-Functional Requirements
ARCHITECTURE ESOURCES (2004)
Abstract
A system has properties that emerge from the combination of its parts. These emergent properties will surely be a matter of accident, not design, if the non-functional requirements, or system qualities, are not specified in advance. This white paper lays out important concepts and discusses capturing non-functional requirements in such a way that they can drive architectural decisions and be used to validate the architecture.
Sign up today - FREE
Mendeley saves you time finding and organizing research. Learn more
- All your research in one place
- Add and import papers easily
- Access it anywhere, anytime
Start using Mendeley in seconds!
Readership Statistics
3 Readers on Mendeley
by Discipline
by Academic Status
33% Student (Master)
33% Ph.D. Student
33% Assistant Professor
by Country
33% Bangladesh
33% Netherlands
33% Brazil