Home | | Software Architectures | How the Documentation is Organized to Serve a Stakeholder

Chapter: Software Architectures : Documenting the Architecture

How the Documentation is Organized to Serve a Stakeholder

Every suite of architectural documentation needs an introductory piece to explain its organization to a novice stakeholder and to help that stakeholder access the information he or she she is most interested in. There are two kinds of "how" information: 1.· A view catalog · 2. A view template

HOW THE DOCUMENTATION IS ORGANIZED TO SERVE A STAKEHOLDER

 

Every suite of architectural documentation needs an introductory piece to explain its organization to a novice stakeholder and to help that stakeholder access the information he or she she is most interested in. There are two kinds of "how" information:

 

·     A view catalog

·     A view template

 

View Catalog

 

A view catalog is the reader's introduction to the views that the architect has chosen to include in the suite of documentation.

 

When using the documentation suite as a basis for communication, it is necessary for a new reader to determine where particular information can be found. A catalog contains this information. When using the documentation suite as a basis for analysis, it is necessary to know which views contain the information necessary for a particular analysis. In a performance analysis, for example, resource consumption is an important piece of information, A catalog enables the analyst to determine which views contain properties relevant to resource consumption.

 

There is one entry in the view catalog for each view given in the documentation suite. Each entry should give the following:

 

1.     The name of the view and what style it instantiates

 

2.     A description of the view's element types, relation types, and properties

 

3.     A description of what the view is for

 

4.     Management information about the view document, such as the latest version, the location of the view document, and the owner of the view document

 

The view catalog is intended to describe the documentation suite, not the system being documented. Specifics of the system belong in the individual views, not in the view catalog. For instance, the actual elements contained in a view are listed in the view's element catalog.

 

View Template

 

A view template is the standard organization for a view. Figure 9.1 and the material surrounding it provide a basis for a view template by defining the standard parts of a view document and the contents and rules for each. The purpose of a view template is that of any standard organization: It helps a reader navigate quickly to a section of interest, and it helps a writer organize the information and establish criteria for knowing how much work is left to do.

 

Study Material, Lecturing Notes, Assignment, Reference, Wiki description explanation, brief detail
Software Architectures : Documenting the Architecture : How the Documentation is Organized to Serve a Stakeholder |


Privacy Policy, Terms and Conditions, DMCA Policy and Compliant

Copyright © 2018-2024 BrainKart.com; All Rights Reserved. Developed by Therithal info, Chennai.