IS480 Team wiki: 2016T2 Team VI Midterm Wiki
Revision as of 14:30, 18 February 2016 by Huiqi.ong.2013 (talk | contribs)
HOME |
Final Wiki
|
OUR PROJECT PROGRESS
Mid Terms Slides:
Team VI Mid Term Slides
Deployment Link:
Summary of Project
Our project iteration has 15 iterations. As at 18 February 2015, we are currently in 11th iteration of the project.
Our Development Progress
OUR PROJECT MANAGMENT
Project Scope
Planned | Actual |
---|---|
The full Change Management Log can be found here.
Project Schedule
Project
Metrics
Schedule Metric
Highlights of Schedule Metrics
Iteration | Planned (Days) | Actual (Days) | SM Score | Action | Status |
---|---|---|---|---|---|
iteration | planned | actual | % | description | Completed |
Bug Metrics
Iteration | Bug Score | Number of Issues | Summary of Bugs and Issues | Action Taken |
---|
Project Risks
Category | Description | Likelihood | Impact | Mitigation |
---|---|---|---|---|
Project Management | High | High | ||
Technology | Medium | High | To duplicate a copy |
The risks above have been managed and mitigated.
Technical Complexity
Technical Complexity 1: Rescheduling
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, Technology and Tools Used | Use Case & ER Diagram |
Analysis and Design | Architectural Diagram, Technology and Tools Used | Architectural Diagram & Technology and Tools Used |
Design | Prototype | |
Testing | User Test Plan |
OUR QUALITY ASSURANCE
User Testing
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/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
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