use case: saving personalization settings locally

[ear7h]

Description

User's personalization settings are saved only to the device that the changes are made on.

User Goal

To save their favorited events, orgs and search terms on their local device for easy information access.

Actor

Student that does not have a verified email

Dependent Use Cases

23 favoriting events

12 favoriting subjects

11 favoriting orgs

Requirements

The system shall allow the user to store all favorites locally.

Pre-Conditions

Student does not have the event, or org favorited. i.e. student has not changed personalization settings.

Post-Conditions

When the student accesses the platform again, their favorites and filter types will be saved, and so be easily accessed.

Trigger

Favoriting an event, org or search term.

Workflow

1) The user favorites an org, or event. 2) The local data gets stored onto device for later use. 3) User closes and reopens app at later time. 4) Favorited object will be present under favorited items.

Alternative Workflow

1) User designates filter type for search. 2) Filter type is saved. 3) User closes and reopens app at later time. 4) The same filter type will be available to be applied to search on local device.

Dependent Design Use cases

None.

Design Workflow

1. The user shall favorite an event, or org or input a search term.
2. The controller shall add the entity to the model and saves it to localStorage.
3. The view shall be updated to represent the updated model.

Design Alternative Workflow

None.

[anthonymeng7]

Prior requirement: Student has favorited a new item, or changed their filtering type.

Requirements: The system shall allow the user to store all favorites locally.