Editing Requirements analysis (section)

=== Measurable goals ===
{{main|Goal modeling}}
Best practices take the composed list of requirements merely as clues and repeatedly ask "why?" until the actual business purposes are discovered. Stakeholders and developers can then devise tests to measure what level of each goal has been achieved thus far. Such goals change more slowly than the long list of specific but unmeasured requirements. Once a small set of critical, measured goals has been established, [[Software prototyping#Throwaway prototyping|rapid prototyping]] and short iterative development phases may proceed to deliver actual stakeholder value long before the project is half over.