Ticket Seller

Part 1: Design Phase

This is the first of a two-phase assignment.  For this phase of the assignment, students will submit a design of their application.  There is no coding required for this phase of the assignment.  Students will design an application for the following business description:

Ticket Seller is a new startup ticketing company. It has contracted you to develop a Visual Basic system to sell and print tickets for your local basketball arena. The system will provide sales in a Microsoft Windows environment at the ticket office. Management will use your program as a prototype for a future global ticket system. Create your own sample data for the designs. Use your creativity in this design.

This application will be menu-driven. Students will design the application according to the following organizational system:

  • A main menu system with the following submenu systems:

i.   setup game / ticket menu.
ii.  sell tickets menu.
iii. reporting menu.

a. Create a setup subsystem to enter:

i.   games.
ii.  dates.
iii. prices.
iv. seats.

b. Create a sell subsystem to:

i.  display available tickets.
ii. sell tickets and take them out of the available ticket pool.
iii. keep track of the total sales.
iv. provide a group discount (10 or more tickets for 1 transaction – 10% off).

c. Business requires two (2) new screen reports to be generated from the ticketing system. The first screen      report shows the daily activity, which shows the number of tickets sold and revenue generated. The second    screen report is weekly results. It has the total tickets sold, the total revenue generated, and tickets available  for sale. Create a report subsystem for daily and weekly sales.

The following items must be submitted for this phase of the assignment

  1. A written paper (at least two pages 1.5 line spacing) describing how the application will be designed

a. Include a cover page
b. Include details about components that will be used in the UI design for each subsystem
c. Programming conventions that will be used in the program code
d. Describe logical flow of subsystems

i. Steps user will execute to accomplish tasks in each subsystem
For example: If a user is in the sell ticket subsystem, what are the required tasked the user must perform to purchase ticket(s)

e. Graphical rendering (such as flowchart, use case), of the application components and interactions.


Part II: Coding Phase

The next step in the process is to take the design you created in the last phase and implement it into Visual Basic. First create the forms and drop the objects into the form. Next write the code behind the scenes to create the menus. Remember, you are only to demonstrate the menu function and not create a major database to track sales.

Create a Windows application to demonstrate the menu flow, include the following elements:

  1. Create a main menu system for the:
    1. setup game / ticket menu.
    2. sell tickets menu.
    3. reporting menu.
  2. Create a setup subsystem to enter:
    1. games.
    2. dates.
    3. prices.
    4. seats.
  3. Create a sell subsystem to:
    1. display available tickets.
    2. sell tickets and take them out of the available ticket pool.
    3. keep track of the total sales.
    4. provide a group discount (10 or more tickets for 1 transaction – 10% off).
  4. Business requires two (2) new screen reports to be generated from the ticketing system. The first screen report shows the daily activity, which shows the number of tickets sold and revenue generated. The second screen report is weekly results. It has the total tickets sold, the total revenue generated, and tickets available for sale. Create a report subsystem for daily and weekly sales.
  5. Provide the Visual Basic code for the entire subsystem.
Field of study: 
Date Due: 
Saturday, November 24, 2018

Answer

Part 1: Design Phase & Part II: Coding Phase

Ticket Seller

Price : $19

Pay $19 to view and download this answer instantly
Click here to pay Money Back guarantee