Skip to main content

Design for Software Engineerings

Software design is the step where requirements become a structure of modules, classes and interfaces. It applies principles such as SOLID, separation of concerns and low coupling with high cohesion, and uses design patterns like Factory, Observer and Strategy as proven solutions. Good design makes later changes cheap and keeps the code understandable.

Stage: Design and Construction · Part of the Software Engineering roadmap · Last reviewed 19 November 2026

What to learn in Design

Design interview questions

What does the Open/Closed Principle mean?

Software entities should be open for extension but closed for modification. You add new behaviour by writing new code, for example a new class behind an interface, instead of editing tested code. This lowers the chance of breaking existing features, though it needs sensible abstractions to work.

When should you avoid using a design pattern?

Avoid a pattern when the problem is simple or has not yet repeated. Patterns add indirection, and forcing a Factory or Singleton onto a small script makes it harder to read. Introduce a pattern when you see a real, recurring pain such as duplicated branching logic, then refactor towards it.

Where Design fits in the Software Engineering roadmap

Design belongs to the Design and Construction stage (intermediate level), which takes about 33 hours. Write good code.

Back to the full Software Engineering roadmap