Design and evaluate an interactive product for booking tickets for events such a

Design and evaluate an interactive product for booking tickets for events such as concerts, music festivals, plays, and sporting events. Most venues and events have booking websites or apps already, and there are many ticket agencies that also provide reduced tickets and exclusive options, so there are plenty of existing products to research first.
Answer the following questions with an in-depth paper written in APA format, and cite any sources that you use:
Carry out the following activities to discover requirements for this product:
Identify and capture some user requirements for this product. This could be done in a number of ways. For example, observing friends or family using ticket agents, thinking about your own experience of purchasing tickets, studying websites for booking tickets, interviewing friends and family about their experiences, and so on.
Based on the information you glean about potential users, choose two different user profiles and produce one persona and one main scenario for each, capturing how the user is expected to interact with the product.
Using the data gathered in part 1 and your subsequent analysis, identify different kinds of requirements for the product, according to the headings introduced in section 11.3. Write up the requirements using a format similar to the atomic requirements shell shown in Figure 11.1 or in the style of user stories.
Based on the information gleaned from the activity in Chapter 11, suggest three different conceptual models for this system. Consider each of the aspects of a conceptual model discussed in this chapter: interface metaphor, interaction type, interface type, activities it will support, functions, relationships between functions, and information requirements. Of these conceptual models, decide which one seems most appropriate and articulate the reasons why.
Using the scenarios generated for the online booking facility, produce a storyboard for the task of booking a ticket for one of the conceptual models in step 1. Show it to two or three potential users and record some informal feedback.
One option for creating a storyboard is the following:
Click on Create a Storyboard – Above the Save button at the bottom right, there is a button with 6 little squares; this is the Storyboard button; click that – At the top menu, click on More… and Select Web & Wireframes – You can choose items from Icons, Wireframes, or any of the other options to create your storyboard – Remember, you have to click on an item and drag it to your storyboard box – Save your storyboard.
You can create a storyboard any way you like, even handwriting it and scanning it to your computer.
Considering the product’s concrete design, sketch out the application’s initial interface. Search for “sketching a website interface” in Google for ideas on how to do this. Consider the design issues introduced in Chapter 7 for the chosen interface type. Write one or two sentences explaining your choices and consider whether the choice is a usability consideration or a user experience consideration.
Sketch out an experience map for the product. Google this as well if you need suggestions. Use the scenarios and personas you generated previously to explore the user’s experience. In particular, identify any new interaction issues that had not been considered previously, and suggest what could be done to address them.
How does the product differ from applications that typically might emerge from the maker movement? Do software development kits have a role? If so, what is that role? If not, why not?

Leave a Reply

Your email address will not be published.