Classes
What a class box represents and how to name and draw one.
UML diagrams, explained on video
19 short walkthroughs, mostly from the Georgia Tech Software Development Process course, with two full guides from Lucid Software. Pair them with the Chapter 9 documentation views.
Build a class diagram piece by piece, then tie it together.
What a class box represents and how to name and draw one.
Recording the data a class holds, with types and visibility.
Adding the behaviour a class offers, with parameters and return types.
Dependency, association, aggregation, composition and generalization.
When one class uses another only briefly, such as a parameter, and how the dashed arrow shows it.
Linking classes with associations and multiplicities, and marking whole–part aggregation.
Modelling is-a inheritance between a superclass and its subclasses.
Pick the right relationship for each scenario before watching the solution.
Walkthrough of the quiz answers and why each relationship fits.
Practical advice for turning requirements into a clean class diagram.
How a system is split up and where it runs.
How a system splits into components, the interfaces they provide and require, and how they wire together.
How software artifacts map onto physical nodes: devices, execution environments and the links between them.
What the system does and how objects talk over time.
Actors, use cases and the include / extend relationships that describe what a system does for its users.
A complete walkthrough of use case notation, from system boundary to generalization, with a worked example.
Lifelines, messages and activations: modelling an interaction as it unfolds in time.
Step-by-step construction of a sequence diagram, including fragments for loops and alternatives.
Where these diagrams fit in the wider development process.
Eliciting, analysing and specifying requirements before design begins.
Building the product right versus building the right product.
Corrective, adaptive, perfective and preventive maintenance after release.