HeaderSIS.jpg

Difference between revisions of "Mid-term wiki"

From IS480
Jump to navigation Jump to search
Line 58: Line 58:
  
 
=== <span style="color:#000066;">Risk Assessment & Mitigation</span> ===
 
=== <span style="color:#000066;">Risk Assessment & Mitigation</span> ===
 +
 +
 +
 +
<h4>PAST RISK and how it was managed</h4>
 +
 +
The team faced several challenges over the course from acceptance to Midterms and was put to the test to manage both identified and unidentified risks.
 +
 +
Identified risk 1: Unable to acquire data for predictive modelling<br>
 +
As expected due to strict PDPA controls over sensitive data,our client was not able to provide us with the huge chunks of data for analysis purposes.Because we already forecast this possibility,it enabled us to quickly drop the predictive model and move onto prescriptive models which we had brainstormed to cover our scope in the event of no data.
 +
 +
 +
Identified risk 2: First hand experience on building simulator<br>
 +
The team faced problems debugging errors the simulator was producing.Uncle google was not able to provide us with much help ,hence the team relatively took more than planned time to.
 +
 +
 +
Identified risk 3: No prior knowledge on MongoDB<br>
 +
We allocated a team member to research on MondoDB before implementation period.While implementating this team member was able to share his expertise and mentored fellow team members.Despite this effort,this new unexplored database took us more than the planned time causing the iteration to delay.
 +
 +
 +
Identified risk 4:New semantic UI<br>
 +
Initially the team was skeptical with Semantic  due to its low maturity,but the library was powerful enough to support us with the functions we needed.
 +
 +
 +
Unidentified risk 5:Tasks were not assigned based on competency and availability<br>
 +
Even though the team memebers were taking 4 modules in average,some members had other commitments such as Inter-University sports competition.This ate into their time and as a result hindered them from completing thier tasks on time.Also,team members were not able to cope with the complexity involved in their assigned task.To tackle this,a informal dialogue chat is held at the start of every meeting to update PM on their personnal schedule and preference.This helps the PM to allocate task more appropriately.
  
 
== <span style="color:#000066;">User Test</span> ==
 
== <span style="color:#000066;">User Test</span> ==

Revision as of 21:44, 4 October 2014

Code Blue 1.jpg
Home The Team Project Overview Project Management Project Documentation Project Resources

Project Progress Summary

Download our mid-term presentation slides: midterm slides
Link to deployed site: dynamicqueuemanagement-smusis.rhcloud.com/

To login to the site, please use the following credential:
Username: guest
Password: guest$1

Project Highlights

  1. Project scope is extended with new functionalities.
    1. Login function was implemented - the reason for implementing the login feature was to allow each user to have their own copy of simulation settings. Previously, without this feature, users who uses the system will end up overriding each others settings.
    2. User management - Management of the user includes creating a new user, deleting a user and editing a user. This feature was added because we wish to empower our user to have control.
    3. Seeds configuration - Seeds played a big part in any simulation software as it affects the reproducibility and fairness of simulation results. With the seeds currently being hardcoded, providing this feature allows extra flexibility for our users who have the use case for changing seeds.
  2. Significant time spent in database changeover and in exploring visualisation libraries
    1. Database was changed from MySQL to MongoDB - the reason for this changeover was we realised the bulk of the data we are storing are non-relational in nature, and therefore, it does make more sense in using a document-oriented database over a relational database. In addition, as the amount of data that will be stored are large, there is also the significance performance saving in terms of each write and read operations.
    2. Due to the steep learning of D3 data visualization library, team explores other alternatives such as Highchart, Chart.js, nvd3, Google Chart before finally settling on C3.js for data visualization.
  3. Overhaul of Simulation interface
    1. Based on the user testing prior to acceptance, common feedbacks was the main interface showing the simulation animation was unable to display all information in a screen (without scrolling), therefore, effort was put in to re-structure the layout of the elements.
  4. Implementation of speed toggling for simulation with animation.
  5. Behind schedule for reporting module
    1. only 2 out of the 4 charts was implemented. The other 2 charts was pushed back.

Project Management

Schedule

Metrics

Change Management

After User test,new functionalites and ideas were suggested to us by both student testers,professors and healthcare practitioners.The team used its change management process to validate each function and ranked them.We met our client (kar way) to validate our priority against hers and decided to include the following functions into our project scope.


Change UT2.jpg

We had difficulties evaluating the two pending functions and consulted our supervisor for advice.He acknowledged the complexity involved and advised us to make a decision after getting a good understanding and more details of them.We will spend some time discussing the feasibility with relevant stakeholders after midterms and make a decision.As of the now,the pending functions are not included in our project plan.

Risk Assessment & Mitigation

PAST RISK and how it was managed

The team faced several challenges over the course from acceptance to Midterms and was put to the test to manage both identified and unidentified risks.

Identified risk 1: Unable to acquire data for predictive modelling
As expected due to strict PDPA controls over sensitive data,our client was not able to provide us with the huge chunks of data for analysis purposes.Because we already forecast this possibility,it enabled us to quickly drop the predictive model and move onto prescriptive models which we had brainstormed to cover our scope in the event of no data.


Identified risk 2: First hand experience on building simulator
The team faced problems debugging errors the simulator was producing.Uncle google was not able to provide us with much help ,hence the team relatively took more than planned time to.


Identified risk 3: No prior knowledge on MongoDB
We allocated a team member to research on MondoDB before implementation period.While implementating this team member was able to share his expertise and mentored fellow team members.Despite this effort,this new unexplored database took us more than the planned time causing the iteration to delay.


Identified risk 4:New semantic UI
Initially the team was skeptical with Semantic due to its low maturity,but the library was powerful enough to support us with the functions we needed.


Unidentified risk 5:Tasks were not assigned based on competency and availability
Even though the team memebers were taking 4 modules in average,some members had other commitments such as Inter-University sports competition.This ate into their time and as a result hindered them from completing thier tasks on time.Also,team members were not able to cope with the complexity involved in their assigned task.To tackle this,a informal dialogue chat is held at the start of every meeting to update PM on their personnal schedule and preference.This helps the PM to allocate task more appropriately.

User Test

Technical Complexities

Synchronization between simulation and animation clock

Learning Outcome

Chun Yang -
Faris -
Nigel -
Clarice -
Syafi -
Basith -