Some UMLs
Activity Diagram
- black bars signify tasks start and end at same time
- Often decision diamonds don’t have questions inside
- instead, label the lines coming off it
Use Case Diagram
- class-based, not entity biased
- i.e. if trading works between users, only have one user; don’t have many instances of the same class
Sequence Diagram
- non-technical, clear
- user can be signified by a little stick man
- show “termination” of object with a cross
- box represents doing a thing
- nested activations represent recursive task
The Report
James really doesn’t want you to cram as many UMLs (and as many UML types) in as possible. Use them sparingly.