HeaderSIS.jpg

IS480 Team wiki: 2013T2 DR.Jean Labs Design & Prototype

From IS480
Revision as of 14:04, 22 January 2014 by Denise.wong.2011 (talk | contribs)
Jump to navigation Jump to search
Agurz avatar.png
Denise avatar.png
Eleazar avatar.png
Dr.jeanlabs logo.jpg
Janan avatar.png
Nicholas avatar.png
Rafael avatar.png

HOME

 

DR.JEAN LABS

 

PROJECT OVERVIEW

 

PROJECT MANAGEMENT

 

PROJECT DOCUMENTATION

 


{ Project Description } { Motivation } { Project Scope } { User Tests } { Design & Prototype }


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


Our Application

Our application is live now! Click here to view our web application!

Personas

Drjeans persona1.png
Drjeans persona2.png
Drjeans persona3.png

Scenarios

Scenario 1 | Rachel wants to find a way to increase awareness of FoodLovers

1-for-1 Promotion!

Rachel is a food aficionado and her dream of setting up a restaurant came true last year when she opened the restaurant FoodLovers. FoodLovers specializes in Western Cuisine and its goal is to bring affordable Western meals to the masses. Located at City Link, FoodLovers’s business faced high competition from other restaurants but Rachel was able to hold her ground and bring in customers through various marketing strategies. However, advertising doesn’t come cheap. Rachel had to incur a fixed cost of a few thousand dollars just for advertising alone and sometimes, these advertisements may not be effective at all.

Tim, one of the employees at FoodLovers, heard about SQKII, a new advertising platform, where advertisers can switch advertising costs from a fixed cost to a variable one, and are only charged a few cents per impressions made by users. Not only is this a cheaper alternative, but they can also derive analytics from this application to find out what type of users are interested in these promotions and how many are actually viewing them.

Without hesitation, Rachel and Tim registered on the SQKII website to test out the application.





Scenario 2 | Kelly wants to find a place to shop and dine with her boyfriend Tony

Kelly and her awesome lunch!

Kelly and Tony had a hectic week in school and they want to unwind this weekend. Kelly wants to have a romantic lunch with Tony and after that, go on a shopping spree. They agreed to meet in town, away from NTU and their textbooks. Kelly was early and she arrived at City Hall MRT first. They did not have a lunch place in mind and so Kelly decided to try out SQKII's location based squib viewing. She easily tracked down deals and promotions happening at City Hall right now. To her surprise, she saw from an advertisement that FoodLovers restaurant is providing a 1-for-1 meal promotion and they served her favourite western cuisine. She immediately shared the advertisement via whatsapp to Tony about this exciting deal and they went to have their lunch there.






Scenario 3 | Kelly goes on a shopping spree!

Kelly on a shopping spree!

After a good lunch, Kelly was all ready to go shopping. Having spent much of her time at “Pulau NTU” for so long, she felt foreign to her surroundings in town. She wanted to buy some clothes and stationery at City Link but she was not sure where to start shopping. She knows that if she scours the entire town, she will probably find some sales or promotions on clothes and stationery but that would take up time. She decided that she would once again summon the help of SQKII to help her trace promotional ads pertaining to clothes and stationery. SQKII generated a few relevant advertisements that came from shops in Kelly’s proximity, with help from SQKII’s in-built location-based services. Kelly made sure to bookmark these advertisements after browsing for her own usage, so that she could refer to them on her shopping trip. In the end, she bought whatever she needed at discounted prices, resulting in a happy Kelly!






Scenario 4 | Tony occupies himself with earning quick cash from ads browsing

Tony earns quick cash by browsing ads

Tagging alongside his girlfriend who was busy shopping, Tony decided to keep himself occupied by using SQKII to earn some cash. He was very lucky to have won $5 from the lucky box bonus in the application the day before and he is looking forward to that big surprise again. For now, he is busy flipping through advertisements of computer games and sports merchandise. One thing that caught his eye was the release of Grand Theft Auto 5 and it was at a promotional price at a store nearby. He thought of his friends who were interested in GTA 5 and he decided to share this advertisement on his Facebook page. This was made easy as he was currently logged into SQKII using Facebook. He decided to bookmark this advertisement so that he could discuss with his roommates on whether they would want to order in bulk for cheaper rates.





