(a) Identify users' needs for this website. You could do this in a number of ways.

For example, you could observe people using ticket agents, think about your own
experience of purchasing tickets, look at existing websites for booking tickets,
talk to friends and family about their experiences, and so on. Record your data
carefully.

The user needs to be able to book a ticket, pay for it and receive the ticket. The
user ideally would need some way of deciding where the ticket is in the stadium,
building, etc.. and the option to select a different location if the one provided
is undesirable. The user needs to be able to purchase more than one ticket at a
time and
to make sure that they are close to each other. The user also needs to have
different ways to receive the ticket. These can be either, by mail at different
speeds, maybe an online printout and also the possibility of holding onto the
tickets at will call. The user also needs to accomplish all of the preceding with
out much difficulty
the steps need to be straight forward and easy to do.

(b) Based on your user requirements, choose two different user profiles and produce
one main scenario for each one, capturing how the user is expected to interact with
the system.

User profile 1:
Pay online, hold tickets at the door, buy multiple tickets at a time, search for
best seats available.
With these attributes the scenario for user one would look like this:
The website would allow the user to put down their name and the number of tickets
they want, then the website would search for the best available seats based on a
predetermined criteria like view of the ball field. The user has the option to
narrow the search to a certain price range if they want. Once the search is done
the page
allows the user to enter credit card information to pay for the tickets or search
for the next best seats if the ones they got were not good enough. If there were
no seats in the price range selected then the site tells the user this. Once the
tickets are paid for the user is given a confirmation number that they need to
print off and
bring with them to the event so that they can pick up their tickets from will call.

User profile 2:
Pay online, print off tickets, no waiting in lines, buy multiple tickets at a time,
no numbered seating.
With these attributes the scenario for user two would look like this:
The website would allow the user to enter the number of seats they want and then
the site checks to make sure that they haven't already sold out. If they haven't
then the site goes to a page allowing the user to enter their credit card
information so that they can purchase the tickets. After the tickets are purchased
the site goes
to a confirmation page which needs to be printed off because this is used as the
ticket(s). The site also tells the user that the seating is first come first serve
so make sure to show up on time so that the whole party can sit together. The
ticket also enables the user to jump right to the front of the line and enter the
event instead
of waiting to purchase or pick up their ticket(s).

(c) Using the scenarios generated from your data gathering, perform a task analysis
on the main task associated with the ticket booking system, i.e., booking a ticket.
Scenario 1:
0. In order to book a ticket
1. go the website
2. Put down your name
3. Enter the number of tickets wanted
3.1 Enter the search criteria for the tickets
3.2 Perform the search
3.3 Accept search or search again
4. Pay for tickets
5. Get confirmation number

Scenario 2:
0. In order to book a ticket
1. Go to the website
2. Enter the number of tickets you want
3. Pay for the tickets
4. Print off confirmation page