CERTIFICATE

A

ONCOMPUTERIZED RAILWAY RESERVATION SYSTEM

Submitted in partial fulfillment of the requirements for the award of the Degree of Masters of COMPUTER SCIENCE

SUBMITTED TO

Department of Computer Science

MAHARSHI DAYANAND UNIVERSITY, ROHTAK

STUDY CENTER: SUBMITTED BY:

IGC SANJAY KANT (27081396)

MEERUT (U.P.) SANDEEP DUA (27081398)

CODE- 08616

VISHWAS KR. SHARMA (270831399)Whats In The Project?

Title (cover page)

Title of the Project

Contents

Certificate from Study Center

Acknowledgement

Student Profile

Introduction

Existing System with Limitations

Problem Analysis

The Problem

Identify preliminary solutions

Project Analysis

Cost benefit analysis

Feasibility Study

Project Design

System Analysis

Design Hints & Guidelines

System Design & Development

System Design

System Development

Data Structure Diagram

Tables Description

Coding & Module Specification

Development Environment

Module Description

System Evaluation and Testing

System Implementation

System Maintenance

System Documentation

The program under Visual Basic Environment

GLOSSARY

CONCLUSION

BIBLOGRAPHY

I take this opportunity to express my sincere thanks and deep gratitude to all those people who extended their wholehearted co-operation and their help for me in completing this project successfully.

Many people have helped to create this project and each of their contribution has been valuable. It took me almost one & half month long to conceive, develop, program and explain the various functions contained in the project.

I would like to thank Mr. RAMAN BATRA IGC Meerut for providing me an opportunity to give the information of these organizations.

At last but not the least I give my hearty thanks to my family members and well wishers who took great pains to boot up my morale always.

DATE: 14-06-2004

SANJAY KANT , SANDEEP DUA , VISHWAS KR. SHARMA

CERTIFICATEIt is to certify that the project work titled COMPUTERISED RAILWAY RESERVATION, which is being submitted by me in partial fulfillment of the requirement for the award of the Degree of M.Sc. (Computer Science) of Diploma Name in the Directorate of Distance Education is an authentic work carried out by me at IGC Meerut under the supervision and the guidance of SH. Raman BatraThe matter imbedded in this project work has not been submitted earlier for the award of any other Degree or Diploma.

Signature & Name of the Study Center Head)

Mr. Raman Batra

IGC (Center Code 08616)

Meerut

Signature and Name of Supervisor)

Mr. Raman Batra

Signature of Student)

SANJAY KANT ,

SANDEEP DUA ,

VISHWAS KR. SHARMA

INTRODUCTION

ANALYZE THE PROBLEMS

The next task is to identify problems. Problem analysis is a difficult task.

Let me give you an example.

Think of any problem you have (it could be traffic jams or lack of motivation in your work group or anything else) and state it in not more than 20 words. Write it down on a piece of paper.

It has been seen that most people would have used the words we need to or we want to in the statement of the problem. Can you see the common pitfall? You are not stating the problem but the possible solution.

So to state a problem correctly, we should first be able to identify and define a problem.

WHAT IS A PROBLEM?

A problem can be defined as an undesirable condition or situation that prevents a business or system from achieving its goals. For example, delays in delivering customer orders would be a problem because it would prevent the Sales system from achieving its goal of customer satisfaction.

Now that we know what a problem is, let us look at the difference between a problem and an opportunity. We have defined a problem as an undesirable condition or situation that prevent a business or system from achieving its goals.

An opportunity, on the other hand is a chance to improve the system even though the existing system is performing acceptably.

The best example of an opportunity is cost cutting. No matter how well a business may be performing, management will always be receptive to cost cutting. Cost cutting, however, is not a problem but an opportunity to make the system more effective.

It is important to clearly understand the difference between the two because many users and some analysts get caught up in satisfying opportunities when they should be concentrating only on the solutions to problems.

