HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 265: Line 265:
 
[[File:Elements excel screenshot.png |500px]]
 
[[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.
 
* 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.
 
+
<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>
==<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>==
 
 
<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;"
Line 274: Line 273:
 
|-
 
|-
 
! style="background: #354458; color: white; font-weight: bold; width:50px" | Project Requirements
 
! style="background: #354458; 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: #354458; 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: #354458; 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: #354458; 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: #354458; 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: #354458; 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: #354458; color: white; font-weight: bold; width:50px" | Handover
Line 312: Line 312:
 
[[Media: HS EMR User Guide Final.pdf|User Manual Guide]]<br>
 
[[Media: HS EMR User Guide Final.pdf|User Manual Guide]]<br>
 
[[Media: HS_EMR_UAT_Signoff.pdf|UAT Sign Off]]<br>
 
[[Media: HS_EMR_UAT_Signoff.pdf|UAT Sign Off]]<br>
[[Media: WPProject-Closure.pdf|Project Closure Sign Off]]
+
[[Media: TEProject-Closure.pdf|Project Closure Sign Off]]
 
|-
 
|-
  

Revision as of 18:10, 9 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 students to use our system before they become unavailable due to their schedule.

Metrics

Schedule Metrics

View our Schedule Metrics Here!

WP Schedule Metrics.png
Schedule Metrics Highlights
Iteration Planned Duration (Days) Actual Duration (Days) Schedule Metric Score Action Status
5 14 15 93% Estimates are generally accurate and on track. Proceed as per normal.

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. Follow up action: The following iteration started on the same day. No buffer day is used.

Completed
11 14 15 93%

Iteration 11 was delayed by one day due to complexity in PDF Recognition Case Setup.
Follow up action: Still within the safe range.

Completed

Bug Metrics

View our Bug Metrics here!

Bug Score
WP BugMetrics.png


Bug Distribution based on Severity
WP-BugSummary.png
Iteration Bug Score Summary of bugs Action Taken
5 30
6 High
Most of the bugs in this iteration were due to the date and time error on the charts. Stop current development and resolve the bug immediately. Project Manager reschedules the project.
8 32
6 High
2 Low
The bugs were manageable. Some were due to validations, UI bugs, etc Stop current development and resolve the bug immediately. Project Manager reschedules the project.
9 8
1 High
3 Low
Developers did thorough unit and integration testing. Hence, lesser bugs were found in this iteration. Use the planned debugging time in the iteration

Task Metrics by Iteration

WP EffortMetrics.jpg

View our Task Metrics here!

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 Client changes requirements on an ad hoc basis Project schedule will be affected Medium Medium B Team to evaluate changes on a case to case basis based on change management. Mitigated
2 Unable to get NP nursing students to test due to constraints in Ngee Ann Polytechnic’s academic calendar Unable to get genuine feedback from students and hence affect the usability of the system High High A PM to reschedule project to complete Student's Portal functions before the students are unavailable. 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: 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.

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
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

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

Technical Complexity

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