Difference between revisions of "IS480 Team wiki: 2012T2 Team Prime MidTerm Wiki"
Chheng.2009 (talk | contribs) |
m (→Project Risks) |
||
(18 intermediate revisions by 3 users not shown) | |||
Line 8: | Line 8: | ||
|scope="row" width="700" style="text-align: left; background: #FFFFFB"| | |scope="row" width="700" style="text-align: left; background: #FFFFFB"| | ||
<big>[http://www.swimix.com <span style="color:#843A36">'''Swimix'''</span>]</big> | <big>[http://www.swimix.com <span style="color:#843A36">'''Swimix'''</span>]</big> | ||
− | <big>[ | + | <big>[https://wiki.smu.edu.sg/w/is480/images/0/03/Prime_Midterm_Presentation.pdf <span style="color:#843A36">'''Presentation Slides'''</span>]</big> |
#The team is currently at '''Sprint 5''' (31 Jan 2013 to 26 Feb 2013). View our [https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=8 <span style="color:#FC6B2A">sprint progress</span>]. | #The team is currently at '''Sprint 5''' (31 Jan 2013 to 26 Feb 2013). View our [https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=8 <span style="color:#FC6B2A">sprint progress</span>]. | ||
#Our first user test was conducted in Sprint 4. View our [[IS480_Team_wiki:_2012T2_Team_Prime_MidTerm_Wiki#Testing| <span style="color:#FC6B2A">user test results</span>]]. | #Our first user test was conducted in Sprint 4. View our [[IS480_Team_wiki:_2012T2_Team_Prime_MidTerm_Wiki#Testing| <span style="color:#FC6B2A">user test results</span>]]. | ||
Line 123: | Line 123: | ||
The team has completed 5 sprints thus far, as shown in the burn down charts below.<br><br> | The team has completed 5 sprints thus far, as shown in the burn down charts below.<br><br> | ||
<b><font color="#843A36">BURNDOWN CHARTS</font></b><br> | <b><font color="#843A36">BURNDOWN CHARTS</font></b><br> | ||
− | [[Image:Sprints1to4.png|800px]] | + | [[Image:Sprints1to4.png|800px]]<br> |
− | + | [[Image:Sprint5.png]] | |
− | |||
<b><font color="#843A36">SCHEDULE RATIO CHARTS</font></b><br> | <b><font color="#843A36">SCHEDULE RATIO CHARTS</font></b><br> | ||
− | [[Image:ScheduleRatios_Sprints1234.png|800px]] | + | [[Image:ScheduleRatios_Sprints1234.png|800px]]<br> |
− | + | [[Image:ScheduleRatio_Sprint5.png|400px]] | |
− | |||
<b><font color="#843A36">KEY ISSUES</font></b><br> | <b><font color="#843A36">KEY ISSUES</font></b><br> | ||
Line 205: | Line 203: | ||
2. [https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdFRqZ2F1d0xnRlBveFVxQ1NhS3MzUGc#gid=3 <span style="color:#FC6B2A"><span style="color:#FC6B2A">Bug Log</span>] | 2. [https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdFRqZ2F1d0xnRlBveFVxQ1NhS3MzUGc#gid=3 <span style="color:#FC6B2A"><span style="color:#FC6B2A">Bug Log</span>] | ||
<br> | <br> | ||
+ | |||
+ | ===<font color="#FC6B2A">Change Request Management</font>=== | ||
+ | |||
+ | [[Image:ChangeRequest.png]] | ||
+ | #If the priority is a MUST, we will implement the change | ||
+ | #If the priority is a SHOULD and the time to implement the change is VERY SHORT, SHORT, or MEDIUM, we will implement the change. | ||
+ | #If the priority is a COULD, and the time to implement the change is VERY SHORT, we will implement the change. | ||
+ | #If the priority is a WON'T, then we will not implement the request.<br><br> | ||
+ | |||
+ | View our [https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=16 <span style="color:#FC6B2A">Change Request Log</span>]. | ||
===<font color="#FC6B2A">Project Risks</font>=== | ===<font color="#FC6B2A">Project Risks</font>=== | ||
Line 211: | Line 219: | ||
|+ | |+ | ||
|- | |- | ||
− | ! scope="col" width=" | + | ! scope="col" width="350" style="background-color:#843A36"| <font color="#ffffff">Risk</font> |
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Probability</font> | ! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Probability</font> | ||
! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Impact</font> | ! scope="col" width="100" style="background-color:#843A36"| <font color="#ffffff">Impact</font> | ||
− | ! scope="col" width=" | + | ! scope="col" width="350" style="background-color:#843A36"| <font color="#ffffff">Mitigation</font> |
|- | |- | ||
− | ! scope="row" width="120" style="background-color:#f5f5f5; text-align:center;"|Many issues might be raised during | + | ! scope="row" width="120" style="background-color:#f5f5f5; text-align:center;"|Many issues might be raised during user tests; time is required to rectify these issues |
|align="center"|High | |align="center"|High | ||
|align="center"|Medium | |align="center"|Medium | ||
− | |align="center"| | + | |align="center"|Create a response plan document to help us decide whether to implement a change based on priority, complexity and time needed to rectify the issues. |
|- | |- | ||
Line 226: | Line 234: | ||
|align="center"|Low | |align="center"|Low | ||
|align="center"|Medium | |align="center"|Medium | ||
− | |align="center"|Use a collaborative file management software (e.g. Google Documents, | + | |align="center"|Use a collaborative file management software (e.g. Google Documents, Dropbox) to organise respective folders of the project. Consensus amongst team members to adhere to proper version labelling. |
|- | |- | ||
− | ! scope="row" width="120" style="background-color:#f5f5f5; text-align:center;"| | + | ! scope="row" width="120" style="background-color:#f5f5f5; text-align:center;"|Putting too much focus on fixing user interface issues compared to ensuring the system logic is working properly |
|align="center"|High | |align="center"|High | ||
|align="center"|Medium | |align="center"|Medium | ||
− | |align="center"|Prioritize | + | |align="center"|Prioritize the task according to the criteria and strike a balance between the two. |
|} | |} | ||
− | View the full list of risks [ | + | View the full list of risks [[IS480_Team_wiki:_2012T2_Team_Prime_Risks#Risk_Management|<span style="color:#FC6B2A">here</span>]]. |
===<font color="#FC6B2A">Technical Complexity</font>=== | ===<font color="#FC6B2A">Technical Complexity</font>=== | ||
− | + | #PHP CodeIgniter 2.1.3 | |
+ | ::a. Understand the framework | ||
+ | ::b. Apply the framework | ||
+ | ::c. Customize the code | ||
+ | ::d. Debug the application | ||
+ | #Balance between the UI and code reusability | ||
+ | #Upload image | ||
+ | #Payment | ||
+ | #Shopping cart | ||
+ | #Calendar | ||
+ | #Scope too big for us to handle | ||
==<font color="#843A36">'''Quality of Product'''</font>== | ==<font color="#843A36">'''Quality of Product'''</font>== | ||
Line 254: | Line 272: | ||
|align="center"|Minutes | |align="center"|Minutes | ||
|style="text-align="left"| | |style="text-align="left"| | ||
− | *Team Minutes<br> | + | *[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_Team_Prime_Meeting_Minutes <span style="color:#FC6B2A">Team Minutes</span>]<br> |
− | *Supervisor Minutes <br> | + | *[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_Team_Prime_Meeting_Minutes <span style="color:#FC6B2A">Supervisor Minutes </span>]<br> |
|- | |- | ||
|align="center"|Metrics | |align="center"|Metrics | ||
|style="text-align="left"| | |style="text-align="left"| | ||
− | *Schedule Metric <br> | + | *[https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=0<span style="color:#FC6B2A">Schedule Metric</span>]<br> |
− | *Bug Metric <br> | + | *[https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=17<span style="color:#FC6B2A">Bug Metric</span>]<br> |
|- | |- | ||
Line 267: | Line 285: | ||
|align="center"|Product Backlog | |align="center"|Product Backlog | ||
|style="text-align="left"| | |style="text-align="left"| | ||
− | *Product Backlog < | + | *[https://docs.google.com/spreadsheet/ccc?key=0AmZnvFmI-HxRdElXZk5rekwwRVNYdlN5WEpZanVzOWc#gid=12<span style="color:#FC6B2A">Product Backlog</span>] |
|- | |- | ||
|align="center"|Metrics | |align="center"|Metrics | ||
|style="text-align="left"| | |style="text-align="left"| | ||
− | *UI Mockups <br> | + | *[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_Team_Prime_User_Interface<span style="color:#FC6B2A"> UI Mockups</span>]<br> |
|- | |- | ||
Line 278: | Line 296: | ||
|align="center"|Use Case | |align="center"|Use Case | ||
|style="text-align="left"| | |style="text-align="left"| | ||
− | *Use Case Diagram< | + | *[[IS480_Team_wiki:_2012T2_Team_Prime_Diagrams#Use_Case|<span style="color:#FC6B2A">Use Case Diagram</span>]] |
|- | |- | ||
− | |align="center"|Process Flow Diagram | + | |align="center"|Process Flow Diagram |
|style="text-align="left"| | |style="text-align="left"| | ||
− | *Process Flow Diagram < | + | *[[IS480_Team_wiki:_2012T2_Team_Prime_Diagrams#Process_Flow|<span style="color:#FC6B2A">Process Flow Diagram</span>]] |
|- | |- | ||
Line 289: | Line 307: | ||
|align="center"|ER Diagram | |align="center"|ER Diagram | ||
|style="text-align="left"| | |style="text-align="left"| | ||
− | *ER Diagram< | + | *[[IS480_Team_wiki:_2012T2_Team_Prime_Diagrams#ER_Diagram|<span style="color:#FC6B2A">ER Diagram</span>]] |
|- | |- | ||
|align="center"|System Architecture Diagram | |align="center"|System Architecture Diagram | ||
|style="text-align="left"| | |style="text-align="left"| | ||
− | *System Architecture Diagram < | + | *[[IS480_Team_wiki:_2012T2_Team_Prime_Diagrams#System_Architecture|<span style="color:#FC6B2A">System Architecture Diagram</span>]] |
|- | |- | ||
Line 300: | Line 318: | ||
|align="center"|User Test Plan | |align="center"|User Test Plan | ||
|style="text-align="left"| | |style="text-align="left"| | ||
− | *Execution Plan<br> | + | *[https://docs.google.com/document/d/1rDWL0l9kAKOBZLOz8PW1jfouBJ7jY0wwSyrxm3ULiAU/edit <span style="color:#FC6B2A"> Execution Plan </span>]<br> |
− | *Supporting Documents<br> | + | *[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_Team_Prime_Usability_Tests#Supporting_Documents <span style="color:#FC6B2A"> Supporting Documents </span>]<br> |
|} | |} | ||
+ | |||
===<font color="#FC6B2A">Deployment</font>=== | ===<font color="#FC6B2A">Deployment</font>=== | ||
− | |||
{|class="wikitable" style="text-align: center; height:120px" | {|class="wikitable" style="text-align: center; height:120px" | ||
Line 406: | Line 424: | ||
#A total of '''2 swimming instructors''' participated in the user test in the role of an '''Instructor'''. | #A total of '''2 swimming instructors''' participated in the user test in the role of an '''Instructor'''. | ||
<br> | <br> | ||
− | View the '''Supporting Documents''' for the user test [[IS480_Team_wiki:_2012T2_Team_Prime_Usability_Tests#Supporting_Documents |<span style="color:#FC6B2A">'''HERE.'''</span>]] | + | View the '''Supporting Documents''' for the user test [[IS480_Team_wiki:_2012T2_Team_Prime_Usability_Tests#Supporting_Documents |<span style="color:#FC6B2A">'''HERE'''</span>]].<br> |
+ | View our '''Internal Testing Documents (Before User Test 1)''' [https://www.dropbox.com/s/cuewdqge4c0yxip/Prime_Internal_Test_Cases_BeforeUT1.docx <span style="color:#FC6B2A">'''HERE'''</span>]<br> | ||
+ | View our '''Internal Testing Documents (Before Midterm)''' [https://www.dropbox.com/s/dau9b3jsdz45t2a/Prime_Internal_Test_Cases_V1.docx <span style="color:#FC6B2A">'''HERE'''</span>] | ||
|} | |} | ||
+ | |||
<br> | <br> | ||
Line 507: | Line 528: | ||
|scope="row" width="1000" style="text-align: left; background: #FFFFFB"| | |scope="row" width="1000" style="text-align: left; background: #FFFFFB"| | ||
'''Conclusion'''<br><br> | '''Conclusion'''<br><br> | ||
− | + | Based on the user feedback, we found out that users are mostly receptive to the idea of a swim-related search portal. <br><br> | |
− | The top 2 favourite functions identified by the users were the Manage Search function and the Manage Notification function. They commented that the search function was easy to use and could be very useful to them. The notification function is also something they felt | + | |
− | The function that | + | The top 2 favourite functions identified by the users were the Manage Search function and the Manage Notification function. They commented that the search function was easy to use and could be very useful to them. The notification function is also something they felt is lacking in the industry now. This is because they have made wasted trips to the swimming complex on the lesson day only to find out the lesson was cancelled.<br><br> |
− | + | ||
− | + | The function that had the highest amount of users indicating that they are unlikely to use is the Instructor Review feature. They explained that they would not want to go through the trouble to register an account just to write a review for the instructors. However, they would not mind writing if given the option of a simpler and more convenient alternative. <br><br> | |
+ | |||
+ | A user also commented that he preferred to register classes with the instructor in person instead of registering online because he could infer the instructor’s character and personality through the former. A possible solution is to include a short introduction video clip of each instructor so that users are able to gauge the instructor for themselves through the video.<br><br> | ||
In conclusion, many users expressed that they portal is user-friendly and would be very useful to them. | In conclusion, many users expressed that they portal is user-friendly and would be very useful to them. | ||
− | |||
|} | |} | ||
<br> | <br> | ||
Line 586: | Line 608: | ||
|scope="row" width="1000" style="text-align: left; background: #FFFFFB"| | |scope="row" width="1000" style="text-align: left; background: #FFFFFB"| | ||
'''Conclusion'''<br><br> | '''Conclusion'''<br><br> | ||
− | It was hard for us to get instructors to test our system | + | It was hard for us to get instructors to test our system because they are usually busy all the time while they are at the pool. They will either be teaching a class, or be on duty as a security guard. Thus, we only managed to get 2 instructors testers during their lunch break period when the weather is typically too hot to conduct a swim class. <br><br> |
− | Both instructors found the portal user friendly and | + | Both instructors found the portal user friendly and did not face any problem using the portal. They provided mostly aesthetics feedback, such as the student list is too cluttered and the login button is too small. In addition, an important point which they commented was that since they are always on the go, they preferred to use the system on their smartphone rather than in front of the computer. |
|} | |} | ||
<br> | <br> | ||
Line 601: | Line 623: | ||
! scope="row" style="background-color:#ffffff"|[[Image:Prime_XC.png|150px]]<br>Shen Xiaochuan | ! scope="row" style="background-color:#ffffff"|[[Image:Prime_XC.png|150px]]<br>Shen Xiaochuan | ||
|style="text-align: left"| | |style="text-align: left"| | ||
− | * | + | *Learnt to manage expectations between what users want and what the team is able to deliver<br> |
|- | |- | ||
! scope="row" style="background-color:#ffffff"|[[Image:Prime_HQ.png|150px]]<br>Lim Hui Qing | ! scope="row" style="background-color:#ffffff"|[[Image:Prime_HQ.png|150px]]<br>Lim Hui Qing | ||
|style="text-align: left"| | |style="text-align: left"| | ||
− | * | + | *Learnt the importance of engaging actual users to test the system to ensure that the system is designed according to their expectations<br> |
|- | |- | ||
! scope="row" style="background-color:#ffffff"|[[Image:Prime_JO.png|150px]]<br>Josephine Heng | ! scope="row" style="background-color:#ffffff"|[[Image:Prime_JO.png|150px]]<br>Josephine Heng | ||
|style="text-align: left"| | |style="text-align: left"| | ||
− | * | + | *Learnt the importance of designing the system from the view point of the actual users<br> |
|- | |- |
Latest revision as of 17:14, 8 April 2013
Project Progress Summary
Project Overview
The team is confident of completing the project within the schedule as shown below. |
Project Highlights
Highlight 1: Confirmation of endorsement from Tao Li who has represented Singapore in many international swimming competitions including the Beijing and London Olympics.
Highlight 2: Manage Reviews and Manage Users’ Reviews was replaced with Manage Evaluations
Highlight 3: In Sprint 3, there was a spike in the number of bugs found, due to the fact that more rigorous testing was conducted on the application to prepare for User Test 1 in the Sprint 4.
Project Management
Schedule (Planned Vs Actual)
Note:
No significant changes have been made to the schedule with regards to the proposal and acceptance milestones.
However, significant changes have been made to the project schedule in the subsequent four milestones as shown below.
Changes Made
|
Refer to the PROJECT TIMELINE for a full view of the current project schedule.
Scope (Planned Vs Actual)
Version 1 (Original)
Version 2
Version 3 (Latest)
|
Project Metrics
Schedule Metric
The team has completed 5 sprints thus far, as shown in the burn down charts below.
BURNDOWN CHARTS
KEY ISSUES
Sprint 3:
Sprint 4:
Sprint 5:
|
For more details:
1. Schedule Metric Calculation
2. Schedule Ratio Documentation: Sprint 1
Sprint 2
Sprint 3
Sprint 4
Sprint 5
Bug Metric
Number of Bugs Found
|
Total Bug Score
|
Total Bug Score | Action to be Taken |
---|---|
< 5 | Developers resolve issues within the sprint. |
5 - 9 | Resolve the bugs during the planned debugging time. |
≥ 10 | Stop current development and resolve the bugs immediately. |
For more details:
1. Bug Metric Calculation
2. Bug Log
Change Request Management
- If the priority is a MUST, we will implement the change
- If the priority is a SHOULD and the time to implement the change is VERY SHORT, SHORT, or MEDIUM, we will implement the change.
- If the priority is a COULD, and the time to implement the change is VERY SHORT, we will implement the change.
- If the priority is a WON'T, then we will not implement the request.
View our Change Request Log.
Project Risks
The top 3 risks are prioritised as follows::
Risk | Probability | Impact | Mitigation |
---|---|---|---|
Many issues might be raised during user tests; time is required to rectify these issues | High | Medium | Create a response plan document to help us decide whether to implement a change based on priority, complexity and time needed to rectify the issues. |
Project contains numerous documentation and different versions. Inefficent access to a particular document. | Low | Medium | Use a collaborative file management software (e.g. Google Documents, Dropbox) to organise respective folders of the project. Consensus amongst team members to adhere to proper version labelling. |
Putting too much focus on fixing user interface issues compared to ensuring the system logic is working properly | High | Medium | Prioritize the task according to the criteria and strike a balance between the two. |
View the full list of risks here.
Technical Complexity
- PHP CodeIgniter 2.1.3
- a. Understand the framework
- b. Apply the framework
- c. Customize the code
- d. Debug the application
- Balance between the UI and code reusability
- Upload image
- Payment
- Shopping cart
- Calendar
- Scope too big for us to handle
Quality of Product
Intermediate Deliverables
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | |
Metrics | ||
Requirements | Product Backlog | |
Metrics | ||
Analysis | Use Case | |
Process Flow Diagram | ||
Design | ER Diagram | |
System Architecture Diagram | ||
Testing | User Test Plan |
Deployment
Area | Description |
---|---|
Development Environment |
|
Database |
|
Web Links |
Testing
Objectives
OBJECTIVES:
|
Scope
The table below shows a list of features that were tested for our first user test. The features target parents (representing registered users of Swimix) and swimming instructors.
No. | Features | Reg. User | Instructor |
---|---|---|---|
1 | Register / Log in / Log out |
✓ | ✓ |
2 | Change Password |
✓ | ✓ |
3 | Update User Profile |
✓ | |
4 | Update Instructor Profile |
✓ | |
5 | Search for Class |
✓ | |
6 | Search for Instructor |
✓ | |
7 | Create and Remove Lesson Slot |
✓ | |
8 | Create and Remove Student Details |
✓ |
Insert relevant PICTURE.
THE SESSION
|
Testing Methodology
Collecting of Qualitative Metrics
Collecting of Quantitative Metrics
|
Registered Users
- Solution: Place Login and Register in the same area and allow switching by tabs.
- Solution: Change the View link to a button so users know that they can click on it to view the instructor’s profile
POST-TEST SURVEY RESULTS:
SN | Functions | Very Unlikely | Unlikely | Undecided | Likely | Very Likely |
---|---|---|---|---|---|---|
1 | Search for Class/Instructor |
0 | 0 | 0 | 5 | 3 |
2 | Online Class Registration |
0 | 1 | 2 | 3 | 2 |
3 | Online Payment |
0 | 1 | 0 | 4 | 3 |
4 | Instructor Review |
0 | 2 | 1 | 4 | 1 |
5 | Instructor Rating |
0 | 0 | 2 | 5 | 1 |
6 | Receive Notification |
0 | 0 | 1 | 3 | 4 |
Conclusion The top 2 favourite functions identified by the users were the Manage Search function and the Manage Notification function. They commented that the search function was easy to use and could be very useful to them. The notification function is also something they felt is lacking in the industry now. This is because they have made wasted trips to the swimming complex on the lesson day only to find out the lesson was cancelled. The function that had the highest amount of users indicating that they are unlikely to use is the Instructor Review feature. They explained that they would not want to go through the trouble to register an account just to write a review for the instructors. However, they would not mind writing if given the option of a simpler and more convenient alternative. A user also commented that he preferred to register classes with the instructor in person instead of registering online because he could infer the instructor’s character and personality through the former. A possible solution is to include a short introduction video clip of each instructor so that users are able to gauge the instructor for themselves through the video. |
Instructors
- Solution:
- Use radio buttons instead of dropdown list.
- Solution:
- Display only the student name and contact number.
- Instructors can choose to click on the student's name to view the rest of their information.
POST-TEST SURVEY RESULTS:
SN | Functions | Very Unlikely | Unlikely | Undecided | Likely | Very Likely |
---|---|---|---|---|---|---|
1 | Adding lesson slots to calendar |
0 | 0 | 1 | 1 | 0 |
2 | Selling available class slots |
0 | 0 | 0 | 1 | 1 |
3 | Sending mass notification |
0 | 0 | 0 | 0 | 2 |
4 | Online payment system |
0 | 0 | 2 | 0 | 0 |
Conclusion |