Philosophy of Software Design — Chapters 5 & 6

Philosophy of Software Design — Chapters 5 & 6

John K. Ousterhout

Information Hiding (and Leaking)

General-purpose Modules are Deeper

1 / 10
volgende
Slide 1: Slide
newEditorSoftwareontwikkelingHBOStudiejaar 1

In deze les zitten 10 slides, met interactieve quizzen en tekstslides.

time-iconLesduur is: 45 min
Dit is niet oké

Onderdelen in deze les

Philosophy of Software Design — Chapters 5 & 6

John K. Ousterhout

Information Hiding (and Leaking)

General-purpose Modules are Deeper

Recap: what do you remember from last time?

Tactical vs. strategical programming

Modules should be deep

Chapter 5: Information hiding

Information hiding is a key strategy for creating deep modules. It reduces complexity by concealing implementation details and minimizing what other modules need to know.

Have you encountered any modules in LessonUp which suffer from information leakage?

Was there a time when a well-designed module saved you from having to understand complex internals?

Chapter 6: General purpose modules

Over-specialization is a major source of complexity. Designing modules to be somewhat general-purpose increases reuse, reduces duplication, and makes systems easier to understand.

What trade-offs exist between making a module general-purpose versus special-purpose?

What is your main takeaway from today's chapters?

Next time


Chapter 7: Different Layer, Different Abstraction

Chapter 8: Pull Complexity Downwards