Learn by designing a real system
Each project walks from raw requirements to finished artifacts — identifying objects, assigning responsibilities, drawing diagrams in Studio, and defending your design decisions. Work them in order or jump to the topic you need. Tick off steps as you go — your progress is saved in this browser.
- 01beginner
Online Course Management System
From raw requirements to a responsibility-driven class diagram - object identification, GRASP, and CRC cards.
Object listResponsibility tableCRC cards7 stepsStart - 02beginner
Smart Library Management
Actors and use cases, a SOLID-aware class diagram, and the Borrow Book interaction - the full front half of a design course.
Actor and use-case listSOLID-aware class diagramBorrow Book interaction outline10 stepsStart - 03intermediate
E-Commerce Order Processing
From an object model to a normalized relational schema - ER modeling, normalization, and class-to-table mapping.
Object modelER modelNormalized relational schema7 stepsStart - 04intermediate
Hospital Management
Entities, relationships, and ORM mappings - ownership, keys, cardinality, and loading strategies made concrete.
Entity relationship class diagramORM mapping exampleMapping decisions report6 stepsStart - 05intermediate
Online Food Delivery
Service boundaries, interactions, and API contracts - design the seams of a small service-based system.
Service responsibility mapOrder-flow interaction outlineComponent sketch6 stepsStart - 06advanced
Banking Transaction System
Apply Factory Method and Observer inside one domain model - creation variability and state-change notification, integrated properly.
Factory Method UMLObserver UMLIntegrated class diagram7 stepsStart - 07advanced
Smart Healthcare System
Architectural drivers, option comparison, and a defensible architecture decision - quality attributes made concrete.
Driver listArchitecture comparisonArchitecture sketch6 stepsStart - 08advanced
Integrated System Design
The capstone - requirements to objects to UML to database to APIs to architecture, unified in one system-design document.
Requirements summaryObject modelClass diagram8 stepsStart