Example Mapping

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

Example Mapping is a collaborative technique for exploring rules, examples, and questions in greater detail around a behavior or requirement.

Example Mapping is a collaborative technique for uncovering scenarios, edge cases, and hidden complexity around a specific behavior or requirement. Combined with EventStorming, it zooms into a small area of the domain at greater granularity. section 7.4.1

An EventStorming-flavored mapping proceeds by:

• Picking an event from the timeline and identifying the action that triggers it. section 7.4.1
• Adding scenarios between the action and resulting event, including alternative outcomes and edge cases. section 7.4.1
• Encouraging creative scenario generation, then splitting scenarios when separate actions or more explicit concepts emerge. section 7.4.1

Order cancellation

The Order Canceled event may follow the Cancel Order action. If a customer requests a refund after the order has left the warehouse, the scenario produces Cancelation Denied instead. section 7.4.1

Figure 7.20 EventStorming-flavored Example Mapping

Use the visual mapping to inspect how actions, scenarios, and events are arranged. section 7.4.1

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes

Explains a focused workflow from event selection through scenario generation and concept splitting.

Examples

Uses order cancellation, warehouse departure, refunds, Order Canceled, and Cancelation Denied as concrete scenarios.

What it assumes

Assumes an EventStorming timeline containing an event that participants can inspect.

What you can do after

Apply it in a collaborative workshop to expose hidden scenarios and decide when concepts need separation.

How it connects

Connects Example Mapping with EventStorming, events, actions, scenarios, and edge cases.

liveBookmanning.com

Read Architecture Modernization: Socio-technical alignment of software, strategy, and structure on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Collaborative Software Design: How to facilitate domain modeling decisionsExample Mapping is a collaborative technique for organizing rules, examples, and questions to clarify requirements and discover acceptance criteria.
• 

  liveBookmanning.com
  BDD in Action, Second EditionExample Mapping is a collaborative BDD technique for exploring rules, examples, and questions about a requirement.

Compare how 3 books explain Example Mapping →

Related concepts

• business ruleuses · A business rule is a domain-specific policy, condition, or constraint that governs valid data, decisions, actions, or behavior in an organization or its systems.
• user storyuses · A user story is a concise requirement describing a desired software capability, interaction, or outcome from a user’s or stakeholder’s perspective.
• software design EventStormingcontrasts with · Software design EventStorming is a collaborative modeling technique that explores domain events and processes to inform software structure and behavior.
• discovery workshopuses · A collaborative, structured session in which participants explore and refine user needs, problems, domain concepts, or software requirements.
• feature mappingcontrasts with · Feature mapping is a collaborative requirements technique for exploring and organizing a software feature's behavior, flows, variations, and examples.

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.