The February 15 discussion identified the following list of classes and objects.
| Class | Some Attributes | Needed Objects of Class |
|---|---|---|
| PersonsSchedule | week | One object per schedule |
| Owner | ||
| Days | ||
| Day | Date | One object per day |
| appointments | ||
| Appointment | StartingTime | One object for each appointment |
| EndingTime | ||
| General Annotation | ||
| Private Comment | ||
| MonthlyCalendar | One object for each month | |
| StudentClass | [group with capabilities] | |
| OwnerClass | [Individual with capabilities | |
| OutsiderClass | [group with capabilities] | |
| FromAddress | One object per sent message | |
| ToAddress | ||
| SubjectLine | ||
| Body | ||
| Login | Username | One object per individual |
| Password | ||
| Announcements | Instructions | One object per PersonsSchedule |
| OwnersText | ||
| GUIInterface | One object per user | |
| File | FileName | One object per PersonsSchedule |
This and previous discussions also identified the following classes derived from Class Appointment:
| ApptUnavailable: | appointments cannot be made during this time |
| ApptPossible: | appointments are possible during this time (although outsiders always will have to sign up via e-mail) |
The Class ApptPossible in turn has these derived classes:
The February 15 discussion also identified the following use cases.
This document is available on the World Wide Web as
http://www.cs.grinnell.edu/~walker/courses/223.sp02/project/classes-uses-1.html
|
created February 17, 2002 last revised February 17, 2002 |
|
| For more information, please contact Henry M. Walker at walker@cs.grinnell.edu. |