Business Analysis Extension

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

Schema Version: 2.1
Schema Location: /schemas/extensions/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 Orthogramic Metamodel by providing structured schemas for:

Requirements — Formal, actionable definitions derived from stakeholder needs
Requirement Artifacts — Documents and models 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	Translation layers for BABOK, Volere, IREB, Agile
Manual maintenance	Schema-driven relationships stay synchronized
Audit gaps	Captured elicitation activities support governance

Extension Components

Requirements Schema

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

Core Attributes

Attribute	Type	Required	Description
`requirementID`	string	Yes	Unique identifier
`title`	string	Yes	Requirement name
`description`	string	Yes	Detailed description
`requirementType`	enum	Yes	Category of requirement
`priority`	enum	No	Importance level
`status`	enum	No	Current status

Extended Attributes

Attribute	Type	Required	Description
`acceptanceCriteria`	array	No	Conditions for acceptance
`measurementCriteria`	array	No	How success is measured
`assumptions`	array	No	Underlying assumptions
`constraints`	array	No	Limiting factors
`dependencies`	array	No	Prerequisite requirements
`riskAssessment`	object	No	Risk evaluation
`source`	object	No	Where requirement originated

Requirement Types

Type	Description	Examples
`functional`	What the solution must do	"System shall calculate interest daily"
`non-functional`	Quality attributes	"Page load time < 2 seconds"
`business`	Business rules and policies	"Customer must be verified before trade"
`stakeholder`	Stakeholder needs	"Users need mobile access"
`solution`	Solution constraints	"Must integrate with SAP"
`transition`	Change management needs	"Parallel run required for 30 days"

Priority Levels

Priority	Description	Treatment
`must-have`	Critical for success	Include in MVP
`should-have`	Important but not critical	Target for release
`could-have`	Desirable if resources permit	Backlog
`wont-have`	Explicitly excluded	Future consideration

Domain Linkages

Requirements link to multiple Orthogramic domains:

{
  "domainLinks": {
    "capabilities": ["cap-customer-onboarding", "cap-identity-verification"],
    "valueStreams": ["vs-customer-acquisition"],
    "initiatives": ["init-digital-onboarding"],
    "stakeholders": ["sh-retail-customers", "sh-compliance-team"],
    "information": ["info-customer-data", "info-verification-records"]
  }
}

Requirement Artifacts Schema

Artifacts represent the documents and models produced during business analysis activities.

Core Attributes

Attribute	Type	Required	Description
`artifactID`	string	Yes	Unique identifier
`title`	string	Yes	Artifact name
`artifactType`	enum	Yes	Type of artifact
`description`	string	No	What the artifact contains
`status`	enum	No	Current status

Artifact Types

Type	Description	Examples
`user-story`	Agile user story format	"As a user, I want..."
`use-case`	Use case specification	Actor-system interactions
`process-model`	Business process diagram	BPMN, flowchart
`data-model`	Information structure	ERD, class diagram
`wireframe`	UI mockup	Screen layouts
`prototype`	Working demonstration	Clickable prototype
`decision-table`	Business rules matrix	Condition-action pairs
`state-diagram`	Lifecycle states	Entity state transitions
`context-diagram`	System boundaries	External interfaces
`requirements-spec`	Formal specification	BRD, SRS

Artifact Attributes

Attribute	Type	Description
`version`	string	Current version
`author`	string	Who created it
`createdDate`	date	When created
`lastModified`	date	When last updated
`format`	string	File format
`location`	string	Where stored
`linkedRequirements`	array	Requirements this supports
`reviewStatus`	enum	Approval state

Elicitation Activities Schema

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

Core Attributes

Attribute	Type	Required	Description
`activityID`	string	Yes	Unique identifier
`title`	string	Yes	Activity name
`elicitationType`	enum	Yes	Method used
`description`	string	No	Activity description
`scheduledDate`	date	No	When planned
`actualDate`	date	No	When conducted

Elicitation Types

Type	Description	Best For
`interview`	One-on-one discussion	Detailed requirements, sensitive topics
`workshop`	Group facilitation	Consensus building, complex problems
`observation`	Watching work being done	Process understanding, tacit knowledge
`survey`	Questionnaire	Large audiences, quantitative data
`document-analysis`	Review existing materials	Current state, regulations
`prototyping`	Building to learn	UI requirements, validation
`brainstorming`	Idea generation	Innovation, options identification
`focus-group`	Moderated discussion	User perspectives, validation
`interface-analysis`	System boundary review	Integration requirements

