HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki:2015T2 Team Elements FinalWiki"

From IS480
Jump to navigation Jump to search
 
(26 intermediate revisions by the same user not shown)
Line 6: Line 6:
 
{|style="background-color:#5C005C; color:#DF8DDF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0"  |
 
{|style="background-color:#5C005C; color:#DF8DDF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0"  |
 
| style="padding:0.3em; font-size:100%; background-color:#DF8DDF;  border-bottom:0px solid #DF8DDF; text-align:center; color:#DF8DDF" width="10%" |  
 
| style="padding:0.3em; font-size:100%; background-color:#DF8DDF;  border-bottom:0px solid #DF8DDF; text-align:center; color:#DF8DDF" width="10%" |  
[[Image:Team_Elements_Home.png|30px|link=IS480 Team wiki: 2016T2 Team Elements]]  
+
[[Image:Team_Elements_Home.png|30px|link=IS480 Team wiki: 2016T2 Elements]]  
[[IS480 Team wiki: 2015T2 Team Elements |<font color="#F5F5F5" size=2><b>HOME</b></font>]]
+
[[IS480 Team wiki: 2016T2 Elements |<font color="#F5F5F5" size=2><b>HOME</b></font>]]
  
 
| style="border-bottom:0px solid #5C005C; background:none;" width="1%" | &nbsp;  
 
| style="border-bottom:0px solid #5C005C; background:none;" width="1%" | &nbsp;  
Line 49: Line 49:
 
<br/>
 
<br/>
  
==<div style="background: #354458; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; text-transform:lowercase;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Project Progress Summary</font></div>==
+
==<div style="background: #808080; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; text-transform:lowercase;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Project Progress Summary</font></div>==
  
[[Image:TE_Slides_Icon.jpg|130px|link=]][[Media: WPFinalPresentation v1.0.pdf|Finals Slides]]
+
[[Image:TE_Slides_Icon.jpg|130px|link=]][[Media: Team Elements Final Presentation.pptx|Finals Slides]]
 
[[Image:Elements Deployed Icon.jpg|130px|link=http://sterlingtraininghub.com]][http://sterlingtraininghub.com Deployed Site]
 
[[Image:Elements Deployed Icon.jpg|130px|link=http://sterlingtraininghub.com]][http://sterlingtraininghub.com Deployed Site]
 
[[Image:WP Postericon.JPG|130px|link=]][[Media: ElementsPosterWeb.pdf|Poster]]
 
[[Image:WP Postericon.JPG|130px|link=]][[Media: ElementsPosterWeb.pdf|Poster]]
[[Image:WP Video.png|120px|link=https://www.youtube.com/watch?v=5-sftCP_zxo]][https://www.youtube.com/watch?v=5-sftCP_zxo Pitch Video]
+
[[Image:WP Video.png|120px|link=https://youtu.be/MByzrP9bonU]][https://youtu.be/MByzrP9bonU Pitch Video]
  
  
 
<h3>Project Highlights</h3>
 
<h3>Project Highlights</h3>
[[File:WP Overview HIghlights.JPG|300px]]
+
[[File:TE_Overview_Highlights.png|300px]]
 
* Our project schedule is divided into 12 iterations.
 
* Our project schedule is divided into 12 iterations.
* Till date of 12 April 2015, we have completed 100% of our development progress. We are now left with 2 milestone (Final Presentation and Poster Day) and the last iteration (iteration 12)
+
* Till date of 12 April 2016, we have completed 100% of our development progress. We are now left with 2 milestone (Final Presentation and Poster Day) and the last iteration (iteration 12)
 
* Beta Release - The system has been released on 17 February 2015.
 
* Beta Release - The system has been released on 17 February 2015.
*<h3>[[IS480 Team wiki: 2015T2 White Pinnacle Beta Release|Check out our beta release here!]]</h3>
+
*<h3>[[IS480 Team wiki: 2015T2 Elements Beta Release|Check out our beta release here!]]</h3>
 
*Current iteration: 12
 
*Current iteration: 12
 
*Iteration 13: 13 April 2016 - 22 April 2016
 
*Iteration 13: 13 April 2016 - 22 April 2016
Line 69: Line 69:
 
<h3>Development Progress</h3>
 
<h3>Development Progress</h3>
 
Progress: 100 % Completed
 
Progress: 100 % Completed
[[File:WP Final Development Progress.png|1000px]]
+
Link to the Development metrics: https://docs.google.com/a/smu.edu.sg/spreadsheets/d/1M9W9tuOnP9srr3V0IeMDBQZcdv3H7c9bQ0i-TfhwkTk/edit?usp=sharing
  
==<div style="background: #354458; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; text-transform:lowercase;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Project Management</font></div>==
+
==<div style="background: #808080; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; text-transform:lowercase;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Project Management</font></div>==
  
 
<h3> Project Scope</h3>
 
<h3> Project Scope</h3>
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! Acceptance !! Midterms
+
! Original!! Final
 
|-
 
|-
 
|
 
|
[[File:WP Scope Planned.jpg|500px]]
+
[[File:Team Elements Scope Acceptance.jpg|500px]]
 
  ||  
 
  ||  
[[File:WP Scope Actual.jpg|500px]]
+
[[File:FunctionalitiesScope MidTerms.png|500px]]
 
|}
 
|}
<h4>Final Completed Scope</h4>
+
 
[[File:WP Final Scope.jpg|1000px|link=]]
 
  
 
<h4>Major Scope changes</h4>
 
<h4>Major Scope changes</h4>
* iOS mobile application has been replaced by Responsive Web Application. The team proposed a responsive web application to cater to more devices and client agrees
+
* Removal of online payment as requested by the sponsor
* Responsive Web Application has been added to the scope.
 
* PDF Case Recognition has been added to the scope to allow the admin to quickly set up the cases in the future.
 
* The team documents changes on this change tracker and evaluate changes on a case by case basis.
 
  
[[IS480 Team wiki: 2015T1 WhitePinnacle ChangeManagement|View our Change Management Here!]]
+
[[IS480_Team_wiki:2015T2 Team Elements Change Management|View our Change Management Here!]]
 
<h3>Project Schedule</h3>
 
<h3>Project Schedule</h3>
[[IS480 Team wiki: 2015T1 WhitePinnacle ProjectManagement|View detailed Project Schedule here!]]
+
[[IS480 Team wiki: 2015T2 Team Elements Project Management|View detailed Project Schedule here!]]
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 101: Line 97:
 
|-
 
|-
 
|
 
|
[[File:WP ProjectSchedule Planned.png|500px]]
+
[[File:Team Elements ProjectSchedule Planned.png|500px]]
 
  ||  
 
  ||  
[[File:WP Milestones Finals.jpg|500px]]
+
[[File:Team Elements ProjectSchedule Actual.png|500px]]
 
|}
 
|}
  
 
<h4>Schedule Highlights</h4>
 
<h4>Schedule Highlights</h4>
* There are no major changes to major project milestones such as UT, UAT, deployment. However, the team added a Beta Release after the first deployment. This is to allow students to use our system before they become unavailable due to their schedule.  
+
* There are no major changes to major project milestones such as UT, UAT, deployment. However, the team added a Beta Release after the first deployment. This is to allow Sterling Taining Hub to use our system during oeprations.  
  
 
<h3>Metrics</h3>
 
<h3>Metrics</h3>
 
<h4>Schedule Metrics</h4>   
 
<h4>Schedule Metrics</h4>   
[[IS480 Team wiki: 2015T1 WhitePinnacle ScheduleMetrics|View our Schedule Metrics Here!]]<br>
+
[[IS480_Team_wiki: 2015T2 Team Elements Schedule Metrics|View our Schedule Metrics Here!]]<br>
  
[[Image:WP Schedule Metrics.png|1000px|center|link=]]
+
[[Image:Elements_Schedule_Metrics_Final.JPG|1000px|center|link=]]
  
 
<h5>Schedule Metrics Highlights</h5>
 
<h5>Schedule Metrics Highlights</h5>
  
 
{| class="wikitable" style="margin: auto;width:90%; text-align:center; background: white;"
 
{| class="wikitable" style="margin: auto;width:90%; text-align:center; background: white;"
! style="background: #354458; color: white; font-weight: bold; width:50px" | Iteration
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Iteration
! style="background: #354458; color: white; font-weight: bold; width:50px" | Planned Duration (Days)
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Planned Duration (Days)
! style="background: #354458; color: white; font-weight: bold; width:50px" | Actual Duration (Days)
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Actual Duration (Days)
! style="background: #354458; color: white; font-weight: bold; width:50px" | Schedule Metric Score
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Schedule Metric Score
! style="background: #354458; color: white; font-weight: bold; width:250px" | Action
+
! style="background: #808080; color: white; font-weight: bold; width:250px" | Action
! style="background: #354458; color: white; font-weight: bold; width:50px" | Status
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Status
 
|-
 
|-
|5
+
|4
 
|14
 
|14
|15
+
|17
|93%
+
|82%
|Estimates are generally accurate and on track. Proceed as per normal.
+
|The team is behind schedule.Under-estimated the effort required. Re-estimate tasks for future iterations.
Delayed slightly due to debugging phase, team was unfamiliar with charts and hence took a longer time to solve a date bug in the vital signs chart.  
 
  
Iteration 5 was delayed by one day.  
+
Delayed due to the potential change in sponsor and the team was changing some aspects of the interface after acceptance presentation.
Follow up action: The following iteration started on the same day. No buffer day is used.
+
Follow up action: Iteration 4 was delayed by 3 days. However, the following iteration started after the exam break. No buffer day is used.
 
|Completed
 
|Completed
 
|-
 
|-
|11
+
|10
 
|14
 
|14
|15
+
|19
|93%
+
|74%
 
|
 
|
Iteration 11 was delayed by one day due to complexity in PDF Recognition Case Setup. <br>  
+
Iteration 10 was delayed by 5 days due to the change in a fundamental database structure <br>  
Follow up action: Still within the safe range.
+
Follow up action: Drop functionalities for this iteration and rescheduled them to the next iteration.
 
|Completed
 
|Completed
 
|-
 
|-
Line 149: Line 144:
  
 
<h4>Bug Metrics</h4>
 
<h4>Bug Metrics</h4>
[[IS480 Team wiki: 2015T1 WhitePinnacle BugMetrics|View our Bug Metrics here!]]<br>
+
[[IS480_Team_wiki:2015T2 Team Elements Bug Metrics|View our Bug Metrics here!]]<br>
 
<h5>Bug Score</h5>
 
<h5>Bug Score</h5>
[[Image: WP_BugMetrics.png|800px|center|link=]]
+
[[Image: Elements_Bug_Finals.png|800px|center|link=]] <br>
 
 
 
 
<h5>Bug Distribution based on Severity</h5>
 
[[Image:WP-BugSummary.png|center|link=]]
 
  
 
{| class="wikitable" style="margin: auto;width:90%; text-align:center; background: white;"
 
{| class="wikitable" style="margin: auto;width:90%; text-align:center; background: white;"
! style="background: #354458; color: white; font-weight: bold; width:50px" | Iteration
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Iteration
! style="background: #354458; color: white; font-weight: bold; width:250px" | Bug Score
+
! style="background: #808080; color: white; font-weight: bold; width:250px" | Bug Score
! style="background: #354458; color: white; font-weight: bold; width:250px" | Summary of bugs
+
! style="background: #808080; color: white; font-weight: bold; width:250px" | Summary of bugs
! style="background: #354458; color: white; font-weight: bold; width:250px" | Action Taken
+
! style="background: #808080; color: white; font-weight: bold; width:250px" | Action Taken
 +
|-
 +
|4
 +
|<b>33</b> <br> 2 High <br>
 +
|There was a problem with iron router during deployment. It worked on our local host but not on the deployment server.
 +
|Stop current development and resolve the bug immediately. Project Manager reschedules the project.
 
|-
 
|-
 
|5
 
|5
|<b>30</b> <br> 6 High <br>
+
|<b>29</b> <br> 1 High <br>
|Most of the bugs in this iteration were due to the date and time error on the charts.
+
|Meteor underwent a version change and this new version was buggy, causing compatibility issues and the application could not run.
|Stop current development and resolve the bug immediately. Project Manager reschedules the project.
+
|Stop current development and resolve the bug immediately. Project Manager reschedules the project.  
 
|-
 
|-
 
|8
 
|8
|<b>32</b> <br> 6 High <br> 2 Low<br>
+
|<b>17</b> <br> 2 High <br>  
|The bugs were manageable. Some were due to validations, UI bugs, etc
+
|Due to a confusion in the template names, the options at the side bar were gone
|Stop current development and resolve the bug immediately. Project Manager reschedules the project.  
+
|Stop current development and resolve the bug immediately. Project Manager reschedules the project.
 
|-
 
|-
|9
+
|10
|<b>8</b> <br> 1 High <br> 3 Low<br>
+
|<b>33</b> <br> 2 High <br>
|Developers did thorough unit and integration testing. Hence, lesser bugs were found in this iteration.  
+
|There was a fundamental change in database structure and the emails did not work and always caused an error when creating a new class.  
|Use the planned debugging time in the iteration  
+
|Stop current development and resolve the bug immediately. Project Manager reschedules the project.  
 
|-
 
|-
  
 
|}
 
|}
<h4>Task Metrics by Iteration</h4>
 
[[File:WP_EffortMetrics.jpg|800px]]
 
  
[[IS480 Team wiki: 2015T1 WhitePinnacle TaskMetrics|View our Task Metrics here!]]<br>
 
  
 
<h3>Project Risks</h3>
 
<h3>Project Risks</h3>
 
<h4>Activated Risks</h4>
 
<h4>Activated Risks</h4>
[[IS480 Team wiki: 2015T1 WhitePinnacle RiskManagement|View our risk management here!]] The below table only highlights the two top risks that have been mitigated.  
+
[[IS480_Team_wiki:2015T2 Team Elements Risk Management|View our risk management here!]] The below table only highlights the two top risks that have been mitigated.  
 
{| class="wikitable" style="margin: auto;width:90%; text-align:center; background: white;"
 
{| class="wikitable" style="margin: auto;width:90%; text-align:center; background: white;"
! style="background: #354458; color: white; font-weight: bold; width:50px" | No
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | No
! style="background: #354458; color: white; font-weight: bold; width:250px" | Risk Description
+
! style="background: #808080; color: white; font-weight: bold; width:250px" | Risk Description
! style="background: #354458; color: white; font-weight: bold; width:250px" | Impact
+
! style="background: #808080; color: white; font-weight: bold; width:250px" | Impact
! style="background: #354458; color: white; font-weight: bold; width:50px" | Likelihood
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Likelihood
! style="background: #354458; color: white; font-weight: bold; width:50px" | Impact
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Impact
! style="background: #354458; color: white; font-weight: bold; width:50px" | Category
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Category
! style="background: #354458; color: white; font-weight: bold; width:250px" | Mitigation Plan
+
! style="background: #808080; color: white; font-weight: bold; width:250px" | Mitigation Plan
! style="background: #354458; color: white; font-weight: bold; width:70px" | Status
+
! style="background: #808080; color: white; font-weight: bold; width:70px" | Status
 
|-
 
|-
 
| 1
 
| 1
| Client changes requirements on an ad hoc basis
+
| Sponsor changes requirements on an ad hoc basis
 
| Project schedule will be affected
 
| Project schedule will be affected
 
| Medium
 
| Medium
 
| Medium
 
| Medium
 
| B
 
| B
| Team to evaluate changes on a case to case basis based on change management.
+
| Project Manager and Business Analyst to work with sponsor closely to monitor and modify the team plan after every iteration. Team to evaluate on a case-by-case basis
| Mitigated
+
|Mitigated
 
|-
 
|-
 
| 2
 
| 2
| Unable to get NP nursing students to test due to constraints in Ngee Ann Polytechnic’s academic calendar
+
| Unable to get the administrators to test the system as the training facility is still being built
| Unable to get genuine feedback from students and hence affect the usability of the system
+
| Unable to get genuine feedback from users and hence affect the usability of the system
 
| High
 
| High
 
| High
 
| High
 
| A
 
| A
| PM to reschedule project  to complete Student's Portal functions before the students are unavailable.
+
| Project manager will work closely with the sponsor to source for similar training facilities and conduct observations and tests with them. <br>
| Mitigated
+
Project Manager to work closely with sponsor to plan each functions.
 +
|Mitigated
 
|-
 
|-
  
Line 220: Line 214:
  
 
The above two risks has been <b>mitigated</b>.  
 
The above two risks has been <b>mitigated</b>.  
# Risk 1: The team implemented change management plan in order to evaluate the changes requested by the client. [[IS480 Team wiki: 2015T1 WhitePinnacle ChangeManagement|View our Change Management Here!]]
+
# Risk 1: The team implemented change management plan in order to evaluate the changes requested by the client. [[IS480_Team_wiki:2015T2 Team Elements Change Management|View our Change Management Here!]]
# Risk 2: PM rescheduled the project to complete student's functions before students were unavailable. Student's portal is now fully implemented, tested with NP nursing students and deployed.
+
# Risk 2: Sponsor and the team went to find through their own personal contacts and managed to gather a total of 2 other training hubs to help.
  
 
<h4>Future Risks</h4>
 
<h4>Future Risks</h4>
Line 241: Line 235:
 
| A
 
| A
 
| Provide proper documentation such as  deployment guide and include comments in the codes.
 
| Provide proper documentation such as  deployment guide and include comments in the codes.
|Mitigated
 
|-
 
| 2
 
| Unexpected issues when users use the system
 
 
| Inconvenience will be caused for the users
 
 
| Low
 
| Low
 
| C
 
| Upon handover, the team will be giving the client a 1 month warranty period whereby all bugs found within this 1 month of usage will be solved by the team
 
 
|Mitigated
 
|Mitigated
 
|-
 
|-
Line 259: Line 242:
  
 
<h3>Technical Complexity</h3>
 
<h3>Technical Complexity</h3>
<h4>PDF Text Recognition</h4>
+
<h4>Automated generation of LSP Forms</h4>
* NP HS purchases new cases regularly. The format of these cases are <b>unstructured</b>. The cases are cumbersome to set up, hence the team proposed PDF text recognition case setup to ease the setting up of new cases.
+
* Sterling has regulations to compliy to. These forms take up much time to fill up
* Populate case setup form according to extracted information from the unstructured pdfs
+
* Linking feedback forms with LSP Forms and automatically generating LSP forms
  
* The pdf is unstructured and it is unclear for a person without background to input such case information. Under the healthcare provider's order, there could be many different kinds of orders (medication, non-medication, doctor's remarks, etc). The team will be using picking out  relevant information and put them into the relevant fields for easy setting up of cases
+
[[File:Elements lspGeneration.png|500px]]
 +
* The above image is generated by averaging the results from feedback forms
  
 +
<h4>Generation of Certificates</h4>
 +
* Sterling needs to generate certificates for pupils who have completed their courses
 +
* Populate certs in a given format and exporting them to pdf for printing
  
<b>Challenges Faced during extraction</b><br>
+
[[File:Elements cert generation.png|500px]]
The team faced challenges in extracting the correct information due to the structure of the PDF. iText library reads the information line by line, however the information needed does not make business sense.
+
* The above image is generated from the class list
  
[[File:WP_TC_1.jpg|900px]]
+
<h4>Excel Read&Write</h4>
 +
[[File:Elements excel screenshot.png |500px]]
 +
* For the convenience of the trainer, the trainer can download a copy of the class list into excel and use it to fill up the class' grades and attendance.
  
<b>How the team managed the challenge?</b><br>
+
<div style="background: #808080; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; text-transform:lowercase;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Quality of Product</font></div>
The team found the coordinates and from there on, we managed to get correct information to extract.
 
[[File:WP_TC_2.jpg|900px]]
 
 
 
<h4>Responsive Web Mobile Application</h4>
 
[[File:WP Responsive HowItWorks.png|800px]]
 
[[File:WP Responsive Functions.png|800px]]
 
* This was proposed by the team as a replacement of the iOS application.
 
 
 
==<div style="background: #354458; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; text-transform:lowercase;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Quality of Product</font></div>==
 
 
<h3>Deliverables</h3>
 
<h3>Deliverables</h3>
 
{| class="wikitable" style="margin: auto;width:50%; text-align:center; background: white;"
 
{| class="wikitable" style="margin: auto;width:50%; text-align:center; background: white;"
! style="background: #354458; color: white; font-weight: bold; width:50px" | Stage
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Stage
! style="background: #354458; color: white; font-weight: bold; width:50px" | Specification
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Specification
! style="background: #354458; color: white; font-weight: bold; width:50px" | Modules
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Modules
 
|-
 
|-
! style="background: #354458; color: white; font-weight: bold; width:50px" | Project Requirements
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Project Requirements
| Story boards
+
| Purpose and Motivation
| [[IS480 Team wiki: 2015T1 WhitePinnacle Motivation|Story board]]<br>
+
| [[IS480 Team wiki: 2015T2 Team Elements Project Overview | Purpose and Motivation]]<br>
[[IS480 Team wiki: 2015T1 WhitePinnacle MarketResearch|Market Research]]
+
[[IS480_Team_wiki:2015T2 Team Elements Market Research  | Market Research]]
 
|-
 
|-
! style="background: #354458; color: white; font-weight: bold; width:50px" | Project Management
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Project Management
 
| Minutes
 
| Minutes
| [[IS480 Team wiki: 2015T1 WhitePinnacle MeetingMinutes|Meeting Minutes]]
+
| [[IS480_Team_wiki:2015T2 Team Elements Meeting Minutes | Meeting Minutes]]
 
|-
 
|-
! style="background: #354458; color: white; font-weight: bold; width:50px" | Project Management
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Project Management
 
| Metrics, Risks, Change
 
| Metrics, Risks, Change
 
|  
 
|  
[[IS480 Team wiki: 2015T1 WhitePinnacle ScheduleMetrics|Schedule Metrics]]<br>
+
[[IS480_Team_wiki: 2015T2 Team Elements Schedule Metrics|Schedule Metrics]]<br>
[[IS480 Team wiki: 2015T1 WhitePinnacle BugMetrics|Bug Metrics]]<br>
+
[[IS480_Team_wiki:2015T2 Team Elements Bug Metrics|Bug Metrics]]<br>
[[IS480 Team wiki: 2015T1 WhitePinnacle RiskManagement|Risk Management]]<br>
+
[[IS480_Team_wiki:2015T2 Team Elements Risk Management|Bug Management]]<br>
[[IS480 Team wiki: 2015T1 WhitePinnacle ChangeManagement|Change Management]]
+
[[IS480_Team_wiki:2015T2 Team Elements Change Management|Change Management]]
 
|-
 
|-
! style="background: #354458; color: white; font-weight: bold; width:50px"  | Analysis and Design
+
! style="background: #808080; color: white; font-weight: bold; width:50px"  | Analysis and Design
  | Use Case, ER Diagram, As-Is, To-Be Processes, Sequence Diagrams
+
  | DB Diagram, As-Is, To-Be Processes
  |  [[IS480 Team wiki: 2015T1 WhitePinnacle Documentation|Use Case, ER Diagram, As-Is, To-Be Processes, Sequence Diagrams]], [[Media: WP_UseCaseDescription.pdf|Use Case Description]]
+
  |  [[IS480 Team wiki: 2015T2 Team Elements Documentation|DB Diagram, As-Is, To-Be Processes]]
 
|-
 
|-
  
! style="background: #354458; color: white; font-weight: bold; width:50px" | Design
+
 
 +
! style="background: #808080; color: white; font-weight: bold; width:50px" | Design
 
| Prototype
 
| Prototype
  | [[IS480 Team wiki: 2015T1 WhitePinnacle DesignDocuments|Persona and Prototype]]
+
  | [[IS480_Team_wiki: 2015T2 Team Elements Design Documents|Persona and Prototype]]
 
|-
 
|-
! style="background: #354458; color: white; font-weight: bold; width:50px" | Testing
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Testing
 
| User Test Plan
 
| User Test Plan
 
|  
 
|  
[[IS480 Team wiki: 2015T2 White Pinnacle Heuristic Evaluation|Heuristic Evaluation]]
+
[[IS480_Team_wiki:_2015T2 Elements Heuristic Evaluation|Heuristic Evaluation]]<br>
[[IS480 Team wiki: 2015T2 White Pinnacle User Testing 1|User Testing 1]]<br>
+
[[IS480_Team_wiki:_2015T2 Elements User Testing 1|User Testing 1]]<br>
[[IS480 Team wiki: 2015T2 White Pinnacle User Testing 2|User Testing 2]]<br>
+
[[IS480_Team_wiki:_2015T2 Elements User Testing 2|User Testing 2]]<br>
[[IS480 Team wiki: 2015T2 White Pinnacle User Testing 2|User Testing 3]]
+
[[IS480_Team_wiki:_2015T2 Elements User Testing 3|User Testing 3]]
 
|-
 
|-
! style="background: #354458; color: white; font-weight: bold; width:50px" | Handover
+
! style="background: #808080; color: white; font-weight: bold; width:50px" | Handover
 
| User Manual, Project Closure Sign Off, UAT Sign Off
 
| User Manual, Project Closure Sign Off, UAT Sign Off
 
|  
 
|  
[[Media: HS EMR User Guide Final.pdf|User Manual Guide]]<br>
+
[[Media: Sterling LMS User Guide Final.pdf|User Manual Guide]]<br>
[[Media: HS_EMR_UAT_Signoff.pdf|UAT Sign Off]]<br>
+
[[Media: Sterling LMS_UAT_Signoff.pdf|UAT Sign Off]]<br>
[[Media: WPProject-Closure.pdf|Project Closure Sign Off]]
+
[[Media: TEProject-Closure.pdf|Project Closure Sign Off]]
 
|-
 
|-
  
Line 333: Line 314:
 
<h3>Deployment</h3>
 
<h3>Deployment</h3>
  
Deployed Link: http://hsemr-wpinapp.rhcloud.com/hsemr
+
Deployed Link: http://sterlingtraininghub.com/
  
 
<h3>Testing</h3>
 
<h3>Testing</h3>
We have conducted three user testing and one heuristic evaluation.  
+
We have conducted three user tests and one heuristic evaluation.  
  
 
<h4>Heuristic Evaluation</h4>
 
<h4>Heuristic Evaluation</h4>
Line 342: Line 323:
 
* 5 participants
 
* 5 participants
 
*  This is to learn more about the usability of our application and improve it further in our future designs. This was conducted with a paper prototype. A paper prototype was used because we want to be able to discover UI issues early, so that the cost of changing will not be so high.
 
*  This is to learn more about the usability of our application and improve it further in our future designs. This was conducted with a paper prototype. A paper prototype was used because we want to be able to discover UI issues early, so that the cost of changing will not be so high.
[[IS480 Team wiki: 2015T2 White Pinnacle Heuristic Evaluation|View our Heuristics Evaluation documentation here!]]
+
[[IS480_Team_wiki:_2015T2 Elements Heuristic Evaluation|View our Heuristics Evaluation documentation here!]]
  
 
<h4>User Testing 1</h4>
 
<h4>User Testing 1</h4>
*Date: 29 October 2014
+
*Date: 10 October 2015
*Venue: Ngee Ann Polytechnic, School of Health Sciences
+
*Venue: Sterling Training Hub
* 4 NP Health Sciences students
+
*4 Training Hub Administrators
* 1 NP Health Sciences Lecturer
+
[[IS480_Team_wiki:_2015T2 Elements User Testing 1|View our UT1 documentation here!]]
[[IS480 Team wiki: 2015T2 White Pinnacle User Testing 1|View our UT1 documentation here!]]
 
  
 
<h4>User Testing 2</h4>
 
<h4>User Testing 2</h4>
*Date: 21 January 2015
+
*Date: 29 January 2016
 
*Venue: Sterling Training Hub
 
*Venue: Sterling Training Hub
 
* 3 Sterling Training Hub administrators
 
* 3 Sterling Training Hub administrators
[[IS480 Team wiki: 2015T2 White Pinnacle User Testing 2|View our UT2 documentation here!]]
+
[[IS480_Team_wiki:_2015T2 Elements User Testing 2|View our UT2 documentation here!]]
  
 
<h4>User Testing 3</h4>
 
<h4>User Testing 3</h4>
 
*Date: 25 March 2016
 
*Date: 25 March 2016
 
*Venue: Sterling Training Hub and web
 
*Venue: Sterling Training Hub and web
* 8 NP Health Sciences lecturers
+
* 8 Sterling Training Hub Trainers, 20 Students
[[IS480 Team wiki: 2015T2 White Pinnacle User Testing 3|View our UT3 documentation here!]]
+
[[IS480_Team_wiki:_2015T2 Elements User Testing 3|View our UT3 documentation here!]]
  
==<div style="background: #354458; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; text-transform:lowercase;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Reflections</font></div>==
+
==<div style="background: #808080; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; text-transform:lowercase;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Reflections</font></div>==
  
 
[[File:TE_Learning_Outcomes_1.png|500px|link=]][[File:TE_Learning_Outcomes_2.png|500px|link=]]
 
[[File:TE_Learning_Outcomes_1.png|500px|link=]][[File:TE_Learning_Outcomes_2.png|500px|link=]]
  
==<div style="background: #354458; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; text-transform:lowercase;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Sponsor and Client Testimonial</font></div>==
 
 
<!--Content End-->
 
<!--Content End-->

Latest revision as of 03:01, 15 April 2016

Team Elements Logo.jpg


Team Elements Home.png   HOME

 

Team Elements AboutUs.png   ABOUT US

 

Team Elements PrjOverview.png   PROJECT OVERVIEW

 

Team Elements PrjMgmt.png   PROJECT MANAGEMENT

 

Team Elements Documentation.png   DOCUMENTATION

Main Wiki Midterm Wiki NavigationElements.png Final Wiki



Project Progress Summary

TE Slides Icon.jpgFinals Slides Elements Deployed Icon.jpgDeployed Site WP Postericon.JPGPoster WP Video.pngPitch Video


Project Highlights

TE Overview Highlights.png

  • Our project schedule is divided into 12 iterations.
  • Till date of 12 April 2016, we have completed 100% of our development progress. We are now left with 2 milestone (Final Presentation and Poster Day) and the last iteration (iteration 12)
  • Beta Release - The system has been released on 17 February 2015.
  • Check out our beta release here!

  • Current iteration: 12
  • Iteration 13: 13 April 2016 - 22 April 2016
  • The project has officially been handed over to Sterling Training Hub.

Development Progress

Progress: 100 % Completed Link to the Development metrics: https://docs.google.com/a/smu.edu.sg/spreadsheets/d/1M9W9tuOnP9srr3V0IeMDBQZcdv3H7c9bQ0i-TfhwkTk/edit?usp=sharing

Project Management

Project Scope

Original Final

Team Elements Scope Acceptance.jpg

FunctionalitiesScope MidTerms.png


Major Scope changes

  • Removal of online payment as requested by the sponsor

View our Change Management Here!

Project Schedule

View detailed Project Schedule here!

Planned Actual

Team Elements ProjectSchedule Planned.png

Team Elements ProjectSchedule Actual.png

Schedule Highlights

  • There are no major changes to major project milestones such as UT, UAT, deployment. However, the team added a Beta Release after the first deployment. This is to allow Sterling Taining Hub to use our system during oeprations.

Metrics

Schedule Metrics

View our Schedule Metrics Here!

Elements Schedule Metrics Final.JPG
Schedule Metrics Highlights
Iteration Planned Duration (Days) Actual Duration (Days) Schedule Metric Score Action Status
4 14 17 82% The team is behind schedule.Under-estimated the effort required. Re-estimate tasks for future iterations.

Delayed due to the potential change in sponsor and the team was changing some aspects of the interface after acceptance presentation. Follow up action: Iteration 4 was delayed by 3 days. However, the following iteration started after the exam break. No buffer day is used.

Completed
10 14 19 74%

Iteration 10 was delayed by 5 days due to the change in a fundamental database structure
Follow up action: Drop functionalities for this iteration and rescheduled them to the next iteration.

Completed

Bug Metrics

View our Bug Metrics here!

Bug Score
Elements Bug Finals.png

Iteration Bug Score Summary of bugs Action Taken
4 33
2 High
There was a problem with iron router during deployment. It worked on our local host but not on the deployment server. Stop current development and resolve the bug immediately. Project Manager reschedules the project.
5 29
1 High
Meteor underwent a version change and this new version was buggy, causing compatibility issues and the application could not run. Stop current development and resolve the bug immediately. Project Manager reschedules the project.
8 17
2 High
Due to a confusion in the template names, the options at the side bar were gone Stop current development and resolve the bug immediately. Project Manager reschedules the project.
10 33
2 High
There was a fundamental change in database structure and the emails did not work and always caused an error when creating a new class. Stop current development and resolve the bug immediately. Project Manager reschedules the project.


Project Risks

Activated Risks

View our risk management here! The below table only highlights the two top risks that have been mitigated.

No Risk Description Impact Likelihood Impact Category Mitigation Plan Status
1 Sponsor changes requirements on an ad hoc basis Project schedule will be affected Medium Medium B Project Manager and Business Analyst to work with sponsor closely to monitor and modify the team plan after every iteration. Team to evaluate on a case-by-case basis Mitigated
2 Unable to get the administrators to test the system as the training facility is still being built Unable to get genuine feedback from users and hence affect the usability of the system High High A Project manager will work closely with the sponsor to source for similar training facilities and conduct observations and tests with them.

Project Manager to work closely with sponsor to plan each functions.

Mitigated

The above two risks has been mitigated.

  1. Risk 1: The team implemented change management plan in order to evaluate the changes requested by the client. View our Change Management Here!
  2. Risk 2: Sponsor and the team went to find through their own personal contacts and managed to gather a total of 2 other training hubs to help.

Future Risks

No Risk Description Impact Likelihood Impact Category Mitigation Plan Status
1 Future developers unfamiliar with technologies used Unable to hand over to future developers for future application enhancement High High A Provide proper documentation such as deployment guide and include comments in the codes. Mitigated

The above two risks have not occurred. However, our team anticipated the possibility of it and managed to mitigate these risks.

Technical Complexity

Automated generation of LSP Forms

  • Sterling has regulations to compliy to. These forms take up much time to fill up
  • Linking feedback forms with LSP Forms and automatically generating LSP forms

Elements lspGeneration.png

  • The above image is generated by averaging the results from feedback forms

Generation of Certificates

  • Sterling needs to generate certificates for pupils who have completed their courses
  • Populate certs in a given format and exporting them to pdf for printing

Elements cert generation.png

  • The above image is generated from the class list

Excel Read&Write

Elements excel screenshot.png

  • For the convenience of the trainer, the trainer can download a copy of the class list into excel and use it to fill up the class' grades and attendance.
Quality of Product

Deliverables

Stage Specification Modules
Project Requirements Purpose and Motivation Purpose and Motivation

Market Research

Project Management Minutes Meeting Minutes
Project Management Metrics, Risks, Change

Schedule Metrics
Bug Metrics
Bug Management
Change Management

Analysis and Design DB Diagram, As-Is, To-Be Processes DB Diagram, As-Is, To-Be Processes
Design Prototype Persona and Prototype
Testing User Test Plan

Heuristic Evaluation
User Testing 1
User Testing 2
User Testing 3

Handover User Manual, Project Closure Sign Off, UAT Sign Off

User Manual Guide
UAT Sign Off
Project Closure Sign Off

Deployment

Deployed Link: http://sterlingtraininghub.com/

Testing

We have conducted three user tests and one heuristic evaluation.

Heuristic Evaluation

  • Venue: Singapore Management University, School of Information Systems
  • 5 participants
  • This is to learn more about the usability of our application and improve it further in our future designs. This was conducted with a paper prototype. A paper prototype was used because we want to be able to discover UI issues early, so that the cost of changing will not be so high.

View our Heuristics Evaluation documentation here!

User Testing 1

  • Date: 10 October 2015
  • Venue: Sterling Training Hub
  • 4 Training Hub Administrators

View our UT1 documentation here!

User Testing 2

  • Date: 29 January 2016
  • Venue: Sterling Training Hub
  • 3 Sterling Training Hub administrators

View our UT2 documentation here!

User Testing 3

  • Date: 25 March 2016
  • Venue: Sterling Training Hub and web
  • 8 Sterling Training Hub Trainers, 20 Students

View our UT3 documentation here!

Reflections

TE Learning Outcomes 1.pngTE Learning Outcomes 2.png