Interpret UML diagrams.


Teaching Note:

LINK Connecting computational thinking and program design.


Sample Question:


JSR Notes:

When you are comfortable with OOP programming, and know the three things in the straight-forward sample on D.1.3, then you should be fine. The only thing I'll add here is arrows indicating where one class makes an instance of another, and also some inheritance.

The four new things here are:

The dotted line with "Has" indicates that the Student class has instances of the Schedule class as an attribute.

The dotted line with "Uses" indicates that the MainGUI class makes use of methods in the SortAndSearch class, and the Student class.

The line with the triangular arrow indicates a sub-class pointing to a super-class (an example of inheritance).


The final thing to note is that though "standard", you'll see lots of variation in UML diagrams. And that's arguably Ok, since UML is for you the programmer to help organize yourself - though you will be working with others, so the more standard you can keep things the better.

... But, frankly, the UML seen in the sample IB Paper 2 exam (as above) is really quite poor UML, and very non-standard. Never-the-less, that's the way they did it, so that's the way you should do it. Meantime, "for the record", scroll down below to see much more proper and widely-accepted UML.







Proper Class Diagram URL, for what it's worth, for your possible future studies/work:

uml example with inheritance