Now that the problem has been defined and identified, the next thing to do would be to learn to identify the cause and the effect of a problem. The visible problem may just be the effect of another deeper problem or it may be the cause of a potentially major problem. Dig deep into problems and try to break them up into the lowest level. This is called causal analysis.

Look at the figure in the corresponding slide show.

Go step-by-step.

STEPS 1Identify the causes of the problem. What situation has led to the problem?

STEPS 2

Identify the negative effects of the problem.

If you find that the effect is due to another problem, repeat steps 1 and 2.

This may seem simplistic to you, now but it is critical for you to identify the correct cause of the problem.

IDENTIFY PRELIMINARY SOLUTIONS

After identifying the root causes of all the problems in the current system, the next step is to try and identify some preliminary solutions.

Please note the key word here is preliminary.

The solutions you will try to identify will only be possible solutions and you will not evaluate their feasibility at this stage.

The technique of brainstorming i.e. a group of persons sitting together and throwing out ideas is very useful here.

Many people think that brainstorming is a haphazard and unstructured methodology. However, if done correctly and in a disciplined manner, it is a very important tool for generating solutions to problems.

Remember to allocate the recording of ideas to one person. All the members of the group should throw out their ideas in a specified time interval and all of them should be recorded. No idea is outlandish or infeasible or impractical at this stage. Only after all the ideas have been recorded, they can be analyzed.

CONFIGURATION

HARDWARE SPECIFICATION: -

Processor

:PIII- 850 Operating System

:Windows 98 Hard Disk

:40 GB RAM

:128 MBSOFTWARE SPECIFICATION: -

Front End

:Visual Basic 6.0 Back End

:Oracle Feasibility study

Feasibility study before development or customization of software we think following of the major points, which includes following: -

a) Economical

b) Technical

c) Duration

Economical

This study about the software basically give the suggestion like if we develop a software for our organization than how much it will forfeitable, workable as well as economical. If we developing a software which very economical but not profitable there it is also wrong decision. So for we economical study about the system table following of the point.

How much costing of the software?

What is the output of the customization?

What are the advantages in c0ompression manual we check

whether it is time or not?

Whether it is use friendly or not?

It is mountable for long term.

Understanding about the software

Corrective of software.

TechnicalWe also consider some technical points about development of software.

We see whether the software is reliable or not.

Whether it is work time for long time or not.

What are the languages as well as OS is used for development of software.

It provides security or not.

Software is reusable or not.

Software is updated or not. Software is flexible or not whether software can maintain.

DurationIt is also a major point when we develop software. We also consider about time, how much time software place to complete because for a big organization time factor is money for full successful of the software also Tax some times so we have consider from starting to last that means beginning to software.

COST & BENEFIT ANALYSIS In developing cost estimates for a system, we need to consider servable cost elements. Among them hardware, personnel, facility, operating, & supply costs.

Hardware CostHardware cost relate to the actual purchase or lease of the computer & peripherals Ex. Printer, disk, floppy drive, the best way to control for this cost is to treat it as an operating cost.

Personnel Cost

This includes staff salaries & benefits (health insurance, vocation time, sick pay etc.) as well as pay for those involved in developing system. Costs incurred during the development of a system are one time costs & are labeled developmental costs. Once the system is installed the costs of operating &maintaining the system become recurring costs.

Facility CostsFacility costs are expenses incurred in the preparation of the physical site where the application or the computer will be i operation. This includes wiring, flooring, acoustics, lighting & air conditioning. These costs are treated as one time costs.

Operating Cost

Operating costs include all costs associated with the day to day operating system. The amount depends on the number of sifts the nature of the application & the caliber of the operating staff. There are various ways of

covering operating costs to overhead. Another approach is to change each authorized user for the amount of processing they request from the system. The amount charged is based on the computer time, staff time & the volume of output produced.

Supply CostThese costs are variable costs that increase with increased use of paper, ribbon, disks & the like they should be estimated & include in the overall cost of the system.

