SUMMER TRAINING REPORT

MULTIPLEX DATABASE SYSTEM Submitted in partial fulfillment of the requirements for the award of the degree of

Bachelor of Computer Applications To Guru Gobind Singh Indraprastha University, Delhi

Guide: Ms. Shilpa Taneja

Submitted By: Rahul Khanna (0556032008) Mayank Jaiswal (0566032008)

IITM
Nurturing Excellence
Institute of Information Technology & Management New Delhi-110058 Batch (2007-2010)
1

Certificate
We, 1.( Rahul Khanna- 0556032008) & 2. (Mayank Jaiswal- 0566032008) certify that the Summer Training Project Report (BCA-353) entitle MULTIPLEX DATABASE SYSTEM is done by us and it is an authentic work carried out by us at Institute of Information Technology & Management. The matter embodied in this project work has not been submitted earlier for the award of any degree or diploma to the best of my knowledge and belief.

1. Signature of the Student

2. Signature of the Student

Date:

Certified that the Project Report (BCA-353) entitled MULTIPLEX DATABASE SYSTEM done by the above students is completed under my guidance. Signature of the Guide Date: Name of the Guide: Designation:

Countersigned Director

ACKNOWLEDGEMENT

I express my heartfelt gratitude and privilege to acknowledge our esteemed guide Ms. Shilpa Taneja without whom this project could not have been completed. I thank her for her valuable suggestions. I also express my deepest gratitude towards the teaching staff and the fellow member who helped me to finish the task successfully.

Table of Contents

S No.

Topic

Page No

1 2 3 4 5 6 7

Certificate Acknowledgements List of Tables/Figures Chapter 1 Introduction Chapter 2 - System Analysis Chapter 3 - System Design SRS

2 3 5,6 7 17 24 47

List of Tables

Table No.

Title

Page No

2.1

Input / Output Data Description

4

22

3.1 3.2 3.3 3.4 3.5

Booking Table Login Table Movie Table Tickets Table Logical Database Requirements

26 27 27 28 55

List of Figures
Figure No. Title Page No

1.1 1.2 2.1 3.1 3.2 3.3 3.4

Waterfall Life Cycle Model Gantt Chart Block Diagram Use Case Diagram ER Diagram Of The Proposed System Level 0 DFD Level 1 DFD
5

13 16 19 25 29 31 31

3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.15 3.16

Level 2 DFD Login Form New User Form Operations Form Add Movie Form Book Ticket Form Select Seats Form Cancel Booking Form Cancel Seats Form Report Layout Flow Chart

32,33 34 35 36 37 38 39 40 41 42,43 44,45,46

Chapter 1
6

INTRODUCTION

1.1

General Description

A multiplex is a movie theatre complex with more than three screens. The largest of these complexes are sometimes referred to as a megaplex. The system is being designed to facilitate the members engaged in the booking tickets at multiplexes. The system has a wide application in the sector of multiplexes as it can provide help in various activities. Some of the merits of this system are: The system manages the whole database of the users. The system helps in reducing work load & pressure upon the employees. The system is highly accurate and less error prone as compared to manual system.
7

The system helps in a better way of management of multiplex ticket booking systems. The system saves lots of time and effort as compared to manual system. The system also helps in better storage and preservation of data and information. The system also helps in speedy retrieval and seeking of data with the help of queries. The system can develop and publish various data reports which can be used to carefully study the whole picture.

Overcome all the demerits of old manual system.

1.1.1 Organizational Objectives

To allow managers to reduce the work load of ticketing. Handling the ticket booking process. To manage the data of different movies. To control the ticket payment structure.

1.1.2 Organizational Structure

An organizational structure is a mainly hierarchical concept of subordination of entities that collaborate and contribute to serve one common aim. Organizations are a variant of clustered entities. An organization can be structured in many different ways and styles, depending on their objectives and ambience. The structure of an organization will determine the modes in which it operates and performs.

