HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 107: Line 107:
 
<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 121: 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 135: 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: 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: WP_BugMetrics.png|800px|center|link=]]

Revision as of 18:47, 18 February 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:

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

Project Risks

View our risk management here!

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

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.

Technical Complexity

PDF Text Recognition

  • NP HS purchases new cases regularly. The format of these cases are unstructured. The cases are cumbersome to set up, hence the team proposed PDF text recognition case setup to ease the setting up of new cases.
  • Populate case setup form according to extracted information from the unstructured pdfs

WP PDFRecognition.png

  • 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

Responsive Web Mobile Application

WP Responsive HowItWorks.png WP Responsive Functions.png

  • This was proposed by the team as a replacement of the iOS application.

Quality of Product

Deliverables

Stage Specification Modules
Project Requirements Story boards Story board

Market Research

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

Schedule Metrics
Bug Metrics
Risk Management
Change Management

Analysis and Design Use Case, ER Diagram, As-Is, To-Be Processes, Sequence Diagrams Use Case, ER Diagram, As-Is, To-Be Processes, Sequence Diagrams, Use Case Description
Design Prototype Persona and Prototype
Testing User Test Plan

Heuristic Evaluation
User Testing 1
User Testing 2

Deployment

Deployed Link: http://hsemr-wpinapp.rhcloud.com/hsemr

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: Ngee Ann Polytechnic, School of Health Sciences
  • 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