khansharkhamnida / p3-05

0 stars 0 forks source link

Report Milestone Two: 3.2 Functional Requirements #54

Open khansharkhamnida opened 1 year ago

khansharkhamnida commented 1 year ago

FR1: The system shall allow the manager to visualise the staff workload on the landing page. FR2: The system shall allow the manager to allocate jobs to staff for one week at a time. FR3: The system shall view up to three staff availability and any relevant information, such as the workload assigned, staff’s job preference, staff’s location at a particular date, and availability for the week to make the job assignment easier on the job allocation page. FR4: The system shall display the top three staff with the lowest workload FR5: The system shall highlight all staff with over 40 hours of jobs allocated on the manager’s landing page. FR6: The system shall allow the staff to view their weekly job assignments FR7: The system shall allow the staff to view their overall workload for the month on their landing page. FR8: The system shall allow the staff to add their availability up to 5 weeks ahead of time. FR9: The system shall allow the staff to edit their availability up to 5 weeks ahead of time. FR10: The system shall allow the staff to indicate their job preference for the week. FR11: The system shall allow the staff to reject jobs assigned to them. FR12: The system shall warn the staff to discuss with their manager before proceeding with rejection. FR13: The system shall allow the Administrator to manage managers and staff accounts. FR14: The system shall send an email to the staff upon successful creation of an account. FR15: The system shall send a notification to the manager via email when a staff rejects any jobs. FR16: The system shall remove jobs that are of the same location’s start point of the rejected job location’s end point. FR17: The system shall have a page that will display an overview of the airplanes based on its make and model. FR18: The system shall have a popup when the specific make and model is pressed on the overview of airplanes page. FR19: The system shall display the airplanes registration on the popup for the manager to choose from in the overview of airplanes page. FR20: The system shall bring the manager to the scheduling page when the airplane's registration is pressed. FR21: The system shall allow the manager to schedule based on the individual airplanes. FR22: The system shall have a schedule page on the individual airplanes. FR23: The system shall display the weekly schedule of the individual airplanes on the schedule page. FR24: The system shall allow the manager to pick which flight timing he or she wants to allocate on the specific airplane and date. FR25: The system shall allow the manager to pick which staff he or she wants to allocate on the specific airplane and date. FR26: The system shall include only those staff who are available on that day in the scheduling page. FR27: The system shall include only those staff who are available at location start point in the scheduling page. FR28: The system shall include only those staff who meet the rank criteria in the scheduling page. FR29: The system shall allow the manager to filter the staff based on the rank. FR30: The system shall warn the manager before submission of the schedule for each timing and each day if the staff’s schedule allocation does not meet the criteria of the pilots needed in the aircraft. FR31: The system shall notify the staff of any approval or rejection of the rejected job requests via email. FR32: The system shall bring users to different interfaces for different positions, such as IT Administrator, Staff and Manager. FR33: The system shall allow IT Administrator to create accounts. FR34: The system shall allow IT Administrator to delete accounts. FR35: The system shall allow IT Administrator to modify accounts.