Business Analysis Extension

The Business Analysis extension provides a comprehensive framework for capturing requirements, requirement artefacts, elicitation activities, solution designs and solution evaluations. It bridges stakeholder needs to solution delivery while maintaining full traceability across the Triodian Metamodel.

Schema: business-analysis.schema.json
Specification: JSON Schema Draft-07

Overview

What is the Business Analysis Extension?

The Business Analysis extension formalizes the practice of business analysis within the Triodian Metamodel by providing structured schemas for:

Requirements — Formal, actionable definitions derived from stakeholder needs
Requirement Artefacts — Models, specifications and prototypes produced during analysis
Elicitation Activities — Methods and execution of information gathering
Analysis & Design Definitions — Solution options and refinements
Solution Evaluation — Post-implementation assessment

Why a Business Analysis Extension?

Challenge	How the Extension Helps
Siloed requirements	Links requirements to capabilities, value streams, initiatives
Lost traceability	End-to-end trace from stakeholder to solution
Inconsistent terminology	Mappings to BABOK, Volere, IREB, TOGAF and Agile concepts
Manual maintenance	Schema-driven relationships stay synchronized
Audit gaps	Captured elicitation activities support governance

Extension Components

Business Analysis Record

A business analysis record groups five lists. None is required; a record carries whichever the analysis has produced.

Attribute	Type	Description
`requirements`	Array[Object]	Requirements
`requirementArtefacts`	Array[Object]	Requirement artefacts such as models, specifications and prototypes
`elicitationActivities`	Array[Object]	Elicitation activities such as workshops and interviews
`analysisDesignDefinitions`	Array[Object]	Analysis and design definitions of the solution
`solutionEvaluations`	Array[Object]	Evaluations of implemented solutions

Identifiers (requirementID, artefactID, activityID, designDefinitionID, evaluationID) use the shared identifier form, e.g. REQ-001. Links to other records and domains are URIs.

Requirements Schema

Requirements extend stakeholder needs into formal, actionable definitions with acceptance criteria, measurements, and domain linkages.

Requirement (`requirement`)

Attribute	Type	Required	Description
`requirementID`	String	✓	Unique identifier for the requirement
`type`	Enum	✓	The classification of the requirement
`title`	String	✓	A concise title for the requirement
`description`	String	✓	Detailed description of the requirement
`priority`	Enum		The priority level of the requirement
`owner`	String (URI)		Reference to the owner (organization unit or person) of the requirement
`acceptanceCriteria`	Array[String]		Conditions that must be met for the requirement to be accepted
`measurementCriteria`	Array[String]		Metrics to measure the success of the requirement
`riskLevel`	Enum		Assessed risk level associated with the requirement
`relatedCapability`	String (URI)		Link to the related Capability
`relatedValueStream`	String (URI)		Link to the related Value Stream
`relatedInitiative`	String (URI)		Link to the related Initiative
`stakeholderRequirementRef`	String (URI)		Reference to the original Stakeholder Requirement (1:1 traceability)
`mappings`	Object		Corresponding concepts in BA frameworks (see Framework Mappings)

Requirement Type (`requirement.type`)

Value	Description	Examples
`businessRequirement`	Business goals, rules and policies the solution must satisfy	"Customer must be verified before trade"
`stakeholderRequirement`	Needs of a particular stakeholder or group	"Users need mobile access"
`solutionRequirementFunctional`	What the solution must do	"System shall calculate interest daily"
`solutionRequirementNonFunctional`	Quality attributes of the solution	"Page load time < 2 seconds"
`transitionRequirement`	Capabilities needed to move from the current to the future state	"Parallel run required for 30 days"
`regulatoryRequirement`	Obligations imposed by law, regulation or standards	"Must comply with PCI-DSS for transaction display"

Priority (`priority`)

The shared priority list.

Value	Description	Treatment
`low`	Desirable if resources permit	Backlog
`medium`	Important but not critical	Target for a later release
`high`	Important for near-term objectives	Target for release
`critical`	Critical for success	Include in MVP

Risk Level (`riskLevel`)

The shared four-point risk scale.

Value	Description
`low`	Little risk to delivery or operation
`medium`	Moderate risk; monitor
`high`	Significant risk; mitigation required
`critical`	Severe risk; must be addressed before proceeding

Domain Linkages

Requirements link to capabilities, value streams, initiatives and the stakeholder requirement they derive from:

{
  "relatedCapability": "urn:triodian:capability:CAP-MB-001",
  "relatedValueStream": "urn:triodian:valueStream:VS-DB-001",
  "relatedInitiative": "urn:triodian:initiative:INI-MAE-001",
  "stakeholderRequirementRef": "urn:triodian:stakeholder:STK-RC-001:requirement:SREQ-004"
}

