A Vision with less than 50 features is desirable. If more, consider grouping and abstracting the features. Other Requirements in the Vision In the Vision, system features briefly summarize functional requirements expressed in detail in the use cases. Likewise, the Vision can summarize other requirements (for example, reliability and usability) that are detailed in the Special Requirements sections of use cases, and in the Supplementary Specification (SS). However, there is some risk of unhelpful duplication f.e. in RUP for the Vision and SS that contain identical or similar sections for other requirements such as usability, reliability, performance, and so forth. For other requirements, avoid their duplication or near-duplication in both the Vision and Supplementary Specification (SS) - and in use cases. Rather, record them only in the SS or uses cases (if use case specific). In the Vision, direct the reader to these for the other requirements. Vision, Features, or Use cases -Which First? It is not useful to be rigid about the order of some artifacts. While collaborating to create different requirements artifacts, a synergy emerges in which working on one influences and helps clarify another. Nevertheless, a suggested sequence is: - Write a brief first draft of the Vision.
- Identify user goals and the supporting use cases.
- Write some use cases and start the Supplementary Specification.
- Refine the Vision, summarizing information from these.
Content: - The Glossary artifact template
- Introduction
- Glossary as Data Dictionary
- Units
- Composite Terms
The Glossary artifact template
Revision History (Version, Date, Description, Author)
Definitions
| | Introduction In its simplest form, the Glossary is a list of noteworthy terms and their definitions.
Do'stlaringiz bilan baham: |
