Views

The name of the view should be included in the page name

• Is usually graphical
• Should include a key that explains the notation
• Shows elements and relations among them
• Shows the information you want to convey about the view first
• Should identify elements that are external to scope of the view
  • If external entities are not clearly marked in the diagram, consider adding a context diagram

• Explains elements depicted in primary presentation and their properties
• Is usually a table with element name and textual description
• May contain interface documentation
• May contain behavior documentation

• Points where system can be parameterized or reconfigured. Examples:
  • Number of instances in a pool
  • Support for plug-ins or add-ons
  • Support for different versions of OS, database server or runtime environment
• Maybe the view is a reference architecture
  • Provide guidelines to instantiate it

• Description and rationale for important design decisions (including relevant rejected alternatives)
• Results of analysis, prototypes and experiments
• Context diagram

• Relation (Parent, Refinement, Common elements, etc). Name of view and a link to it.

It is recommended to have a link back to the main page of the SAD. It is assumed that the parent view is referred to in the Related Views section.