Modernization Strategy Selector

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

The Modernization Strategy Selector is a decision-support tool for selecting modernization investments and sequencing priorities across subdomains.

The Modernization Strategy Selector supports portfolio decisions about how much to modernize each subdomain and how to sequence investments. It favors evolutionary delivery over a fixed target-state plan: discovery, architecture design, and delivery proceed in parallel, with feedback continuously refining priorities. section 1.3 section 12.4.1

Map each subdomain across two dimensions:

• Behavior and design modernization ranges from Expose, through Polish, Replicate, and Remodel, to Rethink. section 12.4.1
• Technology modernization measures how far programming languages, frameworks, databases, and infrastructure differ from the current state. section 12.4.1
• Choose the point of diminishing returns rather than applying the same investment to every subdomain. section 12.4.1

Different subdomains, different strategies

Cloud adoption may suit one subdomain, while a complete rewrite in different technologies may better serve a core domain with significant differentiation opportunity. When legacy coupling prevents fine-grained decisions, lift and shift the monolith to the cloud first, then modernize subdomains progressively. section 12.4.1

Figure 12.19 The Modernization Strategy Selector (to be used per subdomain)

Use the per-subdomain selector to compare behavior-and-design change with technology change and identify an appropriate modernization position. section 12.4.1

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

How deep it goes

Defines two axes and five behavior-and-design strategies, stopping short of detailed implementation instructions.

Examples

Uses cloud adoption, complete rewrites, and monolith lift-and-shift followed by subdomain modernization.

What it assumes

Assumes subdomain boundaries and information gathered through architecture, coupling, and modernization analysis.

What you can do after

Evaluate modernization options and sequence subdomain investments while responding to feedback and diminishing returns.

How it connects

Connects architecture modernization with subdomains, technical debt, domain models, portfolio thinking, and evolutionary delivery.

liveBookmanning.com

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

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.