HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T1 Bumblebee Project Documentation"

From IS480
Jump to navigation Jump to search
 
(38 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Image:BumbleBee_logo.jpg|350px|right]]
+
{| style="background-color:#ffffff; color:#ffffff padding: 5px 0 0 0;" width="100%" height="20px" cellspacing="0" cellpadding="0" valign="top" border="0" |
 +
| style="padding:0 .3em;  font-size:100%; border-right:2px solid #ffffff ;  border-bottom:2px solid #ffffff ;text-align:center; background-color#ffffff" width="20%" |
 +
| style="padding:0 .3em;  font-size:100%;  border-right:2px solid #ffffff ;text-align:center; background-color:#ffffff ; " width="20%" |
 +
| style="padding:0 .3em;  font-size:100%; border-right:2px solid #ffffff ; border-bottom:2px solid #ffffff ; text-align:center; " width="20%" | [[Image:Bao.png|130px|center]]
 +
| style="padding:0 .3em;  font-size:100%; border-right:2px solid #ffffff ; border-bottom:2px solid #ffffff ;text-align:center; background-color:#ffffff; " width="20%" |
 +
| style="padding:0 .3em;  font-size:100%; border-bottom:2px solid #ffffff ; text-align:center; background-color:#ffffff; " width="20%" |
 +
|}
  
 
<!--Navigation-->
 
<!--Navigation-->
Line 14: Line 20:
 
| style="padding:0.3em; font-size:90%; background-color:#FBB917; border-bottom:2px solid #000000;text-align:center; " width="12%"|[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_User Interface|<font face = "century gothic" color="#000000">User Interface</font>]]
 
| style="padding:0.3em; font-size:90%; background-color:#FBB917; border-bottom:2px solid #000000;text-align:center; " width="12%"|[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_User Interface|<font face = "century gothic" color="#000000">User Interface</font>]]
 
| style="padding:0.3em; font-size:90%; background-color:#FBB917; border-bottom:2px solid #000000;text-align:center; " width="12%"|[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_User Manual|<font face = "century gothic" color="#000000">User Manual</font>]]
 
| style="padding:0.3em; font-size:90%; background-color:#FBB917; border-bottom:2px solid #000000;text-align:center; " width="12%"|[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_User Manual|<font face = "century gothic" color="#000000">User Manual</font>]]
| style="padding:0.3em; font-size:90%; background-color:#FBB917; border-bottom:2px solid #000000;text-align:center; " width="12%"|[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_User Acceptance Test|<font face = "century gothic" color="#000000">User Acceptance Test</font>]]
+
| style="padding:0.3em; font-size:90%; background-color:#FBB917; border-bottom:2px solid #000000;text-align:center; " width="12%"|[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_User Acceptance Test|<font face = "century gothic" color="#000000">User Testing</font>]]
 
| style="padding:0.3em; font-size:90%; background-color:#FBB917; border-bottom:2px solid #000000;text-align:center; " width="12%"|[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_Meeting Minutes|<font face = "century gothic" color="#000000">Meeting Minutes</font>]]
 
| style="padding:0.3em; font-size:90%; background-color:#FBB917; border-bottom:2px solid #000000;text-align:center; " width="12%"|[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_Meeting Minutes|<font face = "century gothic" color="#000000">Meeting Minutes</font>]]
 
| style="padding:0.3em; font-size:90%; background-color:#FBB917; border-bottom:2px solid #000000;text-align:center; " width="12%"|[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_Presentations|<font face = "century gothic" color="#000000">Presentations</font>]]
 
| style="padding:0.3em; font-size:90%; background-color:#FBB917; border-bottom:2px solid #000000;text-align:center; " width="12%"|[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_Presentations|<font face = "century gothic" color="#000000">Presentations</font>]]
Line 56: Line 62:
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 20%; font-size: 13px;" valign="top"  | <b>Brief Description</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 20%; font-size: 13px;" valign="top"  | <b>Brief Description</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | User can import flight schedule.csv, flight requirements, staff record.csv and staff roster.csv. System will store information in database.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |User can import flight_arrival_schedule.csv/txt, flight_departure_schedule.csv/txt, flight_requirements.csv/txt, staff_record.csv/txt and staff_roster.csv/txt. System will store information in database.
  
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Flow of Events</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Flow of Events</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |  1) User clicks “Browse” and selects targeted files - Flight Schedule.csv, Roster Plan.csv, Staff Record.csv and Flight Requirements.csv.  
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |  1) User selects “Browse” and selects targeted file - flight_arrival_schedule.csv/txt, flight_departure_schedule.csv/txt, flight_requirements.csv/txt, staff_record.csv/txt and staff_roster.csv/txt.
  