Participant Tracking

{
  "participants": [
    {
      "stakeholderID": "sh-001",
      "name": "Jane Smith",
      "role": "Product Owner",
      "participation": "full",
      "contributions": "Defined acceptance criteria for onboarding flow"
    },
    {
      "stakeholderID": "sh-002",
      "name": "Compliance Team",
      "role": "Subject Matter Expert",
      "participation": "partial",
      "contributions": "Clarified regulatory requirements"
    }
  ]
}

Activity Outcomes

Attribute	Type	Description
`outcomes`	array	What was learned
`decisions`	array	Decisions made
`openItems`	array	Unresolved questions
`artifactsProduced`	array	Artifacts created
`requirementsIdentified`	array	New requirements found

Analysis & Design Definition Schema

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

Core Attributes

Attribute	Type	Required	Description
`definitionID`	string	Yes	Unique identifier
`title`	string	Yes	Definition name
`definitionType`	enum	Yes	Type of definition
`description`	string	No	Detailed description
`status`	enum	No	Current status

Definition Types

Type	Description
`solution-option`	Alternative approach evaluated
`selected-design`	Chosen solution approach
`technical-design`	Detailed technical specification
`integration-design`	Interface and integration approach
`data-design`	Data structure and flow design
`ux-design`	User experience design

Solution Option Evaluation

{
  "solutionOptions": [
    {
      "optionID": "opt-001",
      "title": "Build Custom Solution",
      "description": "Develop bespoke onboarding platform",
      "feasibilityAssessment": {
        "technical": "high",
        "operational": "medium",
        "economic": "low",
        "schedule": "low"
      },
      "estimatedCost": 2500000,
      "estimatedDuration": "18 months",
      "pros": ["Full customization", "No vendor dependency"],
      "cons": ["High cost", "Long timeline", "Maintenance burden"],
      "recommendation": "not-recommended"
    },
    {
      "optionID": "opt-002",
      "title": "Configure SaaS Platform",
      "description": "Implement vendor onboarding solution",
      "feasibilityAssessment": {
        "technical": "high",
        "operational": "high",
        "economic": "high",
        "schedule": "high"
      },
      "estimatedCost": 800000,
      "estimatedDuration": "6 months",
      "pros": ["Faster delivery", "Lower cost", "Vendor support"],
      "cons": ["Limited customization", "Ongoing license cost"],
      "recommendation": "recommended"
    }
  ]
}

Impact Analysis

Attribute	Type	Description
`impactedCapabilities`	array	Capabilities affected
`impactedProcesses`	array	Processes changed
`impactedSystems`	array	Systems modified
`impactedData`	array	Data entities affected
`impactedRoles`	array	Roles changed
`changeComplexity`	enum	Overall complexity

Solution Evaluation Schema

Solution evaluation assesses implemented solutions against defined success criteria.

Core Attributes

Attribute	Type	Required	Description
`evaluationID`	string	Yes	Unique identifier
`title`	string	Yes	Evaluation name
`solutionReference`	reference	Yes	What's being evaluated
`evaluationType`	enum	Yes	Type of evaluation
`evaluationDate`	date	No	When conducted

Evaluation Types

Type	Timing	Focus
`pre-implementation`	Before delivery	Readiness assessment
`post-implementation`	After go-live	Benefits realization
`periodic`	Ongoing	Continuous improvement
`triggered`	On-demand	Incident or issue response

Performance Assessment

{
  "performanceMetrics": [
    {
      "metricID": "pm-001",
      "metricName": "Onboarding Completion Rate",
      "targetValue": 85,
      "actualValue": 92,
      "unit": "percent",
      "status": "exceeds-target",
      "measurementDate": "2025-02-01"
    },
    {
      "metricID": "pm-002",
      "metricName": "Average Onboarding Time",
      "targetValue": 10,
      "actualValue": 8,
      "unit": "minutes",
      "status": "meets-target",
      "measurementDate": "2025-02-01"
    }
  ],
  "overallAssessment": "successful",
  "benefitsRealized": 0.95,
  "lessonsLearned": [
    "Early stakeholder engagement reduced rework",
    "Prototype validation caught UX issues early"
  ],
  "recommendations": [
    "Extend solution to business banking customers",
    "Add biometric authentication option"
  ]
}