Organizational structure allows the expressed allocation of responsibilities for different functions and processes to different entities such as the branch, department, workgroup and individual. Individuals in an organizational structure are normally hired under time-limited work contracts or work orders, or under permanent employment contracts or program orders.

This software allows the user to maintain the profiles of individual student and teacher, maintain their attendance and it also maintains the fees structure.

1.1.3 Services Provided

This multiplex ticket booking system software provides various services to the user, mentioned below: A user account. It updates the new released movies and removes the current movies. This software is also used for current ticket booking, advance booking and cancellation of tickets booked earlier.
9

It also maintains the whole database of tickets.

1.1.4 Functions/Activities with respect to the proposed system

Multiplex Ticket Booking System:Level 1 Processes

Login:- The login process enters the user information such as user name and password. If the user is not registered, then the user is not allowed to move to Next Form. If he tries to do so an error message is displayed which says Wrong Username. We can also create a new user.

Movie Updation:- The user updates the new released movies and removes the old ones. Ticketing:- The user books the current available tickets for the customers, cancels the previously booked tickets, and advance books the tickets.

Level 2 Processes Login Add New User Movie Addition Movie Removal Book Ticket Cancel Ticket Details of upcoming movies.

10

1.2

SDLC Methodology

The Systems Development Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project from an initial feasibility study through maintenance of the completed application.

Phases of SDLC Methodology. Feasibility

The feasibility study is used to determine if the project should get the go-ahead. If the project is to proceed, the feasibility study will produce a project plan and budget estimates for the future stages of development.

Requirement Analysis and Design

Analysis gathers the requirements for the system. This stage includes a detailed study of the business needs of the organization. Options for changing the business process may be considered. Design focuses on high level design like, what programs are needed and how are they going to interact, low-level design and data design. During these phases, the software's overall structure is defined. Any glitch in the design phase could be very expensive to solve in the later stage of the software development. Much care is taken during this phase.

Implementation

In this phase the designs are translated into code. Computer programs are written using a conventional programming language or an application generator. Programming tools like Compilers, Interpreters, and Debuggers are used to generate the code. Different high level

11

programming languages like C, C++, Pascal, and Java are used for coding. With respect to the type of application, the right programming language is chosen.

Testing

In this phase the system is tested. Normally programs are written as a series of individual modules, these subjects to separate and detailed test. The system is then tested as a whole. The separate modules are brought together and tested as a complete system. The system is tested to ensure that interfaces between modules work (integration testing), the system works on the intended platform and with the expected volume of data (volume testing) and that the system does what the user requires (acceptance/beta testing).

Maintenance

Inevitably the system will need maintenance. Software will definitely undergo change once it is delivered to the customer. There are many reasons for the change. Change could happen because of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate changes that could happen during the post implementation period.

1.2.3 Proposed Methodology

Waterfall Model: This is the most common and classic of life cycle models, also referred to as a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase must
12

be completed in its entirety before the next phase can begin. At the end of each phase, a review takes place to determine if the project is on the right path and whether or not to continue or discard the project. Unlike what I mentioned in the general model, phases do not overlap in a waterfall model.

Fig 2. Waterfall Life Cycle Model

Advantages Simple and easy to use. Easy to manage due to the rigidity of the model each phase has specific deliverables Phases are processed and completed one at a time. Works well for smaller projects where requirements are very well understood.

and a review process.

Disadvantages Adjusting scope during the life cycle can kill a project No working software is produced until late during the life cycle.
13

High amounts of risk and uncertainty. Poor model for complex and object-oriented projects. Poor model for long and ongoing projects. Poor model where requirements are at a moderate to high risk of changing.

1.3 Data Collection

1.3.1 Data collection can be of two types Primary Data Collection Secondary Data Collection Primary Data Collection

1.3.1.1

In primary data collection, you collect the data yourself using methods such as interviews and questionnaires. The key point here is that the data you collect is unique to you and your research and, until you publish, no one else has access to it. The primary data has been collected through a personal interview of the manager of a multiplex.

1.3.1.2 Secondary Data collection Secondary data is data collected by someone other than the user. The Secondary data has been collected from the website

