Program comprehension

Q: How deeply does Architecture Modernization: Socio-technical alignment of software, strategy, and structure cover program comprehension?

Defines a people-centered assessment and connects it to CodeScene visualizations, but does not provide a detailed comprehension measurement procedure.

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

Code understanding is the organizational knowledge of how a software system's source code works and why it behaves as it does.

Program comprehension is organizational knowledge of how a software system works and why it behaves as it does. It is a current-state complexity signal: when fewer people understand the code, change becomes riskier and modernization decisions become harder. section 12.4.3

Assess program comprehension alongside other current-state signals:

Identify how many people still understand the system and how well they understand it. section 12.4.3
Compare knowledge distribution with ownership, contractor involvement, test quality, layering integrity, and cost to run. section 12.4.3
Use architecture-analysis tooling to expose knowledge loss and communicate system complexity to technical and nontechnical audiences. section 12.4.3

Making knowledge loss visible

A CTO used CodeScene to identify system areas with no owners and areas worked on exclusively by contractors. Visualizations helped explain these risks to leadership and justify proposed changes. section 12.4.3

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

Cover of Architecture Modernization: Socio-technical alignment of software, strategy, and structure

liveBook manning.com

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

Related concepts

working memoryuses · Working memory is a limited, temporary store of information available for immediate access or manipulation during an active task or interaction.
naming standardused by · A naming standard is an established set of rules or patterns for assigning names consistently to software elements, resources, or other artifacts.
testuses · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.
refactoringuses · Refactoring is the restructuring of existing software or code to change its internal organization and improve its design, typically while preserving externally observable behavior.

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.