Business Analysis

Purpose

To formalise the activities, artefacts, and outputs of business analysts, ensuring robust traceability to other Orthogramic domains (e.g., Stakeholder, Capabilities, Initiatives). This domain is designed to be schema-first, reusable, and easily translatable into BABOK, Volere, IREB, TOGAF, and Agile contexts, thereby supporting informed decision-making and continuous improvement across the enterprise.

Core Entities and Attributes

1. Requirement

Extends the concept of Stakeholder Requirements by formalising them into actionable, solution-oriented definitions.

Attribute	Type	Description	Relationships

Attribute	Type	Description	Relationships
`id`	UUID	Unique identifier for the requirement.
`type`	Enum	`Business Requirement`, `Stakeholder Requirement`, `Solution Requirement (Functional)`, `Solution Requirement (Non-Functional)`, `Transition Requirement`, `Regulatory Requirement`.
`title`	String	A concise title for the requirement.
`description`	String	Detailed description of the requirement.
`priority`	Enum	The priority level of the requirement (`Critical`, `High`, `Medium`, `Low`).
`owner`	Link	Links to the `Organisation Unit` (page 27) or `Person` (page 218) responsible for the requirement.
`acceptanceCriteria`	Array of Strings	Conditions that must be met for the requirement to be accepted.
`measurementCriteria`	Array of Strings	Metrics to measure the success of the requirement.
`riskLevel`	Enum	Assessed risk level associated with the requirement (`High`, `Medium`, `Low`, `Negligible`).
`relatedCapability`	Link	Link to the related `Capability` (page 54).	`Requirement` enables or changes `Capability`.
`relatedValueStream`	Link	Link to the related `Value Stream` (page 115).	`Requirement` impacts `Value Stream`.
`relatedInitiative`	Link	Link to the related `Initiative` (page 109).	`Requirement` is implemented by `Initiative`.
`stakeholderRequirementRef`	Link	Reference to the original `Stakeholder Requirement` (page 41) for 1:1 traceability.	`Stakeholder Requirement` from the Stakeholder domain maps into the `Requirement` entity with 1:1 traceability.

2. Requirement Artefact

Represents the various documents and models produced during business analysis activities.

Attribute	Type	Description	Relationships

Attribute	Type	Description	Relationships
`id`	UUID	Unique identifier for the artefact.
`type`	Enum	`User Story`, `Epic`, `Use Case`, `Process Model` (BPMN 2.0-compliant), `Data Model` (links to Information domain), `Wireframe/Prototype`, `Requirements Traceability Matrix`, `Solution Design Document`.
`purpose`	String	The purpose of the artefact.
`linkedRequirements`	Multi-select Links	Links to `Requirement` entities documented or addressed by this artefact.	`Requirement Artefact` documents `Requirement`.
`status`	Enum	The current status of the artefact (`Draft`, `Approved`, `In Review`, `Obsolete`).
`toolReference`	String (URI)	External tool link (e.g., Jira, Confluence, Miro).
`relatedInformationModel`	Link	Link to related `Information Model` (page 103) for artefacts like Data Models.	`Data Model` (as `Requirement Artefact`) links to `Information Model`.

3. Elicitation Activity

Captures the methods and execution details of gathering information for requirements.

Attribute	Type	Description	Relationships

Attribute	Type	Description	Relationships
`id`	UUID	Unique identifier for the activity.
`type`	Enum	`Workshop`, `Interview`, `Observation`, `Survey`, `Document Analysis`, `Prototyping Session`.
`date`	Date/Time	Date and time of the activity.
`facilitator`	Link	Links to an `Organisation Unit` (page 27) or `Person` (page 218) who facilitated the activity.	`Elicitation Activity` is facilitated by `Organisation Unit` or `Person`.
`participants`	Array of Links	Links to `Stakeholder` (page 41) entities who participated.	`Stakeholders` participate in `Elicitation Activity`.
`artefactsProduced`	Array of Links	Links to `Requirement Artefact` entities produced during this activity.	`Elicitation Activity` produces `Requirement Artefact`.

