Task: Optimize Secondary Architectural Views
This task focuses on strategic design decisions that are usually of secondary importance, such as data management, quality of service management, exception handling, etc.
Disciplines: Architecture
Purpose
The purpose of this task is to add in the secondary architectural views when they are important for the system design.
Relationships
Main Description

While not as fundamentally crucial to the majority of real-time and embedded systems as the key architectural view, the secondary architectural views, they do nevertheless define strategic supporting design decisions:

  • Security
  • Data management
  • Quality of Service management
  • Error and exceptional handling policies
  • Service Oriented Architecture (SOA)
  • Business Process Management (BPM)

It should be noted that some or all of these secondary views may be irrelevant for a given system and may be ignored in those cases.

Steps
Specify quality of service management architecture
Quality of Service (QoS) are constraints or limitations of some aspect of a system, usually - but not universally - related to performance. In many complex systems, generalize strategies must be put into place to ensure limit the propagation of errors due to violation of QoS properties of data to ensure adequate QoS on the data and services delivered. These QoS errors can compound in complex ways, both in terms of lag and delays, but also in terms of data accuracy. Quality of Service Management (QoSM) is the set of strategic policies for managing QoS across a complex system, system of systems, or enterprise. It is useful to note that QoS is primarily represented as metadata ("data about data").
Specify data management architecture
Data Management is defined to be the set of strategic policies and rules for storing, manipulating, validating, and managing data. Many real-time systems must manage huge volumes of high-rate data from a variety of sensors, perform data validation, fusion, storage, recall, and display.
Specify security architecture
Security is defined to be "freedom from intrusion or compromise of data privacy or integrity." The Security Architecture is the set of strategic technological and design decisions that provide protection against such intrusion or compromise.
Specify error and exception handling architectural policies
Many real-time and embedded systems are high-reliability or safety-critical. As such, as a part of the Safety and Reliability Architecture alerts and exception handling policies must be identified and clarified.
Specify business process model
BPM is the set of business rules that the technical architecture must support.
Specify service-oriented architecture

SOA is an architectural approach to enterprise architecture through the identification and allocation of services to architectural entities. While this is primarily in use today in IT enterprise architectures, the DoDAF 1.5 standard has defined a number of views specifically to support SOA for military systems, such as C4ISR (Command, Control, Communication, Computers, Intelligence, Surveillance, and Reconnaissance) systems. SOA is normally defined as the interaction of:

  • Servers - architectural elements that provide externally accessible services
  • Service Repositories - databases of services and their servers
  • Service Brokers - elements that can connect clients with desired services by looking them up in a Service Repository
More Information