[ 06.html ]
[ uml0.html ]
and Chapter 22
and do Review Questions at the end of chapter 22.
I don't like the use of aggregation (<>-----) in this book's UML diagram.
I reccommnd you use a simple association (-------) with, possibly,
and arrow head (------>) instead. The book also omits multiplicities
on aggregations. It helps to show the non-default values: 1, 0..1, , etc.
Follow my notes
[ uml0.html ]
I don't like using these. I prefer UML sequence and communication
diagrams combined with class diagrams instead.
I will not refer to them in this course.
I think that the best place to start a project is by writing down a list of steps that help
a user achieve a valuable goal. The list of steps is called a
and provides a start on the "main program". A
can have many scenarios, including those where the user fails to get what the
A use case is a collection of scenarios that are assoicated with a
particular user achieving a particular goal.
Notice the numbering of the alternative scenario that indicates the step
where things go wrong.
Hand in one even numbered question+answer at the start of class.
- Student logs in with SID and password; system shows classes based on Paws report
- Student selects a course from reccomended list and system records enrolment
- Repeat until student logs out
Alternative Scenario 2a -- No open classes fit PAWS
- System suggests student talks to an advisor.
Alternative Scenario 1a -- Bad Password or SID
- Student can try twice more before account is locked
Bonus deadline for good project 1 today. Will be graded and
returned with the others.
[ 07q.html ]
[ lab04.html ]
uses the C++ technique mentioned in Chapter 14.1.
[ 08.html ]
plus Project 1 deadline and quiz 2.