Roadmaps and Scenarios are two closely related concepts in Waltz. Conceptually a Roadmap is used to describe how a set of application taxonomy mappings will change in over time or under differing circumstances. each set of changes is contained within a Scenario. Therefore a Roadmap is a set of Scenarios used to describe changes to a set of applications.
Examples of roadmaps and their Scenarios might be:
- Operations Process vs. Product Roadmap
- Current state (scenario)
- 2025 Target (scenario)
- 2020 Interim (scenario)
- 2025 Alternative Plan (scenario)
In this example we can see a single roadmap with 4 associated Scenarios. Note that Scenarios can be contradictory to allow for alternative views as to what future state may look like.
Each scenario is a grid, the axes of which are a hand-picked collection of measurables. For instance the columns maybe a selection of Business Processes and the rows a selection of Financial Products . This gives us a grid, each cell representing the intersection between a process and a function. Applications can then be associated to cells and given a rating, e.g. App: Settler could be dropped into the cell Settlement processing/Bonds with a rating of Disinvest.
To represent a roadmap Waltz requires:
- a name
- a description
- an x-axis domain
- a y-axis domain
- a rating scheme
The domains currently limited to measurable categories and are fixed so that meaningful comparisons can be made between scenarios. If the axes domains could differ then comparisons would become largely meaningless.
The rating scheme is required and used to provide the valid set of values used to rate applications in the scenario cells.
To represent Scenarios, Waltz needs:
- a name
- description
- type (
CURRENT | INTERIM | TARGET) - effective date
- release status (
DRAFT | ACTIVE | DEPRECATED | OBSOLETE) - position ( to override the natural alphabetical order info )
- set of measurables defining x-axis
- set of measurables defining y-axis
See the Schema Diagram for more information (source)