Mhidayah19 / INF2001-P5_1

0 stars 0 forks source link

1.1.4 Formulate functional requirements(FR) and non-functional requirements(NFRs) #4

Closed LilZBJ closed 12 months ago

LilZBJ commented 1 year ago
  1. Task title ID: Formulate functional requirements(FRs) and non-functional requirements(NFRs)#04

  2. What is this task about? Formulating FRs and NFRs based on the initial requirements and project description provided by the client, and the discussion and emails with the client.

  3. What are the goals of the task? For the FRs, it is to provide high-level statements of what our system should do. It should describe the user requirement in detail, map a problem to a solution without implementation detail and in a way that the client and users can understand, and also to describe the how the system interacts with its environment.

NFRs will describe how well the system should perform. This includes quality attributes, such as reliability, security, usability and performance, as well as design constraints, such as response times and platform constraints.

  1. Success or completion criteria. Describe in detail When FRs and NFRs have all been formulated and agreed upon by the team.

  2. Allocated time 1 week

  3. Start and end date for the issue/task Start date: 12th September,2023 (Tuesday), End date: 19th September 2023 (Tuesday)

  4. Who is the owner? Owner is the person in charge of the task and should be created and maintained by the owner. Owner: 2201476, Lim Jun Hui (jhlim0079)

  5. Task Status. Usually under "To-Do". To-Do

  6. What is the priority of this task? High priority

jhlim0079 commented 12 months ago
  1. Describe the work done in detail Functional requirements(FRs) and non-functional requirements(NFRs) for the project have been formulated.

Functional Requirements

Manager access landing page The manager shall be able to access the manager landing page.

Pilot workload on manager landing page The pilot workload shall be immediately visible on the manager landing page, up to one month earlier.

Airline manager access job allocation page The airline manager shall be able to access the job allocation page.

Airline manager allocating jobs to pilots The airline manager shall be able to allocate jobs to pilots every week, on the job allocation page. The jobs must account for the external requirement Air Navigation (121 — Commercial Air Transport by Large Aeroplanes) Regulations 2018: Minimum of 10 hours rest in rest period including a local night, 12 hours minimum rest without a local night, 2 day offs per week where there are no duties for 34 hours, and pilot staff cannot be rostered to work more than 7 consecutive days with no off days, and 8 days off every 4 weeks .

Airline manager viewing three pilot’s availabilities The airline manager shall be able to view up to three pilot’s availabilities on the job allocation page.

Airline manager access pilot availability page The airline manager shall be able to access the pilot availability page.

Airline manager view assigned workload The airline manager shall be able to view workload that has already been assigned to pilots on the pilot availability page.

Airline manager view pilot’s preference The airline manager shall be able to view the pilot’s preferred job on the staff availability page.

Airline manager view pilot’s location The airline manager shall be able to view where the pilot will be located on a particular date on the staff availability page.

Airline manager view availabilities for the week The airline manager shall be able to view the pilots’ availability for the week on the staff availability page.

Manager view highlighted pilots on the landing page The top three pilots with the lowest workload, as well as pilots with over 40 hours of jobs allocated, shall be highlighted on the manager landing page.

Airline manager viewing aircraft availability The airline manager shall be able to view aircraft availability on the job allocation page.

Airline manager allocate jobs based on route The airline manager shall be able to allocate short haul or long haul jobs depending on the route on the job allocation page.

Pilots access employee(pilot) landing page The pilots shall be able to access the employee(pilot) landing page.

Pilots viewing workload The pilots shall be able to view their weekly job assignments and overall monthly workload on the staff landing page.

Pilots adding or editing availabilities The pilots shall be able to add or edit their availability up to 5 weeks ahead of time on the employee(Pilot) landing page.

Pilots indicating job preference The pilots shall be able to indicate their preference of their jobs up to 5 weeks ahead of time on the employee(Pilot) landing page.

Pilots rejecting job assignments The pilots shall be able to reject job assignments on the employee(Staff) landing page.

Warning pilots on rejecting job assignments A warning shall indicate that pilots should discuss job rejections with the airline manager.

IT administrators can add personnel The company’s IT administrators can add new employees, such as airline managers or pilots, into the system.

Non-functional requirements

Reliability The system shall not experience downtime of more than 1 hour per week(168 hours) of operation.

Security The system shall encrypt sensitive data such as passwords using Secure Hash Algorithm(SHA)-256.) (Additional: The system shall send and receive data using HyperText Transfer Protocol (Secure) (HTTPS) to prevent man-in-the-middle attacks) (Additional 2: The website shall have a valid Secure socket layer (SSL) certificate.)

Usability Pilots, airline managers, and IT administrators shall be able to learn all the functions of the system in under 5 hours. After this training, errors made by experienced users shall not exceed 3 per hour of system use.

Performance The system shall respond to user clicks in under 0.5 seconds.

Platform constraints The web-based application shall be able to support the five most used browsers: Google Chrome, Safari, Edge, Samsung Internet, and Mozilla Firefox.

  1. Has this work been committed to the repo? Work has been committed to repo as of 19 September 2023(Tuesday).

  2. How does the work affect success of completion criteria? FRs help the client and team to understand how the system should interact with the environment, while NFRs help to describe how well the system should perform.

  3. Start and end date of the work done Start date: 12th September,2023 (Tuesday), End date: 19th September 2023 (Tuesday)