Assumptions:

• API/Server adds Alerts (Yellow/Red)
• All Events are recorded and sent to API/Server
• Only Timeline.Event(s) are added to the timeline

Components

Timeline

• Holds all Event(s)
• Add, Remove Events

Visual:

Timeline  +  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  |  -  +
Hour      0     1     2     3     4     5     6     7     8     9     10    11    12    13    14    15    16    17    18    19    20    21    22    23    24
Event                                                   Alarm                                                     Reminder Alert

Timeline.Event(s)

Built from a Factory

• 3 Types: Alarm, Alert, Reminder

Each contain:

• Entity: [User, API, Clock]
• Time: Date
• Action: ActionEvent to be Triggered when Event occurs

Interface

Any interface built will react to events by listening for ActionEvent. Example: If Alarm triggers ActionEvent, AlarmEvent, it will ring and wait for User to turn the alarm off.

Record

Note: All Actions from API, User, and Clock are considered events and are recorded. These events are separate from Timeline.Event(s).

Example: A 24 hour example of all recorded events.

Time  - Entity, Action
13:00 - User,   Add Alarm for 8:00
13:03 - User,   Add Reminder for 18:00
16:00 - API,    Add Alert for 19:00
18:00 - Clock,  Reminder Executes
18:10 - User,   Enters Sleep
...
7:30  - User,    Exits Sleep
8:00  - Clock,   Alarm Executes
8:01  - User,    Stops Alarm
...

• Final use cases
• Final diagram for a day of events
• Final class diagram (uml)
• Describe each part of the design, no more than 10 parts