Can you please solve this question? I need a rich picture, system vision, stakeholder analysis, and event table of this case study. The case study is:

Case 3 EasyTicket

Disclaimer: The situation described in the following case study is fictional, and bears no resemblance to any persons, businesses, or organisations, living or dead. Any such resemblance, if exists, is merely co-incidental in nature, and is not intentional.

EasyTicket has over 35 years of experience in ticketing the biggest live events and venues. It is a leading ticketing partner to the sports and live entertainment industry and operates one of the most advanced multi-channel ticket sales and distribution networks.

The company sells over five million tickets for more than five thousand events each year, including concerts, sporting events, theatre, musicals, festivals, exhibitions and family events. It provides ticketing services to Australias premier venues, such as Melbourne Cricket Ground, Rod Laver Arena and National Gallery of Australia in Canberra to name a few.

The management wants to redesign its legacy ticketing system as part of a modernisation project. The new system should also provide a market leading mobile platform to give customers the ability to browse, buy and deliver tickets on their phones, through both a mobile-enabled site and smartphone apps.

Customers can collect their tickets in one of four ways:

print at home via eTicket service

collect at the venue or pre-paid collection outlet

regular mail

via mobile phone

EasyTicket offers a dedicated team of call centre representatives to resolve queries from customers in regards to ticketing and delivery.

EasyTickets eTicket is print-at-home PDF ticket and is available for selected events. Each eTicket PDF attachment represents an individual ticket to the show, with its own unique barcode that must be scanned for entry. If a customer purchased more than one ticket, the customer must print out and bring along each separate eTicket PDF to the event.

EasyTickets website allows any customer (registered or unregistered) to search for an event. In order to purchase a ticket, the customer should be registered with EasyTicket. The online purchasing is a 4-step process:

1) search for event or venue 2) select tickets 3) enter/register customer details (if unregistered) 4) payment

In order to register, customers provide their title, first name, last name, country, physical address, mailing address, phone number, email address and password. Customers cannot purchase a ticket without registration. In the last step, the customer needs to enter credit card number, expiry date and CCV for payment. 11486 Systems Analysis and Modelling / 6677 Systems Analysis and Modelling G Page | 2 The system can email printable tickets after successful payment. An SMS ticket can also be sent to the customers mobile phone. The system should generate an exception message if purchasing a ticket fails.

In addition to taking advantage of mobile computing, management also wants the new system to use other emerging technologies, such as cloud computing, big data and social networks for decision making and business process improvements as well as to provide quality services to the clients of EasyTicket.

Requirements:

1. Rich picture

a) (1 mark) Entities

b) (1 mark) Links between entities (including labels)

c) (1 mark) Concerns

d) (1 mark) Boundaries

e) (1 mark) A 1 paragraph description and explanation of the importance for one of the boundaries you have identified. This should clearly describe the meaning of the boundary in relation to the case study as well as why this boundary is important in relation to analysis of the case study.

2. System vision (3 marks)

Your report is expected to include a 1-page system vision that covers the following aspects:

a) (1 mark) Problem description

b) (1 mark) System capabilities - high-level requirements and constraints

c) (1 mark) Anticipated business benefits

3. Stakeholder analysis (6 marks)

Your report is expected to include a stakeholder analysis that covers the following aspects:

a) (2 marks) List of identified stakeholders, both those identified directly from the case study and those added based on additional research and assumptions, with a 1 or 2 sentence description for each stakeholder of the relevance to and role within the system. Remember that appropriate citations or reference to assumptions should be included.

b) (2 marks) Classification of all identified stakeholders according to the classifications that have been discussed in this unit

c) (1 marks) For one stakeholder that was identified from the case study, a 1 paragraph explanation and justification of their classifications

d) (1 mark) For one stakeholder that was added based on additional research and assumptions, a 1 paragraph explanation and justification of their classifications

4. Event table (6 marks)

Your report is expected to include an event table. This should cover all elements required in an event table and comprehensively cover only the most important and meaningful events and interactions for the system being described. As a rough guide, it is expected that there should be at least 10 important and meaningful events in your event table, depending upon the case study chosen and your additions based on research and assumptions. The event table should include the following elements:

a) (1 mark) Events identified

b) (1 mark) Event names and types

c) (1 mark) Event source

d) (1 mark) Event triggers and conditions

e) (1 mark) Event actions

f) (1 mark) Event outputs, which includes response and destination

Remember that trivial events such as log on, log off, etc are not important and meaningful at the analysis stage and should not be included in your event table.