Framework Translation Layers

The Business Analysis extension includes translation mappings to major BA frameworks.

BABOK Alignment

Orthogramic Concept	BABOK Equivalent
Requirement	Requirement
Elicitation Activity	Elicitation Technique
Artifact	Deliverable
Analysis & Design Definition	Design Definition
Solution Evaluation	Solution Evaluation

Volere Alignment

Orthogramic Concept	Volere Equivalent
Functional Requirement	Functional Requirement
Non-Functional Requirement	Non-Functional Requirement
Business Requirement	Business Requirement
Constraint	Constraint

IREB Alignment

Orthogramic Concept	IREB Equivalent
Requirement	Requirement
Stakeholder Requirement	Stakeholder Requirement
Solution Requirement	Solution Requirement
Elicitation	Elicitation

Agile Alignment

Orthogramic Concept	Agile Equivalent
Requirement (must-have)	Epic /Feature
Requirement (should-have)	User Story
Acceptance Criteria	Acceptance Criteria
Artifact (user-story)	User Story

JSON Schema Definition

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "https://orthogramic.com/schemas/extensions/business-analysis.schema.json",
  "title": "Business Analysis Extension",
  "definitions": {
    "requirement": {
      "type": "object",
      "required": ["requirementID", "title", "description", "requirementType"],
      "properties": {
        "requirementID": {"type": "string"},
        "title": {"type": "string"},
        "description": {"type": "string"},
        "requirementType": {
          "type": "string",
          "enum": ["functional", "non-functional", "business", "stakeholder", "solution", "transition"]
        },
        "priority": {
          "type": "string",
          "enum": ["must-have", "should-have", "could-have", "wont-have"]
        },
        "status": {
          "type": "string",
          "enum": ["draft", "proposed", "approved", "implemented", "verified", "deferred", "rejected"]
        },
        "acceptanceCriteria": {
          "type": "array",
          "items": {"type": "string"}
        },
        "measurementCriteria": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "metric": {"type": "string"},
              "target": {"type": "string"},
              "method": {"type": "string"}
            }
          }
        },
        "assumptions": {"type": "array", "items": {"type": "string"}},
        "constraints": {"type": "array", "items": {"type": "string"}},
        "dependencies": {"type": "array", "items": {"type": "string"}},
        "riskAssessment": {
          "type": "object",
          "properties": {
            "riskLevel": {"type": "string", "enum": ["high", "medium", "low"]},
            "riskDescription": {"type": "string"},
            "mitigation": {"type": "string"}
          }
        },
        "source": {
          "type": "object",
          "properties": {
            "sourceType": {"type": "string"},
            "sourceReference": {"type": "string"},
            "elicitationActivity": {"type": "string"}
          }
        },
        "domainLinks": {
          "type": "object",
          "properties": {
            "capabilities": {"type": "array", "items": {"type": "string"}},
            "valueStreams": {"type": "array", "items": {"type": "string"}},
            "initiatives": {"type": "array", "items": {"type": "string"}},
            "stakeholders": {"type": "array", "items": {"type": "string"}},
            "information": {"type": "array", "items": {"type": "string"}}
          }
        },
        "frameworkMappings": {
          "type": "object",
          "properties": {
            "babok": {"type": "string"},
            "volere": {"type": "string"},
            "ireb": {"type": "string"},
            "agile": {"type": "string"}
          }
        }
      }
    },
    "artifact": {
      "type": "object",
      "required": ["artifactID", "title", "artifactType"],
      "properties": {
        "artifactID": {"type": "string"},
        "title": {"type": "string"},
        "artifactType": {
          "type": "string",
          "enum": ["user-story", "use-case", "process-model", "data-model", "wireframe", "prototype", "decision-table", "state-diagram", "context-diagram", "requirements-spec"]
        },
        "description": {"type": "string"},
        "status": {"type": "string", "enum": ["draft", "review", "approved", "superseded"]},
        "version": {"type": "string"},
        "author": {"type": "string"},
        "createdDate": {"type": "string", "format": "date"},
        "lastModified": {"type": "string", "format": "date"},
        "format": {"type": "string"},
        "location": {"type": "string", "format": "uri"},
        "linkedRequirements": {"type": "array", "items": {"type": "string"}},
        "reviewStatus": {"type": "string", "enum": ["pending", "in-review", "approved", "rejected"]}
      }
    },
    "elicitationActivity": {
      "type": "object",
      "required": ["activityID", "title", "elicitationType"],
      "properties": {
        "activityID": {"type": "string"},
        "title": {"type": "string"},
        "elicitationType": {
          "type": "string",
          "enum": ["interview", "workshop", "observation", "survey", "document-analysis", "prototyping", "brainstorming", "focus-group", "interface-analysis"]
        },
        "description": {"type": "string"},
        "scheduledDate": {"type": "string", "format": "date"},
        "actualDate": {"type": "string", "format": "date"},
        "duration": {"type": "string"},
        "facilitator": {"type": "string"},
        "participants": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "stakeholderID": {"type": "string"},
              "name": {"type": "string"},
              "role": {"type": "string"},
              "participation": {"type": "string"},
              "contributions": {"type": "string"}
            }
          }
        },
        "outcomes": {"type": "array", "items": {"type": "string"}},
        "decisions": {"type": "array", "items": {"type": "string"}},
        "openItems": {"type": "array", "items": {"type": "string"}},
        "artifactsProduced": {"type": "array", "items": {"type": "string"}},
        "requirementsIdentified": {"type": "array", "items": {"type": "string"}}
      }
    },
    "analysisDesignDefinition": {
      "type": "object",
      "required": ["definitionID", "title", "definitionType"],
      "properties": {
        "definitionID": {"type": "string"},
        "title": {"type": "string"},
        "definitionType": {
          "type": "string",
          "enum": ["solution-option", "selected-design", "technical-design", "integration-design", "data-design", "ux-design"]
        },
        "description": {"type": "string"},
        "status": {"type": "string", "enum": ["draft", "proposed", "approved", "implemented"]},
        "linkedRequirements": {"type": "array", "items": {"type": "string"}},
        "solutionOptions": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "optionID": {"type": "string"},
              "title": {"type": "string"},
              "description": {"type": "string"},
              "feasibilityAssessment": {"type": "object"},
              "estimatedCost": {"type": "number"},
              "estimatedDuration": {"type": "string"},
              "pros": {"type": "array", "items": {"type": "string"}},
              "cons": {"type": "array", "items": {"type": "string"}},
              "recommendation": {"type": "string"}
            }
          }
        },
        "impactedCapabilities": {"type": "array", "items": {"type": "string"}},
        "impactedProcesses": {"type": "array", "items": {"type": "string"}},
        "impactedSystems": {"type": "array", "items": {"type": "string"}}
      }
    },
    "solutionEvaluation": {
      "type": "object",
      "required": ["evaluationID", "title", "solutionReference", "evaluationType"],
      "properties": {
        "evaluationID": {"type": "string"},
        "title": {"type": "string"},
        "solutionReference": {"type": "string"},
        "evaluationType": {
          "type": "string",
          "enum": ["pre-implementation", "post-implementation", "periodic", "triggered"]
        },
        "evaluationDate": {"type": "string", "format": "date"},
        "performanceMetrics": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "metricID": {"type": "string"},
              "metricName": {"type": "string"},
              "targetValue": {"type": "number"},
              "actualValue": {"type": "number"},
              "unit": {"type": "string"},
              "status": {"type": "string"}
            }
          }
        },
        "overallAssessment": {"type": "string", "enum": ["successful", "partial", "unsuccessful"]},
        "benefitsRealized": {"type": "number", "minimum": 0, "maximum": 1},
        "lessonsLearned": {"type": "array", "items": {"type": "string"}},
        "recommendations": {"type": "array", "items": {"type": "string"}}
      }
    }
  }
}

