HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
 
(21 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 50: Line 50:
  
 
<h3>[[Media: Team Elements MidTerms Final.pdf|Midterm slides]]<br></h3>
 
<h3>[[Media: Team Elements MidTerms Final.pdf|Midterm slides]]<br></h3>
Deployed Link: <br>
+
Deployed Link: sterlingtraininghub.com<br>
  
 
<h3>Project Highlights</h3>
 
<h3>Project Highlights</h3>
Line 87: Line 87:
 
* The team documents changes on this change tracker and evaluate changes on a case by case basis.  
 
* The team documents changes on this change tracker and evaluate changes on a case by case basis.  
  
[[IS480 Team wiki: 2015T2 Team Elements Change Management|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 96: Line 96:
 
|-
 
|-
 
|
 
|
[[File:WP ProjectSchedule Planned.png|500px]]
+
[[File:Team Elements ProjectSchedule Planned.png|500px]]
 
  ||  
 
  ||  
[[File:WP ProjectSchedule Actual.png|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 was a removal of a user test in December due to our change in sponsor.
 +
* There was a delay for Beta Release as our sponsor was still deciding on the host for their website.
  
 
<h3>Metrics</h3>
 
<h3>Metrics</h3>
 
<h4>Schedule Metrics</h4>   
 
<h4>Schedule Metrics</h4>   
[[IS480 Team wiki: 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|800px|center|link=]]
+
[[Image:Elements Schedule Metrics.jpg|800px|center|link=]]
  
 
<h5>Schedule Metrics Highlights</h5>
 
<h5>Schedule Metrics Highlights</h5>
Line 120: Line 121:
 
! style="background: #354458; color: white; font-weight: bold; width:50px" | Status
 
! style="background: #354458; 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.  
+
 +
 +
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 5 was delayed by one day. However, 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
 
|-
 
|-
Line 134: Line 137:
  
 
<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_mid_terms.JPG|550px|center|link=]]
 
+
* Numbers above are the total bug scores
<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;"
Line 147: Line 148:
 
! style="background: #354458; color: white; font-weight: bold; width:250px" | Action Taken
 
! style="background: #354458; color: white; font-weight: bold; width:250px" | Action Taken
 
|-
 
|-
|5
+
|4
|<b>30</b> <br> 6 High <br>
+
|<b>33</b> <br> 2 High <br>
|Most of the bugs in this iteration were due to the date and time error on the charts.
+
|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.
 
|Stop current development and resolve the bug immediately. Project Manager reschedules the project.
 
|-
 
|-
|8
+
|5
|<b>32</b> <br> 6 High <br> 2 Low<br>
+
|<b>29</b> <br> 1 High <br>  
|The bugs were manageable. Some were due to validations, UI bugs, etc
+
|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.  
 
|-
 
|-
|9
+
|8
|<b>8</b> <br> 1 High <br> 3 Low<br>
+
|<b>17 (so far)</b> <br> 1 High <br>  
|Developers did thorough unit and integration testing. Hence, lesser bugs were found in this iteration.
+
|Due to a confusion in the template names, the options at the side bar were gone
|Use the planned debugging time in the iteration
+
|Stop current development and resolve the bug immediately. Project Manager reschedules the project.
 
|-
 
|-
  
Line 166: Line 167:
  
 
<h3>Project Risks</h3>
 
<h3>Project Risks</h3>
[[IS480 Team wiki: 2015T1 WhitePinnacle RiskManagement|View our risk management here!]]
+
[[IS480_Team_wiki:2015T2 Team Elements Risk Management|View our risk management here!]]
 
{| 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: #354458; color: white; font-weight: bold; width:50px" | No
Line 177: Line 178:
 
|-
 
|-
 
| 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
 
|-
 
|-
 
| 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>
 +
Project Manager to work closely with sponsor to plan each functions.
 
|-
 
|-
  
Line 196: Line 198:
  
 
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.
  
 
<h3>Technical Complexity</h3>
 
<h3>Technical Complexity</h3>
<h4>PDF Text Recognition</h4>
+
<h4>Generation of Certificates</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 needs to generate certificates for pupils who have completed their courses
* Populate case setup form according to extracted information from the unstructured pdfs
+
* Populate certs in a given format and exporting them to pdf for printing
  
[[File:WP PDFRecognition.png|900px]]
+
[[File:Elements cert generation.png|500px]]
* As seen above, 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 iText library to extract out relevant information and put them into the relevant fields for easy setting up of cases
+
* The above image is generated from the class list
  
<h4>Responsive Web Mobile Application</h4>
+
<h4>Excel Read&Write</h4>
[[File:WP Responsive HowItWorks.png|800px]]
+
[[File:Elements excel screenshot.png |500px]]
[[File:WP Responsive Functions.png|800px]]
+
* 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.
* 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>==
+
<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 220: Line 221:
 
|-
 
|-
 
! 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: 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: 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]]<br>
+
[[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>
 
|-
 
|-
  
Line 257: Line 258:
 
<h3>Deployment</h3>
 
<h3>Deployment</h3>
  
Deployed Link: http://hsemr-wpinapp.rhcloud.com/hsemr
+
Deployed Link: sterlingtraininghub.com
  
 
<h3>Testing</h3>
 
<h3>Testing</h3>
Line 266: Line 267:
 
* 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 2014
*Venue: Ngee Ann Polytechnic, School of Health Sciences
+
*Venue: Sterling Engineering Training Hub
* 4 NP Health Sciences students
+
* 1 Academic One Administrator
* 1 NP Health Sciences Lecturer
+
* 2 Cerealtech School Of Baking Technology Administrator
[[IS480 Team wiki: 2015T2 White Pinnacle User Testing 1|View our UT1 documentation here!]]
+
* 1 administrator from CSIS Industries Administrator
 +
[[IS480_Team_wiki:_2015T2 Elements 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 2015
*Venue: Ngee Ann Polytechnic, School of Health Sciences
+
*Venue: Sterling Engineering Training Hub
* 38 NP Health Sciences students
+
* 3 Sterling Engineering 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!]]
  
  
==<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:Team Elements Mid-Terms LearningOutcome1.JPG|500px|link=]]
 
[[File:Team Elements Mid-Terms LearningOutcome1.JPG|500px|link=]]
 
[[File:Team Elements Mid-Terms LearningOutcome2.JPG|500px|link=]]
 
[[File:Team Elements Mid-Terms LearningOutcome2.JPG|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>==
 
 
[[File:WP ClientTestimonial1.png|1000px]]
 
[[File:WP ClientTestimonial2.png|1000px]]
 
|}
 
 
 
 
  
  
 
<!--Content End-->
 
<!--Content End-->

Latest revision as of 00:47, 10 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 NavigationElements.png Midterm Wiki Final Wiki


Project Progress Summary

Midterm slides

Deployed Link: sterlingtraininghub.com

Project Highlights

Our project schedule is divided into 12 iterations.

  • Till date of 18 February 2015, we have completed about 80% of our development progress.
  • Two user testing with users (before acceptance and before midterms)
  • Beta release on 17 February 2015, with actual administrators using the system (before midterms).
  • Current iteration: 8
  • Iteration 8: 5 February 2015 - 23 February 2015


Development Progress

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

  • The team is confident of completing the project and delivering the application on time.


Project Management

Project Scope

Planned Now

Team Elements Scope Acceptance.jpg

FunctionalitiesScope MidTerms.png

Major Scope changes

  • Addition of LSP Forms for compliance purposes
  • Shifting of Search Module to Secondary functionalities based on additional observations
  • Shifting of Student and Trainer Modules to Tertiary functionalities.
  • Removal of notifications module
  • The team documents changes on this change tracker and evaluate changes on a case by case basis.

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 was a removal of a user test in December due to our change in sponsor.
  • There was a delay for Beta Release as our sponsor was still deciding on the host for their website.

Metrics

Schedule Metrics

View our Schedule Metrics Here!

Elements Schedule Metrics.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

Bug Metrics

View our Bug Metrics here!

Bug Score
Elements Bug mid terms.JPG
  • Numbers above are the total bug scores
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 (so far)
1 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.

Project Risks

View our risk management here!

No Risk Description Impact Likelihood Impact Category Mitigation Plan
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
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.

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.

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

Deployment

Deployed Link: sterlingtraininghub.com

Testing

We have conducted two user testing 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 2014
  • Venue: Sterling Engineering Training Hub
  • 1 Academic One Administrator
  • 2 Cerealtech School Of Baking Technology Administrator
  • 1 administrator from CSIS Industries Administrator

View our UT1 documentation here!

User Testing 2

  • Date: 29 January 2015
  • Venue: Sterling Engineering Training Hub
  • 3 Sterling Engineering Training Hub Administrators

View our UT2 documentation here!


Reflections

Team Elements Mid-Terms LearningOutcome1.JPG Team Elements Mid-Terms LearningOutcome2.JPG