User role creation ticket website Requirements Analysis

 

 

The reason why I will do some research on online ticket booking is actually due to a recent set of PEN questions. The following analysis lacks a lot of user research, so I can do some exercises to improve my personal ability.

At present, the ticket booking website is overwhelming. In addition to the portals of major airlines, there are countless small and professional ticket booking websites, but it involves the process of money transactions, users tend to prefer high-profile and high-reliability websites. Just like tmall, in the ticket booking system, "where to go" and "Ctrip" are the top destinations. Of course, qq has already been coveted, follow up with high speed -go.qq.com.

So what is the situation of the user group targeted at the ticket booking website? The white-collar class who often travel, the middle and high-yielding class who like to travel, the Secretary group of the company, and the tour group owner. Here, we select the white-collar class who often travel to create a user role to output the user requirements and function list.

I. User Role (Ada)

To fully list the user types of a website, a lot of user research is required. However, after a brief analysis, we can find that Ada is a typical model for mainstream users. After refining Ada, we can find it.

　　

 

We can see that Ada's use of qq travel booking tickets is mainly divided into two situations: Tolerances and private rows, thus the requirements are different.

Tolerances:

1. The filtering conditions are clear. (For example, the location is clear, the round-trip time is clear, and the reimbursement price is as comfortable as possible)

2. Complete the task efficiently. (Because you often book tickets, avoid displaying unnecessary information, and search accurately to reach the target)

3. pay more attention to the price. (Within the scope of reimbursement)

4. Pay attention to the information about the change and exit. (Frequent variation in tolerances, requiring loose change rules)

5. You must submit a travel ticket for reimbursement. (Obvious route ticket options)

6. Real-time feedback and reminders are required. (Busy and easy to forget)

Private row:

1. tends to choose the lowest price. (Marked with the lowest price, or even travel because of the low price ;)

2. Information should be safe and reliable. (Preventing property losses)

3. The time can be changed due to the price. (Provides low price information for the time range of the target time ;)

Ii. user requirement analysis (Tool: MindManager)

　　

 

3. Page Information Architecture Analysis (Tool: MindManager)

　　

 

Iv. User Ticket Booking flowchart (brief version) (Tool: Visio 2010)

　　

 

OK. The next step is the output line diagram. My line diagram output is based on the interactive evaluation of the air ticket page of qq tourism.

I have made some analysis on the requirements of the booking page, so the interaction details should be designed.

This section provides a solution based on the analysis of the launched QQ travel ticket booking system.

　　

 

The specific analysis is as follows:

(1) Basic query module

The content is consistent with the basic query module of the Home Page. (the first time you enter the basic query module on the home page, the content must be consistent)

Only the necessary options are provided to complete the basic query. (You have no patience to think about and make repeated choices before you can view the query results)

Current version:

　　

 

1. After the user selects "departure city", the "Arrival City" Option List is not displayed immediately. The same date.

Cause: the user does not have enough patience before seeing the flight information. Make sure that the user's "task flow" is not interrupted.

Solution:

　　

 

2. Date selection module. Each time you click the "Left and Right" arrow, two months are skipped.

　　

 

Problem description: the user clicks the "Left" arrow to display "May" at the same position, but the "April" is actually displayed. In this case, the user needs to move the mouse to the calendar on the right, you can see "July May ". Increases the user's operational responsibility.

Solution: change to one month after each move.

(2) Calendar module

Original version:

　　

 

1. problem: the date is placed at the bottom of the axis.

Most users should check the date when buying tickets;

This is a row of tab groups arranged by date. Logically, the date is an index and the price is a date remark;

The price is attractive to Mainstream users, so you should use bright colors and increase the font size.

2. problem: the date range is fixed and you cannot view the price information for the previous week or the next week.

Price-oriented users can query calendar information in a wide range because they need to save money.

Overall solution:

　　

 

(3) Screening Module

What filtering items need to be set up?

1. * airlines: different airlines have different service quality. Users may have membership cards of a specific company;

2. * model: the comfort of the mainframe and the middleware is different, and the price is almost the same. users prefer the mainframe;

3. * departure time: a vast majority of users have determined the time range before the query, facilitating efficient and accurate identification of the corresponding information;

4. Category: most users will choose economy class. Users will usually select a specific category for a certain flight first (to be discussed)

5. arrival airport: there is only one airport in most cities in China. The arrival airport is displayed in the flight information;

6. Direct Flight/transit: most users do not need to transfer flights; the proportion of transit flights is not large; the flight information shows whether or not to transfer flights;

Original version:

　　

 

　　

 

　　

 

　　

 

Problems:

1. Dropdownlist format problems: hidden options, not intuitive; added users click operation

Filtering is a common function of users. Since it is commonly used, it should not be too concealed;

If you use checkbox, you only need to click three times, and all options are clear at a glance;

If you use dropdownlist, You need to click the mouse six times, which is not intuitive;

2. The "" format time is too digitalized and accurate for the take-off and landing time option

Change "take-off and landing time" to "departure time ";

The digital format option will lead to more thinking. The presentation model is inconsistent with the user's psychological model. You should use the "Morning, noon, afternoon, and evening" that the user is more familiar ", accuracy is achieved through the background;

Solution:

　　

 

(4) sorting module

ORIGINAL VERSION

　　

 

Problems:

1. The "take-off and landing time" and "lowest price" are not obvious button appearances and are hidden in the tab bar.

If you need to click, Please clearly tell the user "I Am a button ";

Is this "tag bar" or "filter bar? Users are not easy to notice, but may also have doubts;

Similar functions should be centrally placed;

When users browse information, the mouse is habitually placed on the right side of the screen; "Slider" and "Reservation" buttons are on the right side;

Solution:

　　

 

(5) Flight Information List Module

Original version:

　　

 

Problems:

1. The information in the Red Circle is too concentrated and an important "All discounts" option is placed

Five types of information are provided in one location: Price, discount, activity, change/return view, all discount options, excessive information, resulting in fatigue and loss;

The View class function and select class function should be placed separately;

When viewing information, the user's eye will constantly move to the "Reservation" button, and all discounts can be placed next to "Reservation;

2. The term "All discounts" is inaccurate and is not what users want most

Users will not choose a higher discount class because they see the lowest price;

The user does not want "Economy Class" to view other spaces;

Solution:

　　

 

Overall line diagram:

　　

 

Author: scholar wilson

Source: flyalone.net