Task: Update an Architecture Perspective

This task updates all views in a given perspective of a defined IT architecture as required based upon provided direction.

Disciplines: UAM IT Architecture

Purpose

This task updates the views in the defined IT architecture at a specified level (perspective). Specifically to:

Update the Entity Model;
Update the Process Model;
Update the Location Model;
Update the Roles Model;
Optionally:
- Update the Architecture Glossary;
- Define additional Architectural Decisions.

Relationships

Roles	Primary Performer: Enterprise Architect	Additional Performers: Business Line or Domain Architect Business Unit or Project Architect
Inputs	Mandatory: Architectural Decision Context and Objectives Model Repository	Optional: Business Goals Business Mission Business Model Business Motivation Model Business Objective Business Perspective Business Strategy Business Vision IT Strategy Logical Perspective Policies and Laws Project Charter Simple Logical Perspective Simple Technical Perspective Technical Perspective
Outputs	Business Perspective Logical Perspective Simple Logical Perspective Simple Technical Perspective Technical Perspective
Process Usage	IT Architecture Processes > Update Logical Perspective > Update Logical Models IT Architecture Processes > Update Technical Perspective > Update Technical Models IT Architecture Processes > Update Business Perspective > Update Business Perspective

Main Description

This task updates the views in a defined IT architecture. The update is required after:

The solution to a problem is defined;
A change to the business has been defined;
A new technology is to be introduced that requires an update to the IT architecture.

The specifics of the required update is defined in an Artifact: Architectural Decision (AD), however additional ADs may be defined if required. All views are updated as needed.

Steps

Update the Context and Scope

The context diagram defines the system's boundary, showing external actors along with an initial definition of internal activities that the actors interact with to accomplish a task ... this is updated if necessary. The Architectural GLossary may also require updating.

Update the Entity Model

Update the entity model:

Identify the new entities involved in the updated system, if any;
Review all relationships (only simple associations at the Business level) between entities;
Identify and describe the attributes of the entity;
Optionally define operations and events.

Check to ensure that the model is consistent and complete. Validate technical choices with domain experts, technical experts and other stakeholders. Technical choices made need to be documented and justified in Architectural Decisions (see: Architectural Decision).

Update the Process Model

Update the process model:

Identify activities from the new or revised business descriptions and scenarios;
Adjust the logical organization of the processes if needed;
Look for location dependencies;
Check for reuse.

Validate the interactions between activities, and the inputs and outputs of the activities (in terms of entities), to ensure consistency with the Entity Model and Roles Model.

Update the Locations Model

Update the locations model:

Collect information about the new locations, or update current locations;
Update the locations model;
Add or update locations relationships.

A Locations Model is complete only when it describes every location that the system has a presence at (within the given scope) at a consistent level of detail. Before you finish, make sure the locations model exhibits the characteristic properties of a good model.

The logical or physical segmentation of the network is defined in terms of "domains" and "zones" as defined in Whitepaper: A Reference Model for Enterprise Security.

Update the Roles Model

Update the roles model:

Update the actors and roles, or add new ones as needed;
Refine the actor and role relationships as needed.

A Roles Model is complete only when it describes every actor involved in business processes (within the given scope). See: Checklist: Actor and Role Checklist Guideline: Users, Actors and Roles, Guideline: Business Roles Model, Guideline: Logical Roles Model and Guideline: Technical Roles Model.

Evaluate your results

Before you finish, make sure the model exhibits the characteristic properties of a good model.

Key Considerations

The business entities identified during this task are high-level, but their definition must be very precise, and agreed by stakeholders.

More Information

Checklists	Business Entities Business Perspective Logical Entities Logical Perspective Technical Perspective
Concepts	Complex IT Architectures Data Modeling
Guidelines	Business Entity Business Entity Model Business Event Business Perspective Logical Activity Logical Actors and Roles Logical Entity Logical Entity Model Logical Event Logical Location Logical Locations Model Logical Perspective Logical Process Model Logical Roles Model Logical Rule Technical Activity Technical Actors and Roles Technical Entity Technical Entity Model Technical Event Technical Location Technical Locations Model Technical Perspective Technical Process Model Technical Roles Model Technical Rule
Supporting Materials	BPL Summary UAM Perspective Languages