Create the ADF for the System-of-Interest

System-of-Interest ADF

Create or revise a system-of-interest Architecture Description Framework based upon the System Description that has been created for the system-of-interest. This whole system view of the system-of-interest provides a sound basis for developing the specific viewpoints / views that express the specific stakeholder concerns. This provides the following benefits:

  • The System-of-Interest ADF  uses consistent terminology and structural models

  • Any correspondences are integrated from the System Description allowing AD Element reuse.

  • Any stakeholder perspectives can be identified

The steps to create an Architecture Description Framework for a system-of-interest are as follows:

  • Identify the system-of-interest

  • Create the work product Architecture Viewpoint Definition (AVPD) for the system-of-interest to define the viewpoints.

    • Identify the context: Stakeholders and Purpose

    • Create the Ontology Definition View using one of the following:

      • The Conceptual Model of the system-of-interest created for the system-of-interest (See Abstract System CM)

      • or use elements from or reference the System Description for the System-of-interest as the basis for the Ontology Definition View.

    • The Viewpoint Relationships View: All of the Viewpoints

    • Each Viewpoint definition

    • Correspondences

    • Rationale

  • Create all of the other AD elements for the Architecture Description Framework

  • Create an Architecture Description to test the SoI ADF

The System Description created for the system-of-interest will be the starting point for creating a new system-of-interest architecture description framework.

The stakeholders, concerns or interests should already be in the system description. The conceptual models found in the Structure (Pattern of Organization) section can be used as a starting point for the Ontology Definition View. The View Relationship View will be the starting point for the Architecture Viewpoint Definition (AVPD).

This process may benefit from workshops on each view as the conversations may raise further interests and concerns or changes to existing AD Elements. This type of iteration is normal and expected.

If there are differences between stakeholders, the CSH process may be useful to align the thinking.

See the topic about the creation of the Architecture Viewpoint Definition (AVPD).

To complete the creation, both the System Description and the resulting Architecture Viewpoint Definition (AVPD) should be reviewed together to ensure that the stakeholders are in agreement and the ontology elements (aspects) are understood.

Finally, the first Architecture Description can be created and reviewed to confirm that the architecture of the system-of-interest is understandable and meets the needs ot the stakeholders.