{ "source": { "repository": "https://github.com/APIOpsCycles/apiops-cycles-method-data", "commit": "4e3a61e4c0427a5b86a79a362e5eed172409434c" }, "locales": [ "en", "fi", "fr", "de", "pt" ], "defaultLocale": "en", "generatedAt": "2026-07-23T20:09:46.873Z", "translations": { "en": { "routeProfiles": [ { "id": "api-architect", "stakeholderId": "api-architect", "title": "API Architect", "summary": "Owns API architecture, design principles, and interface contract quality." }, { "id": "api-consumer-specialist", "stakeholderId": "api-consumer-specialist", "title": "API Consumer Representative", "summary": "Represents the needs of developers, integrators, or other API consumers who use the API directly." }, { "id": "api-designer", "stakeholderId": "api-designer", "title": "API Designer", "summary": "Shapes the interface contract, interaction model, consistency, and usability of the exposed capabilities." }, { "id": "governance-specialist", "stakeholderId": "governance-specialist", "title": "API Governance Owner", "summary": "Represents review, audit, and organization-wide governance practices for API quality and conformity." }, { "id": "api-product-owner", "stakeholderId": "api-product-owner", "title": "API Product Owner", "summary": "Drives the API opportunity, prioritization, and product-level decisions across the lifecycle." }, { "id": "automation-engineer", "stakeholderId": "automation-engineer", "title": "Automation Engineer", "summary": "Implements, tests, integrates, and maintains automation solutions and supporting workflows." }, { "id": "automation-owner", "stakeholderId": "automation-owner", "title": "Automation Owner", "summary": "Owns automation goals, business value, priorities, controls, and lifecycle outcomes." }, { "id": "business-owner", "stakeholderId": "business-owner", "title": "Business Owner", "summary": "Represents business goals, funding, and expected outcomes for the capability, API, or automation initiative." }, { "id": "capability-owner", "stakeholderId": "capability-owner", "title": "Capability Owner", "summary": "Owns the capability vision, value, priorities, lifecycle, and reuse across consumers." }, { "id": "compliance-specialist", "stakeholderId": "compliance-specialist", "title": "Compliance and Legal Specialist", "summary": "Clarifies legal, privacy, regulatory, and contractual requirements that affect the capability, API, interface, or automation." }, { "id": "customer-specialist", "stakeholderId": "customer-specialist", "title": "Customer or Partner Representative", "summary": "Contributes the business customer or partner perspective for the journey, value, and collaboration model." }, { "id": "api-engineer", "stakeholderId": "api-engineer", "title": "Delivery Engineer", "summary": "Owns implementation, automation, testing, and release flow concerns needed to deliver the capability, API, or automation reliably." }, { "id": "api-devrel-specialist", "stakeholderId": "api-devrel-specialist", "title": "Documentation and DevRel Owner", "summary": "Owns onboarding content, developer communication, and documentation quality for API consumers." }, { "id": "domain-specialist", "stakeholderId": "domain-specialist", "title": "Domain Expert", "summary": "Brings deep knowledge of the business domain, concepts, rules, and constraints the capability or interface must reflect." }, { "id": "integration-architect", "stakeholderId": "integration-architect", "title": "Integration Architect", "summary": "Designs integration approaches and implementation styles that connect the capability or API with other systems." }, { "id": "partner-specialist", "stakeholderId": "partner-specialist", "title": "Partner or Vendor Manager", "summary": "Coordinates external partner, supplier, or vendor relationships that influence capability or API strategy and delivery." }, { "id": "platform-architect", "stakeholderId": "platform-architect", "title": "Platform Architect", "summary": "Guides platform, integration, scalability, and architecture decisions that shape how the capability or API is built and operated." }, { "id": "platform-owner", "stakeholderId": "platform-owner", "title": "Platform Owner", "summary": "Owns platform capabilities, roadmap, operational model, and service expectations." }, { "id": "process-owner", "stakeholderId": "process-owner", "title": "Process Owner", "summary": "Owns the business process being automated, including objectives, rules, outcomes, and improvement priorities." }, { "id": "security-specialist", "stakeholderId": "security-specialist", "title": "Security Specialist", "summary": "Ensures security risks, controls, and trust boundaries are addressed throughout the API lifecycle." }, { "id": "operations-specialist", "stakeholderId": "operations-specialist", "title": "Support and Operations Owner", "summary": "Represents runtime support, incident handling, observability, and operational readiness for the capability, API, or automation." } ], "lines": [ { "id": "business-opportunities-line", "slug": "business-opportunities-line", "title": "Business Opportunities Line", "description": "Focuses on identifying and shaping business opportunities as reusable digital capabilities.", "icon": "", "color": "#26b309", "stations": [ "monitoring-and-improving", "api-product-strategy", "user-experience", "market-insights", "business-goals", "competitive-analysis", "ecosystem-vision" ] }, { "id": "platform-architecture-line", "slug": "platform-architecture-line", "title": "Platform Architecture Line", "description": "Covers architecture and platform decisions for reusable capabilities across implementation styles.", "icon": "", "color": "#933469", "stations": [ "api-product-strategy", "api-consumer-experience", "api-platform-architecture", "scalable-infrastructure", "legal-and-compliance", "security-and-privacy", "design-standards", "vendor-management" ] }, { "id": "api-design-line", "slug": "api-design-line", "title": "Design Line", "description": "Focuses on solution and interface design principles that can be used across APIs, integrations, automations, data products, and other implementation styles.", "icon": "", "color": "#db9b0c", "stations": [ "api-platform-architecture", "api-design", "api-delivery", "api-audit" ] }, { "id": "delivery-line", "slug": "delivery-line", "title": "Delivery Line", "description": "Covers delivery and operational practices for reusable capabilities across implementation styles.", "icon": "", "color": "#db9b0c", "stations": [ "api-delivery", "contract-design", "development", "ci-cd", "test-automation", "release-management" ] }, { "id": "publishing-and-adoption-line", "slug": "publishing-and-adoption-line", "title": "Publishing and Adoption Line", "description": "Focuses on publishing reusable capabilities and enabling adoption by consumers.", "icon": "", "color": "#17C6E9", "stations": [ "api-audit", "api-publishing", "monitoring-and-improving", "service-agreements", "api-consumer-adoption", "api-promotion", "partner-integration" ] }, { "id": "operating-model-line", "slug": "operating-model-line", "title": "Operating Model Line", "description": "Covers the operating model for reusable capability management and governance.", "icon": "", "color": "#1a3987", "stations": [ "api-product-strategy", "api-mindset", "roles-and-responsibilities", "upskilling", "operating-guidelines", "portfolio-management", "budget-and-resource-management" ] } ], "cycles": [ { "id": "capability-productization-cycle", "slug": "capability-productization-cycle", "title": "Capability Productization Cycle", "description": "A cycle for turning business capabilities into reusable digital capabilities before selecting the implementation style.", "stations": [ { "id": "api-product-strategy", "title": "Capability Strategy", "description": "Frame the business need as a reusable capability with clear value, consumers, ownership, and business goals before selecting the implementation style." }, { "id": "api-consumer-experience", "title": "Consumer Requirements & Onboarding", "description": "Capture consumer requirements, onboarding needs, constraints, service expectations, and producer responsibilities." }, { "id": "api-platform-architecture", "title": "Architecture & Platform Decisions", "description": "Use requirements and constraints to select the implementation style, architecture pattern, and enabling platform capabilities." }, { "id": "api-design", "title": "Solution & Interface Design", "description": "Design the interface contract and interaction model for the selected implementation style." }, { "id": "api-delivery", "title": "Delivery & Operations", "description": "Build, test, deploy, and operate the capability using the selected implementation style and validated interface contract." }, { "id": "api-audit", "title": "Quality & Readiness Assurance", "description": "Validate the interface contract, controls, documentation, support model, and operational readiness before release." }, { "id": "api-publishing", "title": "Publishing & Enablement", "description": "Publish the capability so consumers can discover it, evaluate it, request access, complete onboarding, use it, and get support." }, { "id": "monitoring-and-improving", "title": "Monitoring & Improvement", "description": "Monitor capability health, consumer outcomes, reliability, reuse, and improvement opportunities." } ] }, { "id": "api-productization-cycle", "slug": "api-productization-cycle", "title": "API Productization Cycle", "description": "The API-focused APIOps Cycles journey for productizing, designing, delivering, publishing, and improving APIs.", "stations": [ { "id": "api-product-strategy", "title": "API Product Strategy", "description": "Before building anything, define your API's value, users, and business goals from day one." }, { "id": "api-consumer-experience", "title": "API Consumer Experience", "description": "Ensure your API is discoverable, understandable, and usable — before and after launch." }, { "id": "api-platform-architecture", "title": "API Platform Architecture", "description": "Ensure scalability, reuse, and governance across your API and platform components." }, { "id": "api-design", "title": "API Design", "description": "Create API designs that are consistent, reusable, and grounded in business intent and shared standards." }, { "id": "api-delivery", "title": "API Delivery", "description": "Build, test, and release APIs using modern delivery pipelines and engineering best practices." }, { "id": "api-audit", "title": "API Audit", "description": "Validate that APIs meet business, design, and operational standards before release." }, { "id": "api-publishing", "title": "API Publishing", "description": "Expose APIs securely and clearly to the right audience with the right documentation and processes." }, { "id": "monitoring-and-improving", "title": "API Monitoring & Improvement", "description": "Use metrics and feedback to track API performance and drive continuous improvement." } ] }, { "id": "integration-productization-cycle", "slug": "integration-productization-cycle", "title": "Integration Productization Cycle", "description": "A cycle for productizing reusable integration capabilities before selecting the implementation style.", "stations": [ { "id": "api-product-strategy", "title": "Integration Capability Strategy", "description": "Frame the reusable integration capability, business need, ownership, and expected reuse before selecting the implementation style." }, { "id": "api-consumer-experience", "title": "Integration Consumer Requirements & Onboarding", "description": "Capture integration consumers, provider responsibilities, onboarding needs, service expectations, and operational constraints." }, { "id": "api-platform-architecture", "title": "Integration Architecture & Platform Decisions", "description": "Select the integration architecture, implementation style, and platform capabilities, taking account of constraints and the governance model." }, { "id": "api-design", "title": "Integration Solution Design", "description": "Design the interface contract, schemas, payloads, and interaction patterns for the selected integration style." }, { "id": "api-delivery", "title": "Integration Delivery & Operations", "description": "Build, test, automate, deploy, and operate the integration capability using its selected implementation style and validated interface contract." }, { "id": "api-audit", "title": "Integration Readiness Assurance", "description": "Assure integration readiness, governance, quality, security, compliance, and operational evidence before release." }, { "id": "api-publishing", "title": "Integration Publishing & Enablement", "description": "Publish the integration capability so teams can discover it, evaluate it, request access, complete onboarding, reuse it, and get support." }, { "id": "monitoring-and-improving", "title": "Integration Monitoring & Improvement", "description": "Monitor integration reliability, reuse, incidents, performance, consumer outcomes, and improvement needs." } ] }, { "id": "automation-cycle", "slug": "automation-cycle", "title": "Automation Cycle", "description": "A cycle for identifying, designing, delivering, enabling, and improving automation opportunities.", "stations": [ { "id": "api-product-strategy", "title": "Automation Opportunity Strategy", "description": "Identify and prioritize automation opportunities by value, feasibility, risk, ownership, and expected process impact." }, { "id": "api-consumer-experience", "title": "Process & User Requirements", "description": "Capture process users, roles, handoffs, exceptions, constraints, and service expectations before designing the automation." }, { "id": "api-platform-architecture", "title": "Automation Platform Decision", "description": "Choose the automation platform, runtime, integration approach, governance controls, and operating constraints." }, { "id": "api-design", "title": "Automation Workflow Design", "description": "Design the automation workflow, triggers, decision points, integrations, data handling, relevant interface contracts, and exception paths." }, { "id": "api-delivery", "title": "Automation Delivery & Operations", "description": "Build, test, deploy, document, and operate the automation using clear ownership, controls, and rollback paths." }, { "id": "api-audit", "title": "Automation Readiness Review", "description": "Review automation readiness, quality, risk, compliance, human oversight, evidence, and release criteria." }, { "id": "api-publishing", "title": "Automation Rollout & Enablement", "description": "Roll out the automation with discovery, onboarding, operating instructions, support paths, and change communication for users and operators." }, { "id": "monitoring-and-improving", "title": "Automation Monitoring & Improvement", "description": "Monitor automation performance, exceptions, reliability, user outcomes, operational impact, and improvement opportunities." } ] } ], "stations": [ { "id": "api-product-strategy", "title": "Strategy", "description": "Frame the business need as a reusable capability before choosing the implementation style." }, { "id": "user-experience", "title": "User Experience - Design APIs with the User in Mind", "description": "Ensure APIs are designed with the end user in mind, providing a seamless and intuitive experience." }, { "id": "api-consumer-experience", "title": "Consumer Requirements & Onboarding", "description": "Capture consumer onboarding, standards, non-functional requirements, service expectations, constraints, security needs, allowed protocols, data freshness, SLAs, observability, recovery, adoption requirements, and producer responsibilities." }, { "id": "market-insights", "title": "Market Insights - Understand the API Landscape", "description": "Analyze market trends, competitor APIs, and industry standards to inform API strategy." }, { "id": "api-platform-architecture", "title": "Architecture & Platform Decisions", "description": "Use requirements and constraints to decide the right architecture pattern and enabling platform capabilities." }, { "id": "business-goals", "title": "Business Goals - Align APIs with Business Objectives", "description": "Ensure APIs are aligned with business objectives and contribute to overall organizational goals." }, { "id": "api-design", "title": "Solution & Interface Design", "description": "Design the interface contract and interaction model after the architecture choice is justified." }, { "id": "competitive-analysis", "title": "Competitive Analysis - Stay Ahead in the API Market", "description": "Analyze competitors' APIs to identify strengths, weaknesses, and opportunities for differentiation." }, { "id": "api-delivery", "title": "Delivery & Operations", "description": "Deliver the selected implementation style with appropriate engineering, testing, security, automation, and operational practices." }, { "id": "ecosystem-vision", "title": "Ecosystem Vision - Build APIs for a Thriving Ecosystem", "description": "Create a vision for how your APIs fit into a larger ecosystem, enabling collaboration and innovation." }, { "id": "api-audit", "title": "Quality & Readiness Assurance", "description": "Audit the capability interface contract, controls, support model, observability, documentation, and lifecycle readiness before release." }, { "id": "scalable-infrastructure", "title": "Scalable Infrastructure - Build APIs on a Solid Foundation", "description": "Ensure your API infrastructure can scale to meet growing demand and support high availability." }, { "id": "api-publishing", "title": "Publishing & Enablement", "description": "Publish reusable capability information so consumers can discover, request, onboard, use, and get support." }, { "id": "legal-and-compliance", "title": "Legal and Compliance - Ensure APIs Meet Regulatory Standards", "description": "Ensure APIs comply with legal and regulatory requirements, protecting your organization and users." }, { "id": "monitoring-and-improving", "title": "Monitoring & Improvement", "description": "Monitor usage, reliability, data quality, consumer outcomes, operational cost, and reuse opportunities after release." }, { "id": "security-and-privacy", "title": "Security and Privacy - Protect Your APIs and Users", "description": "Implement security and privacy measures to protect APIs and user data from threats and breaches." }, { "id": "design-standards", "title": "Design Standards - Ensure Consistent and High-Quality API Design", "description": "Establish design standards and guidelines to ensure consistent and high-quality API design across the organization." }, { "id": "vendor-management", "title": "Vendor Management - Manage Third-Party API Integrations", "description": "Effectively manage third-party API vendors and integrations to ensure reliability and compliance." }, { "id": "contract-design", "title": "Contract Design - Define Clear API Contracts", "description": "Create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines." }, { "id": "development", "title": "Development - Build APIs with Best Practices", "description": "Implement APIs using best practices and frameworks to ensure quality, maintainability, and scalability." }, { "id": "ci-cd", "title": "CI/CD - Automate API Delivery", "description": "Implement continuous integration and continuous delivery (CI/CD) pipelines to automate API delivery and ensure consistent quality." }, { "id": "test-automation", "title": "Test Automation - Ensure API Quality", "description": "Implement automated testing practices to ensure API quality, reliability, and performance." }, { "id": "release-management", "title": "Release Management - Manage API Releases Effectively", "description": "Implement release management practices to ensure smooth and controlled API releases." }, { "id": "service-agreements", "title": "Service Agreements - Define API Service Levels", "description": "Establish service agreements that define expectations, service levels, and responsibilities for API providers and consumers." }, { "id": "api-consumer-adoption", "title": "Consumer Adoption", "description": "Implement strategies to drive consumer adoption and engagement so reusable capabilities are used effectively." }, { "id": "api-promotion", "title": "Promotion", "description": "Promote reusable capabilities to increase visibility, usage, and adoption among target audiences." }, { "id": "partner-integration", "title": "Partner Integration - Collaborate with Partners", "description": "Facilitate partner integrations to enhance API capabilities and expand reach." }, { "id": "api-mindset", "title": "API Mindset - Foster an API-First Culture", "description": "Cultivate an API-first mindset across the organization to drive innovation and collaboration." }, { "id": "roles-and-responsibilities", "title": "Roles and Responsibilities - Define API Team Structures", "description": "Define clear roles and responsibilities for API teams to ensure effective collaboration and accountability." }, { "id": "upskilling", "title": "Upskilling - Enhance API Skills and Knowledge", "description": "Provide training and resources to enhance API skills and knowledge across the organization." }, { "id": "operating-guidelines", "title": "Operating Guidelines - Establish API Governance", "description": "Establish operating guidelines and governance practices to ensure consistent API management and quality." }, { "id": "portfolio-management", "title": "Portfolio Management - Manage API Portfolio Effectively", "description": "Manage the API portfolio effectively to ensure alignment with business goals and strategic initiatives." }, { "id": "budget-and-resource-management", "title": "Budget and Resource Management - Optimize API Investments", "description": "Optimize budget and resource management for API initiatives to ensure effective investments and resource allocation." } ] }, "fi": { "routeProfiles": [ { "id": "platform-architect", "stakeholderId": "platform-architect", "title": "Alusta-arkkitehti", "summary": "Ohjaa alustan, integraation, skaalautuvuuden ja arkkitehtuurin päätöksiä, jotka määrittelevät, miten kyvykkyys tai API rakennetaan ja operoidaan." }, { "id": "platform-owner", "stakeholderId": "platform-owner", "title": "Alustan omistaja", "summary": "Vastaa alustan kyvykkyyksistä, tiekartasta, operatiivisesta mallista ja palveluodotuksista." }, { "id": "api-architect", "stakeholderId": "api-architect", "title": "API-arkkitehti", "summary": "Vastaa API-arkkitehtuurista, suunnitteluperiaatteista ja rajapintasopimusten laadusta." }, { "id": "governance-specialist", "stakeholderId": "governance-specialist", "title": "API-hallinnan omistaja", "summary": "Vastaa API-hallintaprosesseista, ohjeista ja päätöksenteosta, joka määrittelee, miten API-kehityspäätökset tehdään ja dokumentoidaan." }, { "id": "api-consumer-specialist", "stakeholderId": "api-consumer-specialist", "title": "API-hyödyntäjien edustaja", "summary": "Edustaa kehittäjien, integraattoreiden tai muiden API-hyödyntäjien tarpeita, jotka käyttävät APIa suoraan." }, { "id": "api-designer", "stakeholderId": "api-designer", "title": "API-suunnittelija", "summary": "Suunnittelee rajapintasopimuksen, vuorovaikutusmallin, johdonmukaisuuden, käytettävyyden ja tarjottavat kyvykkyydet." }, { "id": "api-product-owner", "stakeholderId": "api-product-owner", "title": "API-tuoteomistaja", "summary": "Ohjaa API-mahdollisuutta, priorisointia ja tuotetasolla tehtyjä päätöksiä elinkaaren aikana." }, { "id": "customer-specialist", "stakeholderId": "customer-specialist", "title": "Asiakas- tai kumppaniedustaja", "summary": "Edustaa asiakkaan tai kumppanin näkökulmaa polkuun, arvoon ja yhteistyömalliin." }, { "id": "automation-engineer", "stakeholderId": "automation-engineer", "title": "Automaatiokehittäjä", "summary": "Toteuttaa, testaa, integroi ja ylläpitää automaatioratkaisuja ja niitä tukevia työnkulkuja." }, { "id": "automation-owner", "stakeholderId": "automation-owner", "title": "Automaation omistaja", "summary": "Vastaa automaation tavoitteista, liiketoiminta-arvosta, priorisoinnista, kontrolleista ja elinkaaren tuloksista." }, { "id": "api-devrel-specialist", "stakeholderId": "api-devrel-specialist", "title": "Dokumentoinnin ja kehittäjäsuhteiden omistaja", "summary": "Varmistaa, että API-dokumentaatio, esimerkit, koulutus ja kehittäjäsuhteiden strategiat tukevat API-hyödyntäjien tarpeita." }, { "id": "integration-architect", "stakeholderId": "integration-architect", "title": "Integraatioarkkitehti", "summary": "Suunnittelee integraatiotavat ja toteutustavat, joilla kyvykkyys tai API yhdistetään muihin järjestelmiin." }, { "id": "partner-specialist", "stakeholderId": "partner-specialist", "title": "Kumppani- ja toimittajavastaava", "summary": "Koordinoi ulkoisia kumppani-, toimittaja- ja alihankkijasuhteita, jotka vaikuttavat kyvykkyys- tai API-strategiaan ja toimitukseen." }, { "id": "capability-owner", "stakeholderId": "capability-owner", "title": "Kyvykkyyden omistaja", "summary": "Vastaa kyvykkyyden visiosta, arvosta, priorisoinnista, elinkaaresta ja uudelleenkäytöstä eri hyödyntäjille." }, { "id": "business-owner", "stakeholderId": "business-owner", "title": "Liiketoiminnan omistaja", "summary": "Edustaa liiketoimintatavoitteita, rahoitusta ja odotettuja tuloksia kyvykkyys-, API- tai automaatiohankkeessa." }, { "id": "domain-specialist", "stakeholderId": "domain-specialist", "title": "Liiketoiminta-asiantuntija", "summary": "Tuo syvällistä tietoa liiketoiminta-alueesta, käsitteistä, säännöistä ja rajoituksista, joita kyvykkyyden tai rajapinnan täytyy heijastaa." }, { "id": "process-owner", "stakeholderId": "process-owner", "title": "Prosessin omistaja", "summary": "Vastaa automatisoitavasta liiketoimintaprosessista, mukaan lukien tavoitteet, säännöt, tulokset ja kehittämisen prioriteetit." }, { "id": "api-engineer", "stakeholderId": "api-engineer", "title": "Toimituskehittäjä", "summary": "Vastaa toteutuksesta, automaatiosta, testauksesta ja julkaisun kulusta, joita kyvykkyyden, APIn tai automaation luotettava toimittaminen edellyttää." }, { "id": "operations-specialist", "stakeholderId": "operations-specialist", "title": "Tuki- ja operaatioiden omistaja", "summary": "Edustaa tuotannon tukea, häiriönhallintaa, havainnoitavuutta ja operatiivista valmiutta kyvykkyydelle, APIlle tai automaatiolle." }, { "id": "security-specialist", "stakeholderId": "security-specialist", "title": "Turvallisuusasiantuntija", "summary": "Varmistaa, että turvallisuusriskit, kontrollit ja luottamusrajat käsitellään koko elinkaaren aikana." }, { "id": "compliance-specialist", "stakeholderId": "compliance-specialist", "title": "Vaatimustenmukaisuus- ja lakiasiantuntija", "summary": "Selventää juridiset, tietosuojaan liittyvät, sääntelyyn liittyvät ja sopimukselliset vaatimukset, jotka vaikuttavat kyvykkyyteen, APIin, rajapintaan tai automaatioon." } ], "lines": [ { "id": "business-opportunities-line", "slug": "business-opportunities-line", "title": "Liiketoimintamahdollisuuksien linja", "description": "Keskittyy tunnistamaan, arvioimaan ja tuotteistamaan liiketoimintamahdollisuuksia uudelleenkäytettävinä kyvykkyyksinä.", "icon": "", "color": "#26b309", "stations": [ "monitoring-and-improving", "api-product-strategy", "user-experience", "market-insights", "business-goals", "competitive-analysis", "ecosystem-vision" ] }, { "id": "platform-architecture-line", "slug": "platform-architecture-line", "title": "Alusta-arkkitehtuurilinja", "description": "Kattaa alustojen, integraatioiden ja rajapintojen arkkitehtuurin suunnittelun.", "icon": "", "color": "#933469", "stations": [ "api-product-strategy", "api-consumer-experience", "api-platform-architecture", "scalable-infrastructure", "legal-and-compliance", "security-and-privacy", "design-standards", "vendor-management" ] }, { "id": "api-design-line", "slug": "api-design-line", "title": "API-suunnittelulinja", "description": "Keskittyy rajapintojen ja integraatioratkaisujen suunnitteluperiaatteisiin ja -käytäntöihin.", "icon": "", "color": "#db9b0c", "stations": [ "api-platform-architecture", "api-design", "api-delivery", "api-audit" ] }, { "id": "delivery-line", "slug": "delivery-line", "title": "Toimituslinja", "description": "Kattaa toteutuksen, testauksen, automaation ja toimituskäytännöt.", "icon": "", "color": "#db9b0c", "stations": [ "api-delivery", "contract-design", "development", "ci-cd", "test-automation", "release-management" ] }, { "id": "publishing-and-adoption-line", "slug": "publishing-and-adoption-line", "title": "Julkaisu- ja käyttöönoton linja", "description": "Keskittyy kyvykkyyksien julkaisemiseen, käyttöönottoon ja hyödyntämisen tukemiseen.", "icon": "", "color": "#17C6E9", "stations": [ "api-audit", "api-publishing", "monitoring-and-improving", "service-agreements", "api-consumer-adoption", "api-promotion", "partner-integration" ] }, { "id": "operating-model-line", "slug": "operating-model-line", "title": "Toimintamallilinja", "description": "Kattaa kyvykkyyksien hallintamallin, vastuut ja governance-käytännöt.", "icon": "", "color": "#1a3987", "stations": [ "api-product-strategy", "api-mindset", "roles-and-responsibilities", "upskilling", "operating-guidelines", "portfolio-management", "budget-and-resource-management" ] } ], "cycles": [ { "id": "capability-productization-cycle", "slug": "capability-productization-cycle", "title": "Kyvykkyyden tuotteistamisen sykli", "description": "Sykli liiketoiminnan kyvykkyyksien muuttamiseen uudelleenkäytettäviksi digitaalisiksi kyvykkyyksiksi ennen toteutustavan valintaa.", "stations": [ { "id": "api-product-strategy", "title": "Kyvykkyysstrategia", "description": "Kuvaa liiketoimintatarve uudelleenkaytettavana kyvykkyytena, jolla on selkea arvo, hyodyntajat, omistajuus ja liiketoimintatavoitteet ennen toteutustavan valintaa." }, { "id": "api-consumer-experience", "title": "Hyödyntäjien vaatimukset ja käyttöönotto", "description": "Kokoa hyödyntäjien vaatimukset, käyttöönoton tarpeet, rajoitteet, palveluodotukset ja tuottajan vastuut." }, { "id": "api-platform-architecture", "title": "Arkkitehtuuri ja alustaratkaisut", "description": "Kayta vaatimuksia ja rajoitteita toteutustavan, arkkitehtuurimallin ja mahdollistavien alustakyvykkyyksien valintaan." }, { "id": "api-design", "title": "Ratkaisu- ja rajapintasuunnittelu", "description": "Suunnittele rajapintasopimus ja vuorovaikutusmalli valitulle toteutustavalle." }, { "id": "api-delivery", "title": "Toimitus ja operointi", "description": "Rakenna, testaa, julkaise ja operoi kyvykkyyttä valitulla toteutustavalla ja validoidulla rajapintasopimuksella." }, { "id": "api-audit", "title": "Laadun ja valmiuden varmistus", "description": "Validoi rajapintasopimus, kontrollit, dokumentaatio, tukimalli ja operatiivinen valmius ennen julkaisua." }, { "id": "api-publishing", "title": "Julkaisu ja kayttoonoton tuki", "description": "Julkaise kyvykkyys, jotta hyodyntajat voivat loytaa sen, arvioida sen, pyytaa kayttooikeutta, suorittaa kayttoonoton, kayttaa sita ja saada tukea." }, { "id": "monitoring-and-improving", "title": "Seuranta ja parantaminen", "description": "Seuraa kyvykkyyden tilaa, hyödyntäjien tuloksia, luotettavuutta, uudelleenkäyttöä ja parannusmahdollisuuksia." } ] }, { "id": "api-productization-cycle", "slug": "api-productization-cycle", "title": "API-tuotteistamisen sykli", "description": "API-keskeinen APIOps Cycles -polku APIen tuotteistamiseen, suunnitteluun, toimittamiseen, julkaisuun ja parantamiseen.", "stations": [ { "id": "api-product-strategy", "title": "API-tuotestrategia", "description": "Ennen kuin rakennat mitään, määrittele APIn arvo, hyödyntäjät ja liiketoiminnalliset tavoitteet heti alusta alkaen." }, { "id": "api-consumer-experience", "title": "API-hyödyntäjäkokemus", "description": "Varmistetaan, että API on löydettävissä, ymmärrettävissä ja käyttökelpoinen ennen käyttöönottoa ja sen jälkeen." }, { "id": "api-platform-architecture", "title": "API-alustan arkkitehtuuri", "description": "Varmistetaan skaalautuvuus, uudelleenkäyttö ja hallinta API- ja alustakomponenttien välillä." }, { "id": "api-design", "title": "API-suunnittelu", "description": "Luo API-suunnitelmia, jotka ovat johdonmukaisia, uudelleenkäytettäviä ja perustuvat liiketoiminnallisiin tavoitteisiin sekä yhteisiin standardeihin." }, { "id": "api-delivery", "title": "API-toteutus", "description": "Rakenna, testaa ja julkaise rajapintoja käyttämällä nykyaikaisia jakeluputkia ja parhaita teknisiä käytäntöjä." }, { "id": "api-audit", "title": "API-auditointi", "description": "Varmista, että APIt täyttävät liiketoiminta-, suunnittelu- ja toimintastandardit ennen julkaisua ja käyttöönottoa." }, { "id": "api-publishing", "title": "API-julkaisu", "description": "Esittele APIt turvallisesti ja selkeästi oikealle yleisölle oikean dokumentaation ja prosessien avulla." }, { "id": "monitoring-and-improving", "title": "APIen seuranta ja parantaminen", "description": "Käytä mittareita ja palautetta API-suorituskyvyn seuraamiseen ja jatkuvan parantamisen edistämiseen." } ] }, { "id": "integration-productization-cycle", "slug": "integration-productization-cycle", "title": "Integraatiokyvykkyyden tuotteistamisen sykli", "description": "Sykli uudelleenkaytettavien integraatiokyvykkyyksien tuotteistamiseen ennen toteutustavan valintaa.", "stations": [ { "id": "api-product-strategy", "title": "Integraatiokyvykkyyden strategia", "description": "Kuvaa uudelleenkaytettava integraatiokyvykkyys, liiketoimintatarve, omistajuus ja odotettu uudelleenkaytto ennen toteutustavan valintaa." }, { "id": "api-consumer-experience", "title": "Integraation hyödyntäjien vaatimukset ja käyttöönotto", "description": "Kokoa integraation hyödyntäjät, tuottajan vastuut, käyttöönoton tarpeet, palveluodotukset ja operatiiviset rajoitteet." }, { "id": "api-platform-architecture", "title": "Integraatioarkkitehtuuri ja alustapaatokset", "description": "Valitse integraatioarkkitehtuuri, toteutustapa ja alustakyvykkyydet huomioiden rajoitteet ja hallintamalli." }, { "id": "api-design", "title": "Integraation ratkaisusuunnittelu", "description": "Suunnittele rajapintasopimus, skeemat, tietosisallot ja vuorovaikutusmallit valitulle integraatiotavalle." }, { "id": "api-delivery", "title": "Integraation toimitus ja operointi", "description": "Rakenna, testaa, automatisoi, julkaise ja operoi integraatiokyvykkyyttä sen valitulla toteutustavalla ja validoidulla rajapintasopimuksella." }, { "id": "api-audit", "title": "Integraation valmiuden varmistus", "description": "Varmista integraation valmius, hallintamalli, laatu, tietoturva, vaatimustenmukaisuus ja operatiivinen näyttö ennen julkaisua." }, { "id": "api-publishing", "title": "Integraation julkaisu ja kayttoonoton tuki", "description": "Julkaise integraatiokyvykkyys, jotta tiimit voivat loytaa sen, arvioida sen, pyytaa kayttooikeutta, suorittaa kayttoonoton, kayttaa sita uudelleen ja saada tukea." }, { "id": "monitoring-and-improving", "title": "Integraation seuranta ja parantaminen", "description": "Seuraa integraation luotettavuutta, uudelleenkäyttöä, häiriöitä, suorituskykyä, hyödyntäjien tuloksia ja parannustarpeita." } ] }, { "id": "automation-cycle", "slug": "automation-cycle", "title": "Automaatiosykli", "description": "Sykli automaatiomahdollisuuksien tunnistamiseen, suunnitteluun, toimittamiseen, käyttöönoton mahdollistamiseen ja parantamiseen.", "stations": [ { "id": "api-product-strategy", "title": "Automaatiomahdollisuuden strategia", "description": "Tunnista ja priorisoi automaatiomahdollisuudet arvon, toteutettavuuden, riskin, omistajuuden ja odotetun prosessivaikutuksen perusteella." }, { "id": "api-consumer-experience", "title": "Prosessin ja käyttäjien vaatimukset", "description": "Kokoa prosessin käyttäjät, roolit, luovutukset, poikkeukset, rajoitteet ja palveluodotukset ennen automaation suunnittelua." }, { "id": "api-platform-architecture", "title": "Automaatioalustan päätös", "description": "Valitse automaatioalusta, ajoymparisto, integraatiotapa, hallintakontrollit ja operatiiviset rajoitteet." }, { "id": "api-design", "title": "Automaatiotyönkulun suunnittelu", "description": "Suunnittele automaation tyonkulku, kaynnistimet, paatospisteet, integraatiot, datankasittely, olennaiset rajapintasopimukset ja poikkeuspolut." }, { "id": "api-delivery", "title": "Automaation toimitus ja operointi", "description": "Rakenna, testaa, julkaise, dokumentoi ja operoi automaatiota selkeällä omistajuudella, kontrolleilla ja palautuspoluilla." }, { "id": "api-audit", "title": "Automaation valmiuskatselmointi", "description": "Katselmoi automaation valmius, laatu, riski, vaatimustenmukaisuus, ihmisen valvonta, näyttö ja julkaisukriteerit." }, { "id": "api-publishing", "title": "Automaation kayttoonotto ja kayttoonoton tuki", "description": "Mahdollista käyttäjien ja operaattorien työ löydettävyyden, käyttöönoton, käyttöohjeiden, tukipolkujen ja muutosviestinnän avulla." }, { "id": "monitoring-and-improving", "title": "Automaation seuranta ja parantaminen", "description": "Seuraa automaation suorituskykyä, poikkeuksia, luotettavuutta, käyttäjien tuloksia, operatiivista vaikutusta ja parannusmahdollisuuksia." } ] } ], "stations": [ { "id": "api-product-strategy", "title": "Strategia", "description": "Kehystä liiketoimintatarve uudelleenkäytettävänä kyvykkyytenä ennen toteutustavan valintaa." }, { "id": "user-experience", "title": "Käyttäjäkokemus - Suunnittele APIt käyttäjälähtöisesti", "description": "Varmistetaan, että rajapinnat on suunniteltu loppukäyttäjää ajatellen ja että ne tarjoavat saumattoman ja intuitiivisen käyttökokemuksen." }, { "id": "api-consumer-experience", "title": "Hyödyntäjien vaatimukset ja käyttöönotto", "description": "Kokoa hyödyntäjien käyttöönotto, standardit, ei-toiminnalliset vaatimukset, palveluodotukset, rajoitteet, tietoturvatarpeet, sallitut protokollat, datan tuoreus, palvelutasot, havainnoitavuus, palautuminen, käyttöönoton vaatimukset ja tuottajan vastuut." }, { "id": "market-insights", "title": "Markkinatietoa - API-maiseman ymmärtäminen", "description": "Analysoi markkinasuuntauksia, kilpailijoiden rajapintoja ja alan standardeja rajapintastrategian laatimiseksi." }, { "id": "api-platform-architecture", "title": "Arkkitehtuuri- ja alustapäätökset", "description": "Käytä vaatimuksia ja rajoitteita oikean arkkitehtuurimallin ja tarvittavien alustakyvykkyyksien valintaan." }, { "id": "business-goals", "title": "Liiketoiminnalliset tavoitteet - Kohdista rajapinnat liiketoimintatavoitteisiin.", "description": "Varmistetaan, että rajapinnat ovat linjassa liiketoiminnan tavoitteiden kanssa ja edistävät organisaation yleisiä tavoitteita." }, { "id": "api-design", "title": "Ratkaisu- ja rajapintasuunnittelu", "description": "Suunnittele rajapintasopimus ja vuorovaikutusmalli sen jälkeen, kun arkkitehtuurivalinta on perusteltu." }, { "id": "competitive-analysis", "title": "Kilpailuanalyysi - pysy kärjessä API-markkinoilla", "description": "Analysoi kilpailijoiden rajapinnat vahvuuksien, heikkouksien ja erottautumismahdollisuuksien tunnistamiseksi." }, { "id": "api-delivery", "title": "Toimitus ja operointi", "description": "Toimita valittu toteutustapa asianmukaisilla suunnittelu-, testaus-, tietoturva-, automaatio- ja operointikäytännöillä." }, { "id": "ecosystem-vision", "title": "Ekosysteemin visio - Rakenna rajapinnat kukoistavaa ekosysteemiä varten.", "description": "Luo visio siitä, miten rajapintasi sopivat laajempaan ekosysteemiin, joka mahdollistaa yhteistyön ja innovoinnin." }, { "id": "api-audit", "title": "Laadun ja valmiuden varmistus", "description": "Auditoi kyvykkyyden rajapintasopimus, kontrollit, tukimalli, havainnoitavuus, dokumentaatio ja elinkaarivalmius ennen julkaisua." }, { "id": "scalable-infrastructure", "title": "Skaalautuva infrastruktuuri - rakenna APIt vankalle perustalle", "description": "Varmistetaan, että API-infrastruktuurisi voi skaalautua vastaamaan kasvavaa kysyntää ja tukea korkeaa käytettävyyttä." }, { "id": "api-publishing", "title": "Julkaisu ja käyttöönoton mahdollistaminen", "description": "Julkaise uudelleenkäytettävän kyvykkyyden tiedot, jotta hyödyntäjät voivat löytää sen, pyytää käyttöä, ottaa sen käyttöön, käyttää sitä ja saada tukea." }, { "id": "legal-and-compliance", "title": "Lainsäädäntö ja vaatimustenmukaisuus - varmista, että APIt täyttävät sääntelystandardit.", "description": "Varmistetaan, että rajapinnat noudattavat lakisääteisiä ja lainsäädännöllisiä vaatimuksia ja suojaavat organisaatiota ja käyttäjiä." }, { "id": "monitoring-and-improving", "title": "Seuranta ja parantaminen", "description": "Seuraa käyttöä, luotettavuutta, datan laatua, hyödyntäjien tuloksia, operatiivisia kustannuksia ja uudelleenkäytön mahdollisuuksia julkaisun jälkeen." }, { "id": "security-and-privacy", "title": "Tietoturva ja yksityisyys - Suojaa APIt ja käyttäjät", "description": "Toteuta tietoturva- ja yksityisyydensuojatoimenpiteet, joilla suojataan rajapintoja ja käyttäjätietoja uhkilta ja tietoturvaloukkauksilta." }, { "id": "design-standards", "title": "Suunnittelustandardit - Varmistaa johdonmukainen ja laadukas API-suunnittelu.", "description": "Suunnittelustandardien ja -ohjeiden laatiminen, jotta varmistetaan yhdenmukainen ja laadukas API-suunnittelu koko organisaatiossa." }, { "id": "vendor-management", "title": "Toimittajan hallinta - Kolmannen osapuolen API-integraatioiden hallinta", "description": "Hallinnoi tehokkaasti kolmannen osapuolen API-toimittajia ja integraatioita luotettavuuden ja vaatimustenmukaisuuden varmistamiseksi." }, { "id": "contract-design", "title": "Sopimussuunnittelu - Määrittele selkeät API-sopimukset", "description": "Luo selkeät ja hyvin määritellyt API-sopimukset, joissa hahmotellaan odotukset, vastuut ja käyttöohjeet." }, { "id": "development", "title": "Kehitys - Rakenna APIt parhaiden käytäntöjen avulla", "description": "Toteuta rajapinnat parhaiden käytäntöjen ja kehysten avulla laadun, ylläpidettävyyden ja skaalautuvuuden varmistamiseksi." }, { "id": "ci-cd", "title": "CI/CD - Automatisoi API-kehitys", "description": "Ota käyttöön jatkuvan integroinnin ja jatkuvan toimituksen (CI/CD) putket API-kehityksen automatisoimiseksi ja tasaisen laadun varmistamiseksi." }, { "id": "test-automation", "title": "Testausautomaatio - varmista API-laatu", "description": "Ota käyttöön automatisoituja testauskäytäntöjä APIn laadun, luotettavuuden ja suorituskyvyn varmistamiseksi." }, { "id": "release-management", "title": "Julkaisunhallinta - Hallitse API-julkaisuja tehokkaasti", "description": "Ota käyttöön julkaisujen hallintakäytäntöjä sujuvien ja valvottujen API-julkaisujen varmistamiseksi." }, { "id": "service-agreements", "title": "Palvelusopimukset - määrittele API-palvelutasot", "description": "Laadi palvelusopimukset, joissa määritellään API-toimittajien ja hyödyntäjien odotukset, palvelutasot ja vastuut." }, { "id": "api-consumer-adoption", "title": "APIn käyttöönotto - APIn käytön edistäminen", "description": "Toteuta strategioita, joilla edistetään API-hyödyntäjien käyttöönottoa ja sitoutumista sekä varmistetaan, että API-rajapintoja käytetään tehokkaasti." }, { "id": "api-promotion", "title": "API-näkyvyys - APIn näkyvyyden ja käytön lisääminen", "description": "Edistetään rajapintoja näkyvyyden, käytön ja hyväksynnän lisäämiseksi kohdeyleisöjen keskuudessa." }, { "id": "partner-integration", "title": "Kumppanien integrointi - Tee yhteistyötä kumppaneiden kanssa", "description": "Helpota kumppani-integraatioita API-ominaisuuksien parantamiseksi ja tavoittavuuden laajentamiseksi." }, { "id": "api-mindset", "title": "API-ajattelutapa - API-first -kulttuurin edistäminen", "description": "Kehitä API-first -ajattelutapaa koko organisaatiossa innovoinnin ja yhteistyön edistämiseksi." }, { "id": "roles-and-responsibilities", "title": "Roolit ja vastuualueet - API-tiimien rakenteiden määrittelyt", "description": "Määrittele API-tiimeille selkeät roolit ja vastuualueet tehokkaan yhteistyön ja vastuuvelvollisuuden varmistamiseksi." }, { "id": "upskilling", "title": "Osaamisen kehittäminen - API-taitojen ja -tiedon parantaminen", "description": "Tarjotaan koulutusta ja resursseja API-taitojen ja -tiedon parantamiseksi koko organisaatiossa." }, { "id": "operating-guidelines", "title": "Toimintaohjeet - API-hallinnon perustaminen", "description": "Laaditaan toimintaohjeet ja hallintokäytännöt, joilla varmistetaan APIn johdonmukainen hallinta ja laatu." }, { "id": "portfolio-management", "title": "Portfolionhallinta - hallinnoi API-portfoliota tehokkaasti", "description": "Hallinnoida API-salkkua tehokkaasti varmistaaksesi, että se on linjassa liiketoiminnan tavoitteiden ja strategisten aloitteiden kanssa." }, { "id": "budget-and-resource-management", "title": "Budjetin ja resurssien hallinta - Optimoi API-investoinnit", "description": "Optimoi API-aloitteiden budjetin ja resurssien hallinta tehokkaiden investointien ja resurssien kohdentamisen varmistamiseksi." } ] }, "fr": { "routeProfiles": [ { "id": "api-architect", "stakeholderId": "api-architect", "title": "Architecte API", "summary": "Responsable de l'architecture API, des principes de conception et de la qualité des contrats d'interface." }, { "id": "integration-architect", "stakeholderId": "integration-architect", "title": "Architecte d'intégration", "summary": "Conçoit les approches d’intégration et les modes de mise en œuvre qui relient la capacité ou l’API aux autres systèmes." }, { "id": "platform-architect", "stakeholderId": "platform-architect", "title": "Architecte de la plateforme", "summary": "Oriente les décisions relatives à la plateforme, à l’intégration, à l’évolutivité et à l’architecture qui déterminent comment la capacité ou l’API est construite et exploitée." }, { "id": "api-designer", "stakeholderId": "api-designer", "title": "Designer API", "summary": "Conçoit le contrat d’interface, le modèle d’interaction, la cohérence et l’utilisabilité des capacités exposées." }, { "id": "domain-specialist", "stakeholderId": "domain-specialist", "title": "Expert du domaine", "summary": "Apporte une connaissance approfondie du domaine métier, des concepts, des règles et des contraintes que la capacité ou l’interface doit refléter." }, { "id": "partner-specialist", "stakeholderId": "partner-specialist", "title": "Gestionnaire de partenaires ou de fournisseurs", "summary": "Coordonne les relations avec les partenaires, fournisseurs ou prestataires externes qui influencent la stratégie et la mise en œuvre de la capacité ou de l’API." }, { "id": "automation-engineer", "stakeholderId": "automation-engineer", "title": "Ingénieur automatisation", "summary": "Met en œuvre, teste, intègre et exploite les solutions d’automatisation et les workflows associés." }, { "id": "api-engineer", "stakeholderId": "api-engineer", "title": "Ingénieur de livraison", "summary": "Assume la responsabilité de la mise en œuvre, de l’automatisation, des tests et du flux de publication nécessaires pour livrer la capacité, l’API ou l’automatisation de manière fiable." }, { "id": "api-product-owner", "stakeholderId": "api-product-owner", "title": "Propriétaire du produit API", "summary": "Pilote l’opportunité API, la priorisation et les décisions au niveau produit tout au long du cycle de vie." }, { "id": "customer-specialist", "stakeholderId": "customer-specialist", "title": "Représentant client ou partenaire", "summary": "Contribue à la perspective du client ou partenaire pour le parcours, la valeur et le modèle de collaboration." }, { "id": "api-consumer-specialist", "stakeholderId": "api-consumer-specialist", "title": "Représentant utilisateur API", "summary": "Représente les besoins des développeurs, intégrateurs ou autres utilisateurs d'API qui utilisent l'API directement." }, { "id": "capability-owner", "stakeholderId": "capability-owner", "title": "Responsable de capacité", "summary": "Responsable de la vision, de la valeur, des priorités, du cycle de vie et de la réutilisation de la capacité auprès des utilisateurs." }, { "id": "automation-owner", "stakeholderId": "automation-owner", "title": "Responsable de l'automatisation", "summary": "Responsable des objectifs, de la valeur métier, des priorités, des contrôles et des résultats du cycle de vie de l’automatisation." }, { "id": "platform-owner", "stakeholderId": "platform-owner", "title": "Responsable de plateforme", "summary": "Responsable des capacités de la plateforme, de la feuille de route, du modèle opérationnel et des attentes de service." }, { "id": "process-owner", "stakeholderId": "process-owner", "title": "Responsable de processus", "summary": "Responsable du processus métier à automatiser, y compris les objectifs, les règles, les résultats et les priorités d’amélioration." }, { "id": "api-devrel-specialist", "stakeholderId": "api-devrel-specialist", "title": "Responsable Documentation & DevRel", "summary": "Responsable des contenus d'onboarding, de la communication avec les développeurs et de la qualité de la documentation API." }, { "id": "governance-specialist", "stakeholderId": "governance-specialist", "title": "Responsable gouvernance", "summary": "Représente les pratiques de revue, d'audit et de gouvernance à l'échelle de l'organisation pour la qualité et la conformité des API." }, { "id": "business-owner", "stakeholderId": "business-owner", "title": "Responsable métier", "summary": "Représente les objectifs métier, le financement et les résultats attendus de l’initiative de capacité, d’API ou d’automatisation." }, { "id": "operations-specialist", "stakeholderId": "operations-specialist", "title": "Responsable support et opérations", "summary": "Représente le support en production, la gestion des incidents, l’observabilité et la préparation opérationnelle pour la capacité, l’API ou l’automatisation." }, { "id": "compliance-specialist", "stakeholderId": "compliance-specialist", "title": "Spécialiste en conformité et juridique", "summary": "Clarifie les exigences juridiques, de confidentialité, réglementaires et contractuelles qui affectent la capacité, l’API, l’interface ou l’automatisation." }, { "id": "security-specialist", "stakeholderId": "security-specialist", "title": "Spécialiste en sécurité", "summary": "Assure que les risques de sécurité, les contrôles et les limites de confiance sont pris en compte tout au long du cycle de vie." } ], "lines": [ { "id": "business-opportunities-line", "slug": "business-opportunities-line", "title": "Ligne des opportunités métier", "description": "Se concentre sur l'identification, l'évaluation et la productisation des opportunités métier sous forme de capacités réutilisables.", "icon": "", "color": "#26b309", "stations": [ "monitoring-and-improving", "api-product-strategy", "user-experience", "market-insights", "business-goals", "competitive-analysis", "ecosystem-vision" ] }, { "id": "platform-architecture-line", "slug": "platform-architecture-line", "title": "Ligne d'architecture de la plateforme", "description": "Couvre les décisions d'architecture relatives aux plateformes, aux intégrations et aux interfaces.", "icon": "", "color": "#933469", "stations": [ "api-product-strategy", "api-consumer-experience", "api-platform-architecture", "scalable-infrastructure", "legal-and-compliance", "security-and-privacy", "design-standards", "vendor-management" ] }, { "id": "api-design-line", "slug": "api-design-line", "title": "Ligne de conception de l'API", "description": "Se concentre sur les principes et les bonnes pratiques de conception des interfaces et des solutions d'intégration.", "icon": "", "color": "#db9b0c", "stations": [ "api-platform-architecture", "api-design", "api-delivery", "api-audit" ] }, { "id": "delivery-line", "slug": "delivery-line", "title": "Ligne de livraison", "description": "Couvre les pratiques de mise en œuvre, de test, d'automatisation et de livraison.", "icon": "", "color": "#db9b0c", "stations": [ "api-delivery", "contract-design", "development", "ci-cd", "test-automation", "release-management" ] }, { "id": "publishing-and-adoption-line", "slug": "publishing-and-adoption-line", "title": "Ligne Publication & Enablement", "description": "Se concentre sur la publication des capacités, leur découvrabilité, leur onboarding et leur adoption.", "icon": "", "color": "#17C6E9", "stations": [ "api-audit", "api-publishing", "monitoring-and-improving", "service-agreements", "api-consumer-adoption", "api-promotion", "partner-integration" ] }, { "id": "operating-model-line", "slug": "operating-model-line", "title": "Ligne de modèle opérationnel", "description": "Couvre la gouvernance, les responsabilités et le modèle opérationnel des capacités.", "icon": "", "color": "#1a3987", "stations": [ "api-product-strategy", "api-mindset", "roles-and-responsibilities", "upskilling", "operating-guidelines", "portfolio-management", "budget-and-resource-management" ] } ], "cycles": [ { "id": "capability-productization-cycle", "slug": "capability-productization-cycle", "title": "Cycle de productisation des capacités", "description": "Cycle pour transformer des capacites metier en capacites numeriques reutilisables avant de choisir le mode de mise en oeuvre.", "stations": [ { "id": "api-product-strategy", "title": "Stratégie de capacité", "description": "Cadrer le besoin metier comme une capacite reutilisable avec une valeur, des utilisateurs, une responsabilite et des objectifs metier clairs avant de choisir le mode de mise en oeuvre." }, { "id": "api-consumer-experience", "title": "Exigences utilisateurs & onboarding", "description": "Capturez les exigences des utilisateurs, les besoins d’onboarding, les contraintes, les attentes de service et les responsabilités des fournisseurs." }, { "id": "api-platform-architecture", "title": "Architecture & décisions de plateforme", "description": "Utiliser les exigences et contraintes pour choisir le mode de mise en oeuvre, le pattern d architecture et les capacites de plateforme necessaires." }, { "id": "api-design", "title": "Conception de solution & d’interface", "description": "Concevoir le contrat d interface et le modele d interaction pour le mode de mise en oeuvre choisi." }, { "id": "api-delivery", "title": "Mise à disposition & opérations", "description": "Construire, tester, deployer et exploiter la capacite avec le mode de mise en oeuvre choisi et le contrat d interface valide." }, { "id": "api-audit", "title": "Assurance qualité & préparation", "description": "Valider le contrat d interface, les controles, la documentation, le modele de support et la preparation operationnelle avant publication." }, { "id": "api-publishing", "title": "Publication & enablement", "description": "Publier la capacite afin que les utilisateurs puissent la decouvrir, l evaluer, demander l acces, terminer l onboarding, l utiliser et obtenir du support." }, { "id": "monitoring-and-improving", "title": "Suivi & amélioration", "description": "Suivez la santé de la capacité, les résultats utilisateurs, la fiabilité, la réutilisation et les opportunités d’amélioration." } ] }, { "id": "api-productization-cycle", "slug": "api-productization-cycle", "title": "Cycle de productisation des API", "description": "Parcours APIOps Cycles centré sur les API pour productiser, concevoir, livrer, publier et améliorer des produits API.", "stations": [ { "id": "api-product-strategy", "title": "Stratégie produit API", "description": "Avant de construire quoi que ce soit, définissez dès le départ la valeur de votre API, ses utilisateurs et ses objectifs métier." }, { "id": "api-consumer-experience", "title": "Expérience utilisateur API", "description": "Veillez à ce que votre API soit découvrable, compréhensible et utilisable - avant et après le lancement." }, { "id": "api-platform-architecture", "title": "Architecture de plateforme API", "description": "Assurez l'évolutivité, la réutilisation et la gouvernance de vos composants d'API et de plateforme." }, { "id": "api-design", "title": "Conception d’API", "description": "Créer des architectures d'API cohérentes, réutilisables et fondées sur les objectifs métier et des normes communes." }, { "id": "api-delivery", "title": "Livraison d’API", "description": "Construire, tester et publier des API en utilisant des pipelines de livraison modernes et les meilleures pratiques d'ingénierie." }, { "id": "api-audit", "title": "Audit API", "description": "Vérifiez que les API répondent aux normes métier, de conception et opérationnelles avant leur publication et leur mise à disposition." }, { "id": "api-publishing", "title": "Publication d’API", "description": "Exposer les API de manière sûre et claire au bon public avec la bonne documentation et les bons processus." }, { "id": "monitoring-and-improving", "title": "Suivi & amelioration API", "description": "Utiliser les mesures et le retour d'information pour suivre les performances de l'API et favoriser l'amélioration continue." } ] }, { "id": "integration-productization-cycle", "slug": "integration-productization-cycle", "title": "Cycle de productisation des capacités d’intégration", "description": "Cycle pour productiser des capacites d integration reutilisables avant de choisir le mode de mise en oeuvre.", "stations": [ { "id": "api-product-strategy", "title": "Stratégie de capacité d’intégration", "description": "Cadrer la capacite d integration reutilisable, le besoin metier, la responsabilite et la reutilisation attendue avant de choisir le mode de mise en oeuvre." }, { "id": "api-consumer-experience", "title": "Exigences des utilisateurs d’intégration & onboarding", "description": "Capturez les utilisateurs d’intégration, les responsabilités des fournisseurs, les besoins d’onboarding, les attentes de service et les contraintes opérationnelles." }, { "id": "api-platform-architecture", "title": "Architecture d integration & decisions de plateforme", "description": "Choisir l architecture d integration, le mode de mise en oeuvre et les capacites de plateforme en tenant compte des contraintes et du modele de gouvernance." }, { "id": "api-design", "title": "Conception de solution d’intégration", "description": "Concevoir le contrat d interface, les schemas, les payloads et les modeles d interaction pour le style d integration choisi." }, { "id": "api-delivery", "title": "Livraison & opérations d’intégration", "description": "Construire, tester, automatiser, deployer et exploiter la capacite d integration avec le mode de mise en oeuvre choisi et le contrat d interface valide." }, { "id": "api-audit", "title": "Assurance qualité des intégrations", "description": "Assurez la préparation, la gouvernance, la qualité, la sécurité, la conformité et les preuves opérationnelles de l’intégration avant publication." }, { "id": "api-publishing", "title": "Publication & enablement de l integration", "description": "Publier la capacite d integration afin que les equipes puissent la decouvrir, l evaluer, demander l acces, terminer l onboarding, la reutiliser et obtenir du support." }, { "id": "monitoring-and-improving", "title": "Suivi & amélioration des intégrations", "description": "Suivez la fiabilité, la réutilisation, les incidents, la performance, les résultats utilisateurs et les besoins d’amélioration de l’intégration." } ] }, { "id": "automation-cycle", "slug": "automation-cycle", "title": "Cycle d’automatisation", "description": "Cycle pour identifier, concevoir, livrer, enable et améliorer des opportunités d’automatisation.", "stations": [ { "id": "api-product-strategy", "title": "Stratégie d’opportunité d’automatisation", "description": "Identifiez et priorisez les opportunités d’automatisation selon la valeur, la faisabilité, le risque, la responsabilité et l’impact attendu sur le processus." }, { "id": "api-consumer-experience", "title": "Exigences processus & utilisateur", "description": "Capturez les utilisateurs du processus, les rôles, les transferts, les exceptions, les contraintes et les attentes de service avant de concevoir l’automatisation." }, { "id": "api-platform-architecture", "title": "Décision de plateforme d’automatisation", "description": "Choisir la plateforme d automatisation, le runtime, l approche d integration, les controles de gouvernance et les contraintes operationnelles." }, { "id": "api-design", "title": "Conception de workflow d’automatisation", "description": "Concevoir le workflow d automatisation, les declencheurs, les points de decision, les integrations, le traitement des donnees, les contrats d interface pertinents et les chemins d exception." }, { "id": "api-delivery", "title": "Livraison & operations de l automatisation", "description": "Construisez, testez, déployez, documentez et exploitez l’automatisation avec une responsabilité et des chemins de rollback clairs." }, { "id": "api-audit", "title": "Revue de préparation de l’automatisation", "description": "Revoyez la préparation, la qualité, les risques, la conformité, la supervision humaine, les preuves et les critères de publication de l’automatisation." }, { "id": "api-publishing", "title": "Deploiement & enablement de l automatisation", "description": "Enablez les utilisateurs et opérateurs avec découverte, onboarding, instructions d’exploitation, chemins de support et communication de changement." }, { "id": "monitoring-and-improving", "title": "Suivi & amélioration de l’automatisation", "description": "Suivez la performance de l’automatisation, les exceptions, la fiabilité, les résultats utilisateurs, l’impact opérationnel et les opportunités d’amélioration." } ] } ], "stations": [ { "id": "api-product-strategy", "title": "Stratégie de capacité", "description": "Décrivez le besoin métier comme une capacité réutilisable avant de choisir le mode de mise en œuvre." }, { "id": "user-experience", "title": "Expérience utilisateur - Concevoir des API en pensant à l'utilisateur", "description": "Veiller à ce que les API soient conçues en pensant à l'utilisateur final, en lui offrant une expérience transparente et intuitive." }, { "id": "api-consumer-experience", "title": "Exigences utilisateurs & onboarding", "description": "Capturez les exigences des utilisateurs, l'onboarding, les standards, les exigences non fonctionnelles, les attentes de service, les contraintes, la sécurité, les protocoles, la fraîcheur des données, les SLA, l'observabilité, la reprise, l'adoption et les responsabilités des fournisseurs." }, { "id": "market-insights", "title": "Aperçus du marché - Comprendre le paysage de l'API", "description": "Analyser les tendances du marché, les API des concurrents et les normes du secteur afin d'éclairer la stratégie en matière d'API." }, { "id": "api-platform-architecture", "title": "Architecture & décisions de plateforme", "description": "Utilisez les exigences et contraintes pour choisir l'architecture, les capacités de plateforme, la gouvernance et le modèle opérationnel." }, { "id": "business-goals", "title": "Objectifs de l'entreprise - Aligner les API sur les objectifs de l'entreprise", "description": "Veiller à ce que les API soient alignées sur les objectifs de l'entreprise et contribuent aux objectifs généraux de l'organisation." }, { "id": "api-design", "title": "Conception de solution & d'interface", "description": "Concevez le mode de mise en œuvre choisi, le contrat d'interface, les modèles d'interaction, les structures de données et les détails d'utilisation avant l'implémentation." }, { "id": "competitive-analysis", "title": "Analyse concurrentielle - Garder une longueur d'avance sur le marché des API", "description": "Analyser les API des concurrents pour identifier les forces, les faiblesses et les possibilités de différenciation." }, { "id": "api-delivery", "title": "Mise à disposition & opérations", "description": "Mettez en œuvre le mode choisi avec des pratiques adaptées d'ingénierie, de test, de sécurité, d'automatisation et d'exploitation." }, { "id": "ecosystem-vision", "title": "Vision de l'écosystème - Créer des API pour un écosystème prospère", "description": "Créez une vision de la manière dont vos API s'intègrent dans un écosystème plus large, favorisant la collaboration et l'innovation." }, { "id": "api-audit", "title": "Assurance qualité & préparation", "description": "Vérifiez le contrat d'interface, les contrôles, le modèle de support, l'observabilité, la documentation et la préparation du cycle de vie avant publication." }, { "id": "scalable-infrastructure", "title": "Infrastructure évolutive - Créer des API sur une base solide", "description": "Veillez à ce que votre infrastructure API puisse évoluer pour répondre à la demande croissante et prendre en charge la haute disponibilité." }, { "id": "api-publishing", "title": "Publication & enablement", "description": "Publiez les informations de capacité afin que les utilisateurs puissent la trouver, l'évaluer, demander l'accès, s'onboarder, l'utiliser et obtenir du support." }, { "id": "legal-and-compliance", "title": "Juridique et conformité - S'assurer que les API respectent les normes réglementaires", "description": "Veillez à ce que les API soient conformes aux exigences légales et réglementaires, afin de protéger votre organisation et vos utilisateurs." }, { "id": "monitoring-and-improving", "title": "Suivi & amélioration", "description": "Suivez l'utilisation, la fiabilité, la qualité des données, les résultats utilisateurs, les coûts opérationnels et les opportunités de réutilisation après publication." }, { "id": "security-and-privacy", "title": "Sécurité et confidentialité - Protégez vos API et vos utilisateurs", "description": "Mettre en œuvre des mesures de sécurité et de confidentialité pour protéger les API et les données des utilisateurs contre les menaces et les violations." }, { "id": "design-standards", "title": "Normes de conception - Garantir une conception cohérente et de haute qualité de l'API", "description": "Établir des normes et des lignes directrices en matière de conception afin de garantir une conception cohérente et de haute qualité de l'API dans l'ensemble de l'organisation." }, { "id": "vendor-management", "title": "Gestion des fournisseurs - Gestion des intégrations d'API de tiers", "description": "Gérer efficacement les fournisseurs d'API tiers et les intégrations pour garantir la fiabilité et la conformité." }, { "id": "contract-design", "title": "Conception des contrats - Définir des contrats API clairs", "description": "Créer des contrats d'interface clairs et bien définis qui décrivent les attentes, les responsabilités et les directives d'utilisation." }, { "id": "development", "title": "Développement - Construire des API avec les meilleures pratiques", "description": "Mettre en œuvre des API en utilisant les meilleures pratiques et les meilleurs cadres afin de garantir la qualité, la maintenabilité et l'évolutivité." }, { "id": "ci-cd", "title": "CI/CD - Automatiser la livraison des API", "description": "Mettre en œuvre des pipelines d'intégration continue et de livraison continue (CI/CD) pour automatiser la livraison des API et garantir une qualité constante." }, { "id": "test-automation", "title": "Automatisation des tests - Assurer la qualité de l'API", "description": "Mettre en œuvre des pratiques de test automatisées pour garantir la qualité, la fiabilité et les performances de l'API." }, { "id": "release-management", "title": "Gestion des versions - Gérer efficacement les versions de l'API", "description": "Mettre en œuvre des pratiques de gestion des versions afin de garantir des versions d'API fluides et contrôlées." }, { "id": "service-agreements", "title": "Accords de service - Définir les niveaux de service de l'API", "description": "Établir des accords de service qui définissent les attentes, les niveaux de service et les responsabilités des fournisseurs et des utilisateurs." }, { "id": "api-consumer-adoption", "title": "Adoption de l'API par les utilisateurs - Favoriser l'utilisation de l'API", "description": "Mettre en œuvre des stratégies visant à favoriser l'adoption et l'engagement des utilisateurs d'API, en veillant à ce que les API soient utilisées efficacement." }, { "id": "api-promotion", "title": "Promotion de l'API - Augmenter la visibilité et l'utilisation de l'API", "description": "Promouvoir les API afin d'accroître la visibilité, l'utilisation et l'adoption parmi les publics cibles." }, { "id": "partner-integration", "title": "Intégration des partenaires - Collaborer avec les partenaires", "description": "Faciliter l'intégration des partenaires afin d'améliorer les capacités de l'API et d'étendre la portée." }, { "id": "api-mindset", "title": "L'état d'esprit de l'API - Favoriser une culture axée sur l'API", "description": "Cultiver un état d'esprit \"API-first\" dans l'ensemble de l'organisation afin de stimuler l'innovation et la collaboration." }, { "id": "roles-and-responsibilities", "title": "Rôles et responsabilités - Définir les structures de l'équipe API", "description": "Définir clairement les rôles et les responsabilités des équipes chargées de l'API afin de garantir une collaboration et une responsabilisation efficaces." }, { "id": "upskilling", "title": "Upkilling - Améliorer les compétences et les connaissances en matière d'API", "description": "Fournir des formations et des ressources pour améliorer les compétences et les connaissances en matière d'API dans l'ensemble de l'organisation." }, { "id": "operating-guidelines", "title": "Lignes directrices opérationnelles - Établir une gouvernance de l'API", "description": "Établir des lignes directrices opérationnelles et des pratiques de gouvernance pour garantir une gestion et une qualité cohérentes de l'API." }, { "id": "portfolio-management", "title": "Gestion de portefeuille - Gérer efficacement le portefeuille d'API", "description": "Gérer efficacement le portefeuille d'API afin de garantir l'alignement sur les objectifs de l'entreprise et les initiatives stratégiques." }, { "id": "budget-and-resource-management", "title": "Gestion du budget et des ressources - Optimiser les investissements dans l'API", "description": "Optimiser la gestion du budget et des ressources pour les initiatives API afin de garantir l'efficacité des investissements et de l'affectation des ressources." } ] }, "de": { "routeProfiles": [ { "id": "api-product-owner", "stakeholderId": "api-product-owner", "title": "API Product Owner", "summary": "Steuert API-Chance, Priorisierung und produktbezogene Entscheidungen über den gesamten Lebenszyklus hinweg." }, { "id": "api-architect", "stakeholderId": "api-architect", "title": "API-Architekt", "summary": "Verantwortet API-Architektur, Entwurfsprinzipien und die Qualität der Schnittstellenverträge." }, { "id": "api-designer", "stakeholderId": "api-designer", "title": "API-Designer", "summary": "Gestaltet Schnittstellenvertrag, Interaktionsmodell, Konsistenz, Benutzerfreundlichkeit und bereitgestellte Capabilities." }, { "id": "api-engineer", "stakeholderId": "api-engineer", "title": "API-Entwickler", "summary": "Verantwortet Implementierung, Automatisierung, Tests und Release-Abläufe, die für die zuverlässige Bereitstellung der Capability, API oder Automatisierung erforderlich sind." }, { "id": "automation-engineer", "stakeholderId": "automation-engineer", "title": "Automatisierungsingenieur", "summary": "Implementiert, testet, integriert und betreibt Automatisierungslösungen und unterstützende Workflows." }, { "id": "automation-owner", "stakeholderId": "automation-owner", "title": "Automatisierungsverantwortlicher", "summary": "Verantwortet Ziele, Geschäftswert, Prioritäten, Kontrollen und Lebenszyklusergebnisse der Automatisierung." }, { "id": "business-owner", "stakeholderId": "business-owner", "title": "Business Owner", "summary": "Vertritt Geschäftsziele, Finanzierung und erwartete Ergebnisse der Capability-, API- oder Automatisierungsinitiative." }, { "id": "capability-owner", "stakeholderId": "capability-owner", "title": "Capability Owner", "summary": "Verantwortet Vision, Wert, Prioritäten, Lebenszyklus und Wiederverwendung der Capability über Nutzer hinweg." }, { "id": "compliance-specialist", "stakeholderId": "compliance-specialist", "title": "Compliance- und Rechtsexperte", "summary": "Klärt rechtliche, Datenschutz-, regulatorische und vertragliche Anforderungen, die Capability, API, Schnittstelle oder Automatisierung betreffen." }, { "id": "domain-specialist", "stakeholderId": "domain-specialist", "title": "Domain-Experte", "summary": "Bringt tiefes Wissen über Geschäftsdomäne, Konzepte, Regeln und Einschränkungen ein, die die Capability oder Schnittstelle widerspiegeln muss." }, { "id": "governance-specialist", "stakeholderId": "governance-specialist", "title": "Governance-Verantwortlicher", "summary": "Repräsentiert Überprüfung, Auditierung und organisationsweite Governance-Praktiken für API-Qualität und Konformität." }, { "id": "integration-architect", "stakeholderId": "integration-architect", "title": "Integrationsarchitekt", "summary": "Entwirft Integrationsansätze und Implementierungsstile, die die Capability oder API mit anderen Systemen verbinden." }, { "id": "customer-specialist", "stakeholderId": "customer-specialist", "title": "Kunden- oder Partnervertreter", "summary": "Vertritt die Perspektive von Kunden oder Partnern hinsichtlich Journey, Wert und Zusammenarbeitsmodell." }, { "id": "partner-specialist", "stakeholderId": "partner-specialist", "title": "Partner- und Lieferantenmanager", "summary": "Koordiniert externe Partner-, Lieferanten- oder Anbieterbeziehungen, die Capability- oder API-Strategie und Umsetzung beeinflussen." }, { "id": "platform-architect", "stakeholderId": "platform-architect", "title": "Plattform-Architekt", "summary": "Leitet Entscheidungen zu Plattform, Integration, Skalierbarkeit und Architektur, die beeinflussen, wie die Capability oder API erstellt und betrieben wird." }, { "id": "platform-owner", "stakeholderId": "platform-owner", "title": "Plattformverantwortlicher", "summary": "Verantwortet Plattform-Capabilities, Roadmap, Betriebsmodell und Serviceerwartungen." }, { "id": "process-owner", "stakeholderId": "process-owner", "title": "Prozessverantwortlicher", "summary": "Verantwortet den zu automatisierenden Geschäftsprozess, einschließlich Ziele, Regeln, Ergebnisse und Verbesserungsprioritäten." }, { "id": "security-specialist", "stakeholderId": "security-specialist", "title": "Sicherheitsspezialist", "summary": "Stellt sicher, dass Sicherheitsrisiken, Kontrollen und Vertrauensgrenzen über den gesamten Lebenszyklus hinweg berücksichtigt werden." }, { "id": "api-devrel-specialist", "stakeholderId": "api-devrel-specialist", "title": "Verantwortlicher für Dokumentation und DevRel", "summary": "Verantwortet Onboarding-Inhalte, Entwicklerkommunikation und Dokumentationsqualität für API-Nutzer." }, { "id": "operations-specialist", "stakeholderId": "operations-specialist", "title": "Verantwortlicher für Support und Betrieb", "summary": "Repräsentiert Runtime-Support, Vorfallbehandlung, Beobachtbarkeit und operative Bereitschaft für Capability, API oder Automatisierung." }, { "id": "api-consumer-specialist", "stakeholderId": "api-consumer-specialist", "title": "Vertreter der API-Nutzer", "summary": "Vertritt die Anforderungen von Entwicklern, Integratoren und anderen Nutzern der API." } ], "lines": [ { "id": "business-opportunities-line", "slug": "business-opportunities-line", "title": "Linie Geschäftsmöglichkeiten", "description": "Konzentriert sich auf die Identifizierung, Bewertung und Produktisierung von Geschäftsmöglichkeiten als wiederverwendbare Capabilities.", "icon": "", "color": "#26b309", "stations": [ "monitoring-and-improving", "api-product-strategy", "user-experience", "market-insights", "business-goals", "competitive-analysis", "ecosystem-vision" ] }, { "id": "platform-architecture-line", "slug": "platform-architecture-line", "title": "Linie Plattformarchitektur", "description": "Behandelt Architekturentscheidungen für Plattformen, Integrationen und Schnittstellen.", "icon": "", "color": "#933469", "stations": [ "api-product-strategy", "api-consumer-experience", "api-platform-architecture", "scalable-infrastructure", "legal-and-compliance", "security-and-privacy", "design-standards", "vendor-management" ] }, { "id": "api-design-line", "slug": "api-design-line", "title": "API-Entwurfslinie", "description": "Konzentriert sich auf Entwurfsprinzipien und Best Practices für Schnittstellen und Integrationslösungen.", "icon": "", "color": "#db9b0c", "stations": [ "api-platform-architecture", "api-design", "api-delivery", "api-audit" ] }, { "id": "delivery-line", "slug": "delivery-line", "title": "Bereitstellungslinie", "description": "Behandelt Implementierung, Tests, Automatisierung und Bereitstellungspraktiken.", "icon": "", "color": "#db9b0c", "stations": [ "api-delivery", "contract-design", "development", "ci-cd", "test-automation", "release-management" ] }, { "id": "publishing-and-adoption-line", "slug": "publishing-and-adoption-line", "title": "Linie Veröffentlichung & Enablement", "description": "Konzentriert sich auf die Veröffentlichung von Capabilities sowie deren Auffindbarkeit, Onboarding und Nutzung.", "icon": "", "color": "#17C6E9", "stations": [ "api-audit", "api-publishing", "monitoring-and-improving", "service-agreements", "api-consumer-adoption", "api-promotion", "partner-integration" ] }, { "id": "operating-model-line", "slug": "operating-model-line", "title": "Linie Betriebsmodell", "description": "Behandelt Governance, Verantwortlichkeiten und das Betriebsmodell für Capabilities.", "icon": "", "color": "#1a3987", "stations": [ "api-product-strategy", "api-mindset", "roles-and-responsibilities", "upskilling", "operating-guidelines", "portfolio-management", "budget-and-resource-management" ] } ], "cycles": [ { "id": "capability-productization-cycle", "slug": "capability-productization-cycle", "title": "Capability-Produktisierungszyklus", "description": "Ein Zyklus, um Geschäftsfähigkeiten in wiederverwendbare digitale Capabilities zu überführen, bevor die Umsetzungsweise gewählt wird.", "stations": [ { "id": "api-product-strategy", "title": "Capability-Strategie", "description": "Rahmen Sie den Geschaeftsbedarf als wiederverwendbare Capability mit klarem Wert, Nutzern, Ownership und Geschaeftszielen, bevor der Implementierungsstil gewaehlt wird." }, { "id": "api-consumer-experience", "title": "Nutzeranforderungen & Onboarding", "description": "Erfassen Sie Nutzeranforderungen, Onboarding-Bedarf, Einschränkungen, Serviceerwartungen und Verantwortlichkeiten der Anbieter." }, { "id": "api-platform-architecture", "title": "Architektur & Plattformentscheidungen", "description": "Nutzen Sie Anforderungen und Einschraenkungen, um Implementierungsstil, Architekturpattern und ermoeglichende Plattformfaehigkeiten auszuwaehlen." }, { "id": "api-design", "title": "Lösungs- & Schnittstellendesign", "description": "Entwerfen Sie den Schnittstellenvertrag und das Interaktionsmodell für die gewählte Umsetzungsweise." }, { "id": "api-delivery", "title": "Bereitstellung & Betrieb", "description": "Bauen, testen, veröffentlichen und betreiben Sie die Capability mit der gewählten Umsetzungsweise und dem validierten Schnittstellenvertrag." }, { "id": "api-audit", "title": "Qualitäts- & Bereitschaftssicherung", "description": "Validieren Sie Schnittstellenvertrag, Kontrollen, Dokumentation, Supportmodell und operative Bereitschaft vor der Veroeffentlichung." }, { "id": "api-publishing", "title": "Veroeffentlichung & Enablement", "description": "Veroeffentlichen Sie die Capability, damit Nutzer sie finden, bewerten, Zugriff beantragen, das Onboarding abschliessen, sie nutzen und Support erhalten koennen." }, { "id": "monitoring-and-improving", "title": "Monitoring & Verbesserung", "description": "Überwachen Sie Capability-Gesundheit, Nutzerergebnisse, Zuverlässigkeit, Wiederverwendung und Verbesserungsmöglichkeiten." } ] }, { "id": "api-productization-cycle", "slug": "api-productization-cycle", "title": "API-Produktisierungszyklus", "description": "Die API-fokussierte APIOps-Cycles-Journey für Produktisierung, Design, Bereitstellung, Veröffentlichung und Verbesserung von APIs.", "stations": [ { "id": "api-product-strategy", "title": "API-Produktstrategie", "description": "Bevor Sie etwas bauen, sollten Sie von Anfang an den Wert, die Benutzer und die Geschäftsziele Ihrer API definieren." }, { "id": "api-consumer-experience", "title": "API Consumer Experience", "description": "Stellen Sie sicher, dass Ihre API auffindbar, verständlich und nutzbar ist - vor und nach der Einführung." }, { "id": "api-platform-architecture", "title": "API-Plattformarchitektur", "description": "Gewährleisten Sie Skalierbarkeit, Wiederverwendung und Governance für Ihre API- und Plattformkomponenten." }, { "id": "api-design", "title": "API-Design", "description": "Erstellen Sie API-Designs, die konsistent, wiederverwendbar und auf Geschäftszielen und gemeinsamen Standards basieren." }, { "id": "api-delivery", "title": "API-Bereitstellung", "description": "Erstellen, Testen und Freigeben von APIs unter Verwendung moderner Bereitstellungspipelines und bewährter technischer Verfahren." }, { "id": "api-audit", "title": "API-Audit", "description": "Stellen Sie sicher, dass APIs vor der Veröffentlichung und Bereitstellung den geschäftlichen, gestalterischen und betrieblichen Standards entsprechen." }, { "id": "api-publishing", "title": "API-Veröffentlichung", "description": "Stellen Sie APIs mit der richtigen Dokumentation und den richtigen Prozessen sicher und klar für die richtige Zielgruppe bereit." }, { "id": "monitoring-and-improving", "title": "API-Monitoring & Verbesserung", "description": "Nutzen Sie Messgrößen und Feedback, um die API-Leistung zu verfolgen und kontinuierliche Verbesserungen voranzutreiben." } ] }, { "id": "integration-productization-cycle", "slug": "integration-productization-cycle", "title": "Integrationszyklus", "description": "Ein Zyklus zur Produktisierung wiederverwendbarer Integrations-Capabilities, bevor der Implementierungsstil gewaehlt wird.", "stations": [ { "id": "api-product-strategy", "title": "Integrations-Capability-Strategie", "description": "Rahmen Sie die wiederverwendbare Integrations-Capability, den Geschaeftsbedarf, Ownership und erwartete Wiederverwendung, bevor der Implementierungsstil gewaehlt wird." }, { "id": "api-consumer-experience", "title": "Integrationsnutzeranforderungen & Onboarding", "description": "Erfassen Sie Integrationsnutzer, Anbieter-Verantwortlichkeiten, Onboarding-Bedarf, Serviceerwartungen und operative Einschränkungen." }, { "id": "api-platform-architecture", "title": "Integrationsarchitektur & Plattformentscheidungen", "description": "Waehlen Sie Integrationsarchitektur, Implementierungsstil und Plattformfaehigkeiten unter Beruecksichtigung von Einschraenkungen und Governance-Modell." }, { "id": "api-design", "title": "Integrationsdesign", "description": "Entwerfen Sie Schnittstellenvertrag, Schemas, Payloads und Interaktionsmuster fuer den gewaehlten Integrationsstil." }, { "id": "api-delivery", "title": "Integrationsbereitstellung & Betrieb", "description": "Bauen, testen, automatisieren, deployen und betreiben Sie die Integrations-Capability mit dem gewaehlten Implementierungsstil und dem validierten Schnittstellenvertrag." }, { "id": "api-audit", "title": "Integrationsbereitschaftssicherung", "description": "Sichern Sie Integrationsbereitschaft, Governance, Qualität, Sicherheit, Compliance und operative Nachweise vor der Veröffentlichung ab." }, { "id": "api-publishing", "title": "Integrationsveroeffentlichung & Enablement", "description": "Veroeffentlichen Sie die Integrations-Capability, damit Teams sie finden, bewerten, Zugriff beantragen, das Onboarding abschliessen, wiederverwenden und Support erhalten koennen." }, { "id": "monitoring-and-improving", "title": "Integrationsmonitoring & Verbesserung", "description": "Überwachen Sie Integrationszuverlässigkeit, Wiederverwendung, Incidents, Performance, Nutzerergebnisse und Verbesserungsbedarf." } ] }, { "id": "automation-cycle", "slug": "automation-cycle", "title": "Automatisierungszyklus", "description": "Ein Zyklus zum Identifizieren, Entwerfen, Bereitstellen, Enablement und Verbessern von Automatisierungsmöglichkeiten.", "stations": [ { "id": "api-product-strategy", "title": "Automatisierungschance & Strategie", "description": "Identifizieren und priorisieren Sie Automatisierungsmöglichkeiten nach Wert, Machbarkeit, Risiko, Ownership und erwarteter Prozesswirkung." }, { "id": "api-consumer-experience", "title": "Prozess-/Nutzeranforderungen", "description": "Erfassen Sie Prozessnutzer, Rollen, Übergaben, Ausnahmen, Einschränkungen und Serviceerwartungen, bevor die Automatisierung entworfen wird." }, { "id": "api-platform-architecture", "title": "Automatisierungsplattformentscheidung", "description": "Waehlen Sie Automatisierungsplattform, Runtime, Integrationsansatz, Governance-Kontrollen und operative Einschraenkungen." }, { "id": "api-design", "title": "Automatisierungs-Workflow-Design", "description": "Entwerfen Sie Automatisierungsworkflow, Trigger, Entscheidungspunkte, Integrationen, Datenverarbeitung, relevante Schnittstellenvertraege und Ausnahmefaelle." }, { "id": "api-delivery", "title": "Automatisierungsbereitstellung & Betrieb", "description": "Bauen, testen, deployen, dokumentieren und betreiben Sie die Automatisierung mit klarer Ownership, Kontrollen und Rollback-Pfaden." }, { "id": "api-audit", "title": "Automatisierungsbereitschaftsprüfung", "description": "Prüfen Sie Automatisierungsbereitschaft, Qualität, Risiko, Compliance, menschliche Aufsicht, Nachweise und Freigabekriterien." }, { "id": "api-publishing", "title": "Automatisierungs-Rollout & Enablement", "description": "Befähigen Sie Nutzer und Betreiber mit Auffindbarkeit, Onboarding, Betriebsanweisungen, Supportpfaden und Änderungs kommunikation." }, { "id": "monitoring-and-improving", "title": "Automatisierungsmonitoring & Verbesserung", "description": "Überwachen Sie Automatisierungsleistung, Ausnahmen, Zuverlässigkeit, Nutzerergebnisse, operative Auswirkungen und Verbesserungsmöglichkeiten." } ] } ], "stations": [ { "id": "api-product-strategy", "title": "Strategie", "description": "Beschreiben Sie den Geschäftsbedarf als wiederverwendbare Capability, bevor Sie die Umsetzungsweise festlegen." }, { "id": "user-experience", "title": "Benutzerfreundlichkeit - Entwerfen Sie APIs mit dem Benutzer im Hinterkopf", "description": "Stellen Sie sicher, dass die APIs mit Blick auf den Endnutzer entwickelt werden und eine nahtlose und intuitive Erfahrung bieten." }, { "id": "api-consumer-experience", "title": "Nutzeranforderungen & Onboarding", "description": "Erfassen Sie Nutzeranforderungen, Onboarding, Standards, nicht-funktionale Anforderungen, Serviceerwartungen, Einschränkungen, Sicherheitsbedarf, Protokolle, Datenaktualität, SLAs, Observability, Wiederherstellung, Adoption und Verantwortlichkeiten der Anbieter." }, { "id": "market-insights", "title": "Markteinblicke - Verstehen Sie die API-Landschaft", "description": "Analysieren Sie Markttrends, APIs von Mitbewerbern und Industriestandards, um eine API-Strategie zu entwickeln." }, { "id": "api-platform-architecture", "title": "Architektur & Plattformentscheidungen", "description": "Nutzen Sie Anforderungen und Einschränkungen, um Architektur, Plattformfähigkeiten, Governance und Betriebsmodell zu wählen." }, { "id": "business-goals", "title": "Geschäftsziele - APIs an Geschäftszielen ausrichten", "description": "Sicherstellen, dass die APIs mit den Geschäftszielen übereinstimmen und zu den allgemeinen Unternehmenszielen beitragen." }, { "id": "api-design", "title": "Lösungs- & Schnittstellendesign", "description": "Entwerfen Sie die gewählte Umsetzungsweise, den Schnittstellenvertrag, Interaktionsmuster, Datenstrukturen und Nutzungsdetails vor der Implementierung." }, { "id": "competitive-analysis", "title": "Wettbewerbsanalyse - Vorsprung auf dem API-Markt", "description": "Analysieren Sie die APIs der Wettbewerber, um Stärken, Schwächen und Möglichkeiten zur Differenzierung zu ermitteln." }, { "id": "api-delivery", "title": "Bereitstellung & Betrieb", "description": "Setzen Sie die gewählte Umsetzungsweise mit geeigneten Engineering-, Test-, Sicherheits-, Automatisierungs- und Betriebspraktiken um." }, { "id": "ecosystem-vision", "title": "Ökosystem-Vision - Aufbau von APIs für ein florierendes Ökosystem", "description": "Entwickeln Sie eine Vision dafür, wie Ihre APIs in ein größeres Ökosystem passen, das Zusammenarbeit und Innovation ermöglicht." }, { "id": "api-audit", "title": "Qualitäts- & Bereitschaftssicherung", "description": "Prüfen Sie Schnittstellenvertrag, Kontrollen, Supportmodell, Observability, Dokumentation und Lifecycle-Bereitschaft vor der Veröffentlichung." }, { "id": "scalable-infrastructure", "title": "Skalierbare Infrastruktur - APIs auf einem soliden Fundament aufbauen", "description": "Stellen Sie sicher, dass Ihre API-Infrastruktur skalierbar ist, um der wachsenden Nachfrage gerecht zu werden und eine hohe Verfügbarkeit zu gewährleisten." }, { "id": "api-publishing", "title": "Veröffentlichung & Enablement", "description": "Veröffentlichen Sie Capability-Informationen so, dass Nutzer sie finden, bewerten, Zugriff beantragen, onboarden, nutzen und Support erhalten können." }, { "id": "legal-and-compliance", "title": "Rechtliche Aspekte und Einhaltung von Vorschriften - Sicherstellen, dass APIs den regulatorischen Standards entsprechen", "description": "Stellen Sie sicher, dass APIs den gesetzlichen und behördlichen Anforderungen entsprechen, um Ihr Unternehmen und Ihre Benutzer zu schützen." }, { "id": "monitoring-and-improving", "title": "Monitoring & Verbesserung", "description": "Überwachen Sie Nutzung, Zuverlässigkeit, Datenqualität, Nutzerergebnisse, Betriebskosten und Wiederverwendungsmöglichkeiten nach der Veröffentlichung." }, { "id": "security-and-privacy", "title": "Sicherheit und Datenschutz - Schützen Sie Ihre APIs und Benutzer", "description": "Implementierung von Sicherheits- und Datenschutzmaßnahmen zum Schutz von APIs und Nutzerdaten vor Bedrohungen und Verstößen." }, { "id": "design-standards", "title": "Designstandards - Sicherstellung eines konsistenten und qualitativ hochwertigen API-Designs", "description": "Festlegung von Designstandards und -richtlinien, um ein einheitliches und hochwertiges API-Design im gesamten Unternehmen zu gewährleisten." }, { "id": "vendor-management", "title": "Vendor Management - Verwalten von API-Integrationen von Drittanbietern", "description": "Effiziente Verwaltung von Drittanbieter-APIs und Integrationen zur Gewährleistung von Zuverlässigkeit und Compliance." }, { "id": "contract-design", "title": "Vertragsgestaltung - Definieren Sie klare Schnittstellenverträge", "description": "Erstellen Sie klare und genau definierte Schnittstellenverträge, die Erwartungen, Verantwortlichkeiten und Nutzungsrichtlinien umreißen." }, { "id": "development", "title": "Entwicklung - Erstellen von APIs mit bewährten Praktiken", "description": "Implementierung von APIs unter Verwendung von Best Practices und Frameworks zur Gewährleistung von Qualität, Wartbarkeit und Skalierbarkeit." }, { "id": "ci-cd", "title": "CI/CD - Automatisierte API-Bereitstellung", "description": "Implementieren Sie Pipelines für kontinuierliche Integration und kontinuierliche Bereitstellung (CI/CD), um die API-Bereitstellung zu automatisieren und eine gleichbleibende Qualität zu gewährleisten." }, { "id": "test-automation", "title": "Testautomatisierung - Sicherung der API-Qualität", "description": "Implementieren Sie automatisierte Testverfahren, um die Qualität, Zuverlässigkeit und Leistung von APIs sicherzustellen." }, { "id": "release-management", "title": "Release Management - Effektive Verwaltung von API-Releases", "description": "Implementierung von Release-Management-Verfahren zur Gewährleistung reibungsloser und kontrollierter API-Releases." }, { "id": "service-agreements", "title": "Servicevereinbarungen - Definieren Sie API-Service-Levels", "description": "Erstellen Sie Dienstleistungsvereinbarungen, in denen die Erwartungen, das Leistungsniveau und die Zuständigkeiten von API-Anbietern und Kunden festgelegt sind." }, { "id": "api-consumer-adoption", "title": "Nutzerakzeptanz - Förderung der API-Nutzung", "description": "Implementierung von Strategien zur Förderung der Akzeptanz und des Engagements von Nutzer, um sicherzustellen, dass APIs effektiv genutzt werden." }, { "id": "api-promotion", "title": "API-Promotion - Erhöhen Sie die Sichtbarkeit und Nutzung von APIs", "description": "Förderung von APIs, um die Sichtbarkeit, Nutzung und Akzeptanz bei den Zielgruppen zu erhöhen." }, { "id": "partner-integration", "title": "Partnerintegration - Zusammenarbeit mit Partnern", "description": "Erleichtern Sie die Integration von Partnern, um die API-Funktionen zu verbessern und die Reichweite zu erhöhen." }, { "id": "api-mindset", "title": "API-Mentalität - Fördern Sie eine API-First-Kultur", "description": "Fördern Sie eine API-zentrierte Denkweise im gesamten Unternehmen, um Innovation und Zusammenarbeit voranzutreiben." }, { "id": "roles-and-responsibilities", "title": "Rollen und Zuständigkeiten - API-Team-Strukturen definieren", "description": "Definieren Sie klare Rollen und Verantwortlichkeiten für API-Teams, um eine effektive Zusammenarbeit und Verantwortlichkeit zu gewährleisten." }, { "id": "upskilling", "title": "Upskilling - Erweiterung der API-Fähigkeiten und -Kenntnisse", "description": "Bereitstellung von Schulungen und Ressourcen zur Verbesserung der API-Fähigkeiten und -Kenntnisse in der gesamten Organisation." }, { "id": "operating-guidelines", "title": "Betriebsleitlinien - Einrichtung einer API-Governance", "description": "Festlegung von Betriebsrichtlinien und Governance-Praktiken zur Gewährleistung einer einheitlichen API-Verwaltung und -Qualität." }, { "id": "portfolio-management", "title": "Portfoliomanagement - Effektive Verwaltung des API-Portfolios", "description": "Effiziente Verwaltung des API-Portfolios, um die Übereinstimmung mit den Geschäftszielen und strategischen Initiativen zu gewährleisten." }, { "id": "budget-and-resource-management", "title": "Budget- und Ressourcenmanagement - Optimierung von API-Investitionen", "description": "Optimieren Sie das Budget- und Ressourcenmanagement für API-Initiativen, um eine effektive Investition und Ressourcenzuweisung zu gewährleisten." } ] }, "pt": { "routeProfiles": [ { "id": "api-architect", "stakeholderId": "api-architect", "title": "Arquiteto API", "summary": "Responsável pela arquitetura API, pelos princípios de desenho e pela qualidade dos contratos de interface." }, { "id": "integration-architect", "stakeholderId": "integration-architect", "title": "Arquiteto de integração", "summary": "Desenha abordagens de integração e estilos de implementação que ligam a capacidade ou API a outros sistemas." }, { "id": "platform-architect", "stakeholderId": "platform-architect", "title": "Arquiteto de plataforma", "summary": "Orienta decisões de plataforma, integração, escalabilidade e arquitetura que moldam como a capacidade ou API é construída e operada." }, { "id": "api-designer", "stakeholderId": "api-designer", "title": "Designer API", "summary": "Modela o contrato de interface, o modelo de interação, a consistência e a usabilidade das capacidades expostas." }, { "id": "automation-engineer", "stakeholderId": "automation-engineer", "title": "Engenheiro de automatização", "summary": "Implementa, testa, integra e mantém soluções de automatização e workflows de suporte." }, { "id": "api-engineer", "stakeholderId": "api-engineer", "title": "Engenheiro de entrega", "summary": "Responsável pela implementação, automatização, testes e fluxo de publicação necessários para entregar a capacidade, API ou automatização de forma fiável." }, { "id": "domain-specialist", "stakeholderId": "domain-specialist", "title": "Especialista de domínio", "summary": "Traz conhecimento profundo do domínio de negócio, conceitos, regras e restrições que a capacidade ou interface deve refletir." }, { "id": "compliance-specialist", "stakeholderId": "compliance-specialist", "title": "Especialista em conformidade e jurídico", "summary": "Esclarece requisitos legais, de privacidade, regulamentares e contratuais que afetam a capacidade, API, interface ou automatização." }, { "id": "security-specialist", "stakeholderId": "security-specialist", "title": "Especialista em segurança", "summary": "Garante que os riscos de segurança, controlos e fronteiras de confiança são tratados ao longo de todo o ciclo de vida." }, { "id": "partner-specialist", "stakeholderId": "partner-specialist", "title": "Gestor de parceiros ou fornecedores", "summary": "Coordena relações com parceiros, fornecedores ou prestadores externos que influenciam a estratégia e entrega da capacidade ou API." }, { "id": "customer-specialist", "stakeholderId": "customer-specialist", "title": "Representante de cliente ou parceiro", "summary": "Contribui com a perspetiva do cliente ou parceiro para o percurso, valor e modelo de colaboração." }, { "id": "api-consumer-specialist", "stakeholderId": "api-consumer-specialist", "title": "Representante dos utilizadores da API", "summary": "Representa as necessidades de programadores, integradores ou outros utilizadores que utilizam a API diretamente." }, { "id": "business-owner", "stakeholderId": "business-owner", "title": "Responsável de negócio", "summary": "Representa os objetivos de negócio, o financiamento e os resultados esperados da iniciativa de capacidade, API ou automatização." }, { "id": "automation-owner", "stakeholderId": "automation-owner", "title": "Responsável pela automatização", "summary": "Responsável pelos objetivos, valor de negócio, prioridades, controlos e resultados do ciclo de vida da automatização." }, { "id": "capability-owner", "stakeholderId": "capability-owner", "title": "Responsável pela capacidade", "summary": "Responsável pela visão, valor, prioridades, ciclo de vida e reutilização da capacidade junto dos utilizadores." }, { "id": "governance-specialist", "stakeholderId": "governance-specialist", "title": "Responsável pela governação API", "summary": "Representa práticas de revisão, auditoria e governação em toda a organização para qualidade e conformidade das APIs." }, { "id": "platform-owner", "stakeholderId": "platform-owner", "title": "Responsável pela plataforma", "summary": "Responsável pelas capacidades da plataforma, roadmap, modelo operacional e expectativas de serviço." }, { "id": "process-owner", "stakeholderId": "process-owner", "title": "Responsável pelo processo", "summary": "Responsável pelo processo de negócio a automatizar, incluindo objetivos, regras, resultados e prioridades de melhoria." }, { "id": "api-product-owner", "stakeholderId": "api-product-owner", "title": "Responsável pelo produto API", "summary": "Conduz a oportunidade API, a priorização e as decisões ao nível do produto ao longo do ciclo de vida." }, { "id": "api-devrel-specialist", "stakeholderId": "api-devrel-specialist", "title": "Responsável por documentação e DevRel", "summary": "Responsável por conteúdos de onboarding, comunicação com programadores e qualidade da documentação para utilizadores da API." }, { "id": "operations-specialist", "stakeholderId": "operations-specialist", "title": "Responsável por suporte e operações", "summary": "Representa o suporte em execução, tratamento de incidentes, observabilidade e prontidão operacional da capacidade, API ou automatização." } ], "lines": [ { "id": "business-opportunities-line", "slug": "business-opportunities-line", "title": "Linha oportunidades de negócio", "description": "Centra-se na identificação e aproveitamento de oportunidades de negócio através de APIs.", "icon": "", "color": "#26b309", "stations": [ "monitoring-and-improving", "api-product-strategy", "user-experience", "market-insights", "business-goals", "competitive-analysis", "ecosystem-vision" ] }, { "id": "platform-architecture-line", "slug": "platform-architecture-line", "title": "Linha de arquitetura da plataforma", "description": "Abrange os aspetos arquiteturais das plataformas API.", "icon": "", "color": "#933469", "stations": [ "api-product-strategy", "api-consumer-experience", "api-platform-architecture", "scalable-infrastructure", "legal-and-compliance", "security-and-privacy", "design-standards", "vendor-management" ] }, { "id": "api-design-line", "slug": "api-design-line", "title": "Linha de conceção de API", "description": "Centra-se nos princípios e práticas de conceção de APIs.", "icon": "", "color": "#db9b0c", "stations": [ "api-platform-architecture", "api-design", "api-delivery", "api-audit" ] }, { "id": "delivery-line", "slug": "delivery-line", "title": "Linha de entrega", "description": "Abrange os processos e práticas de entrega de APIs.", "icon": "", "color": "#db9b0c", "stations": [ "api-delivery", "contract-design", "development", "ci-cd", "test-automation", "release-management" ] }, { "id": "publishing-and-adoption-line", "slug": "publishing-and-adoption-line", "title": "Linha de publicação e adoção", "description": "Centra-se na publicação de APIs e na garantia da sua adoção pelos consumidores.", "icon": "", "color": "#17C6E9", "stations": [ "api-audit", "api-publishing", "monitoring-and-improving", "service-agreements", "api-consumer-adoption", "api-promotion", "partner-integration" ] }, { "id": "operating-model-line", "slug": "operating-model-line", "title": "Linha de modelo operacional", "description": "Abrange o modelo operacional para gestão e governação de API.", "icon": "", "color": "#1a3987", "stations": [ "api-product-strategy", "api-mindset", "roles-and-responsibilities", "upskilling", "operating-guidelines", "portfolio-management", "budget-and-resource-management" ] } ], "cycles": [ { "id": "capability-productization-cycle", "slug": "capability-productization-cycle", "title": "Ciclo de Produto de Capacidades", "description": "Um ciclo para transformar capacidades de negócio em capacidades digitais reutilizáveis antes de selecionar o estilo de implementação.", "stations": [ { "id": "api-product-strategy", "title": "Estrategia da capacidade", "description": "Antes de construir qualquer coisa, defina o valor, os consumidores, a propriedade e os objetivos de negócio da capacidade." }, { "id": "api-consumer-experience", "title": "Requisitos e onboarding de utilizadores", "description": "Recolha requisitos de integração dos consumidores, normas, requisitos não funcionais, expectativas de serviço, restrições, necessidades de segurança, protocolos permitidos, atualidade dos dados, SLAs, observabilidade, recuperação, requisitos de adoção e responsabilidades dos produtores." }, { "id": "api-platform-architecture", "title": "Decisões de arquitetura e plataforma", "description": "Utilize requisitos e restrições para decidir o padrão de arquitetura certo e as capacidades de plataforma de suporte." }, { "id": "api-design", "title": "Conceção da solução e da interface", "description": "Conceba o contrato de interface e o modelo de interação para o estilo de disponibilização selecionado." }, { "id": "api-delivery", "title": "Entrega e operações", "description": "Construa, teste, disponibilize e opere a capacidade usando o estilo de disponibilização selecionado e o contrato de interface validado." }, { "id": "api-audit", "title": "Garantia de qualidade e prontidão", "description": "Audite o contrato de interface, os controlos, o modelo de suporte, a observabilidade, a documentação e a prontidão de ciclo de vida da capacidade antes da disponibilização." }, { "id": "api-publishing", "title": "Publicacao e enablement", "description": "Publique informação sobre a capacidade reutilizável para que os consumidores a possam descobrir, solicitar, integrar, utilizar e obter suporte." }, { "id": "monitoring-and-improving", "title": "Monitorização e melhoria", "description": "Monitorize a utilização, fiabilidade, qualidade dos dados, resultados dos consumidores, custo operacional e oportunidades de reutilização após a disponibilização." } ] }, { "id": "api-productization-cycle", "slug": "api-productization-cycle", "title": "Ciclo de Produto de API", "description": "A jornada APIOps Cycles focada em API para transformar APIs em produto, concebê-las, entregá-las, publicá-las e melhorá-las.", "stations": [ { "id": "api-product-strategy", "title": "Estratégia de produto API", "description": "Antes de construir qualquer coisa, defina o valor da sua API, os utilizadores e os objetivos de negócio desde o primeiro dia." }, { "id": "api-consumer-experience", "title": "Experiência do consumidor da API", "description": "Certifique-se de que a sua API é detetável, compreensível e utilizável - antes e depois do lançamento." }, { "id": "api-platform-architecture", "title": "Arquitetura da plataforma API", "description": "Garanta a escalabilidade, a reutilização e a governação da sua API e dos componentes da plataforma." }, { "id": "api-design", "title": "Conceção da API", "description": "Criar conceções de API que sejam consistentes, reutilizáveis e baseados na intenção de negócios e em padrões compartilhados." }, { "id": "api-delivery", "title": "Entrega da API", "description": "Criar, testar e lançar APIs usando pipelines de entrega modernos e boas práticas de engenharia." }, { "id": "api-audit", "title": "Auditoria da API", "description": "Valide se as APIs satisfazemos padrões de negócio, conceção e operacionais antes da publicação e exposição." }, { "id": "api-publishing", "title": "Publicação da API", "description": "Exponha as APIs de forma segura e clara ao público certo com a documentação e os processos corretos." }, { "id": "monitoring-and-improving", "title": "Monitorizacao e melhoria da API", "description": "Utilizar métricas e feedback para acompanhar o desempenho da API e promover a melhoria contínua." } ] }, { "id": "integration-productization-cycle", "slug": "integration-productization-cycle", "title": "Ciclo de Produto de Integração", "description": "Um ciclo para transformar capacidades de integracao reutilizaveis em produto antes de selecionar o estilo de implementacao.", "stations": [ { "id": "api-product-strategy", "title": "Estratégia da capacidade de integração", "description": "Enquadrar a capacidade de integracao reutilizavel, a necessidade de negocio, o ownership e a reutilizacao esperada antes de selecionar o estilo de implementacao." }, { "id": "api-consumer-experience", "title": "Requisitos e integração de consumidores da integração", "description": "Recolha consumidores da integração, responsabilidades dos fornecedores, necessidades de integração, expectativas de serviço e restrições operacionais." }, { "id": "api-platform-architecture", "title": "Arquitetura de integracao e decisoes de plataforma", "description": "Selecionar a arquitetura de integracao, o estilo de implementacao e as capacidades de plataforma, tendo em conta as restricoes e o modelo de governacao." }, { "id": "api-design", "title": "Conceção da solução de integração", "description": "Conceber o contrato de interface, os esquemas, os payloads e os padroes de interacao para o estilo de integracao selecionado." }, { "id": "api-delivery", "title": "Entrega e operações da integração", "description": "Construir, testar, automatizar, disponibilizar e operar a capacidade de integracao usando o estilo de implementacao selecionado e o contrato de interface validado." }, { "id": "api-audit", "title": "Garantia de prontidão da integração", "description": "Assegure a prontidão, a governação, a qualidade, a segurança, a conformidade e as evidências operacionais da integração antes da disponibilização." }, { "id": "api-publishing", "title": "Publicacao e enablement da integracao", "description": "Publicar a capacidade de integracao para que as equipas a possam descobrir, avaliar, solicitar acesso, concluir o onboarding, reutiliza-la e obter suporte." }, { "id": "monitoring-and-improving", "title": "Monitorização e melhoria da integração", "description": "Monitorize a fiabilidade da integração, a reutilização, os incidentes, o desempenho, os resultados dos consumidores e as necessidades de melhoria." } ] }, { "id": "automation-cycle", "slug": "automation-cycle", "title": "Ciclo de Automação", "description": "Um ciclo para identificar, conceber, entregar, capacitar e melhorar oportunidades de automação.", "stations": [ { "id": "api-product-strategy", "title": "Estratégia da oportunidade de automação", "description": "Identifique e priorize oportunidades de automação por valor, viabilidade, risco, propriedade e impacto esperado no processo." }, { "id": "api-consumer-experience", "title": "Requisitos do processo e dos utilizadores", "description": "Recolha utilizadores do processo, funções, transferências, exceções, restrições e expectativas de serviço antes de conceber a automação." }, { "id": "api-platform-architecture", "title": "Decisão de plataforma de automação", "description": "Escolher a plataforma de automacao, o runtime, a abordagem de integracao, os controlos de governacao e as restricoes operacionais." }, { "id": "api-design", "title": "Conceção do fluxo de trabalho de automação", "description": "Conceber o fluxo de trabalho de automacao, os gatilhos, os pontos de decisao, as integracoes, o tratamento de dados, os contratos de interface relevantes e os caminhos de excecao." }, { "id": "api-delivery", "title": "Entrega e operacao da automacao", "description": "Construa, teste, disponibilize, documente e opere a automação com propriedade, controlos e caminhos de reversão claros." }, { "id": "api-audit", "title": "Revisão de prontidão da automação", "description": "Reveja a prontidão, a qualidade, o risco, a conformidade, a supervisão humana, as evidências e os critérios de disponibilização da automação." }, { "id": "api-publishing", "title": "Rollout e enablement da automacao", "description": "Capacite utilizadores e operadores com descoberta, integração, instruções operacionais, caminhos de suporte e comunicação de alterações." }, { "id": "monitoring-and-improving", "title": "Monitorização e melhoria da automação", "description": "Monitorize o desempenho da automação, exceções, fiabilidade, resultados dos utilizadores, impacto operacional e oportunidades de melhoria." } ] } ], "stations": [ { "id": "api-product-strategy", "title": "Estratégia de produtos API - Transforme APIs em produtos estratégicos", "description": "Antes de construir qualquer coisa, defina o valor da sua API, os utilizadores e os objetivos de negócio desde o primeiro dia." }, { "id": "user-experience", "title": "Experiência do utilizador - Conceber APIs com o utilizador em mente", "description": "Assegurar que as APIs são concebidas tendo em mente o utilizador final, proporcionando uma experiência intuitiva e sem descontinuidades." }, { "id": "api-consumer-experience", "title": "Experiência do consumidor da API - Conceção para os utilizadores reais da sua API", "description": "Certifique-se de que a sua API é detetável, compreensível e utilizável - antes e depois do lançamento." }, { "id": "market-insights", "title": "Informações sobre o mercado - Compreender o cenário das API", "description": "Analisar as tendências do mercado, as APIs da concorrência e as normas da indústria para informar a estratégia de API." }, { "id": "api-platform-architecture", "title": "Arquitetura da plataforma API - Arquitetar APIs para escalabilidade e reutilização", "description": "Garanta a escalabilidade, a reutilização e a governação da sua API e dos componentes da plataforma." }, { "id": "business-goals", "title": "Objectivos comerciais - Alinhar as APIs com os objetivos de negócio", "description": "Assegurar que as APIs estão alinhadas com os objetivos de negócio e contribuem para os objetivos organizacionais globais." }, { "id": "api-design", "title": "Conceção da API - Conceber APIs que proporcionem valor", "description": "Criar conceções de API que sejam consistentes, reutilizáveis e baseados na intenção de negócios e em padrões compartilhados." }, { "id": "competitive-analysis", "title": "Análise competitiva - Fique à frente no mercado de API", "description": "Analisar as APIs dos concorrentes para identificar pontos fortes, pontos fracos e oportunidades de diferenciação." }, { "id": "api-delivery", "title": "Entrega da API - Fornecer APIs seguras e fiáveis", "description": "Criar, testar e lançar APIs usando pipelines de entrega modernos e boas práticas de engenharia." }, { "id": "ecosystem-vision", "title": "Visão do ecossistema - Criar APIs para um ecossistema próspero", "description": "Crie uma visão de como as suas APIs se encaixam num ecossistema maior, permitindo a colaboração e a inovação." }, { "id": "api-audit", "title": "Auditoria de API - Auditoria de APIs para conformidade e qualidade", "description": "Valide se as APIs satisfazemos padrões de negócio, conceção e operacionais antes da publicação e exposição." }, { "id": "scalable-infrastructure", "title": "Infraestrutura escalável - Construir APIs sobre uma base sólida", "description": "Certifique-se de que a sua infraestrutura de API pode ser dimensionada para responder à crescente procura e suportar uma elevada disponibilidade." }, { "id": "api-publishing", "title": "Publicação de API - Publique APIs com confiança", "description": "Exponha as APIs de forma segura e clara ao público certo com a documentação e os processos corretos." }, { "id": "legal-and-compliance", "title": "Legal e Conformidade - Garantir que as APIs cumprems normas regulamentares", "description": "Garanta que as APIs cumprem os requisitos legais e regulamentares, protegendo a sua organização e os seus utilizadores." }, { "id": "monitoring-and-improving", "title": "Monitorização e melhoria - para valor API", "description": "Utilizar métricas e feedback para acompanhar o desempenho da API e promover a melhoria contínua." }, { "id": "security-and-privacy", "title": "Segurança e privacidade - Proteja as suas APIs e os seus utilizadores", "description": "Implementar medidas de segurança e privacidade para proteger as APIs e os dados dos utilizadores contra ameaças e violações." }, { "id": "design-standards", "title": "Normas de conceção - Garantir uma conceção de API consistente e de alta qualidade", "description": "Estabelecer normas e diretrizes de design para garantir um design API consistente e de alta qualidade em toda a organização." }, { "id": "vendor-management", "title": "Gestão de fornecedores - Gerir integrações de APIs de terceiros", "description": "Gerir eficazmente os fornecedores e as integrações de API de terceiros para garantir a fiabilidade e a conformidade." }, { "id": "contract-design", "title": "Conceção de contratos - Definir contratos de interface da API claros", "description": "Criar contratos de interface da API claros e bem definidos que descrevam as expectativas, responsabilidades e diretrizes de utilização." }, { "id": "development", "title": "Desenvolvimento - Criar APIs com as boas práticas", "description": "Implementar APIs utilizando as boas práticas e estruturas para garantir a qualidade, a capacidade de manutenção e a escalabilidade." }, { "id": "ci-cd", "title": "CI/CD - Automatizar a entrega da API", "description": "Implementar pipelines de integração contínua e entrega contínua (CI/CD) para automatizar a entrega de API e garantir uma qualidade consistente." }, { "id": "test-automation", "title": "Automatização de testes - Garantir a qualidade da API", "description": "Implementar práticas de teste automatizadas para garantir a qualidade, fiabilidade e desempenho da API." }, { "id": "release-management", "title": "Gestão de versões - Gerir eficazmente as versões da API", "description": "Implementar práticas de gestão de lançamentos para garantir lançamentos de API sem problemas e controlados." }, { "id": "service-agreements", "title": "Acordos de serviço - Definir níveis de serviço de API", "description": "Estabelecer acordos de serviço que definam as expectativas, os níveis de serviço e as responsabilidades dos fornecedores e consumidores de API." }, { "id": "api-consumer-adoption", "title": "Adoção pelo consumidor da API - Impulsionar a utilização da API", "description": "Implementar estratégias para promover a adoção e o envolvimento dos consumidores de API, assegurando que as APIs são utilizadas eficazmente." }, { "id": "api-promotion", "title": "Promoção da API - Aumente a visibilidade e a utilização da API", "description": "Promover as APIs para aumentar a visibilidade, a utilização e a adoção entre os públicos-alvo." }, { "id": "partner-integration", "title": "Integração de parceiros - Colaborar com parceiros", "description": "Facilitar as integrações de parceiros para melhorar as capacidades da API e expandir o alcance." }, { "id": "api-mindset", "title": "Mentalidade API - Promover uma cultura API-First", "description": "Cultivar uma mentalidade API-first em toda a organização para impulsionar a inovação e a colaboração." }, { "id": "roles-and-responsibilities", "title": "Funções e responsabilidades - Definir as estruturas da equipa API", "description": "Definir funções e responsabilidades claras para as equipas de API para garantir uma colaboração e responsabilização eficazes." }, { "id": "upskilling", "title": "Upskilling - Melhorar as competências e conhecimentos em matéria de API", "description": "Fornecer formação e recursos para melhorar as competências e os conhecimentos sobre API em toda a organização." }, { "id": "operating-guidelines", "title": "Diretrizes operacionais - Estabelecer a governação da API", "description": "Estabelecer diretrizes operacionais e práticas de governação para garantir uma gestão e qualidade consistentes da API." }, { "id": "portfolio-management", "title": "Gestão de portfólio - Gerir eficazmente o portfólio de API", "description": "Gerir eficazmente a carteira de API para garantir o alinhamento com os objetivos de negócio e as iniciativas estratégicas." }, { "id": "budget-and-resource-management", "title": "Orçamento e gestão de recursos - Otimizar os investimentos em API", "description": "Otimizar o orçamento e a gestão de recursos para as iniciativas API, a fim de garantir investimentos e atribuição de recursos eficazes." } ] } } }