Equipment CostEquipment costs include rental & annual deprecation of any equipment such as typewriter, copies, computer terminals & microcomputers used in connection with the system. Other costs associated with the equipment, such as insurance & maintenance should also be included.SYSTEM ANALYSIS

SYSTEM

A system can be defined as A set of arrangement of elements that are organized to accomplish some method, procedure or control by processing information. 0System Analysis stages down the broad frame work of strategy 0stage into its minute details. This is the stage where intensive user interaction assumes a lot of importance.

System DevelopmentDevelopment Phase, translates a set of requirements into an operational system that we call Software. At early stages of hardware development a hardware engineer does not reach for a soldering iron, similarly the Software

engineer should not reach for the compiler. Design is accomplished first.

The first phase of development concentrates on design. The design phase for software with a description of architecture and data design. That is a modular structure is developed first, interfaces are defined and data structure is established. Design criteria are used for the assessment of quality. This preliminary design step is reviewed for completeness and tractability to software requirements.

Procedural aspects of each modular component of the software design are considered next, and is following by the CODING the generation of program using an appropriate programming language or CASE tool occurs after the design is complete. Software engineering methodology views coding as a consequence of good design. Code is then

reviewed for style and clarity, but should otherwise be directly traceable to a detailed design description.

DETAILED ENTITY RELATIONSHIP DIAGRAM

Identification of all the Entities of importance for which data need to be stored and defined their relationship with each other was a major task at this level. All the identified entities were mapped on a E-R-diagram. It is of utmost importance to cover all the necessary entities and defined their relationship with each other correctly because any errors at this stage would result in the reworking in the further stages.

Unique Identification, UID

A unique identification is required to be identified and associated with each other at this stage.

Function Hierarchy

Function hierarchy Is used for grouping related functions under a parent function. The hierarchy is balanced so that all elementary functions comes in the same level of hierarchy. A good hierarchy drawn at this stage helped in menu generation at a later stage.

00

The Basic Objective

The basic objective of the system design was the system being developed should be able to fit into the existing system, that is it become a part of the system and it should not lead to any changes which can adversely affect the existing system. The hospital having many activities which effect one another so the approach of computerization of hospital is generated for the simplification of data handling.

The approach would bring in the following benefits

Standardization of the methods and procedures.

Availability of information centrally.

Minimizing future maintenance requirements.

Reduction in the learning process for new personal.

Packaged systems

The systems would have the following features Completely menu drive interface with the provision of initiating even the batch jobs by the user himself.

On Line help

Strong documentation

Validation checks done by the system itself

Minimization of input to the system to produce maximum output.

DESIGN OF THE SYSTEM

Designing is the most important part of the software development. It requires a careful planning and logical thinking on the system designer. Designing a software means to plan how the various parts of the software are going to achieve the desired goal. It should done with the utmost care because if this phase contains any errors then that will be going to affect the performance of the system, as a result it may take more processing time, more coding, extra work load etc.

As the software is to be designed in MS-ACCESS RDBMS, the concept of the database is must for quality designing. It will be designing of the database, designing of forms, designing of reports.

Separate tables have been created for each entity of the system. In order to make the response time negligible, all the tables have been created in the Memory File System. Moreover indexes have been created on the tables in the number of records have been made random.

DESIGN GOALS

Following goals were kept in mind while designing the new system

Another objective is to reduce the manual work required to be done in the existing system, thereby avoiding errors inherent in the manual work and hence making the outcome consistent and correct.

The important objective of the system is to provide good and reliable information services to the top management, to take major decision which play a key role in the growth of any business concern. As an patient comes, this is well understood and foreseen right from the beginning of the design o he implementation phase of the system.

Due to the fast changes in technology, the computing speed of the machine has grown very high, also the number of man-hour spent on the mundane jobs in the hospital can be drastically it Menu-Drive. This in turn helps the very first used who is unaware of the system to use it with ease.