www.scribd.com www.wikipideia.com www.w3schools.com www.a1vbcode.com

14

1.4
1.4.1

Project Planning
Team with Module Description Chapter 1 ( INTRODUCTION) Mayank Jaiswal Chapter 2 ( SYSTEMS ANALYSIS) Rahul Khanna Chapter 3 ( SYSTEMS REQUIREMENT SPECIFICATIONS) Mayank Jaiswal & Rahul Khanna

1.4.2 Gantt Chart

15

16

Chapter 2 SYSTEM ANALYSIS

17

System Analysis It is the study of systems sets of interacting entities, including computer systems. This field is closely related to operations research. It is also "an explicit formal inquiry carried out to help someone, referred to as the decision maker, identify a better course of action and make a better decision than he might have otherwise made. The development of a computer-based information system often comprises the use of a systems analyst. When a computer-based information system is developed, systems analysis (according to the Waterfall model) would constitute the following steps: The development of a feasibility study, involving determining whether a project is economically, socially, technologically and organizationally feasible. Conducting fact-finding measures, designed to ascertain the requirements of the system's end-users. These typically span interviews, questionnaires, or visual observations of work on the existing system. Gauging how the end-users would operate the system (in terms of general experience in using computer hardware or software), what the system would be used for etc.

18

2.1 Block Diagram

The Block diagram given below depicts the basic flow of information in the System.

Operator

Id & password

Ticketing
Customer

View Operator Details Management

Movie Detail Management

Booking

Advance Booking

Cancellation

Add New Movies

Delete Previous Movies

Receipt

19

2.2 Description of the System

1. Login process In this process, operator can access the software by putting id and password. If id and password is correct he/she can access the software. 2. Ticketing In this process, the operator books the tickets for customers according to their preference. This process also includes advance booking and cancelation. 3. Operator Details This process includes various details of the operator i.e. name, operator id, address, e-mail id, contact no. 4. Movie Updation This process includes adding new movies and replaces the existing ones.

20

2.2.1 Processes and Input Output Identification

1. Login process Input: id, password. Process: Operator will enter his/her ID and password, if valid user then hell/shell be logged in and can now book tickets, cancel tickets, update the movies. Output: The operator now can perform the various operations i.e. booking, cancelation, updating and deletion of movies.

2. Ticketing Input: Selecting the movie, date, show timings. Process: Operator will select the movie, date, and its timings as per customers preferences. The operator will also select the location of the seat. Output: This process results into generation of a movie ticket. 3. Operator Details Input: The operator enters his/her details i.e. name, operator id, address, e-mail id, contact no. Process: In this process the operator has to fill his/her personal details to move to the next form. Output: The output of this process will update the existing operator database. The new entries will be saved in the operator database.

21

4. Movie Updation Input: The operator updates the new released movies. Process: The operator enters the new released movies and removes the old ones. Output: The new movie added is now available along with its date and show timings.

2.2.2 Input Output data description

INPUT/OUTPUT NAME Operator Details Customer Details Movie Details Ticketing Details DATA ELEMENTS operator_id , Password. Customer name, address, contact no, e-mail id. Movie name, date, show timings. Ticket id, Ticket number.

2.2.3 Identification & Description of Mathematical Procedures required

22

The mathematical procedures used will only be basic mathematical operations like sum, subtraction, multiplication and division which will be used to calculate the seats available for a show, etc. 2.2.3.1 Cost of Tickets: Economy Class (Rs. 100/Ticket) Cost of Ticket = Ticket + 3% Entertainment Tax

Silver Class (Rs.200/Ticket) Cost of Ticket = Ticket + 3% Entertainment Tax

Gold Class (Rs.400/Ticket) Cost of Ticket = Ticket + 3% Entertainment Tax

2.2.3.2 Offers: Combo Meal = No. of Tickets Purchased > 3

23

Chapter 3 SYSTEMS REQUIREMENTS SPECIFICATION (SRS)

24