Requirement Artefacts Schema

Requirement artefacts represent the models, specifications and prototypes produced during business analysis activities.

Requirement Artefact (`requirementArtefact`)

Attribute	Type	Required	Description
`artefactID`	String	✓	Unique identifier for the artefact
`type`	Enum	✓	The type of requirement artefact
`purpose`	String	✓	The purpose of the artefact
`linkedRequirements`	Array[String] (URI)		References to requirements documented or addressed by this artefact
`status`	Enum	✓	The current status of the artefact
`toolReference`	String (URI)		External tool link (e.g. Jira, Confluence, Miro)
`relatedInformationModel`	String (URI)		Link to the related Information domain model (e.g. for data models)
`mappings`	Object		Corresponding concepts in BA frameworks

Artefact Type (`requirementArtefact.type`)

Value	Description	Examples
`userStory`	Agile user story format	"As a user, I want..."
`epic`	A large body of work broken down into user stories	"Digital onboarding"
`useCase`	Use case specification	Actor-system interactions
`processModel`	Business process diagram	BPMN, flowchart
`dataModel`	Information structure	ERD, class diagram
`wireframePrototype`	UI mockup or working demonstration	Screen layouts, clickable prototype
`requirementsTraceabilityMatrix`	Matrix tracing requirements to sources, designs and tests	RTM
`solutionDesignDocument`	Formal specification of the solution	BRD, SRS, solution design

Artefact Status (`status`)

The shared document status list.

Value	Description
`draft`	Being written
`inReview`	Under review
`approved`	Approved for use
`superseded`	Replaced by a newer artefact
`obsolete`	No longer applicable

Elicitation Activities Schema

Elicitation activities capture how information was gathered, supporting traceability and audit requirements.

Elicitation Activity (`elicitationActivity`)

Attribute	Type	Required	Description
`activityID`	String	✓	Unique identifier for the activity
`type`	Enum	✓	The type of elicitation activity
`date`	Date-time	✓	Date and time of the activity
`facilitator`	String (URI)		Reference to the facilitator (organization unit or person)
`participants`	Array[String] (URI)		Links to participating Stakeholders
`artefactsProduced`	Array[String] (URI)		References to artefacts produced during this activity
`mappings`	Object		Corresponding concepts in BA frameworks

Elicitation Type (`elicitationActivity.type`)

Value	Description	Best For
`workshop`	Group facilitation	Consensus building, complex problems
`interview`	One-on-one discussion	Detailed requirements, sensitive topics
`observation`	Watching work being done	Process understanding, tacit knowledge
`survey`	Questionnaire	Large audiences, quantitative data
`documentAnalysis`	Review existing materials	Current state, regulations
`prototypingSession`	Building to learn	UI requirements, validation

Participant Tracking

Participants are links to Stakeholder records; record what each contributed in the stakeholder or requirement records themselves.

{
  "facilitator": "urn:triodian:people:PPL-BA-LEAD-001",
  "participants": [
    "urn:triodian:stakeholder:STK-RC-001",
    "urn:triodian:stakeholder:STK-MDT-001"
  ]
}

Analysis & Design Definition Schema

Analysis and design definitions capture solution options, feasibility assessments, and design decisions.

Analysis and Design Definition (`analysisDesignDefinition`)

Attribute	Type	Required	Description
`designDefinitionID`	String	✓	Unique identifier for the analysis/design definition
`description`	String	✓	Description of the solution option or design refinement
`feasibilityRating`	Enum		Assessment of the feasibility of the solution option
`optionComparison`	Array[Object]		Structured comparison of solution options
`relatedCapabilities`	Array[String] (URI)		Capabilities impacted or enabled by the solution
`relatedInitiatives`	Array[String] (URI)		Initiatives related to the solution design
`relatedRisks`	Array[String] (URI)		Risks identified during analysis and design
`linkedRequirements`	Array[String] (URI)		Requirements addressed by this analysis or design
`mappings`	Object		Corresponding concepts in BA frameworks

Option Comparison (`optionComparison`)

Attribute	Type	Description
`optionName`	String	Name of the option
`pros`	Array[String]	Advantages of the option
`cons`	Array[String]	Disadvantages of the option
`score`	Number	Overall score given to the option

Feasibility Rating (`feasibilityRating`)

The shared rating list plus notFeasible.

Value	Description
`low`	Feasible only with significant difficulty, cost or risk
`medium`	Feasible with some difficulty
`high`	Readily feasible
`critical`	Feasibility is a critical concern that must be resolved before proceeding
`notFeasible`	The option cannot be delivered

