Practice App Requirements

Practice App Requirements

1. Functional Requirements

1.1. 🧍 User Requirements

1.1.1. 🔑 Authentication

1.1.1.1. Signup

• 1.1.1.1.1. Guests shall enter their name, email address and passwords to be able to sign up. These are the required information that users have to provide to enter the app.

1.1.1.2. Login

• 1.1.1.2.1. Users shall provide their username and passwords to be able to login if they logged out or they are kicked out due to long inactivity.

1.1.2. 💡 User Interaction

1.1.2.1. User - Event Interaction

1.1.2.1.1. Creating Events

• 1.1.2.1.1.1. Users shall be able to create events by providing a title, description, a valid date, a valid location, and a valid lesson ID.

1.1.2.1.2. Viewing Events

• 1.1.2.1.2.1. Users shall be able to view events they have attended.

1.1.2.1.3. Attending Events

• 1.1.2.1.3.1. Users shall be able to attend events by providing the event id.

1.1.2.1.4. Getting Specific Event Details

• 1.1.2.1.4.1. Users shall be able to see the specific event details, such as “title”, “location”, “host id”, “lesson id”, and “date”, by providing the event id.

1.1.2.2. User - Lecture Interaction

1.1.2.2.1. Enrolling Lessons

• 1.1.2.2.1.1. User should provide his/her user_id and lesson_id of the lesson wants to take.
• 1.1.2.2.1.2. User has to have not taken this lesson before.

1.2. 💻 System Requirements

1.2.1. 🔎 Searching and Browsing

• 1.2.1.1 The system shall allow to filter the lessons according to their categories.
• 1.2.1.2 User should provide keywords wanted to be searched.
• 1.2.1.3 User shall be able to see any category if the category includes a keyword on its name.

2. Non-Functional Requirements

2.1. 🧩 Usability

• 2.1.1 The system should provide a user-friendly interface. It should contain a basic site map and should not contain a confusing linking system.
• 2.1.2 The system should provide a direct feedback mechanism. The moment people interact with the system, we should offer an indication of the success or failure of their actions.
• 2.1.3 The system should have a well-chosen typeface that should be readable and clean without diverting too much attention from the rest of the design.