{"id":107,"date":"2026-03-13T22:53:06","date_gmt":"2026-03-13T22:53:06","guid":{"rendered":"https:\/\/dev.harmonic-framework.com\/influences\/"},"modified":"2026-03-14T00:24:11","modified_gmt":"2026-03-14T00:24:11","slug":"origins","status":"publish","type":"page","link":"https:\/\/dev.harmonic-framework.com\/es\/origins\/","title":{"rendered":"Origins"},"content":{"rendered":"

Harmonic Design does not claim to have originated the ideas it draws on. The frameworks articulated in VBD, EBD, BDT, and Project Design name and structure principles that have emerged through decades of architectural thought and practice. These are the people whose work made that possible.<\/p>\n\n\n\n

\n\n\n\n

Primary Influences<\/h2>\n\n\n
\n
\"Juval<\/div>\n
\n

Juval L\u00f6wy<\/h3>\n

Software architect, founder of IDesign<\/p>\n

L\u00f6wy’s IDesign methodology is the primary foundation for Volatility-Based Decomposition. The Manager-Engine-Resource Accessor taxonomy, the communication rules that enforce clean boundaries, and the project design methodology that derives project plans from architectural decomposition all originate in IDesign. Harmonic Design extends L\u00f6wy’s backend structural model across the interface, test, and project planning layers.<\/p>\n

The author worked with L\u00f6wy as a consultant with IDesign for many years, learning firsthand about identifying volatility, architecting software systems, managing projects from architectural structure, and what it means to practice software engineering as a profession. L\u00f6wy’s influence on the ideas in Harmonic Design is not only intellectual \u2014 it is the product of direct collaboration and mentorship.<\/p>\n

Key works:<\/strong> Righting Software<\/em> (Addison-Wesley, 2019), Programming .NET Components<\/em> (O’Reilly, 2005)<\/p>\n

idesign.net<\/a><\/p>\n<\/div>\n<\/div>\n\n

\n
\"David<\/div>\n
\n

David L. Parnas<\/h3>\n

Computer scientist, professor<\/p>\n

Parnas’s information hiding principle \u2014 that modules should be designed around design decisions likely to change \u2014 is the intellectual foundation of volatility-first decomposition. His 1972 paper “On the Criteria To Be Used in Decomposing Systems into Modules” established the argument that decomposition should be driven by anticipated change rather than functional grouping. HD is the system-scale extension of this principle, applied simultaneously at the backend, interface, test strategy, and project planning levels.<\/p>\n

Key work:<\/strong> “On the Criteria To Be Used in Decomposing Systems into Modules” (Communications of the ACM<\/em>, 1972)<\/p>\n<\/div>\n<\/div>\n\n

\n
\"Alan<\/div>\n
\n

Alan Cooper<\/h3>\n

Software designer, “Father of Visual Basic”<\/p>\n

Cooper’s goal-directed design methodology established the foundational claim that interfaces should serve user goals, not reflect system capabilities. His use of personas and scenarios to drive interaction decisions is a direct precursor to EBD’s core user journey validation mechanism. Cooper also articulated the distinction between implementation models and mental models, which maps directly to EBD’s argument that organizing code around screens misaligns it with the user’s cognitive frame.<\/p>\n

Key work:<\/strong> About Face: The Essentials of Interaction Design<\/a><\/em> (Wiley, 2014, with Reimann, Cronin, Noessel)<\/p>\n

cooper.com<\/a><\/p>\n<\/div>\n<\/div>\n\n

\n
\"David<\/div>\n
\n

David Garlan<\/h3>\n

Professor of Computer Science, Carnegie Mellon University<\/p>\n

Garlan, together with Mary Shaw, helped establish software architecture as a first-class discipline distinct from programming and design. Their work provides the conceptual grounding for system-level decomposition approaches like Volatility-Based Decomposition, reinforcing the idea that architectural structure must be reasoned about explicitly and evaluated continuously as systems evolve.<\/p>\n

Key work:<\/strong> Software Architecture: Perspectives on an Emerging Discipline<\/em> (Pearson, 1996, with Mary Shaw)<\/p>\n

Carnegie Mellon faculty page<\/a><\/p>\n<\/div>\n<\/div>\n\n\n

\n\n\n\n

Additional Influences<\/h2>\n\n\n
\n
\n

Robert C. Martin<\/h3>\n

Martin’s Dependency Rule and boundary discipline align with HD’s communication model. HD provides the volatility-based account of why those dependency directions are correct.<\/p>\n

Key works:<\/strong> Clean Architecture<\/em> (Pearson, 2017), Agile Software Development: Principles, Patterns, and Practices<\/em> (Pearson, 2002)<\/p>\n<\/div>\n<\/div>\n\n

\n
\n

Eric Evans<\/h3>\n

DDD’s bounded context concept and HD’s tier boundaries are complementary rather than competing. HD operates within bounded contexts, governing how each context organizes its internal structure.<\/p>\n

Key work:<\/strong> Domain-Driven Design: Tackling Complexity in the Heart of Software<\/em> (Addison-Wesley, 2003)<\/p>\n<\/div>\n<\/div>\n\n

\n
\n

Martin Fowler<\/h3>\n

BDT builds on Fowler’s test pyramid by grounding its levels in structural tiers. HD extends this by making the test pyramid a consequence of the structural isomorphism across all four layers.<\/p>\n

Key work:<\/strong> “The Practical Test Pyramid” (martinfowler.com<\/em>, 2018)<\/p>\n<\/div>\n<\/div>\n\n

\n
\n

Brad Frost<\/h3>\n

Atomic Design established a hierarchical vocabulary for component composition. EBD inherits this hierarchical instinct while operating at a different granularity \u2014 where Atomic Design hierarchizes visual structure, EBD hierarchizes behavioral intent. The two are complementary.<\/p>\n

Key work:<\/strong> Atomic Design<\/em> (2016)<\/p>\n<\/div>\n<\/div>\n\n

\n
\n

Frederick P. Brooks Jr.<\/h3>\n

Brooks’s observation that adding people to a late project makes it later is reflected in Project Design’s treatment of staffing, compression limits, and the one-to-one rule that aligns with HD’s component boundaries.<\/p>\n

Key work:<\/strong> The Mythical Man-Month<\/em> (Addison-Wesley, 1975)<\/p>\n<\/div>\n<\/div>\n\n

\n
\n

Donald A. Norman<\/h3>\n

Norman’s articulation of affordances, feedback, and the gulf of evaluation provided the cognitive psychology grounding for interaction design as a discipline. His concept of the gulf between the system image and the user’s mental model is directly relevant to EBD’s argument that code structure should reflect the user’s purpose rather than the system’s structure.<\/p>\n

Key work:<\/strong> The Design of Everyday Things<\/em> (Basic Books, 2013)<\/p>\n<\/div>\n<\/div>\n\n

\n
\n

Gregor Hohpe & Bobby Woolf<\/h3>\n

Their catalog of messaging patterns provides the foundational vocabulary for the event-based communication model used in both VBD and EBD. Decoupling producers from consumers through well-defined channels is the messaging-level expression of the same volatility isolation that HD enforces at the structural level.<\/p>\n

Key work:<\/strong> Enterprise Integration Patterns<\/em> (Addison-Wesley, 2003)<\/p>\n<\/div>\n<\/div>\n\n

\n
\n

Gang of Four (Gamma, Helm, Johnson, Vlissides)<\/h3>\n

The GoF cataloged recurring patterns that encapsulate and localize variation at the class and collaboration level. Volatility-Based Decomposition extends this pattern-based thinking from the object scale to the architectural scale.<\/p>\n

Key work:<\/strong> Design Patterns: Elements of Reusable Object-Oriented Software<\/em> (Addison-Wesley, 1994)<\/p>\n<\/div>\n<\/div>\n\n

\n
\n

James E. Kelley & Morgan R. Walker<\/h3>\n

The Critical Path Method provides the mathematical foundation for the network analysis, float calculation, and critical path identification used in Project Design.<\/p>\n

Key work:<\/strong> “Critical-Path Planning and Scheduling” (Proceedings of the Eastern Joint Computer Conference<\/em>, 1959)<\/p>\n<\/div>\n<\/div>\n\n

\n
\n

Dan Saffer<\/h3>\n

Saffer’s analysis of microinteractions \u2014 trigger, rules, feedback, loops and modes \u2014 provides the conceptual foundation for EBD’s Interaction tier, reinforcing the case for isolating atomic user actions in their own structural tier.<\/p>\n

Key work:<\/strong> Microinteractions: Designing with Details<\/em> (O’Reilly, 2013)<\/p>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"

Harmonic Design does not claim to have originated the ideas it draws on. The frameworks articulated in VBD, EBD, BDT, and Project Design name and structure principles that have emerged through decades of architectural thought and practice. These are the people whose work made that possible. Primary Influences Juval L\u00f6wy Software architect, founder of IDesign … Read more<\/a><\/p>","protected":false},"author":0,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_uag_custom_page_level_css":"","footnotes":""},"methodology":[],"class_list":["post-107","page","type-page","status-publish"],"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false,"trp-custom-language-flag":false,"post-thumbnail":false,"hf-card":false,"hf-hero":false},"uagb_author_info":{"display_name":"","author_link":"https:\/\/dev.harmonic-framework.com\/es\/author\/"},"uagb_comment_info":0,"uagb_excerpt":"Harmonic Design does not claim to have originated the ideas it draws on. The frameworks articulated in VBD, EBD, BDT, and Project Design name and structure principles that have emerged through decades of architectural thought and practice. These are the people whose work made that possible. Primary Influences Juval L\u00f6wy Software architect, founder of IDesign…","_links":{"self":[{"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/107","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/types\/page"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/comments?post=107"}],"version-history":[{"count":4,"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/107\/revisions"}],"predecessor-version":[{"id":157,"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/107\/revisions\/157"}],"wp:attachment":[{"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/media?parent=107"}],"wp:term":[{"taxonomy":"methodology","embeddable":true,"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/methodology?post=107"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}