[1.4.2] Restructuring Requirements

Work Done:

Reconstructed Functional Requirements and Non-Functional Requirements

Functional Requirements

FR1: The employee shall view their jobs and workload on the employee landing page. This view should include details about the studio, student and instrument associated with each job FR2: The employee shall have the option to view their jobs and workload by week, or month. The weekly view is in the format of 7 days, from 0900 to 2100 on Monday through Friday, and 0800 to 2100 on Saturday and Sunday. The monthly view is in a format of 28 days, 30 days, or 31 days. These do not include public holidays. FR3: The employee shall add, edit and delete and submit their availability. By default, this can be done up to 5 weeks before the due date, which is the 19th of every month. By default, the system will assume the employee is available throughout business hours. FR4: The employee shall have the option to add, edit, and delete their job preference. These preferences are the instrument, date and time they prefer to teach each lesson. By default, this can be done up to 5 weeks before the due date, which is the 19th of every month. FR5: The manager shall be able to specify the start and due date for employees to submit their availability and preferences. FR6: The employee shall have the option to request to reject job assignments. By default, a job rejection should be submitted 3 days in advance. FR7: The employee must provide a reason before the rejection can be submitted. FR8: The manager shall be able to specify how far in advance a rejection must be submitted. FR9: The employee shall have the option to cancel jobs. By default, the employee must cancel a job 1 hour prior to the start of the class. FR10: The manager shall have the option to specify how far in advance the employee must cancel a job. FR11: The employees shall have the option to export their workload and jobs into either PDF format, Excel format and PNG format FR12: The manager shall view the workload and jobs of employees. These views should include information such as studio, student, instrument and employee for each job. FR13: The manager shall have the option to view the employee's workload and jobs by day, week, month. The manager shall have the option to specify the time blocks to display the employee's workload and jobs in the daily view; 15 min, 30 min or 2 hrs. By default, it is displayed in 15 min time blocks. FR14: The manager shall have the option to filter the employee's workload and jobs by studio or employee FR15: The manager shall create a job and fill in the details such as date, time, student, studio and instrument taught. FR16: The manager has the option to edit existing jobs. They can edit the following details: date, time, studio, student, employee, instruments. FR17: The manager has the option to cancel jobs. By default, the manager can cancel a job any time prior to the start of the class. FR18: The manager shall have the option to specify how far in advance a manager must cancel a job. FR19: The manager shall be able to allocate jobs to employees for each business day within a specific week. FR20: The manager shall have the option to view the availability and preferences of employees while allocating jobs. This includes details about their workload, jobs, the available dates and times submitted by the employee and the preferred instrument, dates and times submitted by the employee. If no availability is submitted, the system will assume the employee is available throughout business hours. By default, the availability and preferences of up to 3 employees will be displayed. FR21: The manager shall have the option to publish job allocations. FR22: the manager shall have a standby list of employees. The standby list is for each individual job. manager shall allocate another employee from the backup list to take the job. FR23: The manager shall have the option to add employees to the standby list for each job during job allocation. The backup list is for each individual job. FR24: The manager shall be able to approve or deny job rejections from employees. If the job rejection is denied, the employee will be notified. If the job rejection is approved, the manager can allocate a new employee to the job. FR25: the manager shall have the option to allocate make-up jobs for the employees based on the employee's availability and preferences. FR26: The manager shall be able to view the employees with the over 40 working hours on the landing page FR27: The manager shall be able to view the employees with the lowest working hours on the landing page FR28: The manager shall be able to monitor how often the preferred instrument, dates and times submitted by the employees are fulfilled. The manager shall have the option to filter by instrument, dates and times, or both. FR29: The manager shall have the option to export the employee’s workload into either PDF format, Excel format and PNG format FR30: The admin shall create employee and manager accounts. FR31: The admin shall be able to edit and delete employee and manager accounts.

Non-Functional Requirements

NFR1: Each music school branch must operate on its own independent, monolithic workload management system. NFR2: The system shall be compatible with various web browsers (e.g., Chrome, Firefox, Safari) NFR3: The system shall have at least 99% uptime over any given month to ensure uninterrupted access for users. NFR4: The system shall provide multilingual support NFR5: The system shall respond to user interactions within 2 seconds. NFR6: The system must be capable of supporting concurrent users, ranging from 10-50 users up to a maximum of 250 users NFR7: The system shall handle a minimum of 10,000 workload items concurrently without significant performance degradation. NFR8: The system shall provide data recovery capabilities to ensure that data can be restored in case of accidental data loss or system failures. NFR9: The system shall have mechanisms in place for failover and disaster recovery to ensure minimal downtime in case of a system failure or unexpected events. NFR10: All passwords must follow these strong password requirements; minimum of 8 characters in length and consisting of at least 1 uppercase, 1 lowercase, and 1 number. NFR11: The system's encryption and database design must follow the standards outlined by the Infocomm Media Development Authority (IMDA) Telecommunication and Security Standards and the Cyber Security Agency of Singapore Security-by-Design Framework. NFR12: The system must follow the guidelines and provisions of the Personal Data Protection Act (PDPA).

Repository Commit status:

no commit

Completion Deadline Effect:

Changelog:

[Day/Month/2023] - (details) 20/09/2023 - Reconstructed Functional and Non-Functional Requirements

Start Date - End Date:

16/9 - 20/9

BenjaminTham-SIT / INF2001_P4-5