Difference between revisions of "IS480 Team wiki: 2016T2 Team VI Final Wiki"
(21 intermediate revisions by 2 users not shown) | |||
Line 36: | Line 36: | ||
|} | |} | ||
− | == | + | <!--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>== | ||
+ | <h3>Deployment Link</h3>: [https://edulearn-exploreandlearn.rhcloud.com/VI here] | ||
+ | <b>Credentials: </b> | ||
+ | <li>Username: branchmanager@email.com</li> | ||
+ | <li>Password: branchmanager</li> | ||
+ | [[Media:Team_VI_Final_Slides.pdf| Final Slides]] | ||
− | < | + | <h3>Project Highlights</h3> |
− | < | + | <li>Conducted 3 user testings. |
− | < | + | <li>Renamed Gamification Module to Treasure Chest Module, which involves a pirate themed banking system for students to redeem points and exchange for gifts. The banking system also serves to inculcate the values of saving among the students. |
+ | <li>Site went live and has been deployed to the enrichment center since 10 Feb. | ||
+ | <li>As of 10 Apr, we achieved 13 active parent users. | ||
− | === | + | ==<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>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> | |
+ | <center>[[File:Team_VI_Iteration_Completion.png|700px]]</center> | ||
+ | <h3>Project Status</h3> | ||
+ | <h3>Project Schedule</h3> | ||
+ | {| 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" | For Mid Terms | ||
+ | |- | ||
+ | | [[File:Team_VI_Project_Schedule.png|550px]] | ||
+ | | [[File:Actualschedule.png|550px]] | ||
+ | |- | ||
+ | | colspan="3" style="border: 1px solid black; text-align: center;" | | ||
+ | [[Image:Team VI Timeline Finals.png|800px|center]] | ||
+ | |} | ||
− | ===Project | + | <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]] | ||
+ | |- | ||
+ | | colspan="3" style="border: 1px solid black; text-align: center;" | | ||
+ | [[Image:Team VI Scope Finals.png|800px|center]] | ||
+ | |} | ||
+ | The full Change Management Log can be found [[IS480_Team_wiki:_2016T2 Team VI Change Management|here]]. | ||
− | == | + | <h3>Metrics</h3> |
+ | <h4>Schedule Metric</h4> | ||
+ | [[Image:Team VI Schedule Metrics Graph.png|600px|center]]<br> | ||
+ | <h4> Highlights of Schedule Metrics </h4> | ||
+ | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:200px" | Iteration | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:600x" | Planned (Days) | ||
+ | ! 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:1000px" | Action | ||
+ | ! 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 | ||
+ | |- | ||
+ | | <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> | ||
+ | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
+ | ! 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:Team Vi Bug Score Per Iteration.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;" | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Iteration | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:100px" | Bug Score | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:100px" | Number of Issues | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:300px" | Summary of Bugs and Issues | ||
+ | ! 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. | ||
+ | |} | ||
+ | |||
+ | <h3>Project Risks</h3> | ||
+ | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
+ | |- | ||
+ | ! width="100px" style="padding: 8px; text-align: center; background:#134E84; color:#ffffff; font-size: 14px;"| Category | ||
+ | ! width="200px" style="padding: 8px; text-align: center; background:#134E84; color:#ffffff; font-size: 14px;"| Description | ||
+ | ! width="80px" style="padding: 8px; text-align: center; background:#134E84; color:#ffffff; font-size: 14px;"| Likelihood | ||
+ | ! width="80px" style="padding: 8px; text-align: center; background:#134E84; color:#ffffff; font-size: 14px;"| Impact | ||
+ | ! 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;"| Mitigated | ||
+ | |- | ||
+ | |style="text-align: center;"| Client Management | ||
+ | |style="text-align: center;"| Changing functional requirements | ||
+ | |style="text-align: center;"| High | ||
+ | |style="text-align: center;"| High | ||
+ | |style="text-align: center;"| Project Manager adjusts 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;"| Mitigated successfully | ||
+ | |- | ||
+ | |style="text-align: center;"| Client Management | ||
+ | |style="text-align: center;"| Hard to get real users to test our application | ||
+ | |style="text-align: center;"| Medium | ||
+ | |style="text-align: center;"| High | ||
+ | |style="text-align: center;"| PM scheduled team members to go down to the centre at different times and conduct testing with the users. | ||
+ | |style="text-align: center;"| Mitigated successfully | ||
+ | |} | ||
− | == | + | <h3>Technical Complexity</h3> |
+ | <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|800px|center]] | ||
+ | |} | ||
+ | We choose 'FullCalendar.io' frontend library for the rendering of our schedules and classes. However, for the need of temporarily rescheduling as our business requirement stated, recursive rendering method in FullCalender.io has limitations in fulfilling that. For example, we need to allow a student who only wishes to temporary reschedule one of his lesson to another time slot, the student will be shifted to another schedule completely if we were to use the recursively rendering method. | ||
− | + | Hence, the team has came up with our own methods of adding a sub layer of relationship into the schedule, which we named it as schedule events that are associated to a particular schedule. These schedule events are recursively created at the moment of the schedule creation and the students are associated to schedule events instead, and each schedule event id will be unique. In this case, the temporary rescheduling of classes for student is thus possible. | |
+ | <br> | ||
+ | <h4>Technical Complexity 2: Geolocation Encoding </h4> | ||
+ | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Diagram | ||
+ | |- | ||
+ | | [[Image:Team VI Technical Complexity Map.png|700px|center]] | ||
+ | |- | ||
+ | |} | ||
− | + | Our client desire a way to easily view the result of the marketing campaigns they have organised. Hence we propose to render each individual sign up on the map to give an intuitive way of understanding the coverage on each campaign over the island. Moreover, calculate the signup rate of all the students against the target number which is to show the effectiveness of each campaign organised | |
+ | We decide to use google map API for the geolocation encoding as well as maplace.js to embed an interactive google map view in our map. We also learn to use the d3.js in creating a graph that will change along with the map in rendering of the data points of student sign up for each campaign. This require a proper setting up of an google application on google developer console as well as prepare the data into suitable format for a successful display on the web page. | ||
− | + | <h3>Deliverables</h3> | |
+ | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Type | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Description | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Documentation | ||
+ | |- | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Requirement Gathering | ||
+ | | 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 | ||
+ | | Minutes, Metrics, Risks, Change | ||
+ | | | ||
+ | [[IS480_Team_wiki:_ 2016T2 Team VI Meeting Minutes|Meeting Minutes]] <br> | ||
+ | [[IS480_Team_wiki:_2016T2 Team VI Metrics|Schedule & Effort Metrics]]<br> | ||
+ | [[IS480_Team_wiki:_2016T2 Team VI Bug Metrics|Bug Metrics]]<br> | ||
+ | [[IS480_Team_wiki:_2016T2 Team VI Risk Assessment|Risk Management]]<br> | ||
+ | [[IS480_Team_wiki:_2016T2 Team VI Change Management|Change Management]] | ||
+ | |- | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Analysis and Design | ||
+ | | 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 | ||
+ | | 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 | ||
+ | | User Test Plan | ||
+ | | [https://wiki.smu.edu.sg/is480/img_auth.php/5/5e/Test_Plan.docx Test Plan] | ||
+ | |- | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Handover | ||
+ | | User Guide | ||
+ | | [[Media:Team VI User Guide.pdf| User Guide]] | ||
+ | |- | ||
+ | |} | ||
− | === | + | ==<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 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> | ||
+ | <ul> | ||
+ | <li>Gather feedback from students in SMU</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> | ||
+ | <li>Testing of functionality</li> | ||
+ | </ul> | ||
+ | <b>Users:</b> 15 SMU Students, 4 IT Consultant, 1 Digital Marketing Consultant | ||
+ | <br> | ||
+ | <b>Venue:</b> SMU , FYP Labs, Starbucks at Parkway | ||
+ | <br> | ||
+ | <b>Date: </b> 4,5,6 Feb 2016 | ||
+ | <br> | ||
+ | <b>Duration:</b> 20 Minutes / User | ||
+ | <b>Participants Demographics:</b> | ||
+ | <li>10 Actual Parents from the center </li> | ||
− | + | Find out more about our User Testing 2 [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2016T2_Team_VI_User_Testing here] | |
+ | <!--/Sub Header--> | ||
+ | <br> | ||
+ | <h3>User Testing 3</h3> | ||
+ | <font size="3"><b>Objective:</b></font> | ||
+ | <ul> | ||
+ | <li>Gather feedback from live users in Explore & Learn </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> | ||
+ | <li>Testing of functionality</li> | ||
+ | </ul> | ||
− | ===Testing:=== | + | <b>Users:</b> 1 Branch Manager, 2 Teachers, 15 Actual Students, 10 Parents |
+ | <br> | ||
+ | <b>Venue:</b> Explore & Learn Center | ||
+ | <br> | ||
+ | <b>Date: </b> 6,7 April 2016 | ||
+ | <br> | ||
+ | <b>Duration:</b> 20 Minutes / User | ||
+ | <br> | ||
+ | <br> | ||
+ | <font size="3"><b>Scope of User Testing 3</b></font> | ||
+ | <ul> | ||
+ | <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 marketing campaign</li> | ||
+ | <li>Branch Manager to view analysis of student </li> | ||
+ | <li>Student To redeem a gift from the redemption portal</li> | ||
+ | <li>Teacher to mark the attendance of a student using the QR code | ||
+ | <li>Teacher to create a feedback for the student | ||
+ | <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 view the feedback given to their children by their teachers</li> | ||
+ | <li>Parents to view the performance over time analysis of their children results</li> | ||
+ | </ul> | ||
+ | <br> | ||
+ | <font size="3"><b>User Testing 3 Focus Group: </b></font> | ||
+ | <ul> | ||
+ | <li>Branch Manager</li> | ||
+ | <li>Parent</li> | ||
+ | <li>Teacher</li> | ||
+ | <li>Students</li> | ||
+ | </ul> | ||
+ | <br> | ||
+ | <font size="3"><b>User Testing 3 Results: </b></font> | ||
+ | <ul> | ||
+ | {| class="wikitable" style="background-color:#FFFFFF;" | ||
+ | |- | ||
+ | ! style="color:white; background-color:#134E84;" | | ||
+ | ! style="color:white; background-color:#134E84;" | Likes | ||
+ | ! style="color:white; background-color:#134E84;" | Dislikes | ||
+ | |- | ||
+ | | <font size="3"><center><b>User Interface</b></center></font> | ||
+ | | <ul | ||
+ | ><li>Color Scheme is good </li> | ||
+ | <li>Users found it intuitive and could know exactly where to click</li> | ||
+ | <li>Pirate Bank Scheme is nice </li> | ||
+ | </ul> | ||
− | = | + | | <ul> |
+ | <li> N/A </li> | ||
+ | </ul> | ||
+ | |- | ||
+ | | <font size="3"><center><b>Functionality</b></center></font> | ||
+ | | <ul> | ||
+ | <li>Liked the concept of gift redemptions </li> | ||
+ | <li>Students are excited about QR Codes to sign in </li> | ||
+ | <li>SMS system is useful | ||
+ | <li>Parents liked how they know when their student has attended lessons </li> | ||
+ | <li>Liked the performance over time analysis chart</li> | ||
+ | |</ul> | ||
+ | <li>Students want get the rewards fast and not inclined with banking system | ||
+ | <li>Wanted a payment system</li> | ||
+ | <li>Dropdown list for students were not user friendly </li> | ||
+ | <li>Map analysis should have options for branch manager to choose the filter conditions</li> | ||
+ | <li>Heatmap marker not user friendly</li> | ||
+ | |} | ||
+ | | <font size="3"><center><b>Changes Made for UT3</b></center></font> | ||
− | === | + | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" |
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Heatmap Function | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Dropdown list function | ||
+ | |- | ||
+ | | [[Image:Screen_Shot_2016-04-09_at_12.29.28_pm.png|500px|center]] | ||
+ | | [[Image:Screen_Shot_2016-04-09_at_12.29.36_pm.png|500px|center]] | ||
+ | |- | ||
+ | | Insert display markers for heatmap | ||
+ | | created auto search function for all existing dropdown lists | ||
+ | |} | ||
+ | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Scheduling Colors | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Select Pop Up | ||
+ | |- | ||
+ | | [[Image:Screen_Shot_2016-04-09_at_12.43.41_pm.png|500px|center]] | ||
+ | | [[Image:Screen_Shot_2016-04-09_at_12.47.18_pm.png|500px|center]] | ||
+ | |- | ||
+ | | Different Colors represents different classrooms for easy identification | ||
+ | | Created a onclick function which shows 'selected' when a user selects a schedule | ||
+ | |} | ||
− | + | Find out more about our User Testing 3 [https://wiki.smu.edu.sg/is480/File%3ATest_Plan.docx User Testing 3] | |
+ | ==<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 Final LO.png|650px|center]] | |
− | + | [[Image:Team VI Final LO 2.png|650px|center]] |
Latest revision as of 09:36, 20 April 2016
HOME |
Final Wiki
|
Contents
OUR PROJECT PROGRESS
Deployment Link
: here
Credentials:
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
Project Status
Project Schedule
Planned | For Mid Terms | |
---|---|---|
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 | Mitigated |
---|---|---|---|---|---|
Client Management | Changing functional requirements | High | High | Project Manager adjusts 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. | Mitigated successfully |
Client Management | Hard to get real users to test our application | Medium | High | PM scheduled team members to go down to the centre at different times and conduct testing with the users. | Mitigated successfully |
Technical Complexity
Technical Complexity 1: Rescheduling
We choose 'FullCalendar.io' frontend library for the rendering of our schedules and classes. However, for the need of temporarily rescheduling as our business requirement stated, recursive rendering method in FullCalender.io has limitations in fulfilling that. For example, we need to allow a student who only wishes to temporary reschedule one of his lesson to another time slot, the student will be shifted to another schedule completely if we were to use the recursively rendering method.
Hence, the team has came up with our own methods of adding a sub layer of relationship into the schedule, which we named it as schedule events that are associated to a particular schedule. These schedule events are recursively created at the moment of the schedule creation and the students are associated to schedule events instead, and each schedule event id will be unique. In this case, the temporary rescheduling of classes for student is thus possible.
Technical Complexity 2: Geolocation Encoding
Diagram |
---|
Our client desire a way to easily view the result of the marketing campaigns they have organised. Hence we propose to render each individual sign up on the map to give an intuitive way of understanding the coverage on each campaign over the island. Moreover, calculate the signup rate of all the students against the target number which is to show the effectiveness of each campaign organised
We decide to use google map API for the geolocation encoding as well as maplace.js to embed an interactive google map view in our map. We also learn to use the d3.js in creating a graph that will change along with the map in rendering of the data points of student sign up for each campaign. This require a proper setting up of an google application on google developer console as well as prepare the data into suitable format for a successful display on the web page.
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 |
Handover | User Guide | User Guide |
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
Participants Demographics:
Find out more about our User Testing 2 here
User Testing 3
Objective:
- Gather feedback from live users in Explore & Learn
- 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: 1 Branch Manager, 2 Teachers, 15 Actual Students, 10 Parents
Venue: Explore & Learn Center
Date: 6,7 April 2016
Duration: 20 Minutes / User
Scope of User Testing 3
- Branch Manager to successfully create a Parent and Student.
- Branch Manager to create a schedule, and assign the student into a class
- Branch Manager to create a marketing campaign
- Branch Manager to view analysis of student
- Student To redeem a gift from the redemption portal
- 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/li>
- 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
- Parents to view the performance over time analysis of their children results
User Testing 3 Focus Group:
- Branch Manager
- Parent
- Teacher
- Students
User Testing 3 Results:
- Color Scheme is good
- Users found it intuitive and could know exactly where to click
- Pirate Bank Scheme is nice
- N/A
- Liked the concept of gift redemptions
- Students are excited about QR Codes to sign in
- SMS system is useful
- Parents liked how they know when their student has attended lessons
- Liked the performance over time analysis chart
- Students want get the rewards fast and not inclined with banking system
- Wanted a payment system
- Dropdown list for students were not user friendly
- Map analysis should have options for branch manager to choose the filter conditions
- Heatmap marker not user friendly
Likes | Dislikes | |
---|---|---|
|
Heatmap Function | Dropdown list function |
---|---|
Insert display markers for heatmap | created auto search function for all existing dropdown lists |
Scheduling Colors | Select Pop Up |
---|---|
Different Colors represents different classrooms for easy identification | Created a onclick function which shows 'selected' when a user selects a schedule |
Find out more about our User Testing 3 User Testing 3