Advanced Levelization Techniques (part 1 of 3)
summary
Covers concrete physical‑design rules: every component is an h/cpp pair with the header included first, all externally visible entities declared in the header and defined only in the cpp, and never using local externs so the include graph is authoritative. Shows tools and enforcement such as BDE verify clang tool, explains packaging (components, packages, package groups) and level numbers, and gives actionable leviz techniques like escalation to break cycles with a box/rectangle example. Watch if you want rules plus code‑level fixes, not just theory.
AI-written summary · about
chapters (11)
- 0:00Introduction to levelization
- 1:46Logical vs physical design
- 10:15Component properties and rules
- 20:58Defining a component
- 25:04Implied physical dependencies
- 28:13Essential physical design rules
- 30:00Collocating public classes
- 35:38Aggregation levels and packages
- 41:40Package hierarchy and reuse
- 54:06Leviz techniques introduction
- 55:30Escalation technique explained
related talks
01h 01mMaintainability and Refactoring Impact of Higher-Level Design Features
01h 30mC++ Modules and Large-Scale Development
01h 21mEmpirically Measuring, & Reducing, C++’s Accidental Complexity
01h 30mC++ Modules and Large-Scale Development
58mA Practical Guide to Loose Coupling
50mCore and other guidelines. The good, the bad, the... questionable?
01h 02mLakos’20: The “Dam” Book is Done!
55mC++ Core and Other C++ Guidelines - The Good, the Bad, the… Questionable?