Complete Example

Mobile Banking Onboarding Requirements

{
  "requirement": {
    "requirementID": "REQ-OB-001",
    "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",
    "requirementType": "functional",
    "priority": "must-have",
    "status": "approved",
    "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": [
      {
        "metric": "Load Time",
        "target": "< 2 seconds",
        "method": "Performance monitoring"
      },
      {
        "metric": "User Satisfaction",
        "target": "> 4.0/5.0",
        "method": "In-app rating"
      }
    ],
    "assumptions": [
      "User has valid authentication token",
      "Transaction data available in real-time"
    ],
    "constraints": [
      "Must comply with PCI-DSS for transaction display",
      "Must support offline mode with cached data"
    ],
    "riskAssessment": {
      "riskLevel": "medium",
      "riskDescription": "Performance degradation with large transaction volumes",
      "mitigation": "Implement pagination and caching"
    },
    "source": {
      "sourceType": "workshop",
      "sourceReference": "WS-2024-11-15",
      "elicitationActivity": "ea-001"
    },
    "domainLinks": {
      "capabilities": ["cap-mobile-banking", "cap-transaction-inquiry"],
      "valueStreams": ["vs-digital-banking"],
      "initiatives": ["init-mobile-app-enhancement"],
      "stakeholders": ["sh-retail-customers", "sh-mobile-team"],
      "information": ["info-transaction-data", "info-account-data"]
    },
    "frameworkMappings": {
      "babok": "Functional Requirement",
      "volere": "Functional Requirement",
      "ireb": "User Requirement",
      "agile": "User Story"
    }
  },
  "elicitationActivity": {
    "activityID": "ea-001",
    "title": "Mobile Banking Requirements Workshop",
    "elicitationType": "workshop",
    "description": "Full-day workshop to gather requirements for mobile app enhancement",
    "scheduledDate": "2024-11-15",
    "actualDate": "2024-11-15",
    "duration": "6 hours",
    "facilitator": "Business Analysis Lead",
    "participants": [
      {
        "stakeholderID": "sh-retail-customers",
        "name": "Customer Focus Group",
        "role": "End Users",
        "participation": "partial",
        "contributions": "Transaction view preferences, pain points"
      },
      {
        "stakeholderID": "sh-mobile-team",
        "name": "Mobile Development Team",
        "role": "Technical SME",
        "participation": "full",
        "contributions": "Technical constraints, API capabilities"
      }
    ],
    "outcomes": [
      "Identified 15 high-priority requirements",
      "Validated quick transaction view as top priority",
      "Confirmed technical feasibility"
    ],
    "requirementsIdentified": ["REQ-OB-001", "REQ-OB-002", "REQ-OB-003"]
  },
  "analysisDesignDefinition": {
    "definitionID": "ADD-001",
    "title": "Transaction View Implementation Design",
    "definitionType": "selected-design",
    "description": "Approved design for implementing quick transaction view",
    "status": "approved",
    "linkedRequirements": ["REQ-OB-001"],
    "impactedCapabilities": ["cap-mobile-banking"],
    "impactedSystems": ["sys-mobile-app", "sys-transaction-api"]
  }
}

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 — Enable translation 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 requirements in the information domain property 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​

