Difference between revisions of "IS480 Team wiki: 2012T2 Team Prime Final Wiki"
(9 intermediate revisions by the same user not shown) | |||
Line 9: | Line 9: | ||
{| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px" | {| cellpadding="10" style="border: 3px solid #222222; text-align: center; height:50px" | ||
|scope="row" width="800" style="text-align: left; background: #FFFFFB"| | |scope="row" width="800" style="text-align: left; background: #FFFFFB"| | ||
− | <big>[https://wiki.smu.edu.sg/w/is480/images/ | + | <big>[https://wiki.smu.edu.sg/w/is480/images/e/e0/Prime_FYP_Final_Presentation_Final.pdf <span style="color:#794721">'''Final Presentation Slides'''</span>]</big><br><br> |
<big>[http://www.swimix.com <span style="color:#794721">'''Swimix Deployed Site Link'''</span>]</big> | <big>[http://www.swimix.com <span style="color:#794721">'''Swimix Deployed Site Link'''</span>]</big> | ||
#The team has completed '''8 sprints''' in total and is now finishing its final milestone. | #The team has completed '''8 sprints''' in total and is now finishing its final milestone. | ||
Line 43: | Line 43: | ||
:The team faced difficulties in implementing the payment feature. To focus our efforts on finishing up the payment feature, the team decided to drop the swim school feature. A secondary reason is that swim schools are not the main target market for Swimix. | :The team faced difficulties in implementing the payment feature. To focus our efforts on finishing up the payment feature, the team decided to drop the swim school feature. A secondary reason is that swim schools are not the main target market for Swimix. | ||
|} | |} | ||
+ | <!-- | ||
===<font color="#FC6B2A">Project Challenges</font>=== | ===<font color="#FC6B2A">Project Challenges</font>=== | ||
Type here | Type here | ||
<br> | <br> | ||
+ | --> | ||
===<font color="#FC6B2A">Project Achievements</font>=== | ===<font color="#FC6B2A">Project Achievements</font>=== | ||
Line 206: | Line 208: | ||
===<font color="#FC6B2A">Technical Complexity</font>=== | ===<font color="#FC6B2A">Technical Complexity</font>=== | ||
− | |||
{|class="wikitable" style="text-align: center; color:#222222" | {|class="wikitable" style="text-align: center; color:#222222" | ||
|+ | |+ | ||
|- | |- | ||
− | ! scope="col" width=" | + | ! scope="col" width="250" style="background-color:#794721"| <font color="#ffffff">Area</font> |
− | ! scope="col" width=" | + | ! scope="col" width="480" style="background-color:#794721"| <font color="#ffffff">Description</font> |
|- | |- | ||
− | ! scope="row" width="120" style="background-color:#FFFFFB; text-align:center;"|1. | + | ! scope="row" width="120" style="background-color:#FFFFFB; text-align:center;"|1. Improvements in Usability |
+ | |align="left"| | ||
+ | *Cross-browser compatibility | ||
+ | |||
+ | |- | ||
+ | ! scope="row" width="120" style="background-color:#FFFFFB; text-align:center;"|2. Improvements in Performance | ||
|align="left"| | |align="left"| | ||
− | * | + | * Loading of user profile |
− | + | * Loading of instructor’s calendar | |
− | + | * Search engine optimization | |
− | + | :*Naming convention of class files | |
− | * | + | :*Mapping on CodeIgniter framework (root folder) |
− | |||
− | :* | ||
− | :* | ||
|- | |- | ||
− | ! scope="row" width="120" style="background-color:#FFFFFB; text-align:center;"| | + | ! scope="row" width="120" style="background-color:#FFFFFB; text-align:center;"|3. Future Improvements |
|align="left"| | |align="left"| | ||
− | *''' | + | *Internationalization |
− | : | + | *Localization |
− | : | + | *Payment security |
− | : | + | :*Responsiveness |
− | + | :*User profile | |
− | : | + | *Instructor’s calendar |
− | : | + | :*Usability |
− | : | + | ::*More data validation needed |
− | + | |}<br> | |
+ | |||
+ | The following technical complexities have been listed in order of complexity (highest to lowest):<br><br> | ||
+ | <big>'''Complexity 1: Calendar'''</big><br><br> | ||
+ | |||
+ | '''Load the Calendar:'''<br> | ||
+ | [[Image:Prime_Calendar1.png]] | ||
+ | |||
+ | '''Load the Class:'''<br> | ||
+ | [[Image:Prime_Calendar2.png]] | ||
+ | |||
+ | <big>'''Complexity 2: Payment'''</big><br><br> | ||
+ | |||
+ | '''Generate the Order Form:'''<br> | ||
+ | [[Image:Prime_Payment1.png]] | ||
+ | |||
+ | '''Confirm Order Form after Payment is Made:'''<br> | ||
+ | [[Image:Prime_Payment2.png]] | ||
+ | |||
+ | <big>'''Complexity 3: Search Engine Optimization'''</big><br><br> | ||
+ | '''Search Engine Optimization:'''<br> | ||
+ | [[Image:Prime_SEO.png]] | ||
==<font color="#843A36">'''Quality of Product'''</font>== | ==<font color="#843A36">'''Quality of Product'''</font>== | ||
Line 283: | Line 307: | ||
|- | |- | ||
− | ! scope="row" rowspan=" | + | ! scope="row" rowspan="3" width="120" style="background-color:#FFFFFB; text-align:center;"|Design |
|align="center"|ER Diagram | |align="center"|ER Diagram | ||
|style="text-align="left"| | |style="text-align="left"| | ||
Line 292: | Line 316: | ||
|style="text-align="left"| | |style="text-align="left"| | ||
*[[IS480_Team_wiki:_2012T2_Team_Prime_Diagrams#System_Architecture|<span style="color:#FC6B2A">System Architecture Diagram</span>]] | *[[IS480_Team_wiki:_2012T2_Team_Prime_Diagrams#System_Architecture|<span style="color:#FC6B2A">System Architecture Diagram</span>]] | ||
+ | |||
+ | |- | ||
+ | |align="center"|Software Architecture Diagram | ||
+ | |style="text-align="left"| | ||
+ | *[[IS480_Team_wiki:_2012T2_Team_Prime_Diagrams#Software_Architecture|<span style="color:#FC6B2A">Software Architecture Diagram</span>]] | ||
|- | |- | ||
Line 439: | Line 468: | ||
:'''Solution: ''' | :'''Solution: ''' | ||
: Include a popup message to inform unregistered users to login first before making payment.<br><br> | : Include a popup message to inform unregistered users to login first before making payment.<br><br> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<br> | <br> | ||
Line 466: | Line 475: | ||
:'''Solution: ''' | :'''Solution: ''' | ||
:Replace the photos with useful information on how the system works. <br><br> | :Replace the photos with useful information on how the system works. <br><br> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<br> | <br> | ||
Line 525: | Line 521: | ||
|style="text-align: left"| | |style="text-align: left"| | ||
#'''Learnt''' to think from the user’s perspective rather than from a developer’s perspective when designing and developing the system <br> | #'''Learnt''' to think from the user’s perspective rather than from a developer’s perspective when designing and developing the system <br> | ||
+ | #'''Learnt''' that no matter how good a system is, without good aesthetics, the system cannot be considered a “success”. | ||
|} | |} |
Latest revision as of 10:56, 22 April 2013
Project Progress Summary
Project Overview
Final Presentation Slides
|
This is where we are on the timeline:
Project Highlights
Event | Highlights / Issue Description |
---|---|
Sprint 6 |
|
Sprint 7 |
|
Project Achievements
- Secured Singapore Olympian swimmer Tao Li as our celebrity sponsor. View our interview with her HERE.
- Successfully conducted 2 rounds of USER TESTS at Yishun Swimming Complex and Sengkang Swimming Complex, with a total of 38 users and 7 swimming instructors.
- Received confirmation of investment on Swimix from investor Dr Virginia Cha, who is also one of our PROJECT ADVISORS from SMU Institute of Innovation & Entrepreneurship.
Project Management
Schedule (Planned Vs Actual)
Since the midterms, the following changes have been made to the project schedule:
|
Refer to the PROJECT TIMELINE for a full view of the current project schedule.
Scope (Planned Vs Actual)
Since the midterms, the following changes have been made to the project scope:
|
Project Metrics
Schedule Metric
The diagrams below show the burndown charts and schedule ratio charts of Sprints 6 to 8 since the midterms.
BURNDOWN CHARTS
KEY ISSUES
Sprint 6:
Sprint 7:
|
For more details:
1. Schedule Metric Calculation
2. Schedule Ratio Documentation: Sprint 1
Sprint 2
Sprint 3
Sprint 4
Sprint 5
Sprint 6
Sprint 7
Sprint 8
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 |
---|---|---|---|
Low awareness of platform | High | High |
|
Low usage of platform | High | Low |
|
Idea may be copied by others | Low | High |
|
View the full list of risks HERE.
Technical Complexity
Area | Description |
---|---|
1. Improvements in Usability |
|
2. Improvements in Performance |
|
3. Future Improvements |
|
The following technical complexities have been listed in order of complexity (highest to lowest):
Complexity 1: Calendar
Complexity 2: Payment
Confirm Order Form after Payment is Made:
Complexity 3: Search Engine Optimization
Search Engine Optimization:
Quality of Product
Intermediate Deliverables
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | |
Metrics | ||
Requirements | Product Backlog | |
UI Mockups | ||
Analysis | Use Case | |
Process Flow Diagram | ||
Design | ER Diagram | |
System Architecture Diagram | ||
Software Architecture Diagram | ||
Testing | User Test 1 | |
User Test 2 |
Deployment
Environment | URL | Username / Password |
---|---|---|
Development |
|
User Test 2
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 | Search for Class / Instructor |
✓ | N/A |
3 | Pay for Class |
✓ | N/A |
4 | Send Mass Notification to Students |
N/A | ✓ |
5 | Send Evaluation Survey to Students |
N/A | ✓ |
6 | Evaluate Instructor |
✓ | N/A |
7 | Add New Lesson Slot |
N/A | ✓ |
8 | Add Student to Lesson Slot |
N/A | ✓ |
THE SESSION
|
Testing Methodology
Collecting of Qualitative Metrics
Collecting of Quantitative Metrics
|
Registered Users
- Solution:
- Replace “Please Select” with “No Preference”, and remove the unnecessary “Zone” search option.
- Solution:
- Underline the instructor's name to make it more obvious to the user.
- Solution:
- Include a popup message to inform unregistered users to login first before making payment.
Instructors
- Solution:
- Replace the photos with useful information on how the system works.
Reflections
Team
1) Good communication can make or break a team 2) Tapping on each other's strengths 3) A stronger focus on team building |