Difference between revisions of "IS480 Team wiki: 2012T1 Bumblebee Final Wiki"
(25 intermediate revisions by 2 users not shown) | |||
Line 24: | Line 24: | ||
{| class="wikitable" cellpadding="15" | {| class="wikitable" cellpadding="15" | ||
|- | |- | ||
− | | style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:left; border: 1px solid #ffffff" valign="top" | <b> | + | | style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:left; border: 1px solid #ffffff" valign="top" | <b>Slides</b> |
|- | |- | ||
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top" | | | style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top" | | ||
Line 69: | Line 69: | ||
|- | |- | ||
|} | |} | ||
− | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki: | + | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Final_Wiki#Top|Back to Top]]</u></font></div> |
Line 96: | Line 96: | ||
|- | |- | ||
|} | |} | ||
− | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki: | + | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Final_Wiki#Top|Back to Top]]</u></font></div> |
===<div style="color: #ffffff; font-size:0%">X Factor</div>=== | ===<div style="color: #ffffff; font-size:0%">X Factor</div>=== | ||
Line 120: | Line 120: | ||
=====''Probabilistic Simulation''===== | =====''Probabilistic Simulation''===== | ||
− | Our system gives our client a clear perspective of cost | + | Our system gives our client a clear perspective of cost profile from human resource planning uncertainties (flight delays, staff resign, etc) and we would also provide recommendation for minimizing additional cost effectively. Technically, we use normal distribution and Kolmogorov-Smirnov test to forecast the uncertainties which SATS could face. After which we run a simulation to plot our client’s cost profile and offer them a report for SATS management analysis purpose. |
==== Aviation Industry Knowledge ==== | ==== Aviation Industry Knowledge ==== | ||
Line 139: | Line 139: | ||
|- | |- | ||
|} | |} | ||
− | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki: | + | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Final_Wiki#Top|Back to Top]]</u></font></div> |
===<div style="color: #ffffff; font-size:0%">Motivation</div>=== | ===<div style="color: #ffffff; font-size:0%">Motivation</div>=== | ||
Line 162: | Line 162: | ||
|- | |- | ||
|} | |} | ||
− | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki: | + | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Final_Wiki#Top|Back to Top]]</u></font></div> |
==Project Scope== | ==Project Scope== | ||
Line 181: | Line 181: | ||
|- | |- | ||
|} | |} | ||
− | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki: | + | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Final_Wiki#Top|Back to Top]]</u></font></div> |
Line 237: | Line 237: | ||
|- | |- | ||
|} | |} | ||
− | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki: | + | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Final_Wiki#Top|Back to Top]]</u></font></div> |
===<div style="color: #ffffff; font-size:0%">Graphical User Interface</div>=== | ===<div style="color: #ffffff; font-size:0%">Graphical User Interface</div>=== | ||
Line 247: | Line 247: | ||
|- | |- | ||
| style= "background:#FBB917; 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:1HomePage.png|center|500px]] | + | |
+ | [[Image:1HomePage.png|center|500px]] | ||
[[Image:2ImportData.png|center|500px]] | [[Image:2ImportData.png|center|500px]] | ||
− | [[Image: | + | [[Image:2aImportDataProcessing.png|center|500px]] |
− | [[Image:4ManageAirlineReqCounterDept.png|center|500px]] | + | [[Image:2bImportDataCompleted.png|center|500px]] |
+ | [[Image:4ManageAirlineReqCounterDept.png|center|500px]] | ||
+ | [[Image:5ManageAirlineReqGateDept.png|center|500px]] | ||
[[Image:5aManageSimulationParameter.png|center|500px]] | [[Image:5aManageSimulationParameter.png|center|500px]] | ||
[[Image:5bManageSimulationParamCost.png|center|500px]] | [[Image:5bManageSimulationParamCost.png|center|500px]] | ||
− | [[Image: | + | [[Image:5aSimulating.png|center|500px]] |
− | [[Image:6SimulationResult.png|center|500px]] | + | [[Image:6SimulationResult.png|center|500px]] |
− | |||
− | |||
[[Image:7GeneratePDF.png|center|500px]] | [[Image:7GeneratePDF.png|center|500px]] | ||
[[Image:8PDFreport.png|center|500px]] | [[Image:8PDFreport.png|center|500px]] | ||
[[Image:9ManageResult.png|center|500px]] | [[Image:9ManageResult.png|center|500px]] | ||
[[Image:10ManageResultChooseDate.png|center|500px]] | [[Image:10ManageResultChooseDate.png|center|500px]] | ||
+ | [[Image:DeleteReport.png|center|500px]] | ||
+ | [[Image:ViewStaffSch6aa.png|center|500px]] | ||
+ | [[Image:ViewStaffSch6a.png|center|500px]] | ||
+ | [[Image:ViewChangiMap.png|center|500px]] | ||
+ | [[Image:ViewStaffLocTask.png|center|500px]] | ||
+ | [[Image:csv.png|center|500px]] | ||
+ | [[Image:csvZoomOut.png|center|600px]] | ||
+ | [[Image:1HomePage.png|center|500px]] | ||
+ | <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_Final_Wiki#Top|Back to Top]]</u></font></div> | ||
+ | |||
+ | ==User Testing and Heuristic Evaluation== | ||
+ | ====<div style="color: #ffffff; font-size:0%">User Testing 2</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>User Testing 2</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" | | ||
+ | '''The goals and objectives of usability testing:''' | ||
+ | |||
+ | • Record and document general feedback and first impressions | ||
+ | |||
+ | • Identify any potential concerns to address regarding application usability, presentation, and navigation | ||
+ | |||
+ | • Get feedback on the usefulness and accuracy of the functions developed | ||
+ | |||
+ | • To match client expectations on the system developed | ||
+ | |||
+ | |||
+ | '''User Testing Conclusion:''' | ||
+ | |||
+ | • Client was satisfied with the system | ||
+ | |||
+ | • Current result seems close and better than the actual result under manual scheduling. However, close monitor of result with client is highly needed to ensure that the result is indeed valid | ||
+ | |||
+ | • Team will consistently send the latest file to client for independent testing | ||
+ | |||
+ | |||
+ | Click [[Media:BumblebeeUserTesting2Report.pdf|here]] to download our report | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | | 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_Final_Wiki#Top|Back to Top]]</u></font></div> | ||
+ | |||
+ | ===<div style="color: #ffffff; font-size:0%">Heuristic Evaluation</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>Heuristic Evaluation</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" | | ||
+ | |||
+ | '''The goals and objectives of usability testing:''' | ||
+ | |||
+ | • Record and document general feedback and first impressions | ||
+ | |||
+ | • Identify any potential concerns to address regarding application usability, presentation, and navigation | ||
+ | |||
+ | |||
+ | '''Heuristic Evaluation Conclusion:''' | ||
+ | |||
+ | • Users have no problem in navigating around the system in general | ||
+ | |||
+ | • There is a need for more instructions from pages to pages | ||
+ | |||
− | + | Click [[Media:BumblebeeHeuristicEvaluationReport.pdf|here]] to download our report | |
|- | |- | ||
+ | |||
|- | |- | ||
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top" | | | style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top" | | ||
|- | |- | ||
|} | |} | ||
− | |||
− | == | + | |
− | ===<div style="color: #ffffff; font-size:0%"> | + | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Final_Wiki#Top|Back to Top]]</u></font></div> |
+ | |||
+ | ===<div style="color: #ffffff; font-size:0%">User Testing 3</div>=== | ||
{| class="wikitable" cellpadding="15" | {| 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> | + | | 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>User Testing 3</b> |
|- | |- | ||
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top" | | | style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top" | | ||
Line 280: | Line 359: | ||
| style= "background:#FBB917; 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" | | ||
− | The goals and objectives of usability testing | + | '''The goals and objectives of usability testing:''' |
• Record and document general feedback and first impressions | • Record and document general feedback and first impressions | ||
Line 289: | Line 368: | ||
• To match client expectations on the system developed | • To match client expectations on the system developed | ||
+ | |||
+ | |||
+ | '''User Testing Conclusion:''' | ||
+ | |||
+ | • Client was satisfied with the system. | ||
+ | |||
+ | • Results are reasonable | ||
+ | |||
+ | • A video as user manual will be done to aid user in using the software | ||
+ | |||
+ | |||
Click [[Media:BumblebeeUserTesting2Report.pdf|here]] to download our report | Click [[Media:BumblebeeUserTesting2Report.pdf|here]] to download our report | ||
Line 300: | Line 390: | ||
|} | |} | ||
− | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki: | + | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Final_Wiki#Top|Back to Top]]</u></font></div> |
==Project Management== | ==Project Management== | ||
+ | |||
===<div style="color: #ffffff; font-size:0%">Time Management</div>=== | ===<div style="color: #ffffff; font-size:0%">Time Management</div>=== | ||
{| class="wikitable" cellpadding="15" | {| class="wikitable" cellpadding="15" | ||
Line 314: | Line 405: | ||
====Milestones==== | ====Milestones==== | ||
− | [[Image:BumblebeeMilestone. | + | [[Image:BumblebeeMilestone.jpg|1000px|center]] |
====Iterations Parallel Plan==== | ====Iterations Parallel Plan==== | ||
Line 334: | Line 425: | ||
|- | |- | ||
|} | |} | ||
− | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki: | + | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Final_Wiki#Top|Back to Top]]</u></font></div> |
+ | |||
===<div style="color: #ffffff; font-size:0%">Quality Management</div>=== | ===<div style="color: #ffffff; font-size:0%">Quality Management</div>=== | ||
{| class="wikitable" cellpadding="15" | {| class="wikitable" cellpadding="15" | ||
Line 358: | Line 450: | ||
|- | |- | ||
|} | |} | ||
− | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki: | + | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Final_Wiki#Top|Back to Top]]</u></font></div> |
===<div style="color: #ffffff; font-size:0%">Risk Management</div>=== | ===<div style="color: #ffffff; font-size:0%">Risk Management</div>=== | ||
{| class="wikitable" cellpadding="15" | {| class="wikitable" cellpadding="15" | ||
Line 454: | Line 546: | ||
|- | |- | ||
|} | |} | ||
− | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki: | + | <div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Final_Wiki#Top|Back to Top]]</u></font></div> |
+ | |||
+ | ==Learning Outcome and Reflection== | ||
+ | ===<div style="color: #ffffff; font-size:0%">Learning Outcome</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>Learning Outcome</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" | | ||
+ | <table border="1" cellpadding="1" cellspacing="1"> | ||
+ | |||
+ | <tr bgcolor="white"> | ||
+ | <th> <font color="black">S/N</font></th> | ||
+ | <th> <font color="black">Description</font> </th> | ||
+ | <th><font color="black">Actions to Realize Learning Outcome(s)</font></th> | ||
+ | </tr> | ||
+ | |||
+ | <tr bgcolor="FBB917"> | ||
+ | <td><b>1</b></td> | ||
+ | <td colspan="3" center><b>Integration of business & technology in a sector context</b></td> | ||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>1.1 Business IT value linkage skills</td> | ||
+ | <td> | ||
+ | *Deep understanding with aviation industry | ||
+ | *Analyse what is SATS doing and what are the current problems that SATS is facing. After understanding SATS' deployment processes, help SATS solve their problem by developing SATS Staff Deployment Software | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>1.2 Cost & benefits analysis skills</td> | ||
+ | <td> | ||
+ | *Conduct cost and benefit analysis by comparing SATS current staffing cost and cost saving that brought about by SATS Staff Deployment Software in terms of time and monetary | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>1.3 Business software solution impact analysis skills</td> | ||
+ | <td> | ||
+ | *Conduct cost and benefit analysis by comparing SATS current staffing cost and cost saving that brought about by SATS Staff Deployment Software in terms of time and monetary | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr bgcolor="FBB917"> | ||
+ | <td><b>2</b></td> | ||
+ | <td colspan="3" center><b>IT architecture, design and development skills</b></td> | ||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>2.1 System requirements specification skills</td> | ||
+ | <td> | ||
+ | *Gather and propose functional and non-functional requirements of Staff Deployment Simulation Software | ||
+ | *Analyze business requirements and propose user interface, infrastructure and applications needed to complete project. | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>2.2 Software and IT architecture analysis and Design skills</td> | ||
+ | <td> | ||
+ | *Design the solution architecture based analysis from gathered requirements. | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>2.3 Implementation skills</td> | ||
+ | <td> | ||
+ | *Implement system, develop and integrate all customized modules and third party functionalities. | ||
+ | *Deploy prototype in every iteration and resolve bug from tests within proposed schedule. | ||
+ | *Conduct User Acceptance Test (UAT) at every milestone for the developed product. | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>2.4 Computational thinking skills</td> | ||
+ | <td> | ||
+ | *Use Greedy Algorithm and Monte Carlo simulation in developing Staff Deployment Simulation Software\ | ||
+ | *Apply algorithm efficiency so that software could run in reasonable amount of time | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>2.5 Technology Application skills</td> | ||
+ | <td> | ||
+ | *Use data visualisation to make the result of our software reader-friendly | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr bgcolor="FBB917"> | ||
+ | <td><b>3</b></td> | ||
+ | <td colspan="3" center><b>Project management skills</b></td> | ||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>3.1 Scope management skills</td> | ||
+ | <td> | ||
+ | *Detail discussion with sponsor with regards to scope of the project | ||
+ | *Discussion with supervisor with regards to scope of the project | ||
+ | *Conducted sign-off with sponsor with regards to scope of the project | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>3.2 Risks management skills</td> | ||
+ | <td> | ||
+ | *Discussed risks with the team with regards to possible risks using risk metric. | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>3.3 Project integration and time management skills</td> | ||
+ | <td> | ||
+ | *Prepared a detailed schedule for the entire project span | ||
+ | *Use schedule metric to make sure the team is on time with schedule and able to deliver the software | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>3.4 Quality management skills</td> | ||
+ | <td> | ||
+ | *Deploy prototype in every iteration and resolve bug from tests within proposed schedule. | ||
+ | *Conduct 3 User Testing (UT) and Heuristic Evaluation for the developed product. | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr bgcolor="FBB917"> | ||
+ | <td><b>4</b></td> | ||
+ | <td colspan="3" center><b>Learning to learn skills</b></td> | ||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>4.1 Search skills</td> | ||
+ | <td> | ||
+ | *Learn how to find solution using the internet - blogs, forums and and articles | ||
+ | </td> | ||
+ | <tr/> | ||
+ | |||
+ | <tr bgcolor="FBB917"> | ||
+ | <td><b>5</b></td> | ||
+ | <td colspan="3" center><b>Communication Skills</b></td> | ||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <td></td> | ||
+ | <td>5.1 Presentation skills</td> | ||
+ | <td> | ||
+ | *Organise requirements and deliverables and present it to supervisor and reviewers | ||
+ | </td> | ||
+ | <tr/> | ||
+ | </table> | ||
+ | <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_Learning#Top|Back to Top]]</u></font></div> | ||
+ | |||
+ | |||
+ | ===<div style="color: #ffffff; font-size:0%">Reflection</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>Reflection</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_Learning.png|600px |center]] | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | | 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_Learning#Top|Back to Top]]</u></font></div> |
Latest revision as of 12:11, 4 December 2012
Back to Main Page | Project Overview | Project Scope | User Testing 2 | Heuristic Evaluation |
Contents
Final Presentation Slides
Slides
Slides |
Click here to download our final presentation slides.
|
Project Overview
Stakeholders
Stakeholders |
The BeesSponsors
|
Project Description
Project Description |
Singapore Airport Terminal Services (SATS) is the leading provider of the gateway services and food solutions in the region. It has a staff of 800 to handle more than 35 airlines. Every year, there are two major airline flight schedule change - summer (April) and winter (November). Each change can be a drastic one and has great impact on staff roster. One of SATS’s goals for its staff roster is to meet all its airlines’ requirements. However, there are many uncertainties such as staff members falling sick, staff resigning and flight delay, that cause the roster planned to be ineffective. Thus, Duty Manager in SATS often has to make last minute changes to the rosters and incur costs such as Staff Recall Cost, Over-Time cost and Meal Allowance Compensation (MAC). To help improve the efficiency involving various costs and consequences of the planned staff roster, our project aims to create a Staff Deployment Simulation Software (SDSS) which will first deploy staff based on flight schedule, flight requirements, staff records and staff roster and then simulate the roster plan by taking into account all the various uncertainties and forecast the various costs that the management would have to incur. Understanding the cost and consequences of a given roster, SATS would then be able to make necessary adjustments to avoid high expenses to the company. The diagram below explains the flow of the software. To predict the uncertainties, we will take in the mean and standard deviation of the listed simulation parameters in diagram above(MC Rate, Flight Delay Rate, Staff Resign Rate, etc). Having those values, our software will then generate a normal distribution of each uncertainty. After such, we will be applying the uncertainties at the planned roster plan such as removing staff from the roster plan if he/she is taking MC. The software will also try to mimic the actions of Duty Manager who does the necessary adjustment to the staff roster to fulfill the airlines requirements i.e. to imitate human decision making process to come out with an optimal staff roster. At the end of the day, our software will generate a management report which will reveal the cost and consequences of implementation of a given roster. The output given will be Total Staff Working Hours, Flight Demand Coverage, Meal Allowance Compensation (MAC), Over Time (OT) Cost, OT hours, Staff Utilization Rate, Unproductive Hours, Recall Cost and Recall Hours. Understanding the cost and consequences of a given roster, SATS would then be able to make necessary adjustment to avoid high expenses and thus, increase cost savings to the company. |
X Factor
X Factor |
EfficiencyOur system is able to handle a highly complex, huge domain size, scheduling problem efficiently in comparison to SATS’ current manual scheduling process. Algorithmic ComplexityOptimal SchedulingWe provide our client an optimized staff schedule to effectively reduce client's overheads from non-optimal scheduling practices. In essence, we developed an optimal scheduling algorithm to maximise SATS’ resources to meet all airline requirements. This optimal scheduling is written based on Greedy Algorithm concepts. Probabilistic SimulationOur system gives our client a clear perspective of cost profile from human resource planning uncertainties (flight delays, staff resign, etc) and we would also provide recommendation for minimizing additional cost effectively. Technically, we use normal distribution and Kolmogorov-Smirnov test to forecast the uncertainties which SATS could face. After which we run a simulation to plot our client’s cost profile and offer them a report for SATS management analysis purpose. Aviation Industry KnowledgeOur system complies with numerous aviation specific business rules. To develop this system, our group has to understand aviation industry practises deeply. For this, We did a 2 months weekly attachment to SATS' Duty Manager(DM) and Customer Service Officer(CSO).
|
Motivation
Motivation |
There are 2 main motivations for working on this project:
|
Project Scope
Use Case
Use Case |
|
Deliverables and Scope
Deliverables and Scope | ||||||||||||||||||||||||||||
Please refer to use case description for greater details. | ||||||||||||||||||||||||||||
Graphical User Interface
Graphical User Interface |
|
User Testing and Heuristic Evaluation
User Testing 2
User Testing 2 |
The goals and objectives of usability testing: • Record and document general feedback and first impressions • Identify any potential concerns to address regarding application usability, presentation, and navigation • Get feedback on the usefulness and accuracy of the functions developed • To match client expectations on the system developed
• Client was satisfied with the system • Current result seems close and better than the actual result under manual scheduling. However, close monitor of result with client is highly needed to ensure that the result is indeed valid • Team will consistently send the latest file to client for independent testing
|
Heuristic Evaluation
Heuristic Evaluation |
The goals and objectives of usability testing: • Record and document general feedback and first impressions • Identify any potential concerns to address regarding application usability, presentation, and navigation
• Users have no problem in navigating around the system in general • There is a need for more instructions from pages to pages
|
User Testing 3
User Testing 3 |
The goals and objectives of usability testing: • Record and document general feedback and first impressions • Identify any potential concerns to address regarding application usability, presentation, and navigation • Get feedback on the usefulness and accuracy of the functions developed • To match client expectations on the system developed
• Client was satisfied with the system. • Results are reasonable • A video as user manual will be done to aid user in using the software
Click here to download our report
|
Project Management
Time Management
Time Management |
MilestonesIterations Parallel PlanSchedule Metric
Schedule TrackingClick here to see our Schedule Tracking. |
Quality Management
Quality Management |
Bug Metric
Bug TrackingClick here to see our Bug Log. |
Risk Management
Risk Management | ||||||||||||||||||||||||||||||||||||||||||||||||
Risk Metric
Risk Table
| ||||||||||||||||||||||||||||||||||||||||||||||||
Learning Outcome and Reflection
Learning Outcome
Learning Outcome | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Reflection
Reflection |