Solution Option Evaluation

{
  "designDefinitionID": "DD-001",
  "description": "Options for the digital onboarding platform: configure a SaaS platform rather than build a bespoke solution",
  "feasibilityRating": "high",
  "optionComparison": [
    {
      "optionName": "Build Custom Solution",
      "pros": [
        "Full customization",
        "No vendor dependency"
      ],
      "cons": [
        "High cost (AUD 2.5M)",
        "18-month timeline",
        "Maintenance burden"
      ],
      "score": 2.1
    },
    {
      "optionName": "Configure SaaS Platform",
      "pros": [
        "Faster delivery (6 months)",
        "Lower cost (AUD 0.8M)",
        "Vendor support"
      ],
      "cons": [
        "Limited customization",
        "Ongoing license cost"
      ],
      "score": 4.3
    }
  ],
  "relatedCapabilities": [
    "urn:triodian:capability:CAP-ONB-001"
  ],
  "relatedInitiatives": [
    "urn:triodian:initiative:INI-DOB-001"
  ],
  "relatedRisks": [
    "urn:triodian:risk:RSK-VND-004"
  ]
}

Solution Evaluation Schema

Solution evaluation assesses implemented solutions against defined success criteria and recommends whether to continue, pivot or retire them.

Solution Evaluation (`solutionEvaluation`)

Attribute	Type	Required	Description
`evaluationID`	String	✓	Unique identifier for the evaluation
`description`	String	✓	Description of the solution evaluation
`evaluationDate`	Date	✓	Date of the evaluation
`metricsObserved`	Array[String] (URI)		References to specific Performance Indicators (KPIs) and their observed values
`recommendation`	Enum	✓	Recommendation based on the evaluation
`relatedInitiatives`	Array[String] (URI)		Initiatives that implemented the solution being evaluated
`relatedRequirements`	Array[String] (URI)		Requirements that were fulfilled by the solution being evaluated
`mappings`	Object		Corresponding concepts in BA frameworks

Recommendation (`recommendation`)

Value	Description
`continue`	The solution meets its objectives; keep it and extend where useful
`pivot`	The solution partly meets its objectives; change direction or scope
`retire`	The solution does not deliver sufficient value; decommission it

Performance Assessment

Observed metrics are recorded as performance indicators and referenced from the evaluation:

{
  "evaluationID": "EVAL-001",
  "description": "Post-implementation review of digital onboarding: completion rate 92% against a target of 85%, average onboarding time 8 minutes against 10. Early stakeholder engagement reduced rework.",
  "evaluationDate": "2025-02-01",
  "metricsObserved": [
    "urn:triodian:performance:KPI-ONB-COMPLETION",
    "urn:triodian:performance:KPI-ONB-TIME"
  ],
  "recommendation": "continue",
  "relatedInitiatives": [
    "urn:triodian:initiative:INI-DOB-001"
  ],
  "relatedRequirements": [
    "urn:triodian:businessAnalysis:requirement:REQ-001"
  ]
}

Framework Mappings

Every business analysis element can carry a mappings object naming the corresponding concept in each framework.

Mapping (`mapping`)

Attribute	Type	Description
`babok`	String	Corresponding BABOK concept
`volere`	String	Corresponding Volere concept
`ireb`	String	Corresponding IREB concept
`togaf`	String	Corresponding TOGAF concept
`agile`	String	Corresponding Agile concept

BABOK Alignment

Triodian Concept	BABOK Equivalent
Requirement	Requirement
Elicitation Activity	Elicitation Technique
Requirement Artefact	Deliverable
Analysis & Design Definition	Design Definition
Solution Evaluation	Solution Evaluation

Volere Alignment

Triodian Concept	Volere Equivalent
Functional Solution Requirement	Functional Requirement
Non-Functional Solution Requirement	Non-Functional Requirement
Business Requirement	Business Requirement
Regulatory Requirement	Constraint

IREB Alignment

Triodian Concept	IREB Equivalent
Requirement	Requirement
Stakeholder Requirement	Stakeholder Requirement
Solution Requirement	Solution Requirement
Elicitation Activity	Elicitation

Agile Alignment

Triodian Concept	Agile Equivalent
Requirement Artefact (`epic`)	Epic /Feature
Requirement Artefact (`userStory`)	User Story
Acceptance Criteria	Acceptance Criteria

Complete Example

Mobile Banking Onboarding Requirements

