Plan

(Physical) Architecture Requirements analysis/capture

james — Sat, 08 Jul 2023 06:23:51 +0000

(Physical) Architecture Requirements analysis/capture james Sat, 07/08/2023 - 06:23

Mandatory

Yes

Security related?

Update of Architecture requirements at end of Physical architecture development to support creation of solution implementation work packages.

Deliverable Section

3.3 Physical Requirements Summary

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

TOGAF Phase

Project Phase

Related workpackage

Physical Architecture (Master Solution Architecture)

(Logical) Architecture Requirements analysis/capture

james — Sat, 08 Jul 2023 06:22:38 +0000

(Logical) Architecture Requirements analysis/capture james Sat, 07/08/2023 - 06:22

Mandatory

Yes

Security related?

Update of Architecture requirements at end of Logical architecture development

Deliverable Section

3.2 Logical Requirements Summary

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

TOGAF Phase

Project Phase

Related workpackage

Logical Architecture (Master Solution Architecture)

Physical Architecture ARB Pack

admin — Sun, 04 Jun 2023 22:50:23 +0000

Physical Architecture ARB Pack admin Sun, 06/04/2023 - 22:50

Effort small

Effort medium

Effort large

Architecture Phase

Physical

Project Phase

Plan

Related workpackage

ARB submission - Physical

Logical Architecture ARB Pack

admin — Sun, 04 Jun 2023 22:49:34 +0000

Logical Architecture ARB Pack admin Sun, 06/04/2023 - 22:49

Effort small

Effort medium

Effort large

Architecture Phase

Logical

Project Phase

Plan

Related workpackage

ARB submission - Logical

admin — Fri, 02 Jun 2023 03:43:50 +0000

ARB submission - Logical

Project Phase

Plan

admin Fri, 06/02/2023 - 03:43

Architecture Phase

Logical

Resources

Project SA

Activities

2. Consultation

5. Document Drafting

6. Stakeholder review

7. Approval process

Work Package ID

WP10.

Architecture assurance check-in 3

admin — Thu, 01 Jun 2023 06:43:20 +0000

Architecture assurance check-in 3

Project Phase

Plan

admin Thu, 06/01/2023 - 06:43

Architecture Phase

Physical

Resources

Core EA

SA Specialist

Project SA

Activities

2. Consultation

Work Package ID

WP14.

ARB submission - Physical

admin — Thu, 01 Jun 2023 06:37:10 +0000

ARB submission - Physical

Project Phase

Plan

admin Thu, 06/01/2023 - 06:37

Architecture Phase

Physical

Resources

Project SA

Activities

2. Consultation

5. Document Drafting

7. Approval process

Work Package ID

WP15.

Solution Options Report

admin — Sat, 13 May 2023 05:41:35 +0000

Solution Options Report admin Sat, 05/13/2023 - 05:41

Mandatory

The purpose of this section is to define the gap between the current (as-is) and target (to-be) state business architectures. Mandatory/optional: This section is optional as not all the domain teams need to produce a business architecture for their respective domains. However, it can also be used by the domains that do not produce a full (current and target) or current state business architecture but still want to know the (priority) areas on which to concentrate, and thus minimise effort. In terms of quality criteria, this section should make clear: • Description of the gap between the current (as-is) and target (to-be) state business architectures. This difference, or delta, defines the scope of work that needs to be undertaken in order to transition from the current to the target business architecture. This scope is thus the scope of the program(s) or project(s) that need to be completed in order to reach the target business architecture. The suggested steps are as follows: • Draw up a matrix with all the Architecture Building Blocks (ABBs) of the baseline architecture on the vertical axis, and all the ABBs of the target architecture on the horizontal axis. • Add to the baseline architecture axis a final row labeled ‘‘New’’, and to the target architecture axis a final column labeled ‘‘Eliminated’’. • Where an ABB is available in both the baseline and target architectures, record this with ‘‘Included’’ at the intersecting cell. • Where an ABB from the baseline architecture is missing in the target architecture, each must be reviewed. If it was correctly eliminated, mark it as such in the appropriate ‘‘Eliminated’’ cell. If it was not, an accidental omission in the target architecture has been uncovered that must be addressed by reinstating the ABB in the next iteration of the architecture design – mark it as such in the appropriate ‘‘Eliminated’’ cell. • Where an ABB from the target architecture cannot be found in the baseline architecture, mark it at the intersection with the ‘‘New’’ row as a gap that needs to filled, either by developing or procuring the building block. When the exercise is complete, anything under ‘‘Eliminated’’ or ‘‘New’’ is a gap, which should either be explained as correctly eliminated, or marked as to be addressed by reinstating or developing/procuring the function. Potential sources of gaps include: • Business domain gaps: o People gaps (e.g., cross-training requirements) o Process gaps (e.g., process inefficiencies) o Tools gaps (e.g., duplicate or missing tool functionality) o Information gaps o Measurement gaps o Financial gaps o Facilities gaps (buildings, office space, etc.) • Data domain gaps: o Data not of sufficient currency o Data not located where it is needed o Not the data that is needed o Data not available when needed o Data not created o Data not consumed o Data relationship gaps • Applications impacted, eliminated, or created • Technology impacted, eliminated, or created

Deliverable Section

2.4 Gap Analysis

Effort small

Effort medium

Effort large

Architecture Phase

Logical

TOGAF Phase

Requirements

Project Phase

Plan

Related workpackage

Solution/Technical Options Analysis

Procurement support

admin — Thu, 11 May 2023 04:56:05 +0000

Procurement support

Project Phase

Plan

admin Thu, 05/11/2023 - 04:56

Architecture Phase

Physical

Resources

Project SA

Creation of requirements for go to market. evaluation of NFR responses Consultation on vendor responses across all requirements

Activities

2. Consultation

Work Package ID

WP11.

Architecture assurance Check-in 2

admin — Thu, 11 May 2023 04:49:26 +0000

Architecture assurance Check-in 2

Project Phase

Plan

admin Thu, 05/11/2023 - 04:49

Architecture Phase

Logical

Resources

Core EA

SA Specialist

Project SA

To provide confidence that the key components of the Architecture (Conceptual, Logical & Technical) remain aligned to the resolution of the original problem or delivery of the identified opportunity. To provide a brief for the release of control from one architectural domain (Concept to Logical/Physical)

Activities

2. Consultation

Work Package ID

WP09.