Flow Diagram

User

DrJean UserFlow.png

Advertisers

DrJean AdvFlow.png

Admin

DrJean AdmFlow.png

Prototype

Low-fidelity | Our Evaluators

A: Kenny Quek Yu Wei from SMU School of Business. Male, 23 years old.

DJL KennyQuek.jpg
DJL KennyQuek2.jpg














B: Tan Xi Jing from SMU School of Law. Male, 23 years old.

DJL atxj.jpg
DJL atxj2.jpg















C: Teo Chin Seng from BNP Baribas Net. Male, 26 years old.

DJL tcs.jpg
DJL tcs2.jpg















D: Royston Tan Wei Ching from NTU Business School. Male, 23 years old.

DJL rtwc.jpg
DJL rtwc2.jpg

















Low-fidelity | Compiled Problems

Problem 1

Name Recommendation of Search Engine
Sources [A.5, B.5, D.5]
Heuristic 7 [Flexibility and efficiency of use] Severity 3 = Major usability problem
Description:

A: There will be a problem with a long list of pending approvals or notifications, especially if this application is widely-used. It will be difficult to trace a particular user, advertiser or squib when the list becomes very long, affecting scalability of the application.

B: Long list of users and advertisers in view users and view advertisers pages. It will be difficult to find a specific user or advertiser without a search function.

C: It will be difficult to find a specific user, advertiser or Squib without a search function.

Proposed Solution:

Add a search field into the application so that admin can filter users or advertisers based on a specific name.

Problem 2

Name Inbox is too cluttered with many notifications
Sources [B.4, D.3]
Heuristic 8 [Aesthetic and Minimalist Design] Severity 4 = Usability catastrophe
Description:

B: There will be a long list of notifications for the admin to look at and it will be cluttered to an extent that it will be pointless for the admin to look through.

C: As an admin, you will have to browse through a long list of notifications and it will be very messy and not informative for the admin.

Proposed Solution:

Categorization of the various notifications would help the admin to know the statistics of each task quickly. For e.g, consolidation of how many cash outs, how many ads awaiting for approval. These numbers would be more informative for the admin.

Problem 3

Name Cash out option is not prominent.
Sources [B.6, C.7]
Heuristic 7 [Flexibility and efficiency of use] Severity 3 = Major usability problem
Description:

B: As a user, he needs to make a few clicks to navigate to his profile before he could cash out. This is very troublesome and it is one of the most important functions that the user uses. It is not intuitive enough for the user to cash out.

C: User wants to cash out fast and swiftly but the only way he/she could cash out is via multiple clicks to their profile page before he/she can cash out.

Proposed Solution:

Put the cash out option in the menu toolbar for easy access and use.

Problem 4

Name Missing back button.
Sources [B.2]
Heuristic 3 [User control and freedom] Severity 1 = Cosmetic problem only
Description:

B: The user always has to click on the menu bar and redo his choosing patterns when he only wishes to go back 1 page before

Proposed Solution:

Implement a back button for user to return one page before.

Problem 5

Name Missing cancel button
Sources [D.2]
Heuristic 3 [User control and freedom] Severity 3 = Major usability problem
Description:

D: No cancel button found in the reject Squibs message prompt means that admin must reject the Squib when the message prompt appears in order to proceed. There is no redo or undo function.

Proposed Solution:

Create a cancel button so that the user can cancel rejecting of the squib. Also , a tab away function could be integrated as well

Problem 6

Name What’s popular page may not be the first thing that user wants to see.
Sources [B.7]
Heuristic 8 [Aesthetic and Minimalist Design] Severity 2 = Minor usability problem
Description:

B: The first thing that the user sees when he logs in is the “What’s Popular” page whereby the top 3 Squibs are shown. He may not be interested in looking at What’s Popular and this takes some of his time off to navigate away.

Proposed Solution:

Have more shortcuts and overview buttons (Refer to App store interface), where there is a top chart’s button that links the user to most popular pages only if the user clicks the button.

Problem 7

Name Prompting of user’s PayPal information one last time before he accepts the cashout.
Sources [B.8]
Heuristic 1 [Visibility of System Status] Severity 1 = Cosmetic problem only
Description:

