CIS267 Assignment

Running Head: VB SCRIPT DESIGN FOR TICKETING SYSTEM

2

VB SCRIPT DESIGN FOR TICKETING SYSTEM

VB Script Design for Ticketing System

Student Name

Course Number

Course Title

Professor

College Affiliation

Date VB Script Design for Ticketing System

Introduction

Menu driven system for this Ticket Seller Company will involve a number of functionalities and interfaces that are carefully designed to ensure best user experience. The system involves menus for reporting, available or all tickets and sell tickets. Users of the system will also have to enter details such as seats, dates, prices and games. Forms will be created for the home page that contains the main menu of the system. Other forms include, form for filling in selling ticket details such as prices and dates, form for showing and selecting the available tickets as well as form for generating reports. The forms will have buttons, combo boxes and select inputs whose functionality will be defined by the VB script codes to be discussed later. This paper provides a detailed discussion of the system design with data flow, programming conventions and graphical rendering.

User Interface Components and Design

The ticketing system will be designed and organized to allow efficient storage of scripts. The user interface will also consist of script documents such as forms and reports. These documents will also contain script forms, subsystems and script units. These scripts will be run or executed by clicking a button in form of a menu item at the home page screen. In addition, the scripts can be run from the button at the toolbar or even use the system menu to run the scripts.

Forms: forms will be used in the user interface for populating the database (Berardi, D., Calvanese, D., & Degiacomo, G., 2005). For instance, the system will have a form for selling tickets. In this form, the customer details will be filled to the database through the form with the input elements for date, games, prices and number of seats. The forms can also contain sub forms for collecting other details that may not be captured in the main form. An example of sub form is the form to capturing customer details and populating the customers table. After the details of the tickets have been filled, the user will be required to register their details in the customer database through a sub form in the selling tickets main form.

Reports; this user interface component is important for obtaining the summary from the various tables in the database. A certain criteria will be applied to query the system database and allow generation of certain level of data that can be presented in report form and be printed. In fact, reports are one of the major business requirements for the system. To design these reports, a hidden query will be used such that when a querying criteria is invoked, the system selects the required data and displays in a report form view and also allow for printing.

Programming conventions

The ticketing system contains several subsystems that will be connected logically to ensure the entire ticketing functionality is achieved. One of the programming conventions to be used is to reuse the scripts by attaching script documents to different subsystems with same requirements. Scripts will also be organized into several independent projects so as to make management easy for the system functionalities and procedures. Script forms and script units will therefore consist of procedures and functions that will be called automatically within the Ticketing System Application.

Logical flow of activities

Setup game and ticket; at this subsystem, the system administrator will set up the games for users to select when buying tickets. A user will access the homepage menu through the system, login in with their details. If the user credentials match those assigned for the administrator role, then they have an option to set a game or ticket. The will enter details such as dates, games, prices and seats available. They then click on the “Save” button to update the details in the database. The customers will then view these details when buying tickets so that they select the preferred game for purchasing tickets (Berardi, D., Calvanese, D., & Degiacomo, G., 2005).

Sell tickets; this subsystem involves selection of game and seats before paying for the ticket. A user will access the homepage with the main menu through the system. They will then click on the “sell tickets” to access the form for selecting the tickets they prefer. This form will be simple with basic data columns like date, game and seats. Then after filling the form, users will have to click on “buy ticket” to make the changes effective and post in the database.

Reporting; reporting will have two functionalities or reports as required in the business requirements. The users will access the form for selecting the type of report they wish to print from the main menu. The menu on this form will also contain dropdowns for selecting the range of dates, say last week, today, next week e.tc. After selecting the report type and date range, they will click on “print report” to view and print the report.

Use case

The following diagram shows use cases for users interacting with the system at different sub systems;

References

Berardi, D., Calvanese, D., & Degiacomo, G. (2005). Reasoning on UML class diagrams. Artificial Intelligence, 168(1-2), 70–118. http://doi.org/10.1016/j.artint.2005.05.003