2) User clicks on “Bootstrap” button.
+
2) User selects “Bootstrap” button.
  
3) System will load the data from the CSV files into corresponding tables in the database.
+
3) System will load the data from the csv or txt files into corresponding tables in the database.
  
 
4) System will direct user to “Manage Simulation Parameters” page.
 
4) System will direct user to “Manage Simulation Parameters” page.
Line 70: Line 76:
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Alternate Flows</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Alternate Flows</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | 1) User selects file with wrong file type (e.g. .txt instead of .csv). System will prompt user to re-select file.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | NA
  
2) User does not select any file. System will prompt user to select file before bootstrap.  
+
|-
 +
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Special Requirements</b>
 +
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | User must select the right csv/txt files with the right formats.
  
3) User selects file with wrong format. System will prompt user which file format is wrong and request user to re-select file.
+
Data format is ignored if irrelevant
  
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Special Requirements</b>
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | User must select the right csv files with the right formats.
 
  
'''Flight Schedule Format'''
+
'''Flight Schedule Format - Departure'''
  
 
Column A: Flight (Text)
 
Column A: Flight (Text)
Line 131: Line 136:
  
 
Column Y: Rem. DEP Daily
 
Column Y: Rem. DEP Daily
 +
 +
 +
'''Flight Schedule  Format - Arrival'''
 +
 +
Column A: Flight (Text)
 +
 +
Column B: C/S (Text)
 +
 +
Column C: ORG (Text)
 +
 +
Column D: VIA (Text)
 +
 +
Column E: nVIA (Number)
 +
 +
Column F: A
 +
 +
Column G: Na (Text)
 +
 +
Column H: STA (h:mm)
 +
 +
Column I: ETA (h:mm)
 +
 +
Column J: TMO
 +
 +
Column K: ATA (h:mm)
 +
 +
Column L: RWY
 +
 +
Column M: EON (h:mm)
 +
 +
Column N: ONB (h:mm)
 +
 +
Column O: POS (Text)
 +
 +
Column P: Gate 1 (Text)
 +
 +
Column Q: Belt (Text)
 +
 +
Column R: REG (Text)
 +
 +
Column S: A/C (Text)
 +
 +
Column T: Date ATA (Text)
 +
 +
Column U: STATE
 +
 +
Column V: REM
 +
 +
Column W Rem. ARR
 +
 +
Column X: Rem. ARR Daily
 +
 +
 +
'''Flight Requirements Format'''
 +
 +
''Gate Departure''
 +
 +
Column A: Airline (Text)
 +
 +
Column B: Aircraft Type (Text)
 +
 +
Column C: CSO at Gate (Number)
 +
 +
Column D: CSA at Gate (Number)
 +
 +
Column E: Gate Opening Hours (Number)
 +
 +
''Counter Departure''
 +
 +
Column G: Airline (Text)
 +
 +
Column H: No of Narrow Aircraft (Number)
 +
 +
Column I: No of Wide Aircraft (Number)
 +
 +
Column J: CSO at Counter (Number)
 +
 +
Column K: CSO at Counter (Number)
 +
 +
Column L: Counter Opening Hours(Number)
 +
 +
''Gate Arrival''
 +
 +
Column N: Airline (Text)
 +
 +
Column O: CSO at Gate (Number)
 +
 +
Column P: CSO at Gate (Number)
  
  
Line 202: Line 295:
 
'''Staff Roster Format'''
 
'''Staff Roster Format'''
  
TBC by client
+
Column A: StaffNo (Text)
 +
 
 +
Column B: RosterID (Text)
  
 +
Column C: RosterCycle (Text)
  
'''Flight Requirements Format'''
+
Column D: Mon (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)
  
Airline_Name
+
Column E: Tue (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)
  
No_of_Narrowed_Flights
+
Column F: Wed (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)
  
No_of_Wide_Flights
+
Column G: Thu (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)
  
Required_CSA
+
Column H: Fri (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)
  
Required_CSO
+
Column I: Sat (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)
  
 +
Column J: Sun (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)
  
 
|-
 
