Use Case Design Workshop
In this hands-on workshop, technical design and implementation leaders create an implementable design for a use case suited to their unique technical and organizational context.
Building on the implementation context developed in the Technical Awareness Workshop, the team will create the deliverables needed to support a Proof-of-Value implementation.
- Key Takeaway: A workable solution design for a chosen Use Case, and an understanding of next steps.
- Audience: Architects, solution designers, technology designers
- Duration: Six 4-hour sessions during a three-week window; includes significant “homework” between sessions
- Mode: Virtual instructor led (as standard)
- Class Size: 5-10
- Prerequisites: Foundation Certification and/or Technical Awareness training. Participants must have internet access to the bian.org domain.
- Prework: Teams will be set with the client and given pre-reading and preparation homework before the workshop begins.
The Path to a Workable Design
Entrance Criteria (Technical Awareness deliverables)
- Pilot Use Case Selection including clear mapping to business strategy, BIAN semantics, and target operational environment,.
- First-Cut Organizational Approach for BIAN work, including skills, roles, teams, and leadership.
- First-Cut BIAN Semantic Approach: Initial tailoring of the standard BIAN Service Domain structure.
- First-Cut Technology Choices to guide and enable implementation.
- First-Cut Governance Approach
Other Entrance Criteria
- High-level business case and value metrics for the chosen use case
- Committed team: About 48 hours of classroom work and homework will be needed over the three-week elapsed time
- Any needed design tooling in place, based on Technology Choices made in Technical Awareness phase
- Implementable design (within the defined technical and data context)
- Documentation of next steps required to implement the design, including human and technical resources
- Updates as required to organizational, semantic, technology and governance approach guidelines.
Beyond this the main outcome is that participants will be very comfortable using BIAN semantics, methods and artifacts for practical work.
The BIAN-Based Whole Bank Landscape
We introduce how BIAN customisation can be approached to extend the reference architecture for the organisation.
The skeleton of a whole bank service landscape model starts to emerge as part of creating the Technical Awareness Workshop deliverables ****which require mapping at least a small subset of the bank’s application and services to the BIAN Service Domain landscape.
In the Use Case Workshop this mapping becomes much more specific for the particular, narrow use case scope.
A larger BIAN service domain view of the bank’s service landscape can be developed based on this work.
This service landscape will evolve during later phases of the journey into a BIAN oriented reference architecture specific to the bank, including organizational, technology and application elements.
This sort of work is a natural outcome of BIAN analysis. It is a form of Application Portfolio Management (often falls into the scope of Enterprise Architecture). APM work is a well-understood path to cost savings and risk reduction and another source of benefits realization from BIAN adoption.
Large scale mapping of the application portfolio is a spin-off effort that can lead to a high value architecture-led rationalisation and refactoring of the bank’s application portfolio. This would of course require a significant effort over an extended period.
Just as with any POC/POV and scaled up implementation work CC&C can provide expert guidance on both the enterprise / business and solution architecture levels.