By craig larman: Applying uml and patterns Lecture 3. Objectives - Write a Supplementary Specification, Glossary, and Vision.
- Compare and contrast system features with use cases.
- Relate the Vision to other artifacts, and to iterative development.
- Define quality attributes.
- Define the elaboration step.
- Motivate the following chapters in this section.
Content 1 Identifying Other Requirements - Supplementary Specification
- Vision
- Glossary (Data Dictionary)
- Reliable Specifications: An Oxymoron?
- Online Artifacts at the Project Website
- Not Much UML During Inception?
- Other Requirement Artifacts Within the UP
- UP Artifacts and Process Context
2 From Inception to Elaboration
- Checkpoint: What Happened in Inception?
- On to Elaboration
- Planning the Next Iteration
- Iteration 1 Requirements and Emphasis: Fundamental OOA/D Skills
- What Artifacts May Start in Elaboration?
1. Identifying Other Requirements 1. Identifying Other Requirements Introduction Supplementary Specification It is not sufficient to write use cases. There are other kinds of requirements that need to be identified, such as: - documentation,
- packaging,
- supportability,
- licensing, and
- so forth.
Introduction (cont.) Glossary The Glossary captures terms and definitions; it can also play the role of a data dictionary Introduction (cont.)
Do'stlaringiz bilan baham: |
