Difference between revisions of "IS480 Team wiki: 2013T2 DR.Jean Labs The Team Final Quality of the Product"
Jump to navigation
Jump to search
Line 151: | Line 151: | ||
For more information, please click[[IS480 Team wiki: 2013T2 DR.Jean Labs UT1|<b> here </b>]] | For more information, please click[[IS480 Team wiki: 2013T2 DR.Jean Labs UT1|<b> here </b>]] | ||
|| Results | || Results | ||
+ | * Revamped the UI | ||
+ | * Terminology changes (i.e. Inactive >> Draft and Pending, Charge Account >> Buy Impressions) | ||
+ | * Create Squib guidelines | ||
+ | * Image Preview | ||
| align="center"| 5 | | align="center"| 5 | ||
| align="center" width = "5%"| 23 - 60 | | align="center" width = "5%"| 23 - 60 | ||
Line 159: | Line 163: | ||
|| For more information, please click[[IS480 Team wiki: 2013T2 DR.Jean Labs UT2|<b> here </b>]] | || For more information, please click[[IS480 Team wiki: 2013T2 DR.Jean Labs UT2|<b> here </b>]] | ||
|| Results | || Results | ||
+ | * Added a Tutorial | ||
+ | * Included Credits to Cash conversion rate | ||
+ | * Standardised size and aligned all squibs | ||
+ | * Implemented Favourite button in View Squib | ||
| align="center"| 10 | | align="center"| 10 | ||
| align="center" width = "5%"| 17 - 24 | | align="center" width = "5%"| 17 - 24 | ||
Line 167: | Line 175: | ||
|| For more information, please click[[IS480 Team wiki: 2013T2 DR.Jean Labs UT3|<b> here </b>]] | || For more information, please click[[IS480 Team wiki: 2013T2 DR.Jean Labs UT3|<b> here </b>]] | ||
|| Results | || Results | ||
+ | * Show credits earned after each Read made | ||
+ | * Updates to UI to make it more intuitive | ||
+ | * Reverse View History order to show from latest | ||
+ | * Picture Zoom | ||
+ | * Step by Step Tutorial | ||
| align="center"| 15 | | align="center"| 15 | ||
| align="center" width = "5%"| 20 - 27 | | align="center" width = "5%"| 20 - 27 | ||
Line 175: | Line 188: | ||
|| For more information, please click[[IS480 Team wiki: 2013T2 DR.Jean Labs UT4|<b> here </b>]] | || For more information, please click[[IS480 Team wiki: 2013T2 DR.Jean Labs UT4|<b> here </b>]] | ||
|| Results | || Results | ||
− | | align="center"| | + | * More detailed statistics (breakdown by squib) |
+ | * Keep me logged in/forget password email reset | ||
+ | * FAQ | ||
+ | | align="center"| 5 | ||
| align="center" width = "5%"| 20 - 27 | | align="center" width = "5%"| 20 - 27 | ||
|- | |- | ||
Line 183: | Line 199: | ||
|| For more information, please click[[IS480 Team wiki: 2013T2 DR.Jean Labs UT5|<b> here </b>]] | || For more information, please click[[IS480 Team wiki: 2013T2 DR.Jean Labs UT5|<b> here </b>]] | ||
|| Results | || Results | ||
− | | align="center"| | + | * User: Lazy loading in View History and View Favourites |
+ | * Advertiser: Expanded Edit Squib View | ||
+ | | align="center"| 40 | ||
| align="center" width = "5%"| 20 - 27 | | align="center" width = "5%"| 20 - 27 | ||
|- | |- |
Revision as of 18:45, 21 April 2014
{ In a nutshell } | { Acceptance Wiki } | { MidTerm Wiki } | { Final Wiki } |
<< Project Summary >> | << Project Management >> | << Quality of the Product >> | << Our Reflections >> |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Quality of the project
Intermediate Deliverables:
Stage | Specification | Modules |
Project Management | Lab Minutes | Lab Minutes |
Supervisor Minutes | Supervisor Minutes | |
Mentor Minutes | Mentor Minutes | |
Schedule Metrics | Schedule Metrics | |
Bug/Risk/Well-Being Metrics | Metrics | |
Requirements | Prototype | Low-Fi Prototype |
Analysis & Design | Use case | Use Case Diagrams |
Flow Diagram | Flow Diagram | |
System Architecture Diagram | System Architecture diagram | |
User test plan | User Tests |
User Testing:
User Test | Date of Test | Objectives | Results | Number of participants | Age range |
Heuristic Evaluation | 19-Oct-13 | It is a way to highlight usability issues in our paper prototype. We followed the Ten Usability Heuristics reading by Jakob Nielsen. Using these, evaluators will list as many usability issues as possible. It is able to help us to identify problems and decide how we can solve it. For detailed and concise description to the usability problem and solution, please see our Heuristic Evaluation findings | Results | 4 | 23 - 26 |
User Test 1 (Advertiser) | 27-Jan-14 to 29-Jan-14 | It is to look at the general usability of Sqkii's advertiser platform whether
1. How easy is it for new advertiser to learn how to use our web application? |
Results
|
5 | 23 - 60 |
User Test 2 (User) | 10-Feb-14 to 12-Feb-14 | For more information, please click here | Results
|
10 | 17 - 24 |
User Test 3 (User) | 20-Feb-14 to 23-Feb-14 | For more information, please click here | Results
|
15 | 20 - 27 |
User Test 4 (Adv) | 3-Mar-14 to 7-Mar-14 | For more information, please click here | Results
|
5 | 20 - 27 |
A|B testing | 8-Apr-14 to 11-Apr-14 | For more information, please click here | Results
|
40 | 20 - 27 |
Summary of the user test.
- A total of 3 user tests has been conducted for both advertiser and user. This is to ensure at we meet the real need of advertiser and value add to users.
- Enable us to build a more user-friendly application that meets the need of advertiser. It is not to convert sales, but to create more eye-balls to their promotion.
- It is value adding to the user's live. MOre useful content was exposed to the user to create more awareness of the promotion and could potentially be their customer.
- Unexpected event occur such in bugs during Closed Beta Launch. However, the team was able to resolve it within a reasonably fast response time, thus delayed some of the functions in Sprint 7. Please see Metric for more details.
- We also faced one hacker that tried to inject codes into our system too! With our fast and quick response time, we manage to spot the outlier and manage to do mitigations and prevent the hacker to further hack our system.
- User Test results were generally very positive with general comments such as "Interesting Concept!", "Nice and pleasing user interface.", "Cool application".