The next objective is that it should be able to interact with the other systems. There are many patients in all over the India or World, so it must be possible to exchange information between different department and any other services in the hospital. This gives the way for having an close system which is the plug and play technique. This makes system more effective in understanding information which is easy to handle. This makes the system compatibly and easy to integrate into any other system. With a view of future expansion of hospital, maintenance and enhancement expected can easily be incorporated in the system.

Ultimately profit is what expected from any organization, a cost effective, reliable and understandable system was chosen with the view of opinion use in effect.

DESIGN OVERVIEW

The design stages takes the final specification of the system from the analysis stages and finds the best way of fulfilling them, given the technical environment and previous decision on required level of automation

The system design is carried out in two phases

Architectural Design Detailed Design

ARCHITECTURAL DESIGN

The high level design maps the business system described in the program requirement specification to logical data structure, it involves:

Identification of the entities that constitutes the systemAll the entities related to the module were identified, checked and consolidated

Identifying the RelationshipsThe relationships between the entities, within and outside the system were identified.

Attribute definitionThe pertaining of the entities was identified and their field characteristics were specified.

NormalizationThe entities were normalization, after first and the second normalization was achieved for all the entities.

Interface

Interface with the other systems were done and attributes related to external entities identified.

DETAILED DESIGNThe low level design maps the logical model of the system to a physical database design.

Table Mapping The Table was created for the system using the design view, which is the part of the MS_ACCESS. This has provision to create the entities and attributes into the Tables. The name of the entity is taken as the table name.

Default Database Design

In Access we can create the tables very easily. The tables divide into two parts. These names are as follow: -

ROWS

COLUMNSThe steps involved here were1. Generation of table

2. Check Validation Rule

3. Check Validation Text

4. Primary Keys

5. Unique Keys

6. Foreign Keys

Relationship

Ms-Access allows many types of relationship between the tables. These relationship names are as follow: -

One to One Relationship

Many to One Relationship

Many to Many Relationship

Program specificationsThe program specifications were written for the master, transactions, reports and queries. The logic for each field, block and form were written so that anyone who does not know the system will be able to code the logic. Field validations and user-friendly error messages were written as part of the program specification.

FRONT END & BACK END USEDWINDOW 98 used as PLATFORM

Windows 98 is latest version of windows and also GUI. This is best then another Operating system and easy.

Windows 98 has come up with another bonanza, that is, Network Communication with other users. The users can connect with other users to share data files and peripheral devices, like Printers.

The Communication tools of Windows 98 include E-Mail and connection to Internet.

VISUAL BASIC used as FRONT END

Visual Basic uses front-end programming because VB use Back end as like MS-ACCESS, ORACLE, FOXPRO and any other Database.

In VB we can use easy database connectivity and design the Form, Report, and others MDI applications with the help of Database.

VB facility the database controls which helps the changing, modifying, deleting and adding facility in database with the help of command buttons and controls.

VB is used for see the Data in many modes such as with the help of MSFlexiGrid Controls, Textbox, Combo box, List box, Image, Picture control and other.

Visual Basic gives the different types of accessing the Database (RDO, ADO and DAO)

Visual Basic is complete programming language that supports programming constructs for looping, decision making and efficient processing. These constructs include

For.next

Do.loop

Selectcase

Withend with

If.then.else

Visual Basic helps of creation Menus, Master-Details Form.

MS-ACCESS 2000 used as BACK END

Ms-Access is a database and partially RDBMS. In Access we can easily create Database design and give the validations. Access allows the many types of relations between the tables.

Access used as Backend with the Visual Basic. Access allows creating the Primary Key, Foreign Key and Unique Key. In Access we can store the data in to the table for using the wizard options.

DATA DICTIONARY

Data dictionary is a structured repository of data about data. It is a list of terms and their definitions for all data items and data stores of a system.

The primary advantages that a data dictionary offers are as follows

Documentation is one of the most obvious advantage of data dictionary. It is a valuable reference in any organization

It improves analysis/user communication by establishing consistence definitions of various elements, terms and procedures.

During implementation it serves as a common base against which programmers compare their data descriptions

Programs that use a given data elements are cross-referenced in the data dictionary, which makes it easy to identify them and make any necessary changes

