book

Balancing Coupling in Software Design: Universal Design Principles for Architecting Modular Software Systems

by Vlad Khononov

October 2023

Intermediate to advanced

321 pages

7h 52m

English

Addison-Wesley Professional

Read now

Unlock full access

Who Should Read This Book?How This Book Is OrganizedCase Studies and WolfDesk

What Is Coupling?Magnitude of CouplingFlow of KnowledgeSystemsKey TakeawaysQuiz
What Is Complexity?CynefinComparing Cynefin DomainsCynefin in Software DesignCynefin ApplicationsCynefin and ComplexityKey TakeawaysQuiz
Nature of ComplexityComplexity and System DesignHierarchical ComplexityDegrees of FreedomComplexity and ConstraintsCoupling and Complex InteractionsExample: Connecting Coupling and ComplexityKey TakeawaysQuiz
ModularityModulesModularity in Software SystemsModularity, Complexity, and CouplingCoupling in ModularityKey TakeawaysQuiz
Structured DesignModule CouplingComparison of Module Coupling LevelsKey TakeawaysQuiz
What Is Connascence?Static ConnascenceDynamic ConnascenceEvaluating ConnascenceKey TakeawaysQuiz
Strength of CouplingIntegration StrengthIntrusive CouplingFunctional CouplingModel CouplingContract CouplingIntegration Strength DiscussionIntegration Strength and Asynchronous ExecutionKey TakeawaysQuiz
Distance and Encapsulation BoundariesAdditional Factors Affecting DistanceDistance Versus ProximityDistance Versus Integration StrengthKey TakeawaysQuiz
Changes and CouplingWhy Software ChangesEvaluating Rates of ChangesVolatility and Integration StrengthInferred VolatilityKey TakeawaysQuiz
Combining the Dimensions of CouplingCombining Strength, Distance, and VolatilityBalancing Coupling on a Numeric ScaleKey TakeawaysQuiz
Resilient DesignSoftware Change VectorsRebalancing CouplingKey TakeawaysQuiz
GrowthInnovationFractal GeometryFractal ModularityKey TakeawaysQuiz
MicroservicesArchitectural PatternsBusiness ObjectsMethodsKey TakeawaysQuiz
Chapter 1: Coupling and System DesignChapter 2: Coupling and Complexity: CynefinChapter 3: Coupling and Complexity: InteractionsChapter 4: Coupling and ModularityChapter 5: Structured Design’s Module CouplingChapter 6: ConnascenceChapter 7: Integration StrengthChapter 8: DistanceChapter 9: VolatilityChapter 10: Balancing CouplingChapter 11: Rebalancing CouplingChapter 12: Fractal Geometry of Software Design

Content preview from Balancing Coupling in Software Design: Universal Design Principles for Architecting Modular Software Systems

Chapter 6 Connascence

From structured design, the baton was passed,

Connascence detailed how ties can be cast.

A spectrum of coupling, to ponder and think,

Connascence reveals the depth of each link.

The preceding chapter discussed structured design’s model for evaluating the strength of inter-module relationships. Module coupling was formulated and introduced in the context of the procedural programming paradigm. However, with the widespread adoption of object-oriented programming, there emerged a need for a more detailed model that could account for the nuances of object-oriented design. Meilir Page-Jones (1996) responded to this need and introduced a model called connascence.

In this chapter, you will learn the connascence model. As you familiarize ...