Service Package Graphic Explanation
The previous table includes all Architecture Flows defined for this Service Package. The "In Graphic" column identifies whether the Architecture Flow is shown ("Yes") or not shown ("No") on the graphic.
The purpose of the graphic is to provide an overall understanding of the Service Package. In order to provide visual clarity, the graphic focuses on showing the Architecture Flows most critical to the scope and operation of the Service Package.
In general, major subsystem to subsystem Architecture Flows are shown. Architecture Flows associated with environmental and human terminators are usually omitted. Secondary subsystem to subsystem and subsystem to system terminator Architecture Flows are included only when they help to understand the overall operation of the Service Package, or highlight a portion of the architecture that otherwise would not be included in any of the Service Package graphics.
Note that the degree to which the Architecture Flows are filtered also varies from Service Package to Service Package. Very broad, complex Service Packages (e.g., ATMS08: Traffic Incident Management System) have a large number of Architecture Flows as compared to some of the simpler Service Packages (e.g., ATIS3: Autonomous Route Guidance). Consequently, some Service Packages have more flows filtered out just to keep the graphic from being overloaded with flows and difficult to understand.