B. Desired freedoms (potential change scenarios)
FIGURE 6-9. Typical vision document outline
FIGURE 6-9. Typical vision document outline should be addressed so that there is a context for assessing design adaptability. The operational concept involves specifying the use cases and scenarios for nominal and off-nominal usage. The use case representation provides a dynamic context for understanding and refining the scope, for assessing the integrity of a design model, and for developing acceptance test procedures. The vision document provides the contractual basis for the requirements visible to the stakeholders.
The architecture description provides an organized view of the software architecture under development. It is extracted largely from the design model and includes views of the design, implementation, and deployment sets sufficient to understand how the operational concept of the requirements set will be achieved. The breadth of the architecture description will vary from project to project depending on many factors. The architecture can be described using a subset of the design model or as an abstraction of the design model with supplementary material, or a combination of both. As examples of these two forms of descriptions, consider the architecture of this book:
• A subset form could be satisfied by the table of contents. This description of the architecture of the book is directly derivable from the book itself.
• An abstraction form could be satisfied by a "Cliffs Notes" treatment. (Cliffs Notes are condensed versions of classic books used as study guides by some college students.) This format is an abstraction that is developed separately and includes supplementary material that is not directly derivable from the evolving product.
The approach described in Section 7.2 allows an architecture description to be tailored to the specific needs of a project. Figure 6-10 provides a default outline for an architecture description.
The software user manual provides the user with the reference documentation necessary to support the delivered software. Although content is highly variable across application domains, the user manual should include installation procedures, usage procedures and guidance, operational constraints, and a user interface description, at a minimum. For software products with a user interface, this manual should be developed early in the life cycle because it is a necessary mechanism for communicating and stabilizing an important subset of requirements. The user manual should be written by members of the test team, who are more likely to understand the user's perspective than the development team. If the test team is responsible for the manual, it can be generated in parallel with development and can be evolved early as a tangible and rel-
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.