Difference between revisions of "IS480 Team wiki: 2016T2 Team VI Midterm Wiki"
(33 intermediate revisions by 2 users not shown) | |||
Line 33: | Line 33: | ||
| style="vertical-align:top;width:20%;" | <div style="padding: 3px; text-align:center; line-height: wrap_content; font-size:15px; border-bottom:1px solid #2554C7; font-family:tahoma">[[IS480_Team_wiki:_2016T2_Team_VI_Midterm_Wiki| <b>Midterm Wiki</b>]] | | style="vertical-align:top;width:20%;" | <div style="padding: 3px; text-align:center; line-height: wrap_content; font-size:15px; border-bottom:1px solid #2554C7; font-family:tahoma">[[IS480_Team_wiki:_2016T2_Team_VI_Midterm_Wiki| <b>Midterm Wiki</b>]] | ||
− | | style="vertical-align:top;width:20%;" | <div style="padding: 3px; text-align:center; line-height: wrap_content; font-size:15px; border-bottom:1px solid #2554C7; font-family:tahoma"><b>Final Wiki</b> | + | | style="vertical-align:top;width:20%;" | <div style="padding: 3px; text-align:center; line-height: wrap_content; font-size:15px; border-bottom:1px solid #2554C7; font-family:tahoma">[[IS480_Team_wiki:_2016T2_Team_VI_Final_Wiki | <b>Final Wiki</b>]] |
+ | |||
|} | |} | ||
− | |||
<!--Content Start--> | <!--Content Start--> | ||
==<div style="background: #134E84; padding: 15px; font-weight: bold;text-indent: 15px;letter-spacing:-0.08em"><font color=#fbfcfd face="Helvetica">OUR PROJECT PROGRESS</font></div>== | ==<div style="background: #134E84; padding: 15px; font-weight: bold;text-indent: 15px;letter-spacing:-0.08em"><font color=#fbfcfd face="Helvetica">OUR PROJECT PROGRESS</font></div>== | ||
+ | <h3>Mid Terms Slides</h3>:[https://drive.google.com/a/smu.edu.sg/folderview?id=0B5iOEjHpTuodeExBTDZJcEhUMFE&usp=sharing here] | ||
+ | <h3>Deployment Link</h3>: https://is480z-lin9z.rhcloud.com/VI/ | ||
− | + | <h3>Project Highlights</h3> | |
− | + | <li>Our team spent a large amount of time dissecting the database to fit the business rules of the enrichment centre. | |
+ | <li>Site went live and has been deployed to the enrichment center. | ||
+ | <li>Our team's AWS account was being compromised and we were charged $3186.86, but we managed to gained approval for our concession. | ||
+ | <li>Able to successfully send SMS and email notification to parents upon successfully marking student's attendance. | ||
+ | <li>Conducted A/B Testing which gave us the go ahead to choose Version B as our user interface for parents portal. | ||
+ | <li>Conducted 2 user testings. | ||
+ | <li>Embarked on Gamification and Analytics for the enrichment center. | ||
− | < | + | ==<div style="background: #134E84; padding: 15px; font-weight: bold;text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#fbfcfd face="Helvetica">OUR PROJECT MANAGMENT</font></div>== |
− | |||
− | <h3> | + | <h3>About our Project</h3> |
+ | Our team aims to provide a web-based student monitoring system and business analysis tool for an enrichment centre, Explore and Learn Pte Ltd. Our project also aims to engage the students through gamification and encourage learning. | ||
− | + | <h3>Summary of Project Progress</h3> | |
+ | Our project iteration has 15 iterations. As at 18 February 2015, we are currently in <b>Iteration 11</b> of the project. | ||
+ | We have completed <b>70%</b> of our functionalities. | ||
− | <h3>Project | + | <h3>Project Status</h3> |
+ | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Task/Function/Feature | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Status | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Confidence Level (0-1) | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Comment | ||
+ | |- | ||
+ | | Deploy onto Digital Ocean | ||
+ | | Our application is currenly deployed on OpenShift and our team is exploring on how to deploy the application onto the DigitalOcean Server after the MId Terms. | ||
+ | | 0.9 | ||
+ | | Sponsor requested for the team to deploy the application to Digital Ocean instead of the original Amazon Web Service (AWS). This is because our sponsor has the relevant experience and it would facilitate the process of future updates of the system. | ||
+ | |- | ||
+ | |} | ||
+ | <h3>Project Schedule</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: #134E84; color: white; font-weight: bold; width:50px" | Planned | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Planned | ||
! style="background: #134E84; color: white; font-weight: bold; width:50px" | Actual | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Actual | ||
|- | |- | ||
− | | [[File:Team_VI_Project_Schedule.png| | + | | [[File:Team_VI_Project_Schedule.png|550px]] |
− | | [[File:Actualschedule.png| | + | | [[File:Actualschedule.png|550px]] |
+ | |- | ||
+ | |} | ||
+ | |||
+ | <h3>Project Scope</h3> | ||
+ | {| class="wikitable" style="margin: auto;width:50%; text-align:center; background: white;" | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | For Acceptance | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | For MidTerms | ||
+ | |- | ||
+ | | [[File:Team VI Project Scope Before.png|550px]] | ||
+ | | [[File:Team VI Scope 4.0.png|550px]] | ||
|- | |- | ||
|} | |} | ||
Line 63: | Line 96: | ||
The full Change Management Log can be found [[IS480_Team_wiki:_2016T2 Team VI Change Management|here]]. | The full Change Management Log can be found [[IS480_Team_wiki:_2016T2 Team VI Change Management|here]]. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<h3>Metrics</h3> | <h3>Metrics</h3> | ||
<h4>Schedule Metric</h4> | <h4>Schedule Metric</h4> | ||
Line 79: | Line 101: | ||
<h4> Highlights of Schedule Metrics </h4> | <h4> Highlights of Schedule Metrics </h4> | ||
{| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
− | ! style="background: #134E84; color: white; font-weight: bold; width: | + | ! style="background: #134E84; color: white; font-weight: bold; width:200px" | Iteration |
− | ! style="background: #134E84; color: white; font-weight: bold; width: | + | ! style="background: #134E84; color: white; font-weight: bold; width:600x" | Planned (Days) |
− | ! style="background: #134E84; color: white; font-weight: bold; width: | + | ! style="background: #134E84; color: white; font-weight: bold; width:600px" | Actual (Days) |
! style="background: #134E84; color: white; font-weight: bold; width:500px" | SM Score | ! style="background: #134E84; color: white; font-weight: bold; width:500px" | SM Score | ||
− | ! style="background: #134E84; color: white; font-weight: bold; width: | + | ! style="background: #134E84; color: white; font-weight: bold; width:1000px" | Action |
! style="background: #134E84; color: white; font-weight: bold; width:500px" | Status | ! style="background: #134E84; color: white; font-weight: bold; width:500px" | Status | ||
|- | |- | ||
− | | | + | | <center>5</center> |
− | | | + | | 14 |
− | | | + | | 18 |
− | | % | + | | 78% |
− | | | + | | Underestimated time required, PM to re-estimate tasks for future iterations. Delayed due to bugs found. Team was unfamiliar with QR code scanning and email notification. Reduced 4 Days of Finals Break |
| Completed | | Completed | ||
|- | |- | ||
+ | | <center>9</center> | ||
+ | | 14 | ||
+ | | 20 | ||
+ | | 70% | ||
+ | | Underestimated time required, PM to re-estimate tasks for future iterations. Delayed due to the database changes required to mimic the business rules, wherey timeslot is not course unique and a teacher is able to teach more than 1 courses at the same time. Use 6 buffer days. | ||
+ | | Completed | ||
|} | |} | ||
<h4>Bug Metrics</h4> | <h4>Bug Metrics</h4> | ||
− | [[Image:Screen_Shot_2016-02-14_at_2.09.58_pm.png| | + | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" |
− | [[Image: | + | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Bug Metrics |
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Bug Count by Category | ||
+ | |- | ||
+ | | [[Image:Screen_Shot_2016-02-14_at_2.09.58_pm.png|550px|center]] | ||
+ | | [[Image:Team VI Bug Count By Category.png|550px|center]] | ||
+ | |- | ||
+ | |} | ||
+ | <br> | ||
+ | <h4> Highlights of Bug Metrics </h4> | ||
{| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
! style="background: #134E84; color: white; font-weight: bold; width:50px" | Iteration | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Iteration | ||
Line 105: | Line 141: | ||
! style="background: #134E84; color: white; font-weight: bold; width:200px" | Action Taken | ! style="background: #134E84; color: white; font-weight: bold; width:200px" | Action Taken | ||
|- | |- | ||
+ | | <center>3</center> | ||
+ | | <center>30</center> | ||
+ | | 20 Low Impact Bugs & 2 High Impact Bugs | ||
+ | | Most bugs are due to validation errors. | ||
+ | | Developers stopped all current development and resolve the bugs. | ||
|} | |} | ||
Line 116: | Line 157: | ||
! width="500px" style="padding: 8px; text-align: center; background:#134E84; color:#ffffff; font-size: 14px;"| Mitigation | ! width="500px" style="padding: 8px; text-align: center; background:#134E84; color:#ffffff; font-size: 14px;"| Mitigation | ||
|- | |- | ||
− | |style="text-align: center;"| Project | + | |style="text-align: center;"| Client Management |
− | |style="text-align: center;"| | + | |style="text-align: center;"| Changing functional requirements |
+ | |style="text-align: center;"| High | ||
+ | |style="text-align: center;"| High | ||
+ | |style="text-align: center;"| Project Manager adjust schedule according to the client's requiremtns and apply change management controls. Developers to update the PM if the changes in requirements affact the project schedule. | ||
+ | |- | ||
+ | |style="text-align: center;"| Technology | ||
+ | |style="text-align: center;"| Lack of experience in new technologies | ||
|style="text-align: center;"| High | |style="text-align: center;"| High | ||
|style="text-align: center;"| High | |style="text-align: center;"| High | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"| Research on the technologies used and designate members to share the knowledge and risks of using the technologies. |
|- | |- | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"| Project Management |
− | |style="text-align: center;"| | + | |style="text-align: center;"| Hard to estimate the amount of time required for tasks |
|style="text-align: center;"| Medium | |style="text-align: center;"| Medium | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"| Medium |
− | |style="text-align: center;"| | + | |style="text-align: center;"| Project Manager and developers to discuss the amount of time required before each iteration. Project Manager to constantly review and re-estimate the time required to complete each functionality. |
|} | |} | ||
Line 132: | Line 179: | ||
<h3>Technical Complexity</h3> | <h3>Technical Complexity</h3> | ||
<h4>Technical Complexity 1: Rescheduling </h4> | <h4>Technical Complexity 1: Rescheduling </h4> | ||
+ | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
+ | |- | ||
+ | | [[Image:Team VI Technical Complexity 1.png|550px|center]] | ||
+ | | [[Image:Team VI Technical Complexity 2.png|550px|center]] | ||
+ | |- | ||
+ | | colspan="3" style="border: 1px solid black; text-align: center;" | | ||
+ | [[Image:Team VI Technical Complexity 3.png|550px|center]] | ||
+ | |} | ||
+ | |||
+ | Currently, we are using the a frontend library called <b>FullCalendar.io</b> to display our schedules and classes. FullCalender.io has many API methods, but we are focusing on the recursive rendering method. | ||
+ | Due to the business requirement for temporarily rescheduling, the recursive rerendering method in FullCalender.io cannot be used to fulfill the requirement. If a student wishes to temporary reschedule to another class, the student will be shifted to another date and the student will be rendered recursively on the changed date range instead due to its repeated schedule ID. | ||
+ | |||
+ | The team has came up with our own methods of generating schedule events that is linked to a particular schedule. These schedule events will instead contain the students that belong to this class, and each schedule event id will be unique. In this case, the student can then make a temporary reschedule of classes. | ||
+ | |||
+ | <br> | ||
+ | <h4>Technical Complexity 2: Database Structure </h4> | ||
+ | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Before | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | After | ||
+ | |- | ||
+ | | [[Image:Team VI Technical Complexity 4.png|550px|center]] | ||
+ | | [[Image:Team VI Technical Complexity 5.png|550px|center]] | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | In order to cater to temporary rescheduling, the database has to be design such in a way that stores each lesson as a unique event together with the attendances. It has differed a lot to our initial understanding and design to the database. Hence we have to rework on the entire data structure and auto create multiple schedule events in the backend according to the schedule. Furthermore, we also learnt that the tuition center has their unique set of course workbook for their students. It requires the system to keep track of the performance of each student on each work book. We used to link the result with the schedule as we define our schedule to be a joint table of teacher, student and course. However, since we made the change to allowed temporary reschedule, the result will have no correct table to join. Hence we purposely create a TeacherStudentCourse (TSC) table for the reporting module. We also included two attributes in the TSC table to keep track of the student current progress level for fast retrieval. And we also realize this data structure has the capability of tracking the results for multiple schedules for the same teacher, student and course. | ||
<h3>Deliverables</h3> | <h3>Deliverables</h3> | ||
Line 142: | Line 215: | ||
! style="background: #134E84; color: white; font-weight: bold; width:50px" | Requirement Gathering | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Requirement Gathering | ||
| Market Research | | Market Research | ||
− | | [ | + | | [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2016T2_Team_VI_Marketplace_Research Market Research] |
|- | |- | ||
! style="background: #134E84; color: white; font-weight: bold; width:50px" | Project Management | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Project Management | ||
Line 154: | Line 227: | ||
|- | |- | ||
! style="background: #134E84; color: white; font-weight: bold; width:50px" | Analysis and Design | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Analysis and Design | ||
− | | Use Case, ER Diagram | + | | Use Case, ER Diagram |
| [[IS480_Team_wiki:_2016T2 Team VI Documentation|Use Case & ER Diagram]] | | [[IS480_Team_wiki:_2016T2 Team VI Documentation|Use Case & ER Diagram]] | ||
|- | |- | ||
! style="background: #134E84; color: white; font-weight: bold; width:50px" | Analysis and Design | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Analysis and Design | ||
− | | Technology and Tools Used | + | | Architectural Diagram, Technology and Tools Used |
| [[IS480_Team_wiki:_2016T2 Team VI Technologies|Architectural Diagram & Technology and Tools Used]] | | [[IS480_Team_wiki:_2016T2 Team VI Technologies|Architectural Diagram & Technology and Tools Used]] | ||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
! style="background: #134E84; color: white; font-weight: bold; width:50px" | Testing | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Testing | ||
| User Test Plan | | User Test Plan | ||
− | | | + | | [https://wiki.smu.edu.sg/is480/img_auth.php/2/2f/UAT2TestPlan.pdf Test Plan] |
|- | |- | ||
|} | |} | ||
==<div style="background: #134E84; padding: 15px; font-weight: bold;text-indent: 15px;letter-spacing:-0.08em"><font color=#fbfcfd face="Helvetica">OUR QUALITY ASSURANCE</font></div>== | ==<div style="background: #134E84; padding: 15px; font-weight: bold;text-indent: 15px;letter-spacing:-0.08em"><font color=#fbfcfd face="Helvetica">OUR QUALITY ASSURANCE</font></div>== | ||
− | <h3>User Testing</h3> | + | <h3>User Testing 1</h3> |
+ | <b>Objective:</b> | ||
+ | <ul> | ||
+ | <li>Gather feedback regarding the user interface from existing users</li> | ||
+ | <li>Identify usability issues based on observations</li> | ||
+ | <li>Improve web application based on user testing results</li> | ||
+ | <li>Identify potential bugs that was not found during testing phase</li> | ||
+ | </ul> | ||
+ | |||
+ | <b>Users:</b> Wong Bing Xiang (Sponsor), Teacher | ||
+ | <br> | ||
+ | <b>Venue:</b> Upper Thomson | ||
+ | <br> | ||
+ | <b>Date: </b> 26/10/2015 | ||
+ | <br> | ||
+ | <b>Duration:</b> 25 Minutes / User | ||
+ | <br> | ||
+ | |||
+ | Find out more about our User Testing 1 [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2016T2_Team_VI_User_Testing here] | ||
+ | |||
+ | <h3>User Testing 2</h3> | ||
<b>Objective:</b> | <b>Objective:</b> | ||
<ul> | <ul> | ||
Line 181: | Line 270: | ||
<li>Testing of functionality</li> | <li>Testing of functionality</li> | ||
</ul> | </ul> | ||
− | |||
<b>Users:</b> 15 SMU Students, 4 IT Consultant, 1 Digital Marketing Consultant | <b>Users:</b> 15 SMU Students, 4 IT Consultant, 1 Digital Marketing Consultant | ||
<br> | <br> | ||
Line 191: | Line 279: | ||
<br> | <br> | ||
<br> | <br> | ||
− | + | <b>Scope of User Testing 2</b> | |
<ul> | <ul> | ||
<li>Branch Manager to successfully create a Parent and Student.</li> | <li>Branch Manager to successfully create a Parent and Student.</li> | ||
<li>Branch Manager to create a schedule, and assign the student into a class</li> | <li>Branch Manager to create a schedule, and assign the student into a class</li> | ||
<li>Teacher to mark the attendance of a student using the QR code | <li>Teacher to mark the attendance of a student using the QR code | ||
− | <li>Teacher to create a feedback for the student | + | <li>Teacher to create a feedback for the student</li> |
− | <li>Parents to edit their own and child's information/li> | + | <li>Parents to edit their own and child's information</li> |
<li>Parents to successfully receive an SMS, Email when their children has attended lesson</li> | <li>Parents to successfully receive an SMS, Email when their children has attended lesson</li> | ||
<li>Parents to view the feedback given to their children by their teachers</li> | <li>Parents to view the feedback given to their children by their teachers</li> | ||
Line 208: | Line 296: | ||
<li>Teacher</li> | <li>Teacher</li> | ||
</ul> | </ul> | ||
− | < | + | <h3>User Testing 2 Results</h3> |
− | |||
{| class="wikitable" style="background-color:#FFFFFF;" | {| class="wikitable" style="background-color:#FFFFFF;" | ||
|- | |- | ||
Line 246: | Line 333: | ||
<!--/Sub Header--> | <!--/Sub Header--> | ||
− | < | + | <h3>AB Testing</h3> |
<b>Objective:</b> | <b>Objective:</b> | ||
<ul> | <ul> | ||
Line 252: | Line 339: | ||
<li>Users to perform the task of viewing the students feedback </li> | <li>Users to perform the task of viewing the students feedback </li> | ||
<li>Improve aesthetics of web application</li> | <li>Improve aesthetics of web application</li> | ||
− | + | ||
<b>Participants Demographics:</b> | <b>Participants Demographics:</b> | ||
− | + | <li>10 Actual Parents from the center </li> | |
− | |||
<b>Experiment Design :</b> | <b>Experiment Design :</b> | ||
Line 271: | Line 357: | ||
Results For AB Testing can available at: | Results For AB Testing can available at: | ||
[https://wiki.smu.edu.sg/is480/img_auth.php/f/f3/AB_Testing_Analysis.xlsx AB Testing Results] | [https://wiki.smu.edu.sg/is480/img_auth.php/f/f3/AB_Testing_Analysis.xlsx AB Testing Results] | ||
+ | |||
+ | ==<div style="background: #134E84; padding: 15px; font-weight: bold;text-indent: 15px;letter-spacing:-0.08em"><font color=#fbfcfd face="Helvetica">TEAM REFLECTIONS</font></div>== | ||
+ | |||
+ | [[Image:Team VI Mid Term Reflections.png|650px|center]] |
Latest revision as of 18:35, 4 April 2016
HOME |
Contents
OUR PROJECT PROGRESS
Mid Terms Slides
:here
Deployment Link
: https://is480z-lin9z.rhcloud.com/VI/
Project Highlights
OUR PROJECT MANAGMENT
About our Project
Our team aims to provide a web-based student monitoring system and business analysis tool for an enrichment centre, Explore and Learn Pte Ltd. Our project also aims to engage the students through gamification and encourage learning.
Summary of Project Progress
Our project iteration has 15 iterations. As at 18 February 2015, we are currently in Iteration 11 of the project. We have completed 70% of our functionalities.
Project Status
Task/Function/Feature | Status | Confidence Level (0-1) | Comment |
---|---|---|---|
Deploy onto Digital Ocean | Our application is currenly deployed on OpenShift and our team is exploring on how to deploy the application onto the DigitalOcean Server after the MId Terms. | 0.9 | Sponsor requested for the team to deploy the application to Digital Ocean instead of the original Amazon Web Service (AWS). This is because our sponsor has the relevant experience and it would facilitate the process of future updates of the system. |
Project Schedule
Planned | Actual |
---|---|
Project Scope
For Acceptance | For MidTerms |
---|---|
The full Change Management Log can be found here.
Metrics
Schedule Metric
Highlights of Schedule Metrics
Iteration | Planned (Days) | Actual (Days) | SM Score | Action | Status |
---|---|---|---|---|---|
14 | 18 | 78% | Underestimated time required, PM to re-estimate tasks for future iterations. Delayed due to bugs found. Team was unfamiliar with QR code scanning and email notification. Reduced 4 Days of Finals Break | Completed | |
14 | 20 | 70% | Underestimated time required, PM to re-estimate tasks for future iterations. Delayed due to the database changes required to mimic the business rules, wherey timeslot is not course unique and a teacher is able to teach more than 1 courses at the same time. Use 6 buffer days. | Completed |
Bug Metrics
Bug Metrics | Bug Count by Category |
---|---|
Highlights of Bug Metrics
Iteration | Bug Score | Number of Issues | Summary of Bugs and Issues | Action Taken |
---|---|---|---|---|
20 Low Impact Bugs & 2 High Impact Bugs | Most bugs are due to validation errors. | Developers stopped all current development and resolve the bugs. |
Project Risks
Category | Description | Likelihood | Impact | Mitigation |
---|---|---|---|---|
Client Management | Changing functional requirements | High | High | Project Manager adjust schedule according to the client's requiremtns and apply change management controls. Developers to update the PM if the changes in requirements affact the project schedule. |
Technology | Lack of experience in new technologies | High | High | Research on the technologies used and designate members to share the knowledge and risks of using the technologies. |
Project Management | Hard to estimate the amount of time required for tasks | Medium | Medium | Project Manager and developers to discuss the amount of time required before each iteration. Project Manager to constantly review and re-estimate the time required to complete each functionality. |
The risks above have been managed and mitigated.
Technical Complexity
Technical Complexity 1: Rescheduling
Currently, we are using the a frontend library called FullCalendar.io to display our schedules and classes. FullCalender.io has many API methods, but we are focusing on the recursive rendering method. Due to the business requirement for temporarily rescheduling, the recursive rerendering method in FullCalender.io cannot be used to fulfill the requirement. If a student wishes to temporary reschedule to another class, the student will be shifted to another date and the student will be rendered recursively on the changed date range instead due to its repeated schedule ID.
The team has came up with our own methods of generating schedule events that is linked to a particular schedule. These schedule events will instead contain the students that belong to this class, and each schedule event id will be unique. In this case, the student can then make a temporary reschedule of classes.
Technical Complexity 2: Database Structure
Before | After |
---|---|
In order to cater to temporary rescheduling, the database has to be design such in a way that stores each lesson as a unique event together with the attendances. It has differed a lot to our initial understanding and design to the database. Hence we have to rework on the entire data structure and auto create multiple schedule events in the backend according to the schedule. Furthermore, we also learnt that the tuition center has their unique set of course workbook for their students. It requires the system to keep track of the performance of each student on each work book. We used to link the result with the schedule as we define our schedule to be a joint table of teacher, student and course. However, since we made the change to allowed temporary reschedule, the result will have no correct table to join. Hence we purposely create a TeacherStudentCourse (TSC) table for the reporting module. We also included two attributes in the TSC table to keep track of the student current progress level for fast retrieval. And we also realize this data structure has the capability of tracking the results for multiple schedules for the same teacher, student and course.
Deliverables
Type | Description | Documentation |
---|---|---|
Requirement Gathering | Market Research | Market Research |
Project Management | Minutes, Metrics, Risks, Change |
Meeting Minutes |
Analysis and Design | Use Case, ER Diagram | Use Case & ER Diagram |
Analysis and Design | Architectural Diagram, Technology and Tools Used | Architectural Diagram & Technology and Tools Used |
Testing | User Test Plan | Test Plan |
OUR QUALITY ASSURANCE
User Testing 1
Objective:
- Gather feedback regarding the user interface from existing users
- Identify usability issues based on observations
- Improve web application based on user testing results
- Identify potential bugs that was not found during testing phase
Users: Wong Bing Xiang (Sponsor), Teacher
Venue: Upper Thomson
Date: 26/10/2015
Duration: 25 Minutes / User
Find out more about our User Testing 1 here
User Testing 2
Objective:
- Gather feedback from students in SMU
- Identify usability issues based on observations
- Improve web application based on user testing results
- Identify potential bugs that was not found during testing phase
- Testing of functionality
Users: 15 SMU Students, 4 IT Consultant, 1 Digital Marketing Consultant
Venue: SMU , FYP Labs, Starbucks at Parkway
Date: 4,5,6 Feb 2016
Duration: 20 Minutes / User
Scope of User Testing 2
- Branch Manager to successfully create a Parent and Student.
- Branch Manager to create a schedule, and assign the student into a class
- Teacher to mark the attendance of a student using the QR code
- Teacher to create a feedback for the student
- Parents to edit their own and child's information
- Parents to successfully receive an SMS, Email when their children has attended lesson
- Parents to view the feedback given to their children by their teachers
User Testing 2 Focus Group:
- Branch Manager
- Parent
- Teacher
User Testing 2 Results
Likes | Dislikes | |
---|---|---|
|
| |
|
|
AB Testing
Objective:
- Compare two version of the web portal and identify the preferred version
- Users to perform the task of viewing the students feedback
- Improve aesthetics of web application Participants Demographics:
- 10 Actual Parents from the center Experiment Design :
Version A | Version B |
---|---|
Feedback is appended at the bottom after selection of each feedback. Users have to scroll up and down to view the feedback. | Feedback is displayed in tabs. Can only view one feedback at a time |
Results For AB Testing can available at: AB Testing Results