B: User would like to be assured that the cash is transferred correctly to the right account and a meticulous user would have to check his PayPal again before cashing out.

Proposed Solution:

Instead of making the user go back to his profile to check the account information, include the PayPal account information on the cash out message prompt.

Problem 8

Name Lack of Heading
Sources [B.1]
Heuristic 1 [Visibility of System Status] Severity 2 = Minor usability problem
Description:

B: The user does not know where he is due to a lack of headings when navigating to various pages.

Proposed Solution:

Add a descriptive heading or title on top of all pages to tell the user which page he is at currently.

Problem 9

Name Inconsistent naming of buttons
Sources [B.3]
Heuristic 4 [Consistency and standards] Severity 2 = Minor usability problem
Description:

B: There are inconsistent button names all about the application. In the “Manage Cashout” page, the buttons are “Rejected” and “Marked as completed”, where it could simply be “Accept” and “Reject” just like some other pages. This becomes less intuitive for the user.

Proposed Solution:

Ensure that all buttons are consistent and have minimal variations in naming of buttons.

Problem 10

Name Comment box not included in Add Squibs page by advertisers.
Sources [B.9]
Heuristic 10 [Help and documentation] Severity 1 = Cosmetic problem only
Description:

B: There could be special messages or instructions that the advertisers wish to relay to the admin.

Proposed Solution:

Add a text field for advertisers to input messages for admin if they have special instructions on handling these newly added Squibs.

Problem 11

Name Users credit should be seen in every page.
Sources [C.6]
Heuristic 1 [Visibility of system status] Severity 2 = Minor usability problem
Description:

C: Users wish to know how much credit he has accumulated so far but he could only access this information in his profile page.

Proposed Solution:

Make user’s credit amount visible in every page so that he could keep track of his credit easily.

Problem 12

Name Lack of tracker to show how much credits have been cashed out by users
Sources [C.5]
Heuristic 1 [Visibility of system status] Severity 4 = Usability catastrophe
Description:

C: There is no tracker to show how much credits have been cashed out for users. Admins cannot keep track of SQKII’s finance.

Proposed Solution:

Have an accounting page for Admins so that they can keep track of the accumulated transactions when users cash out.

Problem 13

Name Manage advertiser’s page is redundant, go straight to view advertisers
Sources [C.4]
Heuristic 7 [Flexibility and efficiency of use] Severity 1 = Cosmetic problem only
Description:

C: There is an additional page of managing advertisers [create or view advertisers] but brings an extra click for the admin and this page has minimal functions to be even considered a page on its own.

Proposed Solution:

Remove the manage advertisers page and integrate [create or view advertisers] in the view advertisers page.

Problem 14

Name Manage user’s page is redundant, go straight to view users
Sources [C.3]
Heuristic 7 [Flexibility and efficiency of use] Severity 1 = Cosmetic problem only
Description:

C: There is an additional page of managing users [create or view users] but brings an extra click for the admin and this page has minimal functions to be even considered a page on its own.

Proposed Solution:

Remove the manage users page and integrate [create or view users] in the view users page.

Problem 15

Name Lack of highlighting at menu toolbar
Sources [C.2]
Heuristic 1 [Visibility of system status] Severity 1 = Cosmetic problem only
Description:

C: User will not be able to know which page he/she is currently on, when the menu toolbar is not highlighted to suggest the current location.

Proposed Solution:

Add a highlight function to the menu toolbar to tell the user where the user is currently at.

Problem 16

Name Approvals of Squibs have missing time limit
Sources [C.1]
Heuristic 1 [Visibility of system status] Severity 2 = Minor usability problem
Description:

C: Admin has no idea what is the time period that he can approve the Squib before the Squib expires.

Proposed Solution:

Add a timer to each Squib shown in the pending approval page for admin.

Problem 17

Name Tab labels are not intuitive.
Sources [A.1]
Heuristic 4 [Consistency and standards] Severity 2 = Minor usability problem
Description:

A: The word ‘pending’ in the admin’s inbox page is ambiguous and the user is confused with what is pending. Even though space is limited, the labels must be understandable for ease of usage.

Proposed Solution:

Change ‘pending’ to ‘pending approval’. Reduce font size if needed but do not compromise on clarity of terms to users.

Problem 18

Name There is only one registration link for user and advertiser to create their account.
Sources [C.8]
Heuristic 7 [Flexibility and efficiency of use] Severity 4 = Usability catastrophe
Description:

A: Users and advertisers require different fields to fill in during the registration so they should not be directed to the same kind of registration form.

Proposed Solution:

Have separate registration links for both users and advertisers in the login page.

Problem 19

Name Filters for dashboards with pending approvals or notification
Sources [A.2]
Heuristic 7 [Flexibility and efficiency of use] Severity 3 = Major usability problem
Description:

A: There will be a problem with a long list of pending approvals or notifications, especially if this application is widely-used. It will be difficult to filter advertisers, different users and squibs that may require more immediate actions.

Proposed Solution:

Adding a filter option that can filter by merchants, users and squibs.

Problem 20

Name Zoom in on Squibs that may have granular details like smaller fonts, pictures.
Sources [A.3]
Heuristic 8 [Aesthetic and Minimalist Design] Severity 1 = Cosmetic problem only
Description:

A: This function allows a clearer view for the users, especially for web mobile where the screen is smaller.

Proposed Solution:

Add a zoom in function for mobile web squibs. Inform the advertisers of the minimum font requirement for optimal viewing.

Problem 21

Name Missing option to reject approved Squibs or accept rejected Squibs.
Sources [A.4]
Heuristic 7 [Flexibility and efficiency of use] Severity 4 = Usability catastrophe
Description:

A: In Manage Squibs page, under Approved tab, the admin must also be able to reject approved Squibs (for various reasons). Similarly, the admin must be able to approve rejected Squibs (for various reasons).

Proposed Solution:

Add in edit functions for both approved or rejected Squibs.

Problem 22

Name Add a User Preference option
Sources [A.6]
Heuristic 7 [Flexibility and efficiency of use] Severity 1 = Cosmetic problem only
Description:

A: Adding in a user’s preference page would allow users to filter away squibs that they are uninterested in and retain those they wish to see.

Proposed Solution:

Add in a user preference option under edit user profile.

Problem 23

Name Keyword tags for advertisements
Sources [A.7]
Heuristic 7 [Flexibility and efficiency of use] Severity 3 = Major usability problem
Description:

A: Providing keyword tags for each advertisement will help advertisers dictate the search words that they want the user to associate their squib with. Also, it helps advertisers tell admin what category their squibs fall under.

Proposed Solution:

Add a field for keywords tag in edit squibs page by advertisers.

Problem 24

Name There is no “No. of views” for each squib in the View Squib page of advertiser.
Sources [D.4]
Heuristic 1 [Visibility of system status] Severity 4 = Usability catastrophe
Description:

D: As an advertiser, it would be of great interest to find out how many impressions have been made on his/her Squib so far. Without this status, it would be difficult to gauge the popularity of this Squib and prevent the advertiser on making necessary decisions on how to manage the Squib (For e.g if the squib is popular and impressions are high, advertiser may wish to extend the duration of their Squib).

Proposed Solution:

Add a no. of views count beside each Squib.

Problem 25

Name Make PayPal account optional in registration page.
Sources [D.6]
Heuristic 7 [Flexibility and efficiency of use] Severity 1 = Cosmetic problem only
Description:

D: Some people may not have PayPal accounts and the thought of creating one before they even see how the application works may turn them off.

Proposed Solution:

Let the filling in of PayPal account details be optional in the registration process and make it compulsory to fill in only when the user wishes to cash out.

Heuristics and Severity Rating

Heuristics Severity Ratings

1. Visibility of system status

2. Match between system and the real world

3. User control and freedom

4. Consistency and standards

5. Error prevention

6. Recognition rather than recall

7. Flexibility and efficiency of use

8. Aesthetic and minimalist design

9. Help users recognize, diagnose, and recover from errors

10. Help and documentation

Not related to any heuristic

0 = I don't agree that this is a usability problem

1 = Cosmetic problem only

2 = Minor usability problem

3 = Major usability problem

4 = Usability catastrophe

Prototype Wireframe

Download the pdf here!