{
  "requirements": [
    {
      "requirementID": "REQ-001",
      "type": "solutionRequirementFunctional",
      "title": "Quick Transaction View on Login",
      "description": "As a mobile banking customer, I want to see my last 10 transactions immediately upon logging in so I can quickly review my recent account activity",
      "priority": "critical",
      "owner": "urn:triodian:organization:OU-MOBILE-001",
      "acceptanceCriteria": [
        "Last 10 transactions display within 2 seconds of login",
        "Transactions show date, description, and amount",
        "User can tap transaction for full details",
        "Displays message if no transactions exist"
      ],
      "measurementCriteria": [
        "Load time under 2 seconds (performance monitoring)",
        "User satisfaction above 4.0/5.0 (in-app rating)"
      ],
      "riskLevel": "medium",
      "relatedCapability": "urn:triodian:capability:CAP-MB-001",
      "relatedValueStream": "urn:triodian:valueStream:VS-DB-001",
      "relatedInitiative": "urn:triodian:initiative:INI-MAE-001",
      "stakeholderRequirementRef": "urn:triodian:stakeholder:STK-RC-001:requirement:SREQ-004",
      "mappings": {
        "babok": "Functional Requirement",
        "volere": "Functional Requirement",
        "ireb": "User Requirement",
        "agile": "User Story"
      }
    }
  ],
  "requirementArtefacts": [
    {
      "artefactID": "ART-001",
      "type": "userStory",
      "purpose": "Capture the quick transaction view as a user story for the mobile backlog",
      "linkedRequirements": [
        "urn:triodian:businessAnalysis:requirement:REQ-001"
      ],
      "status": "approved",
      "toolReference": "https://jira.example.com/browse/MOB-1042"
    }
  ],
  "elicitationActivities": [
    {
      "activityID": "ACT-001",
      "type": "workshop",
      "date": "2024-11-15T09:00:00Z",
      "facilitator": "urn:triodian:people:PPL-BA-LEAD-001",
      "participants": [
        "urn:triodian:stakeholder:STK-RC-001",
        "urn:triodian:stakeholder:STK-MDT-001"
      ],
      "artefactsProduced": [
        "urn:triodian:businessAnalysis:requirementArtefact:ART-001"
      ],
      "mappings": {
        "babok": "Workshops"
      }
    }
  ],
  "analysisDesignDefinitions": [
    {
      "designDefinitionID": "DD-002",
      "description": "Approved design for implementing quick transaction view using the cached transaction API",
      "feasibilityRating": "high",
      "relatedCapabilities": [
        "urn:triodian:capability:CAP-MB-001"
      ],
      "linkedRequirements": [
        "urn:triodian:businessAnalysis:requirement:REQ-001"
      ]
    }
  ]
}

Usage Guidelines

Best Practices

Link requirements to domains — Always connect requirements to capabilities, value streams
Capture elicitation details — Record who participated and what was learned
Document options considered — Show alternatives even if not selected
Maintain traceability — Keep links current as requirements evolve
Use framework mappings — Record BABOK, Volere, IREB, TOGAF and Agile equivalents in mappings for different audiences

Integration with Strategic Response Model

When requirements stem from strategic triggers:

For Data Engineers

The Business Analysis extension helps trace data requirements from business needs to technical specifications. Link requirement artefacts to Information domain models (relatedInformationModel) and to your data catalog entities to maintain end-to-end traceability from business request to data asset.

Stakeholder Domain — Source of stakeholder requirements
Initiatives Domain — Delivery vehicle for requirements
Capabilities Domain — What requirements enable
Strategic Response Model — Trigger-to-response tracing

Overview​

What is the Business Analysis Extension?​

Why a Business Analysis Extension?​

Extension Components​

Business Analysis Record​

Requirements Schema​

Requirement (requirement)​

Requirement Type (requirement.type)​

Priority (priority)​

Risk Level (riskLevel)​

Domain Linkages​

Requirement Artefacts Schema​

Requirement Artefact (requirementArtefact)​

Artefact Type (requirementArtefact.type)​

Artefact Status (status)​

Elicitation Activities Schema​

Elicitation Activity (elicitationActivity)​

Elicitation Type (elicitationActivity.type)​

Participant Tracking​

Analysis & Design Definition Schema​

Analysis and Design Definition (analysisDesignDefinition)​

Option Comparison (optionComparison)​

Feasibility Rating (feasibilityRating)​

Solution Option Evaluation​

Solution Evaluation Schema​

Solution Evaluation (solutionEvaluation)​

Recommendation (recommendation)​

Performance Assessment​

Framework Mappings​

Mapping (mapping)​

BABOK Alignment​

Volere Alignment​

IREB Alignment​

Agile Alignment​

Complete Example​

Mobile Banking Onboarding Requirements​

Usage Guidelines​

Best Practices​

Integration with Strategic Response Model​

Related Documentation​