Work Product Descriptor (Artifact): Context and Objectives
The Context and Objectives artifact defines the scope and context of the IT architecture project. It outlines the activities, data, processes, and actors that are to be defined and implemented by the architecture or project, and includes a Context Diagram illustrating this scope and context. In addition, the objectives of the IT architecture project are defined.
Purpose

The Context and Objectives documentation may be a section within the Business Perspective description, or it may be a separate document if the scope is large. It defines the scope of the IT architecture through definition of the high-level Business Entities, Business Activities, Business Locations and Business Actors involved. Optionally important Business Rules and Business Events may be included. The scope is defined as precisely as possible at this point but may need to be revised later.

The context and objectives, and included Context Diagram: 

  • Provide a single place to define the context and scope;
  • Provide a list of the important entities, activities, locations and actors involved with the "system";
  • Defines precise and agreed definitions for the important entities, activities, locations and actors involved with the "system";
  • Provides an important start for new people who join the architecture team.  

The objectives of the IT architecture are also defined here, as an aid in keeping the effort focused, with the deliverables providing the desired information for the business.

Relationships
Input ToMandatory: Optional:
  • None
External:
  • None
Description
Main Description

Timing

The Context and Objectives is defined at the start of the IT architecture project since it sets the stage for all the rest of the work. Most things defined at this stage will go on to be described in detail during the development of the IT architecture.

Contents

The outline below details the rough contents of the Context and Objectives artifact, consult the "Context and Objectives" template definition below and the example for more detail.

Brief Outline

The Context and Objectives document is composed of four parts, plus a glossary. The outline of the document is:



1. Introduction

Identifies the purpose, background, and objectives of the business defined by the scope document.



2. Business Aspects

2.1 Entities

Identifies the business entities used within the business or system being modeled. Business entities identify significant and persistent pieces of information that are manipulated by business actors and business workers. No structure is attempted at this point, the sole objective being their identification and creation of clear and precise definitions.



2.2 Activities

Identifies the business activities within the scope of the architecture or project. These functions are defined using business activities, with no structure applied, the sole objective being their identification and clear and precise definition.



2.3 Locations

Identifies the locations at which the business or project has a presence.



2.4 Actors

Identifies the actors that interact with the architecture or system being modeled. A Business Actor represents a role played in relation to the business by someone or something in the business environment.

2.5 Business Rules (optional) 

Identifies the rules that the architecture or system being modeled needs to support. A Business Rule is a declaration of policy or a condition that must be satisfied. This section is optional.


2.6 Business Events (optional) 

Identifies the specific events that drive the business or system. A Business Event represents a significant occurrence in the activities of the business that requires immediate action. This section is optional.


3. Context Diagram 

Identifies the specific events that drive the business or system. A Business Event represents a significant occurrence in the activities of the business that requires immediate action. This section is optional.


4. Objectives


Architectural Glossary

The Glossary defines important terms used in the architecture or project (likely defined in a separate document for practical reasons).

Properties
Optional
Planned
Illustrations
Templates
Tailoring
Representation Options

This artifact is generally enclosed within the Business Perspective documentation (see the referenced template), but may be a separate document if the scope is large.

More Information
Checklists
Guidelines
© David W. Enstrom, 2025. All rights reserved.