ICT2201-P6-9 / air-manager

0 stars 0 forks source link

[M1 Feedback Minutes] #41

Closed JonTJT closed 1 year ago

JonTJT commented 1 year ago

Attached are the minutes of the M1 feedback meeting for your kind perusal. The text version is available below for your convenience.

JonTJT commented 1 year ago

M1 Report feedback minutes.docx

JonTJT commented 1 year ago

Assumptions of Non-Functional Requirement:

Issue: Users might be overseas at the current time; hence they need to be able to access the product system through the internet.

Action: As it has been highlighted as a Non-Functional Requirement, no further action is to be taken, however it will be recognised that this requirement is not considered as an assumption as described in the System Requirements Report

Requirement Background:

Issue: Methods on requirements solicitation were not properly addressed. Client requested to state interview exchanges in the report for better documentation of the product requirements.

Action: Include background interview with clients as part of the requirements introduction in future reports, etc. need to mention how we get the requirements

Update of Functional Requirements:

Issue: Functional requirements should include business requirements, such as roles of staff on the plane and types of aircrafts, which affects the number of required staff and required roles to be assigned to the flight

Action: Functional requirement to add roles of staffs and aircrafts, things to be included are,

Action: Re-evaluate the incorrect figures and updated it in future reports

Update Use Case Diagram

Issue:

  1. Administrator should only be allowed to create remove and edit account
  2. Extension use cases lacked the appropriate extension points in the diagram

Actions:

  1. Update Use Case Model by removing the use case relationship from the admin actor.
  2. Update Use Case Model to include extension points in all extension use cases.