A data dictionary is an important step in building a data base. Most data base management systems have a data dictionary as a standard feature

Following points are considered while constructing a Data Dictionary

1. Each data flow in the DFD has one data dictionary entry

2. Definitions must be reality accessible by name

3. There should be no redundancy in the data definition

4. The procedure for writing definitions should be precise

DEVELOPMENT OF SOFTWARE

Software Development depends upon the Cost of each option

The time available to write software, and

The availability of programmers

Starting coding of any subsystem we were required to carefully study information and requirements regarding that application, stored in MS-ACCESS Dictionary. Once the problem is well thought off, and ideas were shared / discussed among other team members, design phase is through i.e. how exactly the user interface will be and what is the best way to deduce the logic of the application, we were required to write down the flow of logic and other parameters being used or getting affected on a document of COMPUTERIZED LIBRARY MANAGEMENT SYSTEM called Requirement Specification Document.

The RSD has to get approved us and used to get further suggestions, also this RDS is used to prepare the documentation of the system at later and helps to keep trace of the changes in the logic.

SYSTEM EVALUATION AND TESTINGDuring system testing, the system is used experimentally to ensure that the software does not fall, i.e. it will run according to specification and in the way users expect. Special test data input for processing and the result examination. A limited number of users may be allowed to use the system so that analysis can seen whether they use it in unforeseen ways. It is preferable to discover any surprises the organization implements the system and encounters them later on. This type of testing which allows only a few, selected users to work on the system is known as BETA TESTING. On the other hand the testing done by the developer (s), themselves is known as ALPHA TESTING.

Testing is generally performed by persons other than those who the original programs to ensure complete and unbiased testing and more reliable software.

The norms followed during the testing phase were thoroughly tested by me, the developer, I was required to release the programs source code. The source code was copied into the area. If some changes were desired in the program, I was suitably informed and was required to made the necessary modifications.

Following testing procedures were used

UNIT TESTINGUnit testing is the testing of a single program module in an isolated environment. The testing of the processing procedure is the main focus. In this regard, all the modules were separately tested first as isolated and complete entities. This helped a lot in discovering problems related to a single module and rectifying them in the contest of the module itself, rather than considering module-related problem in a global context.

INTEGRATION TESTINGIntegration testing is the process of testing the interfaces among system modules. Some testing ensures that data moves between system as intended. In the regard of a particular module was obtained in correct format, so that the next module could accept it appropriately. This could be done either after the entire system was developed, or in stages than one module was developed.

SYSTEM TESTING

System testing is the testing of the system against its initial objectives. Such testing is done either in a simulated environment or in a live environment.

In the case of the system which I developed, the testing was done in a pseudo-real environment. The organization has an area called the Development , where all development work is carried out, whereas the Client is the area where all on-line work is undertaken. Since the kind of work which I was involved dealt with insertion, updating and in tables, all the work was developed in the Development area. I call the environment pseudo-real since all data which is being used for on-line transaction can be copied into the tables of the Development and live data can be worked on. Thus whatever would be the output on the Client is reflected exactly on the Development also. Thus, discovery of error became simpler in that the errors which would occurs in the real-time environment were exactly duplicated in the Development environment.

All the above types of testing were carried out and various extreme cases were also introduced to check for whether the system responded as expected. The various Forms, database packages, procedures, function; visual basic programs and functions were tested to discover they behaved in the manner expected of them and gave accurate results. However, the factor, which helped most in the modification and rectification of the system, was the user response. The user after using the system would invariably come up with some idea to improve the system. Such ideas, if feasible, were incorporated into the system, thus leading to an improvement in the overall efficiency of the system.

SYSTEM IMPLEMENTATION

Implementation, literally, means to put into effect or to carry out. The system implementation phase of software engineering deals with all activities that take place to convert from the old system to the new. Proper implementation is essential to provide system to meet organizations requirements.

During the implementation phase debugging, documentation of the system was created out, module in the project for

