Se Architecture

According to the DoD Integrated Architecture Panel, architecture is the structure of components, their relationships, and the principles and guidelines governing their design and evolution over time. Architecture should involve several points-of-view, as seen in Figure 1. There are four main views in the core architecture data model: Operational View, System/Services View, Technical Standards View, and All-View. Much like four people can give different (but still accurate) descriptions of the same event, these views each provide a unique eye when looking at system architecture.

Figure 1

The operational view states what needs to be done and by who. Included in this view is a high level operational concept. The operational view is concerned with:

* Operational nodes: activities at and connections between nodes

* Tasks and activities performed: task relationships, timing, and coordination

* Information to be exchanged: types of exchange, frequency of exchange, tasks supported by exchanges, quality and quantity of exchange

The systems and services view describes systems, services, and characteristics and relates them to the operational needs. Typically involved in the systems and services view are descriptions of the following

* Interfaces

* Communications

* Functionality

* Evolution & future technology

* Activity sequence and timing

* Physical implementation

The technical standards view describes the standards and conventions used to ensure the system meets the specified operational requirements. This view also includes a future technology forecast (within an appropriate time frame) to describe standards that may be on the rise. The technical standards view creates profiles on which systems are based.

All-View encompasses the three previously mentioned views and describes the scope and context of the architecture. It contains information that is relevant to each view, but does not give a distinct look. Specifically, some products described in this view are:

* Purpose

* Time frame

* Techniques and tactics

* Goals

* Environmental conditions

* Intended users

Architecture guidelines set standards to help lead to the fulfillment of stakeholder requirements. The most crucial guidelines to follow when constructing architecture are as follows:

* Have a purpose in mind. It is much easier to hit a stationary target than a moving one, so having a set goal when beginning an architecture will keep everything running on track. In addition, the process will be more efficient and create a more useful product, as each detail, down to the mundane, will be created with the overall goal as the finish line. This is true for an architecture as a whole, any piece thereof, or groups of architectures.

* Be simple and straightforward. When building architectures, the phrase KISS (Keep It Simple, Stupid) applies. Resources are wasted on systems that are exceedingly complex. The overall purpose should be kept in mind when determining the appropriate amount of detail