4. Analysis & Design Definition

Captures BA-led solution options and refinement, detailing how requirements will be met.

Attribute	Type	Description	Relationships

Attribute	Type	Description	Relationships
`id`	UUID	Unique identifier for the analysis/design definition.
`description`	String	Description of the solution option or design refinement.
`feasibilityRating`	Enum	Assessment of the feasibility (`High`, `Medium`, `Low`, `Not Feasible`).
`optionComparison`	Array of Objects	Structured comparison of solution options, including pros, cons, and scores.
`relatedCapabilities`	Array of Links	Links to `Capability` (page 54) entities impacted or enabled by the solution.	`Analysis & Design Definition` impacts/refines `Capability`.
`relatedInitiatives`	Array of Links	Links to `Initiative` (page 109) entities related to the solution design.	`Analysis & Design Definition` drives `Initiative`.
`relatedRisks`	Array of Links	Links to `Risk` (page 150) entities identified during analysis and design.	`Analysis & Design Definition` identifies/mitigates `Risk`.
`linkedRequirements`	Array of Links	Links to `Requirement` entities addressed by this analysis or design.	`Analysis & Design Definition` addresses `Requirement`.

5. Solution Evaluation

Assesses the performance of implemented solutions against defined metrics and objectives.

Attribute	Type	Description	Relationships

Attribute	Type	Description	Relationships
`id`	UUID	Unique identifier for the evaluation.
`description`	String	Description of the solution evaluation.
`evaluationDate`	Date	Date of the evaluation.
`metricsObserved`	Array of Links	Links to specific `Performance Indicator` (KPIs) (page 106) and their observed values.	`Solution Evaluation` measures against `Performance Indicator`.
`recommendation`	Enum	Recommendation based on the evaluation (`Continue`, `Pivot`, `Retire`).
`relatedInitiatives`	Array of Links	Links to `Initiative` (page 109) entities that implemented the solution being evaluated.	`Solution Evaluation` assesses `Initiative`.
`relatedRequirements`	Array of Links	Links to `Requirement` entities that were fulfilled by the solution being evaluated.	`Solution Evaluation` evaluates `Requirement`.

Relationships to Orthogramic Domains

The Business Analysis domain establishes critical relationships with several existing Orthogramic domains, ensuring comprehensive traceability and integration:

Domain	Relationship

Domain	Relationship
Stakeholder	Existing `Stakeholder Requirements` can become a direct sub-element of the `Requirement` entity, maintaining clear lineage. `Stakeholders` participate in `Elicitation Activities`.
Capabilities/ Value Stream	`Requirements` are mapped to what the organisation must enable or change (`Capability`) or how value is delivered (`Value Stream`). `Analysis & Design Definitions` also impact `Capabilities`.
Initiatives	`Requirements` are implemented through `Initiatives`. `Analysis & Design Definitions` drive `Initiatives`, and `Solution Evaluations` assess `Initiatives`.
Performance	`Solution Evaluation` measures outcomes against `Performance Indicators` (KPIs).
Information	`Data Models` as `Requirement Artefacts` link directly to the `Information` domain.
Organisation	`Requirements` can be owned by an `Organisation Unit`. `Organisation Units` can facilitate `Elicitation Activities`.
People	`People` can facilitate `Elicitation Activities`.
Risk Management	`Analysis & Design Definitions` identify and mitigate `Risks`.

Translation Layer Hooks

Each core entity within the Business Analysis domain includes a mappings element. This attribute provides a crucial interoperability layer, allowing the Orthogramic BA domain to reformat outputs and terminology directly into the language and deliverables of various industry frameworks.

Example:

"mappings": {
   "BABOK": "Requirements Analysis & Design Definition",
   "Volere": "Functional Requirement",
   "IREB": "Requirement Type",
   "TOGAF": "Architecture Building Block",
   "Agile": "User Story"
}

Integration with Updated Orthogramic Layers

The new Business Analysis domain slots naturally into the four conceptual layers of the Orthogramic Metamodel:

