Technical Awareness Training

Overview

This interactive training is a level-setting exercise addressing design, implementation and operational concerns that inform planning, staffing, development and delivery of a BIAN solution.
  • Key Takeaway:  Preparation for technical leadership of BIAN implementation
  • Audience:          Technical team leaders, enterprise architects, solution architects
  • Duration:            Six 4-hour sessions during a two-week window
  • Mode:                 Instructor led live online or on site
  • Class Size:        10-15

The course is tailored to your organization. Participants come away with a practical understanding of how to apply the BIAN approach in your organizational context.

Over a two-week period, classroom work sets the context for offline collaboration on practical exercises (”homework”) with support as needed from the CC&C facilitator.

Agenda

Each classroom session takes a deep dive into one aspect of the BIAN implementation.

We use a mix of classroom work and hands-on team activities in which you create your unique, workable design and implementation approach.

Session 1

  • Overview of Key BIAN design concepts
  • Different model view, service centre vs process – An example
  • How to apply the BIAN Model
  • Different contextual use cases where BIAN model can be leveraged.
  • Introduction to the pilot use case

Session 2

  • Overview of BIAN metamodel
  • Introduction to BIAN Business capability model
  • Introduction to BIAN Service landscape and service domain
  • Deep dive into BIAN Service Domain
  • Create a business architecture view for the pilot use case using BIAN.

Session 3

  • Deep dive into BIAN Service domains
  • Introduction to BIAN Business scenario and Wireframes
  • Developing business scenario and wireframe for the pilot use case
  • Leveraging BIAN artifacts to develop high level conceptual design for the pilot use case.

Session 4

  • Applying BIAN model for Application architecture
  • Different design considering in applying BIAN for application architecture
  • Leveraging BIAN for Application architecture governance.
  • Extend the high-level design for the pilot use case to include application and technology view.

Session 5

  • Deep dive into BIAN Service operations and Semantic APIs
  • Overview of different API architecture and strategy for considering in an organisation
  • leveraging BIAN model for different API strategies and governance
  • How to leverage BIAN Semantic APIs with practical considerations
  • Extend the high-level design for the pilot use case to include Integration view.

    Session 6

    • Deep dive into BIAN Business object model
    • Leveraging BIAN for Data and Information architecture
    • Different practical use cases to considering data architecture with BIAN.
    • Extend the high-level design for the pilot use case to include Information and Data view.

    Team “Homework” Deliverables

    Outside the formal sessions, participants work together to create some specific deliverables.

    This set of plans and guidance becomes the basis for the next BIAN adoption phase: design of the team’s first BIAN use case.

    Deliverables from this “homework” vary for each organization but are likely to include:

    • Pilot Use Case Selection including clear mapping to business strategy, BIAN semantics, and target operational environment,.

      This requires consideration of business value and ROI expectations, feasibility and risk of each candidate implementation, and the organization’s technical and operational capabilities.

    • Organizational Approach, including skills, roles, teams, and leadership. May include pilot team assignments and skills development plans.

      Should address how IT and business operations will prepare and participate.

    • Semantic Approach: BIAN adoption requires organizational decisions about how to map and tailor the standard BIAN Service Domain structure.

      This may require, for example, decomposing some Service Domains into more detailed instances, while consolidating or even eliminating others from the toolkit. These global choices must be centrally governed.

    • Technology Choices that make sense in the organizational context.

      This may include choices regarding development tools, API or ESB tools, standards for APIs and microservices, and data management standards for Systems of Record, Master Data Management, etc.

    • Governance Approach: A successful, scalable BIAN implementation requires some new architecture governance practices specific to BIAN.

    Adoption_Journey_Graphic-right

    Learn more about each phase:

    CC&C’s BIAN Service Offerings

    Business Value Awareness Seminar

    Technical Awareness Training

    BIAN Foundation Certification

    BIAN Data Architecture Certification

    Use Case Design Workshop

    Proof of Value Implementation

    Rollout Enablement