Downloaded 13 times
Uploaded byChris Chedgey
Bridging the Divide between Architecture and Code (Germany JUGs version)
The document discusses the challenges developers face due to 'invisible' and 'accidental' architecture leading to increased complexity and dependency tangles. It outlines a three-step approach to bridging the gap between architecture and code, which includes visualizing the current structure, locking in useful architecture, and incrementally improving it. The suggested methods involve using tools to create a hierarchical dependency model and emphasizing the need for clear modular organization.
More Related Content
Similar to Bridging the Divide between Architecture and Code (Germany JUGs version)
Bridging the Divide between Architecture and Code (Germany JUGs version)
- 1. Bridging the Dividebetween Architecture and Code Chris Chedgey Structure101
- 4.
- 7.
- 8.
- 9.
- 10. The Divide isa problem because…
- 11. The Divide isa problem because… • Invisible, emergent, accidental structure fights against developers
- 12. The Divide isa problem because… • Invisible, emergent, accidental structure fights against developers • Invisible, disconnected architecture could guide developers … but doesn’t
- 13. The Divide isa problem because… • Invisible, emergent, accidental structure fights against developers • Invisible, disconnected architecture could guide developers … but doesn’t
- 14. Invisible structure fightsdevelopers because… • Invisible structure becomes tangled
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22. • Invisible structurebecomes tangled Invisible structure fights developers because…
- 23. • Invisible structurebecomes tangled • Tangles increase complexity Invisible structure fights developers because…
- 24. Tangles increase complexity CCD= (1*1) + (11*2) + (7*3) + … ~ 164 CCD = 362 = 1,296 !!! Cumulative Component Dependency (John Lakos)
- 25. • Invisible structurebecomes tangled • Tangles increase complexity Invisible structure fights developers because…
- 26. • Invisible structurebecomes tangled • Tangles increase complexity • Complexity is hard to understand Invisible structure fights developers because…
- 27. Complexity is hardto understand
- 28. • Invisible structurebecomes tangled • Tangles increase complexity • Complexity is hard to understand Invisible structure fights developers because…
- 29. • Invisible structurebecomes tangled • Tangles increase complexity • Complexity is hard to understand • Tangles make a monolith Invisible structure fights developers because…
- 30. Tangles make amonolith
- 31. Tangles make amonolith
- 32. Tangles make amonolith
- 33. Tangles make amonolith
- 34. Tangles make amonolith ✗
- 35. • Invisible structurebecomes tangled • Tangles increase complexity • Complexity is hard to understand • Tangles make a monolith Invisible structure fights developers because…
- 36. The Divide isa problem because… • Invisible, emergent, accidental structure fights against developers • Invisible, disconnected architecture could guide developers … but doesn’t
- 37. The Divide isa problem because… • Invisible, emergent, accidental structure fights against developers • Invisible, disconnected architecture could guide developers … but doesn’t
- 38. Architecture could guidedevelopers
- 39. Architecture could guidedevelopers • Define/enforce layering
- 40. Architecture could guidedevelopers • Define/enforce layering
- 41. Architecture could guidedevelopers • Define/enforce layering
- 42. Architecture could guidedevelopers • Define/enforce layering
- 43. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages
- 44. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages
- 45. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages
- 46. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages
- 47. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages • Define/enforce interface-implementation
- 48. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages • Define/enforce interface-implementation
- 49. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages • Define/enforce interface-implementation
- 50. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages • Define/enforce interface-implementation • Prevent dependency proliferation
- 51. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages • Define/enforce interface-implementation • Prevent dependency proliferation • Allow for future module replacement
- 52. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages • Define/enforce interface-implementation • Prevent dependency proliferation • Allow for future module replacement • Guide new developers
- 53. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages • Define/enforce interface-implementation • Prevent dependency proliferation • Allow for future module replacement • Guide new developers • Phased/parallel development
- 54. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages • Define/enforce interface-implementation • Prevent dependency proliferation • Allow for future module replacement • Guide new developers • Phased/parallel development • Modularity!
- 55. Architecture could guidedevelopers • Define/enforce layering • Group related modules/packages • Define/enforce interface-implementation • Prevent dependency proliferation • Allow for future module replacement • Guide new developers • Phased/parallel development • Modularity! • …
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63. Bridging the divide 1.Start visualizing the structure you have now
- 64. Bridging the divide 1.Start visualizing the structure you have now 2. Lock-in any useful architecture you have now – overlay the visualization
- 65. Bridging the divide 1.Start visualizing the structure you have now 2. Lock-in any useful architecture you have now – overlay the visualization 3. Improve/extend the architecture – development gets easier and easier
- 66. • You’re goingto need a tool… • That parses code • Hierarchical dependency model • Architectural overlays
- 67. • You’re goingto need a tool… • That parses code • Hierarchical dependency model • Architectural overlays • SonarGraph Hierarchical dependency graph
- 68. DSM - DependencyStructure Matrix • You’re going to need a tool… • That parses code • Hierarchical dependency model • Architectural overlays • SonarGraph • Lattix • IntelliJ Idea Ultimate Hierarchical dependency graph
- 69. DSM - DependencyStructure Matrix LSM – Levelized Structure Map • You’re going to need a tool… • That parses code • Hierarchical dependency model • Architectural overlays • SonarGraph • Lattix • IntelliJ Idea Ultimate • Structure101 Hierarchical dependency graph
- 70. Step 1: Visualizewhat you have
- 71. Step 1: Visualizewhat you have • Immediate productivity boost – A map of the codebase
- 72. Step 1: Visualizewhat you have • Immediate productivity boost – A map of the codebase • See the details in the context of the de facto architecture, e.g. – Eclipse projects – IntelliJ modules – Maven POMs – Java 9 modules – …
- 73. Step 1: Visualizewhat you have • Immediate productivity boost – A map of the codebase • See the details in the context of the de facto architecture, e.g. – Eclipse projects – IntelliJ modules – Maven POMs – Java 9 modules – … • Raise structural awareness – Start simplifying the codebase - reduce coupling and complexity
- 74.
- 75. Step 2: Lockin and shore up de facto architecture
- 76. Step 2: Lockin and shore up de facto architecture • Organize modules into groups
- 77. Step 2: Lockin and shore up de facto architecture • Organize modules into groups • Specify module dependency constraints
- 78. Step 2: Lockin and shore up de facto architecture • Organize modules into groups • Specify module dependency constraints • Overlay onto the visualization – Understand the details in the context of the spec’d architecture – Warned immediately if edits violate spec
- 79. Step 2: StructureSpec Demo
- 80. Step 3: Incrementallyimprove the architecture/structure
- 81. Step 3: Incrementallyimprove the architecture/structure • Deal with the monoliths – Increase %specified
- 82. Step 3: Incrementallyimprove the architecture/structure • Deal with the monoliths – Increase %specified • Lift lower packages into modules
- 83. Step 3: Incrementallyimprove the architecture/structure • Deal with the monoliths – Increase %specified • Lift lower packages into modules • Disentangle packages… – Small/easy: In the code – Broader: Simulate first – Move classes, then refactor for dependencies
- 84. Step 3: Incrementallyimprove the architecture/structure • Deal with the monoliths – Increase %specified • Lift lower packages into modules • Disentangle packages… – Small/easy: In the code – Broader: Simulate first – Move classes, then refactor for dependencies • … and/or Extract modules – Simulate first – Add new module to spec – Refactor for dependencies, then move classes
- 85. Step 3: Structure101Studio Demo
- 86.
- 87. Bridging the gap… Summary 1.Start visualizing the structure you have now
- 88. Bridging the gap… Summary 1.Start visualizing the structure you have now 2. Lock-in and shore-up any useful architecture you have now – overlay the visualization
- 89. Bridging the gap… Summary 1.Start visualizing the structure you have now 2. Lock-in and shore-up any useful architecture you have now – overlay the visualization 3. Improve/extend the architecture – development gets easier and easier
- 90. Questions? @chedgey chris@structure101.com structure101.com Early access toWorkspace: 2018.structure101.com
Editor's Notes
- #67 You cannot do structure in the IDE alone – structure emerges from the code
- #68 You cannot do structure in the IDE alone – structure emerges from the code
- #69 You cannot do structure in the IDE alone – structure emerges from the code
- #70 You cannot do structure in the IDE alone – structure emerges from the code