Strategic Intent: BA supports the articulation and refinement of Strategy and the detailed definition of Stakeholder Requirements.
Execution Framework: BA outputs (e.g., Requirements, Analysis & Design Definitions) directly drive Initiatives and clarify their impact on Value Streams and Capabilities.
Structural Context: Requirement Artefacts (like Process Models, Data Models) link directly to Organisation, Information, and Technology domains, providing detailed structural context.
Dynamic Alignment: BA-led Solution Evaluations feed directly into the Strategic Response Model (SRM) for continuous alignment and adaptation, ensuring that solutions deliver intended business outcomes.

Visualisation

Worked Example

A detailed worked example, tracing a user story through a Requirement, its impact on a Capability, and its implementation via an Initiative, has been provided to demonstrate the practical application and traceability within this domain.

1. Stakeholder Requirement (from `Stakeholder` domain)

Entity: StakeholderRequirement
ID: sr-001
Description: "As a mobile banking customer, I want to see my last 10 transactions immediately upon logging in, so I can quickly monitor my spending."
Source Stakeholder: "Retail Banking Customer" (stk-005 in Stakeholder domain)

2. User Story (as a `Requirement Artefact`)

Entity: RequirementArtefact
ID: ra-us-001
Type: User Story
Purpose: To define a small, shippable piece of functionality for the mobile app.
Content: "As a mobile banking customer, I want to see my last 10 transactions immediately upon logging in, so I can quickly monitor my spending."
Linked Requirements: req-001 (see below)
Status: Approved
Tool Reference: https://jira.example.com/browse/APP-123
Mappings:
- Agile: "User Story"
- BABOK: "Solution Requirement"

3. Requirement (derived from Stakeholder Requirement & User Story)

Entity: Requirement
ID: req-001
Type: Solution Requirement (Functional)
Title: "Display Last 10 Transactions on Mobile App Login"
Description: "The mobile banking application shall display the user's most recent 10 transactions on the main dashboard immediately following successful login."
Priority: Critical
Owner: "Digital Banking Product Team" (org-digbank in Organisation domain)
Acceptance Criteria:
- "User logs in successfully."
- "Dashboard loads within 2 seconds."
- "Displays exactly 10 transactions, ordered by date (most recent first)."
- "Each transaction includes: Date, Payee/Description, Amount, Balance."
Measurement Criteria: "99% of users see transactions displayed within 2 seconds on dashboard."
Risk Level: Low (assuming existing API)
Related Capability: "Customer Mobile Banking" (cap-mobilebank in Capability domain)
Related Value Stream: "Customer Onboarding & Servicing" (vs-custservice in Value Stream domain)
Related Initiative: "Mobile App Enhancement Q3" (init-appq3 in Initiative domain)
Stakeholder Requirement Ref: sr-001
Mappings:
- BABOK: "Solution Requirement (Functional)"
- Volere: "Functional Requirement"
- IREB: "Functional Requirement"
- TOGAF: "Architecture Requirement"

4. Capability (from `Capability` domain, impacted by `Requirement`)

Entity: Capability
ID: cap-mobilebank
Name: "Customer Mobile Banking"
Description: "Enables customers to interact with their banking services via a dedicated mobile application, including account viewing, transfers, and bill payments."
Relationships:
- Impacted by: req-001 (Display Last 10 Transactions)
- Enabled by: (links to underlying systems and processes)

5. Initiative (from `Initiative` domain, implementing `Requirement`)

Entity: Initiative
ID: init-appq3
Name: "Mobile App Enhancement Q3"
Description: "An agile development initiative to deliver key enhancements to the mobile banking application in Q3."
Owner: "Head of Digital Product" (peo-hdigital in People domain)
Status: In Progress
Relationships:
- Implements: req-001 (Display Last 10 Transactions on Mobile App Login)
- Delivers Value Stream: vs-custservice
- Contributes to Strategic Theme: "Enhance Customer Digital Experience" (strat-cx in Strategy domain)

Schema Reference

Schema file available on GitHub: Orthogramic_Metamodel/blob/main/schemas/business-analysis.schema.json