Guideline: The Scope of Requirement Elicitation
Identifies relevant tasks within the process of requirements elicitation and details the involved parties.
Relationships
Parent Practices
Main Description
End-users, clients, analysts and designers have to list the potential requirements. The context in which the system will be deployed must be understood. The functional and non-functional requirements must be established. The requirements document must be checked, approved and updated with consensual requirements. Limits and constraints can be found in the expression of non-functional requirements and in the definition of the context in which the system will be deployed.

This material is made available under the Creative Commons—Attribution-ShareAlike License v3.0.

© Copyright 2013, 2014 by Institute for Software & Systems Engineering, University of Augsburg
Contributors
Contact: Jan-Philipp Steghöfer
Impressum

Parts of this material is based on the Eclipse Process Framework Practice Library, distributed under the Eclipse Public License V1.0.