liveBook · Manning

Notation

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

Notation is a defined system of symbols, conventions, or visual marks for representing information.

Notation is a defined set of symbols and usage rules for representing domain interactions, processes, systems, decisions, and unresolved questions. In collaborative modeling, the symbols support conversation rather than serving as an artifact to perfect or reuse unchanged. section 8.4.1 section 7.1.3

Two related modeling approaches use distinct notation sets:

  • Process modeling EventStorming uses yellow actors or roles, blue actions or commands, pink systems, orange domain events, purple policies, green information, and fuchsia or red hot spots. section 8.4.1
  • EventStorming syntax constrains how elements connect; for example, an orange domain event can follow a pink system directly. section 8.4.1
  • Domain Storytelling uses actors, work items, activities, sequence numbers, annotations, and groups to express interactions and their order. section 8.5.1

Making a workflow visible

A contract-approval model connects a salesperson’s request to the contracts system, the Contract Approval Requested event, a legal-approval policy, the approvals system, and information about outstanding approvals. A prescription-validation story sequences a customer’s medication order, prescription upload, doctor confirmation, and order acceptance. section 8.4.1 section 8.5.1

Figure 8.4 Process modeling EventStorming notation and syntax

Use the visual syntax reference to compare process-modeling EventStorming elements and their permitted relationships. section 8.4.1

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

How deep it goes
Defines symbol meanings and some sequencing rules, then demonstrates them through contract-approval and prescription-validation workflows.
Examples
Uses contract approval, prescription validation, sticky notes, pictographic icons, sequence numbers, and workflow diagrams as teaching examples.
What you can do after
Apply it via EventStorming or Domain Storytelling to map workflows and expose missing knowledge or improvement opportunities.
How it connects
Connects EventStorming and Domain Storytelling with actors, systems, activities, domain events, policies, information, and workflows.

Also explained in

Compare how 2 books explain notation →

Related concepts

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.