Accuracy of Results,

Minimization of response Time,

Clarity and Simplicity of the code,

Minimization of Hard Coding i.e. (a generic approach was followed )

Minimization of amount of memory used.

Various types of errors were discovered while debugging the modules. These ranged from errors to failure to account for various processing cases. Proper documentation of each module was done by embedding comments in the executable portion of the code. To enhance the readability, comments, indentation, parenthesis, black spaces, blank lines and borders were around the blocks of comments. Care was taken to use descriptive names for table, field, modules, forms etc., The proper use of indentation, parenthesis and blank lines was also ensured during coding.

Testing of the Report Generation module was carried out to find out the response time of the system for the generating reports. To make the response time negligible

SYSTEM MAINTENANCE

Maintenance is a fact of life in the development of information systems. However the making of changes & adjustments dont necessarily signal correction of error or the occurrence of problems.

Among the most frequent changes requested by end users is the addition of information to a report format. Information requirements may be revised as the result of system usage or changing operational needs. Perhaps oversights that occurred during the development process need to be corrected.

Often, the need arises to capture additional data for storage in a database or perhaps when it is necessary to add error detection features to prevent system users from inadvertently taking an unwanted action.

These are the realities of application maintenance, when they occur, however they are an indication that the system is being used & that it is serving a useful function rather than being shelved by the intended, such as :

More accurately defining the users requirements during system development.

Assembling better systems documentation.

Making better use of existing tools & techniques.

Including proper comments.

SYSTEM DOCUMENTATIONDocumentation is the process of collecting, organizing, storing and maintaining on paper (or some relatively permanently medium ) a complete record of why application were developed, for whom , what function they perform, and how these functions are carried out. Thus it provides an explanation of how a system operates & what feature characterize models & algorithms. Producing documentation is an important but often neglected activity of programmers.

Documentation of the system always reduces maintenance costs and makes maintenance much more easier. Documentation can be broadly classified as :

1. INTERNAL DOCUMENTATION

2. EXTERNAL DOCUMENTATION

INTERNAL DOCUMENTATION

Internal documentation in the code can be extremely useful in enhancing the understandability of programs. Internal documentation of programs is done by the use of comments. All the languages provide means of writing comments in the programs. Comments are textual statements that are meant for the reader and are not executed. Comments , if properly written, and if kept consistent with the code, can be invaluable during maintenance.

The purpose of comments is not to explain the internal logic of the program the program itself is the best documentation for the details of logic. The comments should explain what the code is done is doing, and not how it is done it.

Comments should be provided for the block of code, particularly those parts of code which are hard to follow.

Providing comments for module is most useful as module form the unit testing , compiling , verification and modification. Comments for a module are often called prologue for the module. It is best to standardized the structure of the prologue of the module. It is desirable that prologue contains the following information :

a) Module functionality or what the module is doing

b) Parameters are their purpose

c) Assumptions about the input, if any

d) Global variable accessed and or modified in the module

As explanation of parameters ( whether they are input only, output only or both input and output , why they are needed by the module and how the parameters are modified ) can be quite useful during maintenance.

In addition to that given above , often information can be included, depending on the local coding standards. Example include :

Name of the author,

Date of compilation

Last date of modification.

Note that if the module is modified, then the prologue should also be modified, if necessary. A prologue that is inconsistent with the internal logic of the module is prologue worse than having no prologue at all.

While coding programs for the Station Coding System special attention has been paid to the internal documentation of the system, in addition to the external documentation. Each program/module has :

Program/module name on top

Date of creation of the program

Last modification date

The S/W tool used to developed the program

Description of input to the program/module

Description of the output produced

How the module is related to other modules

Purpose of variables/constants used

Apart from this comment lines have been inserted wherever it was felt that they were necessary. Moreover meaningful variable names/constants have been assigned to different variable/constants used in the programs.

EXTERNAL DOCUMENTATION

The external documentation of the system contains all the relevant information about the system which is not included within the programs. The external documentation typically explains :

