WhoNot selectedWhyNot selectedWhereArchitecture & Platform DecisionsCycleCapability Productization CycleDesign Line

Station

Architecture & Platform Decisions

Use requirements and constraints to select the implementation style, architecture pattern, and enabling platform capabilities.

Architecture choices should follow from evidence about business impact, locations, trust boundaries, capacity, latency, data ownership, consistency, operability, security, privacy, governance, and cost.

Method map

Navigate the method

Select a station, cycle, or stakeholder perspective to explore the method.

StrategicGovernanceConsumerTechnicalUser ExperienceUser ExperienceMarket InsightsMarket InsightsBusiness GoalsBusiness GoalsCompetitive AnalysisCompetitive AnalysisEcosystem VisionEcosystem VisionScalable InfrastructureScalable InfrastructureLegal and ComplianceLegal and ComplianceSecurity and PrivacySecurity and PrivacyDesign StandardsDesign StandardsVendor ManagementVendor ManagementContract DesignContract DesignDevelopmentDevelopmentCI/CDCI/CDTest AutomationTest AutomationRelease ManagementRelease ManagementService AgreementsService AgreementsConsumer AdoptionConsumer AdoptionPromotionPromotionPartner IntegrationPartner IntegrationAPI MindsetAPI MindsetRoles and ResponsibilitiesRoles and ResponsibilitiesUpskillingUpskillingOperating GuidelinesOperating GuidelinesPortfolio ManagementPortfolio ManagementBudget and Resource ManagementBudget and Resource ManagementStrategy1Capability StrategyConsumer Requirements & Onboarding2Consumer Requirements &OnboardingArchitecture & Platform Decisions3Architecture & PlatformDecisionsSolution & Interface Design4Solution & InterfaceDesignDelivery & Operations5Delivery & OperationsQuality & Readiness Assurance6Quality & ReadinessAssurancePublishing & Enablement7Publishing & EnablementMonitoring & Improvement8Monitoring & ImprovementBusiness Opportunities LinePlatform Architecture LineDesign LineDelivery LinePublishing and Adoption LineOperating Model Line

Outcomes

  • A justified architecture choice
  • Documented risks, locations, capacity, security, privacy, and operability constraints
  • Clear rationale for API, event, file, stream, data product, direct integration, or hybrid implementation style

Journey criteria

Entry criteria

  • Capability opportunity is identified and documented.
  • The capability addresses a clear business need and is reusable by its intended consumers.
  • The selected interface provides an appropriate abstraction for consumers.
  • The capability value proposition has been validated with business and consumer stakeholders.
  • Consumer segments are identified.
  • A high-level implementation roadmap is defined.

Exit criteria

  • The capability addresses a clear business need and is reusable by its intended consumers.
  • The selected interface provides an appropriate abstraction for consumers.
  • The capability value proposition has been validated with business and consumer stakeholders.
  • Consumer segments are identified.
  • A high-level implementation roadmap is defined.

People to involve

Related resources

canvasBusiness Impact CanvasIdentify business, availability, security, data, compliance, and operational risks that should shape architecture and platform decisions.canvasLocation CanvasMap consumer, producer, system, data, network, regulatory, and trust-boundary locations to ensure compliance and performance across regions.canvasCapacity CanvasPlan capacity for current and future demand, including volumes, peaks, latency, availability, scaling, caching, and rate limits for the selected capability and implementation style.

Metro lines

Design Line

Focuses on solution and interface design principles that can be used across APIs, integrations, automations, data products, and other implementation styles.