Difference between revisions of "Final wiki"
Abdulbm.2011 (talk | contribs) (Created page with "400px|center <!---------------START of header ----------------------> {| style="border-collapse: separate; border-spacing: 0; border-width: 3px; bor...") |
Abdulbm.2011 (talk | contribs) |
||
Line 49: | Line 49: | ||
=== <span style="color:#000066; font-size:25px">Schedule</span> === | === <span style="color:#000066; font-size:25px">Schedule</span> === | ||
<p> '''Planned Vs. Actual project plan.''' </p> | <p> '''Planned Vs. Actual project plan.''' </p> | ||
− | + | ||
− | |||
<p> '''Project Iteration Overview.''' </p> | <p> '''Project Iteration Overview.''' </p> | ||
− | + | ||
<p> Below is a screenshot of the detailed project schedule (our current iteration in progress). Click on the link to view our full | <p> Below is a screenshot of the detailed project schedule (our current iteration in progress). Click on the link to view our full | ||
[https://docs.google.com/a/smu.edu.sg/spreadsheet/pub?key=0AisITGQ7LXVIdFlQNlhMLWlkV2tKWThwUVE4SEZpZnc&single=true&gid=2&output=html project schedule] . </p> | [https://docs.google.com/a/smu.edu.sg/spreadsheet/pub?key=0AisITGQ7LXVIdFlQNlhMLWlkV2tKWThwUVE4SEZpZnc&single=true&gid=2&output=html project schedule] . </p> | ||
− | + | ||
=== <span style="color:#000066;"> <big>Metrics</big></span> === | === <span style="color:#000066;"> <big>Metrics</big></span> === | ||
<br/> | <br/> | ||
− | + | ||
<br/> | <br/> | ||
<br/> | <br/> | ||
− | + | ||
<br/> | <br/> | ||
<br/> | <br/> | ||
− | + | ||
<br/> | <br/> | ||
<br/> | <br/> | ||
− | + | ||
<br/> | <br/> | ||
<br/> | <br/> | ||
− | + | ||
<br/> | <br/> | ||
<br/> | <br/> | ||
− | + | ||
<br/> | <br/> | ||
<p>RACI metric - we use this metric so that every member in the team is in-charge-of at least one major module or task throughout the entire project. This helped to organise the way we keep one another updated with our progress and be more efficient during meetings. How it helps us to be more efficient is when, we can work simultaneously in smaller groups on tasks categorised by the modules in the table. </p> | <p>RACI metric - we use this metric so that every member in the team is in-charge-of at least one major module or task throughout the entire project. This helped to organise the way we keep one another updated with our progress and be more efficient during meetings. How it helps us to be more efficient is when, we can work simultaneously in smaller groups on tasks categorised by the modules in the table. </p> | ||
Line 82: | Line 81: | ||
=== <span style="color:#000066;">Change Management</span> === | === <span style="color:#000066;">Change Management</span> === | ||
− | |||
− | |||
− | |||
− | |||
− | |||
=== <span style="color:#000066;">Risk Assessment & Mitigation</span> === | === <span style="color:#000066;">Risk Assessment & Mitigation</span> === | ||
Line 92: | Line 86: | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==<div style="background: #000066; padding: 12px; font-weight: bold; font-size: 100%; line-height: 0.5em;"><font face="Arial" color="white">User Test</font></div>== | ==<div style="background: #000066; padding: 12px; font-weight: bold; font-size: 100%; line-height: 0.5em;"><font face="Arial" color="white">User Test</font></div>== | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==<div style="background: #000066; padding: 12px; font-weight: bold; font-size: 100%; line-height: 0.5em;"><font face="Arial" color="white">Technical Complexities</font></div>== | ==<div style="background: #000066; padding: 12px; font-weight: bold; font-size: 100%; line-height: 0.5em;"><font face="Arial" color="white">Technical Complexities</font></div>== | ||
Line 268: | Line 139: | ||
==<div style="background: #000066; padding: 12px; font-weight: bold; font-size: 100%; line-height: 0.5em;"><font face="Arial" color="white">Learning Outcome</font></div>== | ==<div style="background: #000066; padding: 12px; font-weight: bold; font-size: 100%; line-height: 0.5em;"><font face="Arial" color="white">Learning Outcome</font></div>== | ||
− | <b>Chun Yang</b> - | + | <b>Chun Yang</b> - This project provided me the platform to further develop as a developer as I had the opportunities to try out various new technologies to build onto the development capabilities that I am already possessed with. The "simulation' nature of this project was different from what we were taught and that gave me a tough yet good experience <br/> |
− | <br/><b>Faris</b> - | + | <br/><b>Faris</b> - |
<br/> | <br/> | ||
− | <br/><b>Nigel</b> - | + | <br/><b>Nigel</b> - <br/> |
− | <br/><b>Clarice</b> - | + | <br/><b>Clarice</b> - <br/> |
− | <br/><b>Syafi</b> - | + | <br/><b>Syafi</b> - |
<br/> | <br/> | ||
− | <br/><b>Basith</b> - | + | <br/><b>Basith</b>-Project management is not just about having a good plan, proper metrics and deadlines.Apart from keeping your supervisor and client happy,one has to make sure the team is happy ,driven and motivated as well. Practice flexibility,give them the space and breaks and most importantly read between the lines.After all,like machines humans can break down too!! <br/> |
==<div style="background: #000066; padding: 12px; font-weight: bold; font-size: 100%; line-height: 0.5em;"><font face="Arial" color="white">X-FACTOR</font></div>== | ==<div style="background: #000066; padding: 12px; font-weight: bold; font-size: 100%; line-height: 0.5em;"><font face="Arial" color="white">X-FACTOR</font></div>== | ||
− |
Revision as of 02:43, 20 November 2014
Home | The Team | Project Overview | Project Management | Project Documentation | Project Resources |
---|
Contents
Project Progress Summary
Download our mid-term presentation slides: midterm slides
Step 1: Go to deployed site: dynamicqueuemanagement-smusis.rhcloud.com/
Step 2: Login to the site with your given credential.
Project Highlights
- Following are the summary of the new scope added during the course of project.
- Login function was implemented - the reason for implementing the login feature is to allow each user to have control over their setting and data. Previously, without this feature, users of them system ended up overriding previous settings.
- User management(admin) - Management of the user includes the basic CRUD features(Create,read,update and delete). This feature is to allow our client to give access to users whom are interesting in the product.
- Treatment Configuration(admin) - This is allow the admin to key in the tests that will be populated in user's dropdown as well as to select the tests that he/she wants to appear as default in user's profile.This is to ensure users do not re-enter tests name and legitimate tests.
- Datatable view of text file -
- Seeds configuration checkbox - Seeds played a big part in simulation as it affects the reproducibility and fairness of simulation results. With the seeds currently being hardcoded, this new feature gives users to fix/unfix random seeds.
- Significant time spent in database changeover and in exploring visualisation libraries
- 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.
- 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.
- Overhaul of Simulation interface
- 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.
- Implementation of speed toggling for simulation with animation.
- Behind schedule for reporting module
- only 2 out of the 4 charts was implemented. The other 2 charts was pushed back.
Project Management
Schedule
Planned Vs. Actual project plan.
Project Iteration Overview.
Below is a screenshot of the detailed project schedule (our current iteration in progress). Click on the link to view our full project schedule .
Metrics
RACI metric - we use this metric so that every member in the team is in-charge-of at least one major module or task throughout the entire project. This helped to organise the way we keep one another updated with our progress and be more efficient during meetings. How it helps us to be more efficient is when, we can work simultaneously in smaller groups on tasks categorised by the modules in the table.
Refer to the first responsibility in the table:
For example, Basith as the Project Manager is responsible for organising meetings with supervisor, sponsor and industry users for application testing. Clarice will assist him in checking the internal deadlines for the project. And he will have to consult Chun Yang, our lead developer, if our development progress is good before we present our work to the stakeholders. Syafi, who is the business analyst needs to make make sure our application on production side is running well (90% bugs free). Not forgetting to always involve everyone in the team, Nigel and Faris will be kept in the loop, while they can still focus on their coding tasks.
Change Management
Risk Assessment & Mitigation
User Test
Technical Complexities
Java to JavaScript
One of the requirements for this project is to have a real-time animation visualization of the simulation run, similar to what most commercial simulation software is capable of providing. As the team has decided our project output is going to be a web-based simulator, we decided to leverage the capabilities of SVG for the development of the real-time animation visualization.
Therefore, it is impractical for the team to continue with the inherited simulation model written in Java, as rendering of the animation visualization would require constant communication with the server. With that, the team decided to re-write the entire simulation model using JavaScript, which would run on the client’s browser.
This further adds on to the challenges that the team has as not only do we have to understand how does the simulation model was programmed with the current codebase architecture currently, we need to implement it using Javascript. It was a difficult task as most of us are not well-versed with the scripting languages, and our only experience with it was utilizing it for client-side validation. In order to develop a simulation model with it, the team needs to understand how prototypal pattern works, how can we emulate “class” like what we have in Java, even though it is a classless language.
In addition, similar to writing codes in Java, there is also the issue of how do we structure our javascript code to have it maintainable. As all javascript code is included on the same page, we also have to be careful of not polluting the global namespace, which may cause naming conflict and cause code to break. The usage of module pattern (component-based development) is also a first-hand experience for many of us.
Lastly, as JavaScript is slow in nature, we also need to explore ways where we could optimize our javascript code to have it performance-friendly. In doing so also requires the team to have an understanding of how javascript variable scoping and lookup works.
Synchronize patient’s current X and Y position between events’ tween
Animation of the patient follows the following steps:
When an event is triggered, get the tween to move the patient to a particular destination. For e.g. A StartConsult event will animate the patient to a particular doctor’s room.
- a.Get the patient current X and Y position.
- b.Calculate the dX and dY using destination’s coordinates and patient’s current X, Y.
- c.Construct the tween using the dX and dY calculated.
- d.Add the tween into the patient timeline for execution.
The issues arose when intervals between 2 events are too close; the reason for it is because the simulation clock is always running faster than the animation clock
Simulation Time | Event Triggered | Function Call | what does it does? |
20 | StartConsult | Get tween method is called | Animation clock start, takes 3 seconds to complete. Gradually change patient X and Y to destination coordinates. |
30 | EndConsult | Get tween method is called | Get wrong current X and Y coordinates as previous tween is still altering the coordinates. |
The solution here is to construct a tween object with no dX and dY value, and making use of an undocumented attributes and callback in the GreenSock library, we calculate and update the current X and Y before the tween is executed.
Learning Outcome
Chun Yang - This project provided me the platform to further develop as a developer as I had the opportunities to try out various new technologies to build onto the development capabilities that I am already possessed with. The "simulation' nature of this project was different from what we were taught and that gave me a tough yet good experience
Faris -
Nigel -
Clarice -
Syafi -
Basith-Project management is not just about having a good plan, proper metrics and deadlines.Apart from keeping your supervisor and client happy,one has to make sure the team is happy ,driven and motivated as well. Practice flexibility,give them the space and breaks and most importantly read between the lines.After all,like machines humans can break down too!!