What is the basic purpose of the system ?

Why the system was developed ?

The platform on which the system will run.

The various trouble shooting mechanisms.

The operations guide.

CONCLUSION

The project made me realize the significance of developing software for client, where all the eventualities have to be taken care of, unlike at educational institution, where the sole aim is to learn. What may be seen to the developed to be a software complete in all respects, I was required to meet the stringent demands of the in-house client in the materials department. Through this seemed tough at first, I realized that pressure goaded us on to develop better and better applications.

During the project, the real importance for following all the principle of System Analysis and Design drawled on me. I felt the necessity of going through the several stages, because only such a process could make one understand the problems at hand, more so due to the enormous size of data stores involved and their manipulation

In retrospect, I would like to say that the institute provided us with sample opportunities to learn Oracle 8 and its tools. I specifically was able to learn MS-ACCESS and its Tools. I specially was able to learn VISUAL BASIC 6.0. I also succeeded in understanding a number of tricky concept in database, which were earlier only hazy blobs in the realm of our comprehension.However my project library management is an asset to the organization, even then FURTHER ENHANCEMENT are possible in this project such as new forms & reports can be included as and when required.

Unfortunately due to lack of time we can developed any report in this system but this is not the end of this system software, it is beginning. We can change and modify this software due to more requirement of needs and also removed some errors which is finding in this system software.

We also developed some complex reports which is required and makes this software more powerful and friendly for user by which user can handle library data more easily and can calculate all the calculation without any other software i.e., users all the requirements will be fulfill by this software and user can manage all the numeric data calculations.

LIMITATION

Limitation about the Software about we can say as in development in Visual Basic as size increase searching as speed will be show in compare dos.

SCOPE FOR FUTURE

It will be save money according to its performance also will be helpful fast accessing of the organization.

BIBLIOGRAPHY

BOOK NAME

AUTHOR1. Complete Reference of MS-Office

Techmedia

2. An Introduction to Database Systems

C. J. Date

3. System Analyses and Design

E M. Awad

4. The Complete VISUAL BASIC

Tulec

5. Programming in VB

P.K.M Bride

6. Visual Basic from the Ground Up

Gary Cornell

7. Mastering in VB

Steve 8. VB with MS-Access

Rita Sahoo

9. Visual Basic 6.0

Smith

GLOSSARY OF TERMS USEDS.No.TermsDescription

1BACK UPA copy of something preserved to insure against the damage of primary copy.

2DATA BASEA repository of stored data.

3DBMSData Base Management System is a layer if Software between the physical database itself & the users of the system.

4DDData Dictionary, which is a data base that Contains data about data i.e. description of other in the system

5FLOW CHARTFLOW CHART which depicts relation between different entities in the system.

6HARDWAREThe physical equipment in a system comprising of computers, terminals, Keyboards & Other ancillary items.

7ITDInformation Technology Division.

8MENUA group of options from which Selection is to be made.

9MODULEA small components of a larger system

10ON-LINEA term describing people, equipment or Devices that are in direct communication with the computer

11PIPreliminary Investigation

12PROGRAMA sequence of instruction given to the Computer to solve a particular problem.

13PROTOTYPEA development model of the system for test Purpose

14RDBMSA data Base/ Management System in which Relationships are defined by tables.

15RSDRequirement Specification Document.

16SCALABILITYThe ability to increase the performance With the growth in Hardware.

17SOFTWAREComputer program, procedure & Associated documentation concerned with the operator of a system.

WELCOME TO ENQUIRY COUNTER

STEPPING CHART FOR ENQUIRY COUNTER

EXIT

CANCELLATION FORM

RESERVATION FORM

TRAINS SEATS DETAILS

MORE DETAIL WITH

TIMINGS

DETAILS ABOUT TRAINS

AND ITS ROUTES

ENQUIRY COUNTER

SELECT ANY ONE OF THESE

Details About

Timings

Details About

Seats

Details About

Timings

Cancella -

tion

Form

Reservation

Form