Construct · 3 fields · 4 citations

Where does architecture collide?

One name. Different field. Different construct. One map.

● jingle · one word, three constructs Nearest construct by meaningstackcompare the meanings
How to read this

Every construct on the map is compared with every other by the meaning of its definitions, and the closest one is surfaced here. The nearest construct to architecture is stack.

Hold this as a prompt, not a verdict. Two constructs sitting close in meaning is a reason to read them side by side and decide for yourself whether they are one idea under two names. It is not proof that they are. Compare the meanings in the Collider.

architecture3 CONSTRUCTSSoftware arch.PERRY & WOLF · SYSTEM FORMEnterprise arch.ZACHMAN · ORG BLUEPRINTSleep architectureOHAYON · SLEEP STAGES

Spokes are fields; dashed arcs are shared lineage. Tap a field for its definition, unit, and measures.

1987Enterprise arch.1992Software arch.2004Sleep architecture
2026

Drag to watch the word get claimed. Each field appears at the publication date of the earliest source cited for it. Tap a year to see which.

Software engineering

the fundamental organization of a software system, covering its components, their relationships, and its design principles.

The fundamental organization of a software system: the set of structures made up of its components, their externally visible properties, and the relationships among them, together with the principles governing the system's design and evolution. Perry and Wolf's 1992 Foundations for the study of software architecture modelled it as elements, form, and rationale, and separated a particular architecture from the architectural styles that constrain whole families of systems. The referent is the high-level structure of code and its constraints, chosen to meet quality attributes, not a company's operating blueprint, a designed building, or the staging of biological sleep.[1][2]

Unit
A software system's component-and-connector structure and its governing principles
Recovery means
Not applicable
Measured by
Described in architecture views and documents, and evaluated by methods such as ATAM against quality attributes like modifiability and performance

Information systems and enterprise

a blueprint aligning an organization's business processes, information, and technology infrastructure to support its mission as a whole.

A holistic blueprint that aligns an organization's business processes, information, and technology infrastructure so that they support the enterprise's mission as a coherent whole. Zachman's 1987 A framework for information systems architecture arranged these descriptions as a matrix of perspectives and abstractions, later elaborated by practice frameworks such as TOGAF. The referent is the organization-wide structure that governs how business and IT fit together, not the internals of one software system, a physical building, or the pattern of a night's sleep.[3]

Unit
An organization-wide alignment of business, information, and technology, described across perspectives
Recovery means
Not applicable
Measured by
Captured in framework artefacts such as Zachman matrices or TOGAF deliverables, and assessed by maturity models and business-IT alignment audits

Sleep science

The nightly pattern of sleep stages

The structural organization of sleep across the night: the amount, sequence, and cyclic alternation of the distinct sleep stages, the non-REM stages and REM, as they recur through successive cycles. Ohayon, Carskadon, Guilleminault, and Vitiello's 2004 meta-analysis derived normative values for these parameters across the human lifespan, quantifying how stage proportions and continuity shift with age. The referent is the temporal architecture of a sleeping brain, recorded by polysomnography, not the structure of software, an enterprise, or a building.[4]

Unit
The proportion, sequence, and cycling of sleep stages across a night
Recovery means
After sleep loss the architecture rebounds, with slow-wave sleep increasing on recovery nights
Measured by
Scored from polysomnography into stages, and summarised as time in each stage, sleep efficiency, and cycle structure

Next

Run it through the Collider, or take the citations with you.

See how architecture sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in ColliderExport BibTeXReport this collision

Nearby collisions

program2 fields · 2 citationsjingle · one word, two constructsadhesion4 fields · 4 citationsjingle · one word, four constructsadjacency3 fields · 3 citationsinvariant · one construct, three systems

References

  1. Perry, D. E., & Wolf, A. L. (1992). Foundations for the study of software architecture. ACM SIGSOFT Software Engineering Notes, 17(4), 40–52. https://doi.org/10.1145/141874.141884
  2. International Organization for Standardization. (2011). ISO/IEC/IEEE 42010:2011, Systems and software engineering, Architecture description. ISO.
  3. Zachman, J. A. (1987). A framework for information systems architecture. IBM Systems Journal, 26(3), 276–292. https://doi.org/10.1147/sj.263.0276
  4. Ohayon, M. M., Carskadon, M. A., Guilleminault, C., & Vitiello, M. V. (2004). Meta-analysis of quantitative sleep parameters from childhood to old age in healthy individuals: Developing normative sleep values across the human lifespan. Sleep, 27(7), 1255–1273. https://doi.org/10.1093/sleep/27.7.1255

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct