HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T2 Team VI Final Wiki"

From IS480
Jump to navigation Jump to search
Line 258: Line 258:
 
<br>
 
<br>
 
<b>Duration:</b> 20 Minutes / User
 
<b>Duration:</b> 20 Minutes / User
<br>
 
<br>
 
<b>Scope of User Testing 2</b>
 
<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>Teacher to mark the attendance of a student using the QR code
 
<li>Teacher to create a feedback for the student</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 view the feedback given to their children by their teachers</li>
 
</ul>
 
<br>
 
 
<b>Participants Demographics:</b>
 
<b>Participants Demographics:</b>
 
<li>10 Actual Parents from the center </li>
 
<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-->
 
<!--/Sub Header-->
Line 342: Line 331:
 
<li>Liked the concept of gift redemptions </li>
 
<li>Liked the concept of gift redemptions </li>
 
<li>Students are excited about QR Codes to sign in </li>
 
<li>Students are excited about QR Codes to sign in </li>
<li>SMS system is useful <li>
+
<li>SMS system is useful
 
<li>Parents liked how they know when their student has attended lessons </li>
 
<li>Parents liked how they know when their student has attended lessons </li>
 
<li>Liked the performance over time analysis chart</li>
 
<li>Liked the performance over time analysis chart</li>
 
+
|</ul>
</ul>
+
<li>Students want get the rewards fast and not inclined with banking system
| <ul>
 
<li>Students want get the rewards fast and not inclined with banking system <li>
 
 
<li>Wanted a payment system</li>
 
<li>Wanted a payment system</li>
 
<li>Dropdown list for students were not user friendly </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>Map analysis should have options for branch manager to choose the filter conditions</li>
 
<li>Heatmap marker not user friendly</li>
 
<li>Heatmap marker not user friendly</li>
 
</ul>
 
 
|-
 
|-
 
|}
 
|}

Revision as of 11:35, 8 April 2016

Team VI Logo.PNG


HOME

 

ABOUT US

 

PROJECT OVERVIEW

 

PROJECT MANAGEMENT

 

DOCUMENTATION

 

Final Wiki

OUR PROJECT PROGRESS

Mid Terms Slides

:here

Deployment Link

: https://is480z-lin9z.rhcloud.com/VI/

Project Highlights

  • Conducted 3 user testings.
  • Renamed Gamification Module to Redemption 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.
  • Site went live and has been deployed to the enrichment center.
  • Our team spent a large amount of time dissecting the database to fit the business rules of the enrichment centre.
  • Our team's AWS account was being compromised and we were charged $3186.86, but we managed to gained approval for our concession.
  • Able to successfully send SMS and email notification to parents upon successfully marking student's attendance.
  • Conducted A/B Testing which gave us the go ahead to choose Version B as our user interface for parents portal.

    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 Actual
    Team VI Project Schedule.png Actualschedule.png

    Project Scope

    For Acceptance For MidTerms
    Team VI Project Scope Before.png Team VI Scope 4.0.png

    The full Change Management Log can be found here.

    Metrics

    Schedule Metric

    Team VI Schedule Metrics Graph.png

    Highlights of Schedule Metrics

    Iteration Planned (Days) Actual (Days) SM Score Action Status
    5
    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
    9
    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
    Team VI Bug Count By Category.png


    Highlights of Bug Metrics

    Iteration Bug Score Number of Issues Summary of Bugs and Issues Action Taken
    3
    30
    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

    Team VI Technical Complexity 1.png
    Team VI Technical Complexity 2.png
    Team VI Technical Complexity 3.png

    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
    Team VI Technical Complexity 4.png
    Team VI Technical Complexity 5.png

    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
    Schedule & Effort Metrics
    Bug Metrics
    Risk Management
    Change Management

    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 Participants Demographics:

  • 10 Actual Parents from the center
  • 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
    Likes Dislikes
    User Interface
    • Color Scheme is good
    • Users found it intuitive and could know exactly where to click
    • Pirate Bank Scheme is nice
    • N/A
    Functionality
    • 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
  • TEAM REFLECTIONS

    Team VI Mid Term Reflections.png