Establish Future State Enterprise Architecture Description, Business Architect or Enterprise Architect
Description
The Future State Enterprise Architecture Description is created or updated to reflect areas that need to be changed or improved.
An Enterprise Architecture Framework is selected and used to create the Enterprise Architecture Description.
If technology related elements are included, then appropriate Architecture Frameworks for these technology areas are selected and the resulting Technology Architecture Descriptions are created. These specific Architecture Descriptions may be created by the teams that will use these architectures (e.g. IT, Facilities, or technology specific teams).
Audit Criteria
- Enterprise Architecture Framework Selected.
- Future State Enterprise Architecture Description created or revised.
- Demonstrate that architectural options have been evaluated.
- Other Architecture Descriptions created as needed (e.g. Intermediate transitions or other technology).
- Architecture Team is ensuring that the Architecture Descriptions are understood and used.
Document Templates
- Enterprise Architecture Description (See Selected Enterprise Architecture Framework).
Forms
- See models in the selected Enterprise Architecture Framework.
Process Details
- Modelling approaches (e.g. MBSE and UML)
- Organizational design
- Process models
- Competency frameworks.
References
Managing Successful Projects with PRINCE2™
- Managing Successful Programmes (Blueprints).
Additional Details
Management System Contents
Quality Manual
The Quality Manual contains the following information:
Sections | Description |
Introduction | The formal introduction to the management system. This section defines the:
|
Organisation, Roles and Responsibilities | This section presents the organisation using the management system, the key roles and responsibilities of people within the organisation. |
Quality Management System | This section describes the way the Management System works. This section describes:
|
Appendices | The appendices provide a starting point for Quality Management System Auditors or Assessors. The appendices include:
|
Document Control and Revision History Information | This information provides a summary of changes to the document and provides a document control tracking area for various published and approved versions of this document. (When the Quality Manual is published as an online document, the information is at the end of the document; when the Quality Manual is published as a hard copy document (uncontrolled), the revision history information will be at the front of the document. |
A document template for the Quality Manual is available in PMLC_TPL001 Quality Manual.
Organisation's Set of Standard Processes (OSSP)
The OSSP contains similar information to the Quality Manual. There is no required structure for an OSSP. An example OSSP is available for review.
Process Model
The process model identifies all of the processes used in the management system. This allows all of the critical interfaces to be defined. The process model may take the form of a separate document however, at a minimum, the process model will be a picture of all of the processes and a description of their interfaces. A template for the process model document is available in the document PMLC_TPL002 Process Model.
Organisational Blueprint
The organisational blueprint identifies the structure, people, processes, systems and facilities, rewards and measurements, and planning structure for the organisation. This blueprint helps identify where processes are owned within the organisation.