liveBook · Manning

Modernization core domain chart

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

A modernization core domain chart is a prioritization visualization that compares modernization opportunities using business value, impact, and effort across domains.

Modernization offers more possible starting points than a team can pursue at once. A modernization core domain chart makes those choices visible so people can compare subdomains and decide where to start—or what to tackle next. It adapts the Core Domain Chart into a collaborative impact-versus-effort view. section 16.2.2

Plot each candidate subdomain by the value of modernizing it on the horizontal axis and the complexity of modernizing it on the vertical axis. Value includes progress toward business outcomes, such as new product capabilities, and learning that helps with later decisions, such as validating a technology choice or pattern. section 16.2.2

Figure 16.8 The modernization Core Domain Chart

Use the chart to see which opportunities combine high value with low complexity, and which require substantial effort for little apparent return. section 16.2.2

Two contrasting positions help frame the discussion:

  • Low-hanging fruit has high modernization value and low complexity, making it an attractive early investment. section 16.2.2
  • The “last toothpaste in the tube” has low value and high complexity. Leave it until later or avoid modernizing it unless a risk or other benefit changes the value assessment. section 16.2.2

Comparing two legacy subdomains

A legacy component that can be rewritten without changing the surrounding system, while adding features that advance a product goal, may be low-hanging fruit. A million lines of untested stored procedures that are unlikely to change offer a much weaker return for the effort. If those procedures pose a serious security or reputation risk, preventing that loss belongs in the value discussion. section 16.2.2

Treat the positions as a basis for discussion, not a permanent verdict. When a decision needs finer criteria, use a scorecard. The chart can also make prioritization decisions legible alongside a roadmap and portfolio of modernization investments. section 16.2.2 section 16.1.1

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

How deep it goes
Defines two axes and explains contrasting quadrants with examples; defers finer-grained criteria to scorecards.
Examples
Contrasts an independently rewritable legacy component with a million untested stored procedures unlikely to change.
What it assumes
Assumes candidate subdomains and business outcomes are identifiable; defines the chart axes without teaching subdomain discovery.
What you can do after
Practice/perform collaborative prioritization by plotting subdomains against modernization value and complexity.
How it connects
Connects Core Domain Charts, scorecards, modernization roadmaps, and business-value-based investment decisions.

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.