event mgmt

4
Purpose: Event Management System will aim at providing an automated one stop solution for booking, cancelling or modifying of tickets for different events by registered users. An agency manager will be responsible for maintaining the list of events and users registered with the application. Actors: User: Registering with the application, Booking/Cancelling/Modifying tickets Agency Manager: Approving/Rejecting new user applications, E-mailing the applicants regarding status of their applications, maintaining a list of events for which tickets can be booked. Data Tables Required: CUSTOMER_DETAILS MemberID(primary key) City State Zip Phone BirthDate CCType CCNumber Password Email ID EVENTS_DETAILS

Upload: rahul-rulzz

Post on 07-Jul-2016

214 views

Category:

Documents


1 download

DESCRIPTION

oioui

TRANSCRIPT

Page 1: Event Mgmt

Purpose:

Event Management System will aim at providing an automated one stop solution for booking, cancelling or modifying of tickets for different events by registered users. An agency manager will be responsible for maintaining the list of events and users registered with the application.

Actors:User: Registering with the application, Booking/Cancelling/Modifying tickets

Agency Manager: Approving/Rejecting new user applications, E-mailing the applicants regarding status of their applications, maintaining a list of events for which tickets can be booked.

Data Tables Required:

CUSTOMER_DETAILS MemberID(primary key)       City                      State                    Zip                       Phone                 BirthDate           CCType              CCNumber        PasswordEmail ID          EVENTS_DETAILS

EventNumber(primary Key)     EventDescription  EventDate        Venue            Category        Status            Available Tickets    

ORDER_DETAILS

Page 2: Event Mgmt

Order Number(primary Key)               Event NumberMemberID                      Date                                             Venue                             TicketPrice                     Quantity  Status

Application Specific Details

First screen presented to the user should be the login screen. It should contain a link for New User Registration. Clicking on the link user should be redirected to the Registration subflow.

In Registration subflow, capture all the user information listed in the Customer_Details table through a screen flow using tabbed navigation harness.

Route the work object to the Agency Manager for approval/rejection of the registration request. In either case, send appropriate mail to the customer (to simulate this, ensure that the Agency Manager receives this mail).

In the event the Agency Manager approves the request, the Customer_Details table should be appended with the new user details.

If the user is an existing one, he should be presented with the options for placing or modifying/cancelling his orders based on the unique Order ID entered by him.

In case of placing new order, show the user the list of events using an embedded selectable list view report.

Based on the event selection, show the discounted price to customer based on his customer type (CCType). Implement this using SOAP protocol and decision logic. If the price is acceptable to the customer, route the work object to the payment workbasket.

In case of cancellation / modification, display all the orders in an embedded selectable list view and prompt the user to select the desired order. Route the work object to payment workbasket.

Page 3: Event Mgmt

In either of these operations, update the tables Event_Details and Order_Details to maintaining consistency with respect to available seats, deleted/modified orders etc.

Create a separate work pool for Agency Manager which will allow him to add/delete/modify event details in the Event_Details table.