3.1 Use Case Diagram

Login

View Operator Details

Add Movie

Operator Update Movie Customer Book Ticket

Cancel Booking

List of Upcoming Movies

Fig 3.1 Use case diagram

3.2 Database Description

25

3.2.1 Database Table Structure Bookings Field Type Size Description Constraints

Booking_id

Number

10

Booking id (Primary Key)

Not Null

Movie_id

Number

10

Movie id (Foreign Key)

Time_Slot

HH:MM:SS

Timings of the show

Audi

Varchar

Name of the audi

Tickets Booked

Number

Long Integer

Number of tickets booked by the customer

Seats

Number

60

Description of the seat

M_name

Varchar

10

Name of the movie

Login
26

Field

Type

Size

Description

Constraints

User_id

Number

10

Id of the operator (Primary Key) Password of the operator

Not Null

Password

Varchar

10

Movie Field Type Size Description Constraints

Movie_id

Number

10

Id of the movie (Primary Key) Name of the movie Category of the movie Language of the movie Name of the Audi Starcast of the movie

Not Null

M_name

Varchar

20

Type

Varchar

Language

Varchar

15

Audi

Varchar

10

Starcast

Varchar

15

Tickets

27

Field Ticket_Id Transaction_Id M_date Movie_id Audi Seat_Num Amount

Type Number Number DD-MM-YY Number Varchar Varchar Float

Size 10 10 8 10 8 8 5

Description Id of the ticket (Primary Key) Id of the transaction Date of the movie Movie id (Foreign Key) Name of the audi Number of seats

Constraints Not Null Not Null

Ticket id

Amount to be paid by the customer

Transaction_I d M_date

Operator id

Passwor d

Book
1 M

Ticket

M_name

Operator

Cancel
1

Seat_Num

Reserv ed For
1

Name Add
M M

Movie id
M

Movie

Type Language Audi No.

Remov e

3.2.2 ER Diagram
28

Starcast

3.3 System DFD

A DFD is a graphical representation that depicts information flow and the transforms that are applied as data move from input to output. The basic form of a DFD is also known as a data flow graph or a bubble chart. DFD may be used to represent a system or software at any level of abstraction. DFDs can be partitioned into levels that represent increasing information flow and functional detail.

DFD Notations

It represents a process or transform that is applied to data.

: It represents data store-stored information that is used by Software

29

: It represents one or more data items.

: It represents external entities.

Level Zero DFD / Context Level DFD

Verify

Verified Movie Details

Operator

Opt_ID & Password Booking Details

Multiplex Database System

Tickets

Customers

Movie Details Details Booking Details Save Details

Level Verify Details1

Details

DFD

Save Details Details

Verify Details Details Opt_ID & Password

Operator

1 Login

Verify Details

Save Details Details

Operator Details

Select Option

2 Movie Details Maintenance

3 Booking Details

Select Option

4 Ticketing

30
Booking

Movie

Ticket

Level 2 DFD

2.1 Movie Updation Process

New Movie Details

2.1 Add Movie

New Movie Details

Operator
Exists Movie

Movie

2.2 Remov e Movie

Save

Exists Movie

Save Changes

2.3 Update Movie

Operators can add/remove a movie and the changes will be made in the movie table.

31

1.1 Ticketing

Movie Details

1.3.1 Book Ticket

Movie Details

Operator
Ticket

Customer

1.3.2 Cancel Ticket

Movie Details

Movie Details

Operators can Book/Cancel a seat and the changes will be made in the ticket table along with a receipt generated

32

3.4 Proposed System Design (GUI)

3.4.1 Form Layout

Login Form

Login

Login

User Name:

Password:

Login Exit New User

Validations

33

1. If a user wants to enter the system, he/she must be registered to use the system. 2. Password and username provided by the user must be correct.

New User Form:

New User

Add User Name:

Password:

Confirm Password:

Add User

Exit

34

Validations
1. No two users can have the same username.

2. Both the passwords should match in order to add a new user.

Operations Form

Operations