|-
Line 228: Line 325:
 
|-
 
|-
 
|}
 
|}
 +
'''
  
 
====Manage Airline Requirements====
 
====Manage Airline Requirements====
Line 241: Line 339:
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Flow of Events</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Flow of Events</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | 1) User clicks on “Manage Airline Requirements”.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | 1) User selects on “Manage Airline Requirements”.
 +
 
 +
2) System will direct user to Manage Airline Requirements page where user can choose to manage requirements of airlines.
 +
 
 +
3) There are 3 tabs in Manage Airline Requirements: Gate Departure, Counter Departure or Gate Arrival.
 +
 
 +
4) Gate Departure tab
 +
 
 +
i. User chooses airlines and the system will displayed the flight requirements of the particular airline in table.
 +
 
 +
ii. User then chooses the aircraft type from the dropdown list provided and fill in the required number of counter CSA and CSO and gate opening hour.
 +
 
 +
iii. User selects “Save” button.
  
2) System will direct user to Manage Airline Requirements page where user can choose to manage counter requirements of airlines.
+
iv. System will save and display user’s newly added requirement in the table.
  
3) User chooses airlines and the system will displayed the flight requirements of the particular airline.
+
5) Counter Departure tab
  
4a) User may then add on the list of user requirements, by choosing the number of narrow or/and wide body flight(s) and its required number of CSA and CSO.
+
i. User chooses airlines and the system will displayed the flight requirements of the particular airline in table.
  
5a) User clicks “Save” button.
+
ii. User may then add on the list of user requirements, by choosing the number of narrow or/and wide body flight(s) and its required number of counter CSA and CSO and counter opening hour.
  
6a) System will save and display user’s inputs and use these criteria to simulate the roster plan.
+
iii. User selects “Save” button.
  
4b) User select existing flight requirements listed on table and clicks “Edit” button
+
iv. System will save and display user’s newly added requirement in the table.
  
5b) System will populated the field with the respective values selected.
+
6) Gate Arrival tab
  
6b) User changes the value and clicks “Save” button.
+
i. User chooses airlines and the system will displayed the flight requirements of the particular airline in table.
 +
 
 +
ii. User may then add the required number of gate CSA and CSO.
 +
 
 +
iii. User selects “Save” button.
 +
 
 +
iv. System will save and display user’s newly added requirement in the table.
  
7b) System will save and display user’s inputs and use these criteria to simulate the roster plan.
 
 
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Alternate Flows</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Alternate Flows</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | 1) Some fields such as condition, required CSO or required CSA are left empty when user clicks “Save”.  
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |1) Edit Airline Requirements
 +
 
 +
i. User selects existing flight requirements listed on table and selects “Edit” button
 +
 
 +
ii. User changes the value and selects “Save” button.
 +
 
 +
iii. System will save and display user’s inputs and populate the new edited data into the table list of airline requirements.
 +
 
 +
2) Delete Airline Requirements
 +
 
 +
i. User selects existing flight requirements listed on table.
 +
 
 +
ii. User selects “Delete Row” button.
 +
 
 +
iii. System will delete the selected existing row of data.
  
2) System will prompt that there is an incomplete input in the empty field.
 
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Special Requirements</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Special Requirements</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | All fields must be filled before save.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |All fields must be filled before data can be saved.
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Preconditions</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Preconditions</b>
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | User wants to customize the airline requirements for certain flights.
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | User wants to customize the airline requirements for certain flights.
 
Bootstrap is completed.
 
  
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Post Conditions</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Post Conditions</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | Customise airline requirements will be saved into the database and will be used for simulation.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |Data of customized airline requirements will be saved into the database and will be used for simulation.
  
 
|-
 
|-
 
|}
 
|}
 
  
 
====Manage Simulation Paramaters====
 
====Manage Simulation Paramaters====
Line 291: Line 415:
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 20%; font-size: 13px;" valign="top"  | <b>Brief Description</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 20%; font-size: 13px;" valign="top"  | <b>Brief Description</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | User can input MC rate, staff resign rate, flight delay rate, new staff rate and call back staff.csv  for simulation.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | User can input CSA Monthly Salary, CSO Monthly Salary, OT Rate per hour, Recall rate per hour for both off day and rest day, MAC Cost per hour for breakfast, lunch, dinner and supper, simulation period, MC rate, ad hoc leave rate, staff resign rate, new staff rate for simulation.
  
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Flow of Events</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Flow of Events</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | 1) User keys in mean and standard deviation for uncertainties such as MC rate, staff resign rate, flight delay rate and new staff rate. User also input1) User keys in simulation period.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | 1) User keys in CSA Monthly Salary, CSO Monthly Salary, OT Rate per hour, Recall rate per hour for both off day and rest day, MAC Cost (breakfast, lunch, dinner and supper).
 +
 
 +
2) User keys in simulation period.
  
2) User keys in mean and standard deviation for uncertainties such as MC rate (person/day), ad-hoc leave rate (person/day), staff resign rate (person/month), and new staff rate (person/month).  
+
3) User keys in mean and standard deviation for uncertainties such as MC rate (person/day), ad-hoc leave rate (person/day), staff resign rate (person/month), and new staff rate (person/month).  
  
3) User clicks “Start Simulation” button.  
+
4) User selects “Start Simulation” button.  
  
4) System will generate a normal distribution for each parameter.  
+
5) System will generate a normal distribution for each parameter.  
  
5) System will generate a normal distribution for flight delays based on flight schedule.csv
+
6) System will generate a normal distribution for flight delays based on flight arrival schedule.csv and flight departure schedule.csv.
  
6) System will store the parameters and the generated distribution in the database.  
+
7) System will store the parameters and the generated distribution in the database.  
  
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Alternate Flows</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Alternate Flows</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |1) User inputs a value that is not valid (e.g. negative value or non numerical value for MC rate).
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |NA
 
 
2) System will prompt user to re-enter the value.
 
  
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Special Requirements</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Special Requirements</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | User must key in a valid value for the parameters. All parameters are mandatory.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | User must key in a valid value for the simulation parameters.  
 +
Input for OT cost, Recall cost, MAC Cost and Simulation Period are mandatory.
 +
Input for MC rate, ad hoc leave rate, staff resign rate, new staff rate for simulation are not mandatory but both mean and standard deviation of each parameter are required once either one of the input fields is filled.
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Preconditions</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Preconditions</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |User wants to input parameters into the database for simulation purpose.  
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |UUser wants to input the simulation parameters into the database for simulation purpose.  
User’s inputs for parameters are valid and correct.
+
User’s input for parameters are valid and correct.
 
 
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Post Conditions</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Post Conditions</b>
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | Parameters will be stored into the database according to user’s inputs.
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | Parameters will be stored into the database according to user’s inputs.
 
+
Simulation Parameters.csv, Flight Arrival Simulation Parameters.csv, Flight Departure Simulation Parameters.csv are created.
Simulated value of each parameter is generated by the system.
 
  
 
|-
 
|-
Line 339: Line 463:
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 20%; font-size: 13px;" valign="top"  | <b>Brief Description</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 20%; font-size: 13px;" valign="top"  | <b>Brief Description</b>
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | Based on input flight schedule and flight requirements, system will allocate tasks to staff based on their qualifications and their corresponding roster.  
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | Based on input flight schedule and flight requirements, system will allocate tasks to staff based on their qualifications and their corresponding roster.  
 +
Based on the given uncertainties, system will apply uncertainties onto a roster plan. Following that, the system mimics action done by Duty Manager such as allocating task to other staff who is available at a particular time.
 +
  
Based on the given uncertainties, system will apply uncertainties onto a roster plan. Following that, the system mimics action done by Duty Manager such as allocating task to other staff who is free at a particular time.
 
  
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Flow of Events</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Flow of Events</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |1) User clicks “Start Simulation” after manage simulation parameters.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |1) User selects “Start Simulation” after filling up data for Manage Simulation Parameters.
  
2) System will Start Scheduling Staff Roster (stage 1/2) to fulfill all the flight requirements
+
2) System will Start Scheduling Staff Roster (stage 1/2) to fulfill all the flight requirements
  
3a) If user clicks “Cancel”, system will stop scheduling staff roster immediately.
+
3) After scheduling staff roster is successful, system will continue to simulate staff deployment (stage 2/2).
  
3b) After scheduling staff roster is successful, system will continue to simulate staff deployment (stage 2/2).
+
4) After system finished the deployment, system will direct user to Simulation Result page.  
  
4b) After system finished the deployment, system will direct user to Simulation Result page.
+
|-
 +
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Alternate Flows</b>
 +
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | 1) Cancel Simulation at stage 1
  
4c) User clicks on “Cancel” button.
+
i. User selects “Cancel”.
  
5c) System will stop the simulation. Only staff roster schedule will be updated in database.
+
ii. System will stop scheduling staff roster immediately.
 +
 
 +
2) Cancel Simulation at stage 1
 +
 
 +
i. User selects “Cancel”.
 +
 
 +
ii. System will stop the simulation. Only staff roster schedule will be updated in database.
  
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Alternate Flows</b>
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | NA
 
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Special Requirements</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Special Requirements</b>
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | Bootstrap is successful.
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | Bootstrap is successful.
Manage Simulation Parameters is done.  
+
Manage Simulation Parameters is done.
 +
Manage Airline Requirements is done if it is not bootstrapped.
  
 
|-
 
|-
Line 373: Line 504:
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Post Conditions</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Post Conditions</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | Staff schedule is created.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | Staff_Deployment_Roster table  in the database is populated.
 
Simulation result of the planned roster will be generated and displayed on simulation result page.
 
Simulation result of the planned roster will be generated and displayed on simulation result page.
 
 
 
|-
 
|-
 
|}
 
|}
 +
 
====Manage Result====
 
====Manage Result====
 
{| class="wikitable" cellpadding="15"
 
{| class="wikitable" cellpadding="15"
Line 386: Line 516:
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 20%; font-size: 13px;" valign="top"  | <b>Brief Description</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 20%; font-size: 13px;" valign="top"  | <b>Brief Description</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | This use case allows user to manage the result from the previous simulations. This includes filter function, view and deletes results function. User can choose to export viewed result as PDF. The result includes Total Staff Working Hours, Staff Utilization Rate, Unproductive Hours, OT Hours, OT Cost, Recall Cost, Recall Hours, Meal Allowance Compensation (MAC) and Flight Demand Coverage.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | This use case allows user to manage the result from the previous simulations. This includes filter function, view and deletes results function. User can choose to export viewed result as PDF. The result includes Total Staff Working Hours, Staff Utilization Rate, Unproductive Hours, OT Hours, OT Cost, Recall Cost, Recall Hours and Meal Allowance Compensation (MAC).
  
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Flow of Events</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Flow of Events</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | 1) User clicks on ‘Manage Result’ option.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | 1) User select the ‘Manage Result’ option.
 +
2) User can choose to filter the result specific to certain periods based on dates.
  
2) User can choose to filter the result specific to certain periods based on dates.
+
3) System will display the list of past simulation results within the periods specified.
  
3) System will display the list of past simulation results within the periods specified.
+
4) User selects the result.
  
4) User clicks on the result.
+
5) User views the result.
  
5) User can choose to
+
6) System displays the simulation result.
  
a.view the result.
+
7) User selects the “Export PDF” option.
  
b.delete the result(s).
+
8) System organizes the result into report structure.
  
6a) System displays the simulation result.  
+
9) System exports the result as PDF report and prompts user to locate destination to save the PDF report.
  
7a) User clicks on “Export PDF” option.
+
10) User locates destination and saves the file.
  
8a) System organizes the result into report’s structure.
+
|-
 
+
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Alternate Flows</b>
9a) System exports the result as PDF report and prompts user to locate destination to save the PDF report.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | Delete the result(s).
 
 
10a) User locates destination and saves the file.
 
  
 +
i. User ticks on the specific results.
  
6b) System will delete the record of result(s) selected.
+
ii. User selects the “Delete” button.
  
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Alternate Flows</b>
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | NA
 
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Special Requirements</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Special Requirements</b>
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |Simulate Staff Deployment is successful.
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |Simulate Staff Deployment is successful.
All uncertainties are mandatory.
 
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Preconditions</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Preconditions</b>
Line 432: Line 558:
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Post Conditions</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |<b>Post Conditions</b>
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  | Result is displayed/ viewed, filtered or deleted.
+
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |Result is displayed/ viewed, filtered or deleted.
 
The simulation result is exported into a PDF file.
 
The simulation result is exported into a PDF file.
  
Line 446: Line 572:
 
|}
 
|}
 
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation#Top|Back to Top]]</u></font></div>
 
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation#Top|Back to Top]]</u></font></div>
 
 
  
 
===<div style="color: #ffffff; font-size:0%">Sequence Diagram</div>===
 
===<div style="color: #ffffff; font-size:0%">Sequence Diagram</div>===
Line 479: Line 603:
 
|-
 
|-
 
|}
 
|}
 
===<div style="color: #ffffff; font-size:0%">ER Diagram</div>===
 
{| class="wikitable" cellpadding="15"
 
|-
 
| style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:lrft; border: 1px solid #ffffff" valign="top" | <b>ER Diagram</b>
 
|-
 
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
 
|-
 
| style= "background:#FBB917; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
 
[[Image:Bumblebee_ER_Diagram.jpg|center]]
 
<br/>
 
|-
 
 
|-
 
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
 
|-
 
|}
 
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation#Top|Back to Top]]</u></font></div>
 
 
===<div style="color: #ffffff; font-size:0%">Logical Diagram</div>===
 
{| class="wikitable" cellpadding="15"
 
|-
 
| style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:lrft; border: 1px solid #ffffff" valign="top" | <b>Logical Diagram</b>
 
|-
 
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
 
|-
 
| style= "background:#FBB917; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
 
[[Image:BumblebeeLogicalDiagram.jpg]]
 
|-
 
 
|-
 
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
 
|-
 
|}
 
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation#Top|Back to Top]]</u></font></div>
 

Latest revision as of 17:49, 9 October 2012

Bao.png
Home Project Overview Project Documentation Project Management Learning and Growth
Diagrams User Interface User Manual User Testing Meeting Minutes Presentations

Use Case

Use Case
Use Case Diagram v4.jpg


Use Case Description

Use Case Description

Bootstrap Data

Name Bootstrap Data
Brief Description User can import flight_arrival_schedule.csv/txt, flight_departure_schedule.csv/txt, flight_requirements.csv/txt, staff_record.csv/txt and staff_roster.csv/txt. System will store information in database.
Flow of Events 1) User selects “Browse” and selects targeted file - flight_arrival_schedule.csv/txt, flight_departure_schedule.csv/txt, flight_requirements.csv/txt, staff_record.csv/txt and staff_roster.csv/txt.

2) User selects “Bootstrap” button.

3) System will load the data from the csv or txt files into corresponding tables in the database.

4) System will direct user to “Manage Simulation Parameters” page.

Alternate Flows NA
Special Requirements User must select the right csv/txt files with the right formats.

Data format is ignored if irrelevant


Flight Schedule Format - Departure

Column A: Flight (Text)

Column B: C/S (Text)

Column C: DES (Text)

Column D: VIA (Text)

Column E: nVIA (Number)

Column F: A

Column G: Na (Text)

Column H: STD (h:mm)

Column I: ETD (h:mm)

Column J: COB

Column K: OFB (h:mm)

Column L: CTOT

Column M: RWY

Column N: ATD (h:mm)

Column O: POS (Text)

Column P: Gate 1 (Text)

Column Q: Gate 2 (Text)

Column R: CTR (Text)

Column S: REG (Text)

Column T: A/C (Text)

Column U: Date ATD (Text)

Column V: STATE

Column W REM

Column X: Rem. DEP

Column Y: Rem. DEP Daily


Flight Schedule Format - Arrival

Column A: Flight (Text)

Column B: C/S (Text)

Column C: ORG (Text)

Column D: VIA (Text)

Column E: nVIA (Number)

Column F: A

Column G: Na (Text)

Column H: STA (h:mm)

Column I: ETA (h:mm)

Column J: TMO

Column K: ATA (h:mm)

Column L: RWY

Column M: EON (h:mm)

Column N: ONB (h:mm)

Column O: POS (Text)

Column P: Gate 1 (Text)

Column Q: Belt (Text)

Column R: REG (Text)

Column S: A/C (Text)

Column T: Date ATA (Text)

Column U: STATE

Column V: REM

Column W Rem. ARR

Column X: Rem. ARR Daily


Flight Requirements Format

Gate Departure

Column A: Airline (Text)

Column B: Aircraft Type (Text)

Column C: CSO at Gate (Number)

Column D: CSA at Gate (Number)

Column E: Gate Opening Hours (Number)

Counter Departure

Column G: Airline (Text)

Column H: No of Narrow Aircraft (Number)

Column I: No of Wide Aircraft (Number)

Column J: CSO at Counter (Number)

Column K: CSO at Counter (Number)

Column L: Counter Opening Hours(Number)

Gate Arrival

Column N: Airline (Text)

Column O: CSO at Gate (Number)

Column P: CSO at Gate (Number)


Staff Record Format

Column A: Group(Text)

Column B: Function (Text)

Column C: STF NO. (Text)

Column D: NA

Column E: NA

Column F: DOJ (d-mmm-yy)

Column G: Year of Service (as of 2011) (number)

Column H: DCS Trained (number)

Column I: Sabre 9W (Text)

Column J: Sabre IT (Text)

Column K: Sabre BI (Text)

Column L: Sabre VN (Text)

Column M: BABS- BA (Text)

Column O: Travelsky - CA/CZ/HX/MF/MU/NX/ZH (Text)

Column K: Babel - EY (Text)

Column L: Babel - GE (Text)

Column M: Jalpas - JL (Text)

Column N: Topas - KE (Text)

Column O: Pictures - LH (Text)

Column P: Liason - MH (Text)

Column Q: Able- NH (Text)

Column R: Artis II - OZ (Text)

Column S: Smile - PR (Text)

Column T: Jalpas - JL (Text)

Column U: Altea - QF (Text)

Column V: Royal - TG (Text)

Column W: Troya- TK (Text)

Column X: Fastair - UA (Text)

Column Y: Shares - CO (Text)

Column Z: Smile - PR (Text)

Column AA: SITA - AI (Text)

Column AB: Kriscom - SQ (Text)


Staff Roster Format

Column A: StaffNo (Text)

Column B: RosterID (Text)

Column C: RosterCycle (Text)

Column D: Mon (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)

Column E: Tue (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)

Column F: Wed (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)

Column G: Thu (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)

Column H: Fri (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)

Column I: Sat (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)

Column J: Sun (Normal shift - Row [2]: Start Time, Row [3]: End Time, Split Shift – Row[2]: 1st Start Time – End Time, Row[3] 2nd Start Time – End Time) (Text)

Preconditions User wants to load data from CSV to database.
Post Conditions Data from the CSV is loaded to database.

Manage Airline Requirements

Name Manage Airline Requirements
Brief Description This use case allows user to customize (add, edit) the business logic of airline requirements in the simulation.
Flow of Events 1) User selects on “Manage Airline Requirements”.

2) System will direct user to Manage Airline Requirements page where user can choose to manage requirements of airlines.

3) There are 3 tabs in Manage Airline Requirements: Gate Departure, Counter Departure or Gate Arrival.

4) Gate Departure tab

i. User chooses airlines and the system will displayed the flight requirements of the particular airline in table.

ii. User then chooses the aircraft type from the dropdown list provided and fill in the required number of counter CSA and CSO and gate opening hour.

iii. User selects “Save” button.

iv. System will save and display user’s newly added requirement in the table.

5) Counter Departure tab

i. User chooses airlines and the system will displayed the flight requirements of the particular airline in table.

ii. User may then add on the list of user requirements, by choosing the number of narrow or/and wide body flight(s) and its required number of counter CSA and CSO and counter opening hour.

iii. User selects “Save” button.

iv. System will save and display user’s newly added requirement in the table.

6) Gate Arrival tab

i. User chooses airlines and the system will displayed the flight requirements of the particular airline in table.

ii. User may then add the required number of gate CSA and CSO.

iii. User selects “Save” button.

iv. System will save and display user’s newly added requirement in the table.

Alternate Flows 1) Edit Airline Requirements

i. User selects existing flight requirements listed on table and selects “Edit” button

ii. User changes the value and selects “Save” button.

iii. System will save and display user’s inputs and populate the new edited data into the table list of airline requirements.

2) Delete Airline Requirements

i. User selects existing flight requirements listed on table.

ii. User selects “Delete Row” button.

iii. System will delete the selected existing row of data.

Special Requirements All fields must be filled before data can be saved.
Preconditions User wants to customize the airline requirements for certain flights.
Post Conditions Data of customized airline requirements will be saved into the database and will be used for simulation.

Manage Simulation Paramaters

Name Manage Simulation Parameters
Brief Description User can input CSA Monthly Salary, CSO Monthly Salary, OT Rate per hour, Recall rate per hour for both off day and rest day, MAC Cost per hour for breakfast, lunch, dinner and supper, simulation period, MC rate, ad hoc leave rate, staff resign rate, new staff rate for simulation.
Flow of Events 1) User keys in CSA Monthly Salary, CSO Monthly Salary, OT Rate per hour, Recall rate per hour for both off day and rest day, MAC Cost (breakfast, lunch, dinner and supper).

2) User keys in simulation period.

3) User keys in mean and standard deviation for uncertainties such as MC rate (person/day), ad-hoc leave rate (person/day), staff resign rate (person/month), and new staff rate (person/month).

4) User selects “Start Simulation” button.

5) System will generate a normal distribution for each parameter.

6) System will generate a normal distribution for flight delays based on flight arrival schedule.csv and flight departure schedule.csv.

7) System will store the parameters and the generated distribution in the database.

Alternate Flows NA
Special Requirements User must key in a valid value for the simulation parameters.

Input for OT cost, Recall cost, MAC Cost and Simulation Period are mandatory. Input for MC rate, ad hoc leave rate, staff resign rate, new staff rate for simulation are not mandatory but both mean and standard deviation of each parameter are required once either one of the input fields is filled.

Preconditions UUser wants to input the simulation parameters into the database for simulation purpose.

User’s input for parameters are valid and correct.

Post Conditions Parameters will be stored into the database according to user’s inputs.

Simulation Parameters.csv, Flight Arrival Simulation Parameters.csv, Flight Departure Simulation Parameters.csv are created.

Simulate Staff Deployment

Name Simulate Staff Deployment
Brief Description Based on input flight schedule and flight requirements, system will allocate tasks to staff based on their qualifications and their corresponding roster.

Based on the given uncertainties, system will apply uncertainties onto a roster plan. Following that, the system mimics action done by Duty Manager such as allocating task to other staff who is available at a particular time.


Flow of Events 1) User selects “Start Simulation” after filling up data for Manage Simulation Parameters.

2) System will Start Scheduling Staff Roster (stage 1/2) to fulfill all the flight requirements

3) After scheduling staff roster is successful, system will continue to simulate staff deployment (stage 2/2).

4) After system finished the deployment, system will direct user to Simulation Result page.

Alternate Flows 1) Cancel Simulation at stage 1

i. User selects “Cancel”.

ii. System will stop scheduling staff roster immediately.

2) Cancel Simulation at stage 1

i. User selects “Cancel”.

ii. System will stop the simulation. Only staff roster schedule will be updated in database.

Special Requirements Bootstrap is successful.

Manage Simulation Parameters is done. Manage Airline Requirements is done if it is not bootstrapped.

Preconditions User wants to deploy staff based on input flight schedule, flight requirements, staff record and roster plan.

User wants to simulate the current roster plan based on the uncertainties generated. Bootstrap is completed and uncertainties are successfully generated.

Post Conditions Staff_Deployment_Roster table in the database is populated.

Simulation result of the planned roster will be generated and displayed on simulation result page.

Manage Result

Name Manage Result
Brief Description This use case allows user to manage the result from the previous simulations. This includes filter function, view and deletes results function. User can choose to export viewed result as PDF. The result includes Total Staff Working Hours, Staff Utilization Rate, Unproductive Hours, OT Hours, OT Cost, Recall Cost, Recall Hours and Meal Allowance Compensation (MAC).
Flow of Events 1) User select the ‘Manage Result’ option.

2) User can choose to filter the result specific to certain periods based on dates.

3) System will display the list of past simulation results within the periods specified.

4) User selects the result.

5) User views the result.

6) System displays the simulation result.

7) User selects the “Export PDF” option.

8) System organizes the result into report structure.

9) System exports the result as PDF report and prompts user to locate destination to save the PDF report.

10) User locates destination and saves the file.

Alternate Flows Delete the result(s).

i. User ticks on the specific results.

ii. User selects the “Delete” button.

Special Requirements Simulate Staff Deployment is successful.
Preconditions User has produced simulation result(s).

User wants to export simulation result as PDF file or view the simulation result. Simulate Staff Deployment is completed.

Post Conditions Result is displayed/ viewed, filtered or deleted.

The simulation result is exported into a PDF file.


Sequence Diagram

Sequence Diagram

Bootstrap Data

BootstrapDataSD.jpg

Manage Airline Requirements

ManageAirlineRequirementsSD.jpg

Manage Simulation Parameters

ManageSimulationParametersSD.jpg

Simulate Staff Deployment

SimulateStaffDeploymentSD.jpg

Manage Result

ManageResultSD.jpg