Blueprint schema changelog

A schema version describes the modeling contract. Tool releases and engagement deliverables have separate scope.

Blueprint is a versioned schema that evolves as modelling practice reveals missing concepts and connections. Supported migrations between versions can be applied automatically.

It detects the model version and plans changes to files, properties and references. It applies updates in a copy in the next version directory and reports changes it cannot rewrite automatically. Preview the changes before applying a supported migration.

Entries: 12

  1. Releases

    Blueprint 2.8

    Release date

    The 2.8 line makes typed references and explicit relationships between bounded contexts mandatory, and extends how models describe quality verification and software dependencies.

    • Validate links between declared model elements and state how bounded contexts collaborate, with unresolved typed references reported as errors.
    • Connect quality targets to measurable objectives, measurement probes and fitness functions that state which requirements they verify.
    • Model third-party packages with their versions and licences, and connect them to the services that import them and the risks or decisions that concern them.
    Read the version changelog
  2. Releases

    Realm 2.0: first public version

    Release date

    The Realm schema for modelling private real estate becomes publicly available.

  3. Releases

    Brandvoice 1.6: first public version

    Release date

    The Brandvoice schema for brand strategy and brand voice becomes publicly available.

  4. Releases

    Blueprint 2.7

    Release date

    The 2.7 line introduces clearer names for infrastructure, interactions and organization, then expands the model with infrastructure relationships, delivery planning and explicit operation ownership.

    • Describe what a service needs and which infrastructure supplies it in each environment, separating where a resource runs from who manages it.
    • Break milestones into work items with dependencies, blockers and sprint or date schedules, linked to goals, risks and decisions.
    • State which services handle each operation, including calls within one process that need no network transport.
    Read the version changelog
  5. Releases

    Blueprint 2.6

    Release date

    The 2.6 line adds value streams and evidence links, changes actors to support multiple personas, and makes entity lifecycle changes explicit in operations.

    • Trace value streams across bounded contexts, connecting their stages to capabilities and the whole stream to goals and KPIs.
    • Describe several personas for one actor to capture different needs and behaviours within the same role.
    • Link modelling claims to evidence and record its strength so readers can assess what supports the model.
    Read the version changelog
  6. Releases

    Blueprint 2.5

    Release date

    Model user stories, use cases and delivery milestones, with personas and priorities that connect user needs to planned work.

    • Describe user stories and step-by-step use cases.
    • Plan delivery milestones with dates, dependencies and success criteria.
    • Capture user goals, pain points and behaviours in actor personas.
  7. Releases

    Blueprint 2.4

    Release date

    Connect the model to source code, classify domain concepts and capture questions and operation examples.

    • Link model elements to the source code that implements them.
    • Classify domain concepts as entities, value objects or services.
    • Record domain questions and examples of operation inputs and outputs.
  8. Releases

    Blueprint 2.3

    Release date

    Extend model elements with metadata and start with names and descriptions before adding implementation details.

    • Add custom metadata to model elements.
    • Use consistent names and descriptions for concepts and rules.
    • Sketch rules and operations before specifying their logic or communication details.
  9. Releases

    Blueprint 2.2

    Release date

    Model screens and navigation, assign ownership and connect domain attributes to data models.

    • Connect screens, user actions and navigation to domain operations.
    • Assign model ownership to teams, departments or organizations.
    • Describe concept attributes and map them to data models.
  10. Releases

    Blueprint 2.1

    Release date

    Make causal links and process activities explicit, and connect tests to architecture checks.

    • Show which operations produce or react to other operations.
    • Describe processes through activities, participants and possible outcomes.
    • Connect test cases to automated architecture checks.
  11. Releases

    Blueprint 2.0

    Release date

    Use a shared metamodel with consistent naming, typed identifiers and versioning to keep model elements and their references coherent.

    • Use shared naming and reference conventions across the model.
    • Describe domain concepts, actors, relationships and lifecycles.
    • Connect architecture decisions to their impact on goals and capabilities.
  12. Releases

    Blueprint 1.0

    Release date

    The first version, under an earlier name, provides a foundation for describing software systems as structured models.

    • Describe a shared domain vocabulary and business rules.
    • Record operations alongside goals, risks and design decisions.
    • Link test expectations to the rules they verify.

The reference schema is Apache-2.0. That licence does not cover the whole toolchain.