Requirements Schema​

Core Attributes​

Extended Attributes​

Requirement Types​

Priority Levels​

Domain Linkages​

Requirement Artifacts Schema​

Core Attributes​

Artifact Types​

Artifact Attributes​

Elicitation Activities Schema​

Core Attributes​

Elicitation Types​

Participant Tracking​

Activity Outcomes​

Analysis & Design Definition Schema​

Core Attributes​

Definition Types​

Solution Option Evaluation​

Impact Analysis​

Solution Evaluation Schema​

Core Attributes​

Evaluation Types​

Performance Assessment​

Framework Translation Layers​

BABOK Alignment​

Volere Alignment​

IREB Alignment​

Agile Alignment​

JSON Schema Definition​

Complete Example​

Mobile Banking Onboarding Requirements​

Usage Guidelines​

Best Practices​

Integration with Strategic Response Model​

Related Documentation​

Overview

What is the Business Analysis Extension?

Why a Business Analysis Extension?

Extension Components

Requirements Schema

Core Attributes

Extended Attributes

Requirement Types

Priority Levels

Domain Linkages

Requirement Artifacts Schema

Core Attributes

Artifact Types

Artifact Attributes

Elicitation Activities Schema

Core Attributes

Elicitation Types

Participant Tracking

Activity Outcomes

Analysis & Design Definition Schema

Core Attributes

Definition Types

Solution Option Evaluation

Impact Analysis

Solution Evaluation Schema

Core Attributes

Evaluation Types

Performance Assessment

Framework Translation Layers

BABOK Alignment

Volere Alignment

IREB Alignment

Agile Alignment

JSON Schema Definition

Complete Example

Mobile Banking Onboarding Requirements

Usage Guidelines

Best Practices

Integration with Strategic Response Model

Related Documentation