3. Bases of estimates
Figure 6-4. Typical business case outline
Figure 6-4. Typical business case outline tion constraints, quality thresholds). These artifacts are intended to evolve along with the process, achieving greater fidelity as the life cycle progresses and requirements understanding matures. Figure 6-5 provides a default outline for a release specification.
There are two important forms of requirements. The first is the vision statement (or user need), which captures the contract between the development group and the buyer. This information should be evolving, but varying slowly, across the life cycle. It should be represented in a form that is understandable to the buyer (an ad hoc format that may include text, mockups, use cases, spreadsheets, or other formats). A use case model in the vision statement context serves to capture the operational concept in terms the user/buyer will understand.
Evaluation criteria, the second form of requirements contained in release specifications, are transient snapshots of objectives for a given intermediate life-cycle milestone. Evaluation criteria in release specifications are defined as management artifacts rather than as part of the requirements set. They are derived from the vision statement as well as many other sources (make/buy analyses, risk management concerns, architectural considerations, shots in the dark, implementation constraints, quality
Was this article helpful?
What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.