@prefix owl: . @prefix xsd: . @prefix rdfs: . @prefix skos: . @prefix dcterms: . @prefix vann: . @prefix arch: . @prefix ad: . @prefix am: . @prefix easvc: . @prefix easvcrd: . @prefix : . ## ═══════════════════════════════════════════════════════════════════════════════ ## EA-as-a-Service Worked Example — Acme Corp EA Function ## ## Scenario: A mid-size financial services company (Acme Corp) has a 4-person ## EA team that operates as an internal consultancy. This example models their ## service catalog, three engagements at different lifecycle stages, satisfaction ## tracking, capability portfolio, and maturity assessment. ## ## Extensions used: easvc:ea-service, ad:arch-decision (for outcome tracing) ## No ML/AI dependencies — this is a pure EA service management example. ## ═══════════════════════════════════════════════════════════════════════════════ a owl:Ontology ; owl:imports ; vann:preferredNamespaceUri "https://model.example.com/acme-ea#" ; vann:preferredNamespacePrefix "acme" ; dcterms:title "Acme Corp EA-as-a-Service — Worked Example"@en ; dcterms:description '''Worked example demonstrating the EA-as-a-Service extension. Models a 4-person EA team operating as an internal consultancy at a mid-size financial services company. Shows service catalog, engagements, outcomes, satisfaction tracking, capability portfolio, and maturity assessment.'''@en ; dcterms:created "2026-05-03"^^xsd:date ; dcterms:modified "2026-05-03"^^xsd:date ; dcterms:creator "Kalin Maldzhanski"^^xsd:string . ## ═══════════════════════════════════════════════════════════════════════════════ ## STAKEHOLDERS — The EA Team and Their Clients ## ═══════════════════════════════════════════════════════════════════════════════ :ChiefArchitect a arch:Stakeholder ; skos:prefLabel "Maria Chen — Chief Architect"@en ; skos:definition "Head of the EA function. Responsible for EA strategy, governance, and stakeholder relationships."@en . :SeniorArchitectDomain a arch:Stakeholder ; skos:prefLabel "James Park — Senior Domain Architect"@en ; skos:definition "Domain architect covering retail banking and payments. 8 years experience."@en . :SeniorArchitectPlatform a arch:Stakeholder ; skos:prefLabel "Aisha Okafor — Senior Platform Architect"@en ; skos:definition "Platform architect covering cloud infrastructure and integration. TOGAF certified."@en . :JuniorArchitect a arch:Stakeholder ; skos:prefLabel "Tom Eriksson — Junior Architect"@en ; skos:definition "Junior architect, 2 years in role. Building skills in ArchiMate and portfolio assessment."@en . ## Stakeholders who consume EA services :VPRetailBanking a arch:Stakeholder ; skos:prefLabel "Sarah Williams — VP Retail Banking"@en . :HeadOfPayments a arch:Stakeholder ; skos:prefLabel "David Kim — Head of Payments"@en . :CTOOffice a arch:Stakeholder ; skos:prefLabel "CTO Office"@en . :ComplianceDirector a arch:Stakeholder ; skos:prefLabel "Elena Rossi — Compliance Director"@en . :ProductOwnerMobile a arch:Stakeholder ; skos:prefLabel "Raj Patel — Product Owner, Mobile Banking"@en . ## ═══════════════════════════════════════════════════════════════════════════════ ## EA CAPABILITIES — What the Team Can Do ## ═══════════════════════════════════════════════════════════════════════════════ :CapArchimateModeling a easvc:EACapability ; skos:prefLabel "ArchiMate Modeling"@en ; easvc:capabilityDescription "Enterprise architecture modeling using ArchiMate 3.2 notation across all layers."@en ; easvc:capabilityLevel "advanced" . :CapTOGAFADM a easvc:EACapability ; skos:prefLabel "TOGAF ADM"@en ; easvc:capabilityDescription "Architecture development using TOGAF Architecture Development Method."@en ; easvc:capabilityLevel "advanced" . :CapPortfolioAnalysis a easvc:EACapability ; skos:prefLabel "Portfolio Analysis"@en ; easvc:capabilityDescription "Application portfolio rationalization using TIME framework and fitness scoring."@en ; easvc:capabilityLevel "intermediate" . :CapSPARQLQuerying a easvc:EACapability ; skos:prefLabel "SPARQL Querying"@en ; easvc:capabilityDescription "Querying the architecture knowledge graph using SPARQL for impact analysis and reporting."@en ; easvc:capabilityLevel "intermediate" . :CapSHACLValidation a easvc:EACapability ; skos:prefLabel "SHACL Validation"@en ; easvc:capabilityDescription "Defining and running SHACL shapes for automated architecture governance."@en ; easvc:capabilityLevel "intermediate" . :CapStakeholderFacilitation a easvc:EACapability ; skos:prefLabel "Stakeholder Facilitation"@en ; easvc:capabilityDescription "Facilitating architecture workshops, review boards, and decision sessions with business stakeholders."@en ; easvc:capabilityLevel "advanced" . :CapCloudArchitecture a easvc:EACapability ; skos:prefLabel "Cloud Architecture"@en ; easvc:capabilityDescription "Designing cloud-native architectures on AWS and Azure. FinOps cost optimization."@en ; easvc:capabilityLevel "advanced" . :CapFinancialModeling a easvc:EACapability ; skos:prefLabel "Financial Modeling"@en ; easvc:capabilityDescription "TCO modeling, cost-benefit analysis, and investment case development for architecture decisions."@en ; easvc:capabilityLevel "beginner" . ## ═══════════════════════════════════════════════════════════════════════════════ ## SERVICE CATALOG — What the EA Function Offers ## ═══════════════════════════════════════════════════════════════════════════════ :AcmeEAServiceCatalog a easvc:ServiceCatalog ; skos:prefLabel "Acme Corp EA Service Catalog 2026"@en ; skos:definition '''The complete catalog of architecture services offered by the Acme Corp EA function to business and IT stakeholders. Updated quarterly.'''@en ; easvc:offersService :ArchReviewService, :PortfolioAssessmentService, :ImpactAnalysisService, :TargetStateService, :TechRadarService, :OnboardingService ; easvc:hasEACapability :CapArchimateModeling, :CapTOGAFADM, :CapPortfolioAnalysis, :CapSPARQLQuerying, :CapSHACLValidation, :CapStakeholderFacilitation, :CapCloudArchitecture, :CapFinancialModeling ; easvc:hasMaturityAssessment :MaturityQ1_2026 . ## ─── Architecture Review Service ──────────────────────────────────────────── :ArchReviewService a easvc:EAService ; skos:prefLabel "Architecture Review"@en ; skos:definition '''Review of a proposed architecture against enterprise standards, principles, and quality attributes. Produces a review report with findings, conditions, and recommendations.'''@en ; easvc:serviceType easvcrd:ArchitectureReview ; easvc:requiredCapability :CapArchimateModeling, :CapStakeholderFacilitation ; easvc:hasServiceLevelExpectation [ a easvc:ServiceLevelExpectation ; easvc:expectedTurnaroundDays 5 ; easvc:expectedScope "Review of proposed architecture. Deliverable: review report with findings and recommendations."@en ; ] . ## ─── Portfolio Assessment Service ─────────────────────────────────────────── :PortfolioAssessmentService a easvc:EAService ; skos:prefLabel "Portfolio Assessment"@en ; skos:definition '''Application portfolio rationalization for a business domain. TIME classification, fitness scoring, and modernization recommendations.'''@en ; easvc:serviceType easvcrd:PortfolioAssessment ; easvc:requiredCapability :CapPortfolioAnalysis, :CapSPARQLQuerying, :CapArchimateModeling ; easvc:hasServiceLevelExpectation [ a easvc:ServiceLevelExpectation ; easvc:expectedTurnaroundDays 20 ; easvc:expectedScope "TIME assessment of application portfolio for a business domain. Deliverable: portfolio heatmap, rationalization recommendations."@en ; ] . ## ─── Impact Analysis Service ──────────────────────────────────────────────── :ImpactAnalysisService a easvc:EAService ; skos:prefLabel "Impact Analysis"@en ; skos:definition '''Analysis of the impact of a proposed change on the architecture landscape — affected systems, dependencies, risks, and downstream effects.'''@en ; easvc:serviceType easvcrd:ImpactAnalysis ; easvc:requiredCapability :CapSPARQLQuerying, :CapArchimateModeling ; easvc:hasServiceLevelExpectation [ a easvc:ServiceLevelExpectation ; easvc:expectedTurnaroundDays 3 ; easvc:expectedScope "Impact analysis for a proposed change. Deliverable: impact report with affected systems and risk assessment."@en ; ] . ## ─── Target State Design Service ──────────────────────────────────────────── :TargetStateService a easvc:EAService ; skos:prefLabel "Target State Design"@en ; skos:definition '''Design of future-state architecture for a domain, capability, or platform. Includes current-state analysis, gap analysis, and transition roadmap.'''@en ; easvc:serviceType easvcrd:TargetStateDesign ; easvc:requiredCapability :CapArchimateModeling, :CapTOGAFADM, :CapCloudArchitecture, :CapStakeholderFacilitation ; easvc:hasServiceLevelExpectation [ a easvc:ServiceLevelExpectation ; easvc:expectedTurnaroundDays 30 ; easvc:expectedScope "Target-state architecture with gap analysis and transition roadmap. Deliverable: architecture definition document."@en ; ] . ## ─── Technology Radar Service ─────────────────────────────────────────────── :TechRadarService a easvc:EAService ; skos:prefLabel "Technology Radar"@en ; skos:definition '''Quarterly assessment and communication of technology trends, recommendations, and adoption guidance for the organization.'''@en ; easvc:serviceType easvcrd:TechnologyRadar ; easvc:requiredCapability :CapCloudArchitecture, :CapArchimateModeling ; easvc:hasServiceLevelExpectation [ a easvc:ServiceLevelExpectation ; easvc:expectedTurnaroundDays 15 ; easvc:expectedScope "Technology radar publication with Adopt/Trial/Assess/Hold recommendations."@en ; ] . ## ─── Onboarding Consultation Service ──────────────────────────────────────── :OnboardingService a easvc:EAService ; skos:prefLabel "Onboarding Consultation"@en ; skos:definition '''Consultative engagement for new projects or initiatives — architecture context, standards orientation, and integration guidance.'''@en ; easvc:serviceType easvcrd:OnboardingConsultation ; easvc:requiredCapability :CapStakeholderFacilitation, :CapArchimateModeling ; easvc:hasServiceLevelExpectation [ a easvc:ServiceLevelExpectation ; easvc:expectedTurnaroundDays 2 ; easvc:expectedScope "1-hour consultation session. Deliverable: summary email with relevant standards and contacts."@en ; ] . ## ═══════════════════════════════════════════════════════════════════════════════ ## ARCHITECTURE ELEMENTS — Systems Being Served ## (These would normally come from the ArchiMate model; simplified here) ## ═══════════════════════════════════════════════════════════════════════════════ :PaymentPlatform a am:ApplicationComponent ; skos:prefLabel "Payment Platform"@en ; skos:definition "Core payment processing platform handling card transactions, direct debits, and SEPA transfers."@en . :MobileBankingApp a am:ApplicationComponent ; skos:prefLabel "Mobile Banking Application"@en ; skos:definition "Customer-facing mobile banking application (iOS and Android)."@en . :RetailBankingDomain a am:Capability ; skos:prefLabel "Retail Banking"@en ; skos:definition "Business capability covering all retail banking products and services."@en . :CustomerOnboarding a am:Capability ; skos:prefLabel "Customer Onboarding"@en ; skos:definition "Business capability for onboarding new retail banking customers."@en . ## ═══════════════════════════════════════════════════════════════════════════════ ## ENGAGEMENT 1 — Completed: Payment Platform Target State Design ## Status: Closed, satisfaction assessed ## ═══════════════════════════════════════════════════════════════════════════════ :Req-PaymentTargetState a easvc:ServiceRequest ; skos:prefLabel "Request: Payment Platform Target State Design"@en ; easvc:requestedBy :HeadOfPayments ; easvc:requestDate "2026-01-15"^^xsd:date ; easvc:requestForService :TargetStateService ; easvc:requestDescription '''Need a target-state architecture for the payment platform. Current platform is on-premises, monolithic, and struggling with PSD2 compliance. Want to understand options for cloud migration and API-first redesign.'''@en ; easvc:resultsInEngagement :Eng-PaymentTargetState . :Eng-PaymentTargetState a easvc:ServiceEngagement ; skos:prefLabel "Payment Platform Target State Design"@en ; easvc:engagementStatus easvcrd:Closed ; easvc:assignedArchitect :SeniorArchitectDomain ; easvc:engagementFor :PaymentPlatform ; easvc:engagementStartDate "2026-01-20"^^xsd:date ; easvc:engagementEndDate "2026-02-14"^^xsd:date ; easvc:hasOutcome :Outcome-PaymentTargetState . :Outcome-PaymentTargetState a easvc:ServiceOutcome ; easvc:producedDeliverable :PaymentTargetStateModel ; easvc:influencedDecision :ADR-PaymentMigration ; easvc:outcomeDescription '''Produced target-state architecture for cloud-native payment platform on AWS. Identified 4 migration phases over 18 months. Architecture review board approved the target state. Directly influenced ADR-042: Migrate Payment Platform to AWS EKS.'''@en ; easvc:hasSatisfactionAssessment :Sat-PaymentTargetState . :PaymentTargetStateModel a arch:Model ; skos:prefLabel "Payment Platform Target State Architecture v1.0"@en . :ADR-PaymentMigration a ad:Decision ; skos:prefLabel "ADR-042: Migrate Payment Platform to AWS EKS"@en . :Sat-PaymentTargetState a easvc:SatisfactionAssessment ; easvc:hasSatisfactionScore 5 ; easvc:satisfactionFeedback '''Excellent work. The target-state architecture was clear, well-justified, and the phased migration plan was realistic. The architecture review board approved it without conditions. James understood our business constraints perfectly.'''@en ; easvc:satisfactionDate "2026-02-20"^^xsd:date . ## ═══════════════════════════════════════════════════════════════════════════════ ## ENGAGEMENT 2 — In Progress: Retail Banking Portfolio Assessment ## Status: In Progress ## ═══════════════════════════════════════════════════════════════════════════════ :Req-RetailPortfolio a easvc:ServiceRequest ; skos:prefLabel "Request: Retail Banking Portfolio Assessment"@en ; easvc:requestedBy :VPRetailBanking ; easvc:requestDate "2026-03-01"^^xsd:date ; easvc:requestForService :PortfolioAssessmentService ; easvc:requestDescription '''We have 38 applications in the retail banking domain. Many are legacy, some are redundant. Need a TIME assessment to prioritize modernization investment for the 2027 budget cycle.'''@en ; easvc:resultsInEngagement :Eng-RetailPortfolio . :Eng-RetailPortfolio a easvc:ServiceEngagement ; skos:prefLabel "Retail Banking Portfolio Assessment"@en ; easvc:engagementStatus easvcrd:InProgress ; easvc:assignedArchitect :JuniorArchitect ; easvc:engagementFor :RetailBankingDomain ; easvc:engagementStartDate "2026-03-05"^^xsd:date . ## ═══════════════════════════════════════════════════════════════════════════════ ## ENGAGEMENT 3 — Completed: Mobile Banking Architecture Review ## Status: Closed, mixed satisfaction ## ═══════════════════════════════════════════════════════════════════════════════ :Req-MobileReview a easvc:ServiceRequest ; skos:prefLabel "Request: Mobile Banking Architecture Review"@en ; easvc:requestedBy :ProductOwnerMobile ; easvc:requestDate "2026-02-10"^^xsd:date ; easvc:requestForService :ArchReviewService ; easvc:requestDescription '''We are proposing a new microservices architecture for the mobile banking backend. Need an architecture review before we start implementation.'''@en ; easvc:resultsInEngagement :Eng-MobileReview . :Eng-MobileReview a easvc:ServiceEngagement ; skos:prefLabel "Mobile Banking Architecture Review"@en ; easvc:engagementStatus easvcrd:Closed ; easvc:assignedArchitect :SeniorArchitectPlatform ; easvc:engagementFor :MobileBankingApp ; easvc:engagementStartDate "2026-02-12"^^xsd:date ; easvc:engagementEndDate "2026-02-18"^^xsd:date ; easvc:hasOutcome :Outcome-MobileReview . :Outcome-MobileReview a easvc:ServiceOutcome ; easvc:producedDeliverable :MobileReviewReport ; easvc:outcomeDescription '''Reviewed proposed microservices architecture. Found 2 critical issues: (1) no API gateway pattern — direct client-to-service calls, (2) shared database anti-pattern between 3 services. Recommended API gateway and database-per-service. Review board approved with conditions.'''@en ; easvc:hasSatisfactionAssessment :Sat-MobileReview . :MobileReviewReport a arch:Model ; skos:prefLabel "Mobile Banking Architecture Review Report"@en . :Sat-MobileReview a easvc:SatisfactionAssessment ; easvc:hasSatisfactionScore 3 ; easvc:satisfactionFeedback '''The review findings were valid and helpful. However, the turnaround took 6 days instead of the expected 5, and the report lacked specific implementation guidance for the API gateway recommendation. We had to schedule a follow-up session.'''@en ; easvc:satisfactionDate "2026-02-25"^^xsd:date . ## ═══════════════════════════════════════════════════════════════════════════════ ## ENGAGEMENT 4 — Declined: Compliance Validation Request ## Status: Declined (capability gap) ## ═══════════════════════════════════════════════════════════════════════════════ :Req-ComplianceValidation a easvc:ServiceRequest ; skos:prefLabel "Request: PSD2 Compliance Architecture Validation"@en ; easvc:requestedBy :ComplianceDirector ; easvc:requestDate "2026-03-10"^^xsd:date ; easvc:requestForService :ArchReviewService ; easvc:requestDescription '''Need validation that our payment architecture meets PSD2 Strong Customer Authentication requirements. Regulatory audit in Q3.'''@en ; easvc:declineRationale '''Declined — the EA team currently lacks deep PSD2/SCA regulatory expertise. Recommended engaging external specialist consultancy (Deloitte or PwC) for this specific validation. EA team can support with architecture documentation and system dependency mapping as input to the external review.'''@en . ## ═══════════════════════════════════════════════════════════════════════════════ ## ENGAGEMENT 5 — Quick: Onboarding Consultation for New Project ## Status: Closed ## ═══════════════════════════════════════════════════════════════════════════════ :Req-OnboardingNewProject a easvc:ServiceRequest ; skos:prefLabel "Request: Onboarding for Customer Onboarding Redesign Project"@en ; easvc:requestedBy :ProductOwnerMobile ; easvc:requestDate "2026-04-01"^^xsd:date ; easvc:requestForService :OnboardingService ; easvc:requestDescription "New project starting to redesign customer onboarding flow. Need architecture context and standards orientation."@en ; easvc:resultsInEngagement :Eng-OnboardingNewProject . :Eng-OnboardingNewProject a easvc:ServiceEngagement ; skos:prefLabel "Onboarding: Customer Onboarding Redesign"@en ; easvc:engagementStatus easvcrd:Closed ; easvc:assignedArchitect :ChiefArchitect ; easvc:engagementFor :CustomerOnboarding ; easvc:engagementStartDate "2026-04-02"^^xsd:date ; easvc:engagementEndDate "2026-04-02"^^xsd:date ; easvc:hasOutcome :Outcome-Onboarding . :Outcome-Onboarding a easvc:ServiceOutcome ; easvc:outcomeDescription '''1-hour consultation covering: existing customer onboarding architecture, relevant enterprise standards (API-first, event-driven), integration points with KYC and identity systems, and recommended architecture patterns. Follow-up architecture review scheduled for sprint 3.'''@en ; easvc:hasSatisfactionAssessment :Sat-Onboarding . :Sat-Onboarding a easvc:SatisfactionAssessment ; easvc:hasSatisfactionScore 4 ; easvc:satisfactionFeedback "Very useful session. Got the context we needed to start. Maria was well-prepared and knew our domain."@en ; easvc:satisfactionDate "2026-04-03"^^xsd:date . ## ═══════════════════════════════════════════════════════════════════════════════ ## MATURITY ASSESSMENT — Where the EA Function Stands ## ═══════════════════════════════════════════════════════════════════════════════ :MaturityQ1_2026 a easvc:EAMaturityAssessment ; skos:prefLabel "Acme EA Maturity Assessment — Q1 2026"@en ; easvc:maturityLevel easvcrd:Level3_Defined ; easvc:maturityAssessmentDate "2026-03-15"^^xsd:date ; easvc:maturityAssessedBy :ChiefArchitect ; easvc:maturityFindings '''Level 3 (Defined) — Standardized processes in place for architecture review and target-state design. Service catalog published and communicated to stakeholders. SHACL validation running in CI/CD for ArchiMate models. Strengths: - Strong stakeholder relationships in payments and retail banking - Architecture review process well-established (12 reviews in 2025) - Knowledge graph approach adopted — SPARQL queries replacing manual reporting Gaps to address for Level 4 (Managed): - Satisfaction tracking not yet systematic (implementing this quarter) - Financial modeling capability is weak — cannot produce TCO or ROI analysis - Portfolio assessment capability limited to senior staff - No formal demand management — requests come via email and Slack Improvement plan: - Q2: Implement satisfaction tracking for all engagements - Q2: Financial modeling training for 2 architects - Q3: Formalize demand management with service request workflow - Q4: Reassess maturity — target Level 4 by end of 2026'''@en .