Component evolution

Q: How deeply does Collaborative Software Design: How to facilitate domain modeling decisions cover component evolution?

Defines four stages and their implications, but stops short of explaining the complete Wardley Mapping process.

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

A position representing the degree to which a capability has evolved from novel creation toward standardized utility.

Component evolution positions each capability on a path from novel creation to standardized utility: Genesis, Custom Build, Product & Rental, and Commodity & Utility. The stage depends on organizational context and helps groups choose appropriate decisions and management practices. section 12.1.2

Use the stages to:

Discuss capabilities collaboratively rather than treating their maturity as an individual judgment. section 12.1.2
Question whether an organization should build a capability itself, particularly when alternatives appear to be maturing into products. section 12.1.2
Adapt strategy, resource allocation, supply-chain choices, and operational practices to the capability’s stage. section 12.1.2

BigScreen capability mapping

Management and development teams placed capabilities on an evolution axis. The exercise surfaced a question about building planning software, while cinema-room capabilities suggested IMAX was reaching its market cap and 4DX was becoming a solid product. section 12.1.2

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

Cover of Collaborative Software Design: How to facilitate domain modeling decisions

liveBook manning.com

Read Collaborative Software Design: How to facilitate domain modeling decisions on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Architecture Modernization: Socio-technical alignment of software, strategy, and structureAn evolution stage is a phase describing the maturity and evolutionary position of a component in a Wardley Map.

Compare how 2 books explain component evolution →

Related concepts

Wardley Mappingused by · Wardley Mapping is a visual strategy technique that maps user needs and supporting components in a value chain and positions them by evolutionary maturity.
productincludes · A product is a good, service, software offering, or other managed offering made available to customers or users to provide value.
commodityincludes · A commodity is a standardized, broadly available, interchangeable capability whose predictability and limited differentiation make efficiency its primary competitive advantage.
custom-builtincludes · Custom-built is the Wardley Mapping evolution stage in which a component is deliberately created for a specific need rather than acquired as a standardized offering.
genesisincludes · Genesis is the Wardley Mapping evolution stage in which a component is novel, uncertain, and shaped by experimentation.
slopecontrasts with · Slope is the rate at which a dependent quantity changes relative to an independent quantity, often represented by a line’s gradient or a coefficient in a linear relationship.

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.