LOW LEVEL DESIGN · STEP 4 OF 9
Modeling and UML
Turning requirements into classes, and drawing them so an interviewer can follow. Each lesson is an animated walkthrough with a small Java example you can run, notes and the interview questions with answers.
- 1 Class diagrams and relationshipsHow to read and draw UML class diagrams for low-level design: the class box, visibility, association, aggregation, composition, inheritance, realization, dependency and multiplicity, each shown on a parcel locker system and mapped to Java code, plus a fast way to sketch one in an interview.
- 2 Use case diagramsHow to read and draw UML use case diagrams: primary and secondary actors, the system boundary, use cases as goals, include, extend and actor generalization, all on a clinic appointment system, plus how to use one in the first minutes of a design interview to fix the scope, with Java that turns each use case into a method.
- 3 Sequence diagramsHow to read and draw UML sequence diagrams: lifelines, activation bars, synchronous, asynchronous and return messages, and loop, alt and opt frames, all on one real flow, booking bus seats with a hold, a payment that may fail and a ticket message, with matching Java code that prints the same trace.
- 4 Activity diagramsHow to read and draw UML activity diagrams: start and end nodes, actions, decisions and merges with guards, fork and join for parallel work, swimlanes and a little object flow, shown on a job application workflow, with Java that codes the decisions as ifs and the fork and join with CompletableFuture, plus when to pick it over a sequence or state diagram.
- 5 From requirements to classesA repeatable method for the first fifteen minutes of any low-level design round: clarify the requirements, underline nouns to get candidate classes, drop the weak ones, turn verbs into methods, give each rule to the class that owns the data, add relationships, then check with one flow. Worked end to end on a gym class booking system in Java.