Operations

Add Movie

Book Ticket

Change Movie

Cancel Booking

Remove Movie

Exit

35

No Validations

Add Movie Form

Add Movie

Name:

Type:

Language:

Audi:

Star cast:

Add

36

Exit

Validations 1. Only one movie can be added at one time. 2. The multiplex can contain a maximum of four movies. Therefore to add a movie after 4 movies the user may have to remove a movie first. 3. One Audi can contain only one movie. Book Ticket Form
Book Movie 1 Movie:

Date:

Time:

Continue

37

End

Validations 1. A user can book tickets for one week in advance. 2. No booking can be made for previous dates and time.
Select seats 1

3. User can select movies only between the movies listed in the list box. Select Seats Formclass @100 Ecomomy
A B

Billing Amount

Economy Class

Silver class @200

C D

Silver Class

Gold Class
Gold class@400
E F

Total Amount 38 Cancel

Confirm & Pay

Cancel Booking Form

Cancel Booking

Movie:

Date:

Time:

Continue

End

39

Validations 1. Only previously booked tickets can be canceled, check boxes associated to vacant seats get disabled. 2. Tickets with previous dates and time cannot be cancelled.

Cancel Seats Form

Cancel Seats

Ecomomy class @100

A B

Billing Amount

Economy Class

Silver class @200

C D

Silver Class

Gold Class
Gold class@400
E F

Total Amount

Confirm & Return

Cancel 40

3.4.2 Report Layout

Economy Class Ticket

41

Silver Class Ticket

Gold Class Ticket

42

43

3.4.3Flowchart

Start Enter Username and password

No

Vali d

Yes
Movie Details Operati on Selecte d Add/ Remove Movies

Add Movie Movie Details

Book Ticket

Update Movies

A Enter Customer Details

Calculation

Report

Stop 44

Add Movie s

Select the Audi for new movie to be added

Input all the details for the movie

Save Records in the database

45

Change Movie

Optio n Select ed

Remove Movie

Select the movie to be changed

Select the movie to be removed

Input all the details of the new movie

Save changes in the database

Save Records in the database

46

SRS Documentation
1. Introduction A software requirements specification (SRS) is a complete description of the behavior of the system to be developed. This Software Requirement Specification is written accordance with the IEEE STD 830-1998 model.

1.1 Purpose This SRS Document contains the complete software requirements for a College Internal Assessment System (CIAS) and describes the design decisions, architectural design and the detailed design needed to implement the system. It provides the visibility in the design and provides information needed for software support. The intended audiences for this document are the development team, testing team and the end users of the product

1.2 Scope The software product College Internal Assessment System will be an application that will be used for maintain the records in an organized manner and to replace old paper work system. The application will manage the information about internal marking system in a college. Reports will also be generated.

1.3 Definitions, Acronyms and Abbreviations Following abbreviations have been used throughout this document: IEEE : The Institute of Electrical and Electronics Engineers, Inc. SRS : Software Requirements Specification
47

CIAS : College Internal Assessment System

1.4 References

www.iitm.ipu.ac.in http://www.scribd.com/

1.5 Overviews This document has been prepared in accordance with the IEEE STD 830-1998, IEEE Recommended Practice for Software Requirements Specification. [IEEE 830-1998 (1998)]. It provides the information of Product perspective, Product functions, User characteristics, Constraints, Assumptions and dependencies and specific requirement.

2. The Overall Description This section of the SRS describes all general factors of the product and its requirements.

2.1 Product Perspective The application will be a window-based, self contained and independent software product.

Front end client application (with data entry/update/delete/ view and reporting facility)

Backend Database

48

2.1.1 System Interfaces None.

2.1.2 User Interfaces The application that will be developed will have a user friendly and menu based interface. Following screens will be provided: A login screen for entering the username and password, so that the authorized operator

can have an access without any problems. There will be a screen which will be displaying the major tasks that the system will be

performing i.e. add movies, change movie, update movie, book tickets etc. All the major tasks mentioned above will have their separate forms and will perform the

desired actions.

Following reports will also be generated: Ticket

2.1.3 Hardware Interfaces Screen resolution of at least 800 X 600required for proper and complete viewing of

screens. Higher resolution would not be a problem Support for printer (dot-matrix/desk-jet/inkjet, etc. any will do) that is, appropriate

drivers are installed and connected printer will be required for printing of the reports. Standalone system or network based not a concern, as it will be possible to run the

application on any of these.

49

2.1.4 Software Interfaces Any window based operating system can be used (windows 95/98/2000/XP/NT) Oracle as DBMS for database. Future release of the application will aim at upgrading

oracle 8i as the DBMS. Visual basic 6 for coding, developing the software.

2.1.5 Communications Interfaces None.

2.1.6 Memory Constraints At least 64MB RAM and 2GB space on hard disk will be required for running the application.

2.1.7 Operations The product release will not cover any automated housekeeping aspects of the database. The DBA at the client site (i.e. the hospital) will be responsible for manually deleting old/non required data. Database backup and recovery will also have to be handled by the DBA. However, the system will provide a RESET SYSTEM function that will delete (upon confirmation from the administrator) all the existing information from the database.

2.1.8 Site Adaptation Requirements The terminals at the client site will have to support the hardware and software interfaces specified in the above sections.

50

2.2 Product Functions The system will allow access only to authorized operators entering the appropriate password. A summary of the major function that the software will perform are as follows: A login facility to allow only the authorized operators to have an access to the software

system. This prevents the unauthorized operators to misuse the software. Operator (as Data Entry Operator) will be able to add movies, change movie, remove

movie and book tickets.

2.3 User Characteristics Educational level: At least graduate should be comfortable with English language. Experience: The operator should be well versed about the nature and the processes of the

multiplex. Technical expertise: should be comfortable using general purpose applications on a

computer.

2.4 Constraints GUI is only in English. Login and password is used for identification of operator and there is no facility for

Guest.

2.5 Assumption and Dependencies Nil

51

2.6 Apportioning of Requirements Not required.

3. Specific Requirements This section contains the software requirements to a level of detail sufficient to enable designers to design the system and the tester to test that system.

3.1 External interfaces This interface will be the actual interface through which the user will communicate with the application and perform the desired tasks. The following screens will be provided:

Login Screen: The login screen will be the first screen that a operator will face. This screen is responsible to allow the authorized operator to access the application. It will accept the username and password from the operator and verify it. If the username and password match, then the operator will be allowed an access to the application else and error will be raised i.e. ACCESS DENIED. The fields available on this screen will be: Username Password

52

Menu Screen: This screen will display 6 small screens inside of it which will perform the major tasks. In the menu screen we can select any of these six screens and perform the desired actions. The six screens will be Add Movie, Change Movie, Remove Movie, Book Ticket, Cancel Booking, Exit.

Add Movie Screen: Name Type Language Audi Starcast

Change Movie Screen: Change the movie

Remove Movie Screen: Delete the movie

Book Ticket Screen: Movie Name Date

53

Time

Cancel Booking Screen: Movie Name Date Time

3.2 System features

Description The system will maintain all the information regarding the details of the movie. This system will also allow the operator to add/delete/update the movies .

Sequencing information After a successful login the operator will be allow to choose from the options such as Add Movie, Change Movie, Remove Movie, Book Ticket and Report generation.

3.3 Performance Requirements None

3.4 Design Constraints None

54

3.5 Software System Attribute 3.5.1 Security The application will be password protected. The operator will have to enter the correct user name and password in order to access the software.

3.5.2 Maintainability The system will be designed in a maintainable order. The system can be easily modified and renewed according to the need of the user.

3.5.5 Portability The system will be easily portable on any windows based application that has oracle installed.

3.6 Logical Database Requirements The following information will be stored in the database:

Operator Details Movie

operator_id , Password, Name, date , time, audi, movie id.

Customer Details

Name, Address, Contact Number.

3.7 Other Requirements None.

55