The Architecture Summary document is composed of four basic parts that correspond to the four IT architecture
aspects, plus an optionally a Rules section and Events section. A glossary is also included. Note that since
we are documenting an existing situation the Technical Perspective (or level) is used. The outline of the document
is:
1. Introduction
Identifies the purpose, background, and objectives of this document; include an outline of the scope of the
effort.
2. Technical Entities
Describe the data used within the system being summarized. This identifies the significant and
persistent pieces of information that are manipulated by the roles and processes in scope. Some structure is
attempted based upon existing documentation, with an emphasis on the relationships between the information. Creation of
clear and precise definitions is also highly desirable.
3. Technical Processes
Describe the business activities within the scope of the architecture or project. They are defined using simple
business activities, with no structure applied, the sole objective being their identification and clear and precise
definition.
4. Technical Locations
Describe the locations at which the system has a presence.
5. Technical Roles
Describe the roles that interact with the system being modeled. Specific users or categories of users may be a
more obvious thing to document, but if possible the different actors that they assume when interacting with the system
through roles should be pulled out.
6. Technical Rules (optional)
Describe the rules that govern the systems being examined. This section is optional.
7. Technical Events (optional)
Describe the specific events that drive the systems. An event represents a significant occurrence in the
activities of the business that requires immediate action. This section is optional.
8. Glossary
The glossary defines important terms used to describe the current situation, ideally using business terminology, but
technical terms should be defined as well.
|
