The Office of Student Life of a university has hired you to design a mobile app to help

students ease their frustrations when it is time to register for classes.

Below is a list of features that your client would like to include in the app:

Generate up to $50$ different schedules that fit your classes.

Filters to tailor the schedule to your life such as focusing on late classes,

minimizing gaps, and even input your work schedule and meeting times.

Port your created schedule to Google Calendar with the click of a button.

Follow classes and receive a notification when a spot opens up$.$

Task $1$: Create user stories for each of the features mentioned in the list above. You

may choose to have more than one user story for each feature. Each user story must

also include the acceptance tests$/$criteria$.$ Note that for each feature, you must show

at least one $($user story, acceptance criteria$)$ pair.

Task $2$: For each of the user stories from Task $1,$ list the following use case

information $($i$.$e$.,$ you must have exactly one use case for each user story$)$:

Name

Actors

Entry Conditions

Exit Conditions

Event Flow $($showing both basic and alternate flows $--$ required$)$

Special Requirements $($if any$)$

Task $3$: Create a UML use$-$case diagram for this app. There should be only one

diagram that includes all the use cases described. The use case diagram should clearly

show the actors, subject $($with boundary clearly shown$),$ use cases, associations

between actors and use cases, multiplicity of associations $($if any$)$ and relationships

between use cases $($if any$).$