A

PROJECT REPORT
ON
“CAR PARKING”

Session (2018-2021)

SUBMITTED BY:-
Name- Hitesh Dixit
Roll No :- 180624106012
Class- BCA 6th SEM

SUBMITTED TO:

Project Guide:- H.O.D:-

Mr. Mohit Kumar Tyagi Mr. Mohit Kumar Tyagi
Director Coordinator
Dr. Nitin Singh Ms. Ritu Singh

NEELKANTH VIDYAPEETH PAWLI KHAS,

MODIPURAM, MEERUT
 A
PROJECT REPORT
ON
“CAR PARKING”

Session (2018-2021)

SUBMITTED BY:-
Name- Hitesh Dixit
Roll No :- 180624106012
Class- BCA 6th SEM

SUBMITTED TO:

Project Guide: - H.O.D:-

Mr. Mohit Kumar Tyagi Mr. Mohit Kumar Tyagi
Director Coordinator
Dr. Nitin Singh Ms. Ritu Singh

NEELKANTH VIDYAPEETH PAWLI KHAS,

MODIPURAM, MEERUT
 ACKNOWLEDGEMENT
The satisfaction that accompanies successful completion of any work would be incomplete

without the mention of the people who made it possible.

Primarily, I would like to thank my faculty members for giving me the opportunity to fulfill

my aspiration. With deep sense and regards, I am obliged to Mr. Mohit Kumar Tyagi ,

Project Guide and project coordinator, as he had a direct influence, some way, in my

motivation and gratefulness for being part of the responsible project guide of the institute. I

am very thankful to him for his valuable guidance and remarkable patience in guiding my

work to its fulfillment.

I wish to thank my parents for their constant encouragement which is like snow, so after when

it falls and longer when it falls and longer when it dwells upon, the deeper it sinks in mind.

I will be failing in my mission if I do not thank other people who directly or indirectly helped

me in the successful completion of this project.

So, my heart full thanks to all friends mainly who supported and encouraged me in preparing

this project report as best as possible.

HITESH DIXIT
BCA VI SEM
ROLL NO. (180624106012)
 DECLARATION

This is to be certify that this Project Report entitled “CAR PARKING”

which is submitted by HITESH DIXIT (180624106012), in the partial

fulfillment, for the award of degree of Bachelor of Computer Application

in Department of Computer Application, of NEELKANTH

VIDYAPEETH PAWLIKHAS MODIPURAM, Meerut, affiliated to

CHAUDHARY CHARAN SINGH UNIVERSITY, MEERUT (U.P.); is

carried out by him/her under my supervision.

The matter embodied in this Project Work has not been submitted earlier for

award of any degree or diploma in any university/institution to the best of

our knowledge and belief.

(Mr. Mohit Kumar Tyagi) (Mr. Mohit Kumar Tyagi (Mr. Nitin Singh)

Project Guide Head of the Department Director

Date: __/__/____
 INTRODUCTION

Car Parking Management System is software which is helpful for bus operators, who wants to

operate many bus trips in a day. Vehicle Management System is a windows application

written for 32-bit Windows operating systems which focused in the area of adding, editing

and deleting the passengers, staff and the bus routes. In this software a person can be register

as a user and he can manage the bus routes and the staff, passengers’ details. He can add a

bus and its details including bus route details. User can also add the details of the staff and

their duty time in the system.

There are mainly 5 modules in this software

 Bus Management

 Route Management

 Employee Management

 Passenger Management

In Bus module a user can add a new bus details to the database. He can set the details of the

route and the timing also. Bus details like the type, engine number, seating capacity and the

route in which the bus is going to be operated are added. Whenever the user wants to modify

these details he can update new values through this software. Route Management module

deals with the route management of the bus. A user can add the route and if he wants he can

change it or delete that route. The main advantage is that this module is helpful for the agents

to get details of the route and the details of the bus which have trip to that route. He can also
get the information of the number of seats available in a particular day. Employee details of

any bus can add to the database and this is helpful to the bus operators in the case of the

salary and bates for the employee. An operator can add the personal details and if we want to

edit or delete he can done modification using the Vehicle Management System. This is very

helpful for the passenger also; if they have any complaint against staff he can approach the

operator and easily identify the employee. Details of every passenger are stored in the system.

A user can add a passenger only one time and if he came again operator can identify that

person. Operator can add, edit and delete the details of the passenger.

HARDWARE CONFIGURATION:-

Processor : Pentium III 630MHz

RAM : 128 MB

Hard Disk : 20GB

Monitor : 15” Color monitor

Key Board : 122 Keys

SOFTWARE CONFIGURATION

Operating System : Windows NT,

Windows 98,

Windows XP.

Language : Java 2 Runtime Environment

Database : MS Access2007.
 SYSTEM ANALYSIS

EXISTING SYSTEM:

System Analysis is a detailed study of the various operations performed by a system and

their relationships within and outside of the system. Here the key question is- what all

problems exist in the present system? What must be done to solve the problem? Analysis

begins when a user or manager begins a study of the program using existing system.

During analysis, data collected on the various files, decision points and transactions

handled by the present system. The commonly used tools in the system are Data Flow

Diagram, interviews, etc. Training, experience and common sense are required for

collection of relevant information needed to develop the system. The success of the

system depends largely on how clearly the problem is defined, thoroughly investigated

and properly carried out through the choice of solution. A good analysis model should

provide not only the mechanisms of problem understanding but also the frame work of

the solution. Thus it should be studied thoroughly by collecting data about the system.

Then the proposed system should be analyzed thoroughly in accordance with the

needs.

System analysis can be categorized into four parts.

 System planning and initial investigation

 Information Gathering

 Applying analysis tools for structured analysis

 Feasibility study
  Cost/ Benefit analysis

In the existing system all the jobs of the bus route management is done manually. This is very

difficult to the operators who want to handle hundreds of trips and many buses in a day. The

currents system is that an operator wants to keep the physical records of the bus route in his

office and a separate record for the passengers’ and for the booked seats. In current system

there is no way to store the details of the employees’ working in the bus. So many complaints

against staff can arise from the passengers’ side. More over there is no detailed record of the

bus and routes in which they service

PROPOSED SYSTEM

The proposed system is very useful for the operators and passengers. This avoids the

overheads for the operators. They can minimize the working stress and can keep essential

documents related to the bus and the passengers as a softcopy. The advantage of the proposed

system is the reduction in the cost of the office equipments and the transaction is done

quickly. Any operator can answer if any seats for a particular route in a particular day are

available or not.

Our proposed system has several advantages

 User friendly interface

 Fast access to database

 Less error

 More Storage Capacity

 Search facility
  Look and Feel Environment

 all the working Quick transaction

One of the most difficult tasks of system analysis is developing a clear, in-depth

understanding of the problem being investigated, without which it becomes impossible to

specify the requirements for a new project with any accuracy. Several questions should be

posed for this. Some of those may be:

 What is the problem?

 How complex is it?

 What are its likely causes?

 Why is it important that the problem be solved?

 What are possible solutions to the problem?

 What types of benefits can be expected once the problem is solved?

It takes considerable skill to determine the true cause of a system problem. A systems analyst

might begin to define the problem by determining if the problem can be classified ac-cording

to one or more common types of systems problems. With knowledge of the common types of

systems problems, the analyst can diagnose a problem by examining its characteristics.

Organizations usually face problems or have opportunity due to the following facts:

 A new product or plant or branch

 A new market or new process

 Failure of an existing system

 Inefficiency of an existing system

  Structural error in the existing system etc

For identifying problems/opportunities, we scan the following:

 The performance of the system

 The information being supplied and its form

 The economy of processing

 The control of the information processing

 The efficiency of the existing system

 The security of the data and software

 The security of the equipment and personnel etc

After identification of the problem, it is defined and a general direction or method for solving

this problem is also determined. The management establishes the term of reference as well as

the resources to be provided for the project. System development is an iterative process and

the first identifiable stage of it is problem definition, whose final output is terms of reference.

Careful analysis of this system suggests a number of different problems:

1. Problem of reliability: Current system is not reliable. It seems to vary in quality and

result from one month to the next. Some items it gives good output, but sometimes the

output is worst.

2. Problem of accuracy: There are too many mistakes in reports and calculations.

3. Problem of timeliness: In the current system the reports and output produced is

mostly late and in most of the cases it is useless because it is not on time.
4. Problem of validity: The output and reports mostly contains misleading information.

The transactions and calculations are sometimes not valid.

5. Problem of economy: The current system is very costly. We have to spend lots of

money in manual filing, calculations and remembering the information, but still not get

the desired results.

6. Problem of capacity: The current system is suffering from problem of capacity also.

The workload is too much. Few peoples cannot handle.

System analysis and design refers to the process of examining a business situation with the

intent of improving it through better procedures and methods. Systems development can

generally be through of having two major components: System Analysis and System

Design. System design is the process of planning a new system or replace or complement

an existing system. But before this planning can be done, we must thoroughly understand

the existing system and determine how computers can best be used to make its operation

more effective. System analysis, then, is the process of gathering and interpreting facts,

diagnosing problems and using the information to recommend improvement to the system.

In brief, we can say that analysis specifies what the system should do. Design states hew

to accomplish the objective.

In this project we have used Rapid Application Development (RAD) model; RAD is an

incremental software development process model that emphasizes an extremely short

development cycle. The following phases are encompassed:

Business modeling: All the information about the business functioning of the gateway

development is collected, how the data and information is flow from one end to another
end using the following questions: What information drives the department process? What

information is generated? Who generates it? Where does the information go? Who process

it?

Data modeling: The information collected in business modeling phase is refined into a set

of data objects that are needed to support the project. The attributes of each object are

identified and the relationship between these objects defined.

Process modeling: Processing descriptions and functions like adding, modifying, deleting

student records, assigning marks, generating mark sheet, printing reports, providing

information, file handling etc. are created.

Application generation: The fourth generation techniques are used to generate

application, like reusing the predefined functions or creating reusable components.

Testing: Most of the functions are already tested, as they are predefined functions.

However, new components or functions are also tested after application generation.
 FEASIBILITY ANALYSIS

Whatever we think need not be feasible .It is wise to think about the feasibility of any

problem we undertake. Feasibility is the study of impact, which happens in the organization

by the development of a system. The impact can be either positive or negative. When the

positives nominate the negatives, then the system is considered feasible. Here the feasibility

study can be performed in two ways such as technical feasibility and Economical Feasibility.

Steps in feasibility analysis:

Eight steps involved in the feasibility analysis are:

1. From a project team and appoint a project leader.

2. Prepare system flowcharts.

3. Enumerate potential proposed systems.

4. Define and identify characteristics of proposed system.

5. Determine and evaluate performance and cost effectiveness of each proposed

system.

6. Weight system performance and cost data.

7. Select the best proposed system.

8. Prepare and report final project directive to management.

Economic Feasibility:

Economic analysis is the most frequently used technique for calculating the effectiveness of a

proposed system. More commonly known as cost/benefit analysis; in this procedure we

determine the benefits and savings that are expected from a proposed system and compare

them with costs. We found the benefits outweigh the costs; we take a decision to design and

implement the new proposed system.

Development of this application is highly economically feasible .The organization needed not

spend much m money for the development of t he system already available. The only thing is

to be done is making an environment for the development with an effective supervision. I f

we are doing so , we can attain the maximum usability of the corresponding resources .Even

after the development , the organization will not be in a condition to invest more in t he

organization .Therefore , the system is economically feasible.

Technical Feasibility:

This is concerned with specifying equipment and software that will successfully satisfy the

user requirement. The technical needed of the system may vary considerable, but might

include:

 The facility to produce outputs in a given time.

 Response time under certain conditions.

 Ability to process a certain volume of transaction at a particular speed.

 Facility to communicate data to distant location.

After examining technical feasibility, we give more importance to the configuration of the

system then the actual make of hardware. The configuration gives the complete picture about

the system’s requirements.

Ten to twelve workstations are required, these units should be interconnected through LAN so

that could operate and communicate smoothly. They should have enough speeds of input and

output to achieve a particular quality of printing.

We can strongly says that it is technically feasible, since there will not be much difficulty in

getting required resources for the development and maintaining the system as well. All the

resources needed for the development of the software as well as the maintenance of the same

is available in the organization here we are utilizing the resources which are available already.

Operational Feasibility:

It is mainly related to human organizational and political aspects. The points to be considered

are:

 What changes will be brought with the system?

 What organizational structures are disturbed?

 What news skills will required?

 Do the existing staff members have these skills?

 If not, can they be trained in due course of time?

Generally project will not be rejected simply because of operational infeasibility but such

considerations are likely to critically affect the nature and scope of the eventual

recommendations.
For operational feasibility study we appointed a small group of people who are familiar with

information system techniques, who understand the of the business that are relevant to the

project and skilled in system analysis and design process.

Social Feasibility:

Social feasibility is a determination of whether a proposed project will be acceptable to the

people or not. This determination typically examines the probability of the project being

accepted by the group directly affected by the proposed system change.

Management Feasibility:

It is a determination of whether a proposed project will be acceptable to management. If

management does not accept a project or gives a negligible support to it, the analyst will tend

to view the project as a non-feasible one.

Legal Feasibility:

Legal feasibility is a determination of whether a proposed project infringes on known Acts,

Statutes, as well as any pending legislation. Although in some instances the project might

appear sound, on closer investigation it may be found to infringe on several legal areas.

Time Feasibility:

Time feasibility is a determination of whether a proposed project can be implemented fully

within a stipulated time frame. If a project takes too much time it is likely to be rejected.
 SYSTEM DESIGN
Introduction:

The system objectives outlined during the feasibility study serve as the basis from which the

work of the system design is initiated. Much of the activities involved at this stage is of

technical nature requiring a certain degree of experience in designing systems, sound

knowledge of computer related technology and through understanding of computers available

in the market and the various facilities provided by the vendors. Nevertheless, a system

cannot be designed in isolation without the active involvement of the user. The user has a

vital role to play at this stage too. As we know that data collected during feasibility study will

be utilized systematically during the system design. It should, however, be kept in mind that

detailed study of existing the system is not necessarily over with the completion of the

feasibility study. Depending on the plan of feasibility study, the level of detailed study will

vary and the system design stage will also vary in the amount of investigation that still needs

to be done. This investigation is generally an urgent activity during the system design as the

designer needs to study minute’s details in all aspects of the system. Sometimes, but rarely,

this investigation may from a separate stage between feasibility study and computer system

design. Designing a new system is a creative process, which calls for logical as well as lateral

thinking. The logical approach involves systematic moves towards the end product keeping in

mind the capabilities of the personnel and the equipment at each decision making step. Lateral

thought implies encompassing of ideas beyond the usual functions and equipment. This is to

ensure that no efforts are being made to fit previous solutions into new situations.
System Design Considerations:

The system design process is not a step-by-step adherence of clear procedures and guidelines.

Though, certain clear procedures and guidelines have emerged in recent days, but still much

of design work depends on knowledge and experience of the designer.

When designer starts working on system design, he will face different type of problems.

Many of these will be due to constraints imposed by the user or limitations of the hardware

and software available in the market. Sometimes, it is difficult to enumerate the complexity of

the problems and solutions thereof since the variety of likely problems is so great and no

solutions are exactly similar. However, following considerations should be kept in mind

during the system–designing phase:

The primary objective of the design: Of course, is to deliver the requirements as specified in

the feasibility report. In general, the following design objectives should be kept in mind:

a. Practicality: The system must be stable and can be operated by people with average +.

b. Efficiency: This involves accuracy, timeliness and comprehensiveness of the system

output.

c. Cost: It is desirable to aim for a system with a minimum cost subject to the condition that it

must satisfy all the requirements.

d. Flexibility: The system should be modifiable depending on the changing needs of the user.

Such modifications should not be entail extensive reconstructing or recreation of software. It

should also be portable to different computer systems.

e. Security: This is very important aspect of the design and should cover areas of hardware

reliability, fall back procedures, physical security of data and provision for detection of fraud

and abuse.

System design involves first logical design and then physical construction of the system. The

logical design describes the structure and characteristics of features, like the outputs, inputs,

files, databases and procedures. The physical construction, which follows the logical design,

produces actual program software, files and a working system.

The designer constraints:

Hardware: The existing hardware will obviously affect the system design.

Software: The available software (operating system, utilities, language etc.) in the market

will constraint the design.

Budget: The budget allocated for the project will affect the scope and depth of design.

Time-scale: The new system may be required by a particular time (e.g. the start of a financial

year).This may put a constraint on the designer to find the best design.

Interface with other systems: The new system may required some data from another

computerized system or may provide data to another system in which case the files must be

compatible in format and the system must operate with a certain processing cycle.

Processing Techniques:

The options available to the designer are:

 Batch processing
  Real-time processing

 Online processing

 A combination of all the above

You are already aware of these techniques. It is quite interesting to note, however that a

combination of these is often found to be ideal in traditional data processing applications.

This increases throughput of the system as also brings down the response time of on-line

activities. In most of die business applications, 24-hour data is acceptable enough and hence it

is possible to update voluminous data after office-hours in batch mode.

Design Methodologies:

The scope of the system design is guided by the framework for the new system developed

during analysis. More clearly defined logical method for developing system that meets user

requirements has led to new techniques and methodologies that fundamentally attempt to do

the following:

 Improve productivity of analysts and programmers.

 Improve documentation and subsequent maintenance and enhancements.

 Cut down drastically on cost overruns and delays.

 Improve communication among the user, analyst designer, and programmer.

 Standardize the approach to analysis and design.

 Simplify design by segmentation.

SYSTEM REQUIREMENTS

This management system can be used in windows 98, Windows2000, Windows XP and

Windows NT, supported for other platform such as Applet, Macintosh and UNIX.

The system must be running Windows 98, Windows 98 or Windows NT4.0 operating system

and must meet the following hardware requirements.

 For Windows 95 based computers , a 486 / 66 MHz or higher

processor with 8MB

 For Windows 98 based computers , a 500/88MHz or higher

processor with 32 Mb of RAM

 For Windows NT based computers , a 488 / 66 MHz or higher

processor with 16 MB of RAM

 For Windows 200 based computers , a 700/850 MHz or higher

processor with 512 MB of Ram

INPUT DESIGN

Input design is the process of converting user-oriented input to a computer based

format. Input design is a part of overall system design, which requires very careful

attention .Often the collection of input data is the most expensive part of the system. The

main objectives of the input design are …

1. Produce cost effective method of input

2. Achieve highest possible level of accuracy

3. Ensure that the input is acceptable to and understood by the staff.

Input Data

The goal of designing input data is to make entry easy, logical and free from errors as

possible. The entering data entry operators need to know the allocated space for each field;

field sequence and which must match with that in the source document. The format in which

the data fields are entered should be given in the input form .Here data entry is online; it

makes use of processor that accepts commands and data from the operator through a key

board. The input required is analyzed by the processor. It is then accepted or rejected. Input

stages include the following processes

 Data Recording

 Data Transcription

 Data Conversion

 Data Verification

 Data Control

 Data Transmission

 Data Correction

One of the aims of the system analyst must be to select data capture method and

devices, which reduce the number of stages so as to reduce both the changes of errors and the

cost .Input types, can be characterized as.

 External

 Internal
  Operational

 Computerized

 Interactive

Input files can exist in document form before being input to the computer. Input design

is rather complex since it involves procedures for capturing data as well as inputting it to the

computer.

OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate the results of

processing to users. They are also used to provide a permanent copy of these result for latter

consultation .Computer output is the most important and direct source of information to the

users. Designing computer output should proceed in an organized well through out the

manner. The right output must be available for the people who find the system easy o use.

The outputs have been defined during the logical design stage. If not, they should defined at

the beginning of the output designing terms of types of output connect, format, response etc,

Various types of outputs are

 External outputs

 Internal outputs

 Operational outputs

 Interactive outputs

 Turn around outputs

 All screens are informative and interactive in such a way that the user can ful fill his

requirements through asking queries.

DATABASE DESIGN

The general theme behind a database is to handle information as an integrated whole.

A database is a collection of interrelated data stored with minimum redundancy to serve many

users quickly and effectively. After designing input and output, the analyst must concentrate

on database design or how data should be organized around user requirements. The general

objective is to make information access, easy quick, inexpensive and flexible for other users.

During database design the following objectives are concerned:-

 Controlled Redundancy

 Data independence

 Accurate and integrating

 More information at low cost

 Recovery from failure

 Privacy and security

 Performance

 Ease of learning and use

TABLES USED

USERS

FieldName DataType Key

Name Text -

Category Text -

Username Text -

Password Text -

BOOKING

FieldName DataType Key

Booking_No Number Primary

Pass_No Text -

PassName Text -

Bus_RegNo Text -

SeatNo Text -

Date_of_Travel Text -

Time_of_Travel Text -

Pass_From Text -

Destination Text -
 Amount Text -

BUSES

FieldName DataType Key

Bus_RegNo Text Primary

BusNo Text -

Model Text -

Capacity Number -

DateBought Date/Time -

Insurance_Status Text -

Date_Insured Date/Time -

Insurance_Expiry Date/Time -

Emp

FieldName DataType Key

empNo Text Primary

Sname Text -

Fname Text -

Lname Text -
 Gender Text -

DOB Date/Time -

Designation Text -

Telephone Number -

E_Mail Text -

Address Text -

Passenger

FieldName DataType Key

Pass_No Text Primary

Pass_Name Text -

Address Text -

Tel_No Number -

Date_of_Travel Date/Time -

Depot Text -

To Text -

Pay_Status Text -

Booked_Status Text -
Payment

FieldName DataType Key

Payment_No Text Primary

Pass_No Text -

Pass_Name Text -

Payment_Mode Text -

Date_Payment Date/Time -

Amount_Paid Currency -

Received_By Text -

Route

FieldName DataType Key

Route_No Text Primary

RouteName Text -

Depot Text -

Destination Text -

Distance Text -

Fare_Charged Number -
Schedules

FieldName DataType Key

Route_Name Text -

empNo Text -

Driver_Name Text -

Trip_No Number -

Date_Scheduled Date/Time -

Dept_Time Text -

Trips

FieldName DataType Key

Trip_No Text Primary

Bus_RegNo Text -

Route_No Text -

S_Date Text -
Validator

FieldName DataType Key

Bus_No Text -

DriverNo Text -

RouteNo Text -

Date_Schedule Text -

Trip_No Text -
 STRUCTURE DESIGN

Introduction:

Structure design is a data flow based methodology. The approach begins with a system

specification that identifies inputs and outputs and describes the functional aspects of the

system. The specifications then are used as a basis for the graphics representation. The step is

the definition of the modules and their relationship to one another in a form called a structure

chart, using a data dictionary and other structure tools.

Logical design proceeds from the top down. General features such as reports and inputs are

identified first. Then each is satisfied individually and in more detail. Hence, the structure

design partitions a program into small, independent modules. They are arranged in a hierarchy

that approximates a model of the business area and is organized in a top-down manner. Thus,

structured design is an attempt to minimize the complexity and make a problem manageable

by subdividing it into smaller segments which is called modularization or decomposition. In

this way, structuring minimizes intuitive reasoning and promotes maintainable provable

systems.

A design is said to be top-down if it consists of a hierarchy of modules. with each module

having a single entry and a single exit subroutine. The primary advantages of this design are

as follows:

 Critical interfaces are tested first.

 Early versions of the design, through incomplete, are useful enough to resemble the

real system.
  Structuring the design, parse, provides control and improves morale.

 The procedural characteristics define the order that determines processing.

Major System Design Activities:

Several development activities are carried out during structured design. They are data base

design, implementation planning, system test preparation, system interface specification, and

user documentation.

a. Data base design: This activity deals with the design of the physical database. A key is to

determine how the access paths art to be implemented.

b. Program design: In conjunction with database design is a decision on the programming

language to be used and the flowcharting, coding, and debugging procedure prior to

conversion. The operating system limits the programming languages that will run of the

system.

c. System and program test preparation: Each aspect of the system has a separate test

requirement. System testing is done after all programming and testing completed. The test

cases cover every aspect of the proposed system, actual operations, and user interface and so

on. System program test requirements become a part of design specification–a pre requisite to

implementation.

In contrast to the system testing is acceptance testing. Which puts the system through a

procedure design to convince the user that the proposed system will meet the started and

requirements. Acceptance testing is technically similar to system testing but politically it is

different. Acceptance testing is conducted in the presence of the user, audit representatives, or

the entire staff.

 PROCESS MODELING
Data Flow Diagram:

Graphical description of a system`s data and how the processes transform the data is known

as Data Flow Diagram (or DFD).

Unlike detail flowcharts. DFDs do not supply detailed descriptions of modules but

graphically describe a system`s data and how the data interact with the system.

To construct data flow diagrams, we use:

 Arrows

 Circles

 Open–ended boxes

 Squares

An arrow identifies data flow–data in motion. It is a pipeline through which information

flows. Like the rectangle in flowcharts, circles stand for a process that converts data/into in–

formation. An open–ended box represents a data store data at rest, or a temporary repository

of data. A square defines a source (originator) or destination of system data.

The following seven rules govern construction of data flow diagrams (DFD).

 Arrows should not cross each other.

 Squares, circles, and files must bear names.

 Decomposed data flows must be balanced (all data flows on the decomposed diagram

must reflect flows in the original diagram).

  No two data flows, squares, or circles can have the same name.

 Draw all data flows around the outside of the diagram.

 Choose meaningful names for data flows, processes, and data stores.

 Use strong verbs followed by nouns.

 Control information such as record counts, passwords, and validation requirements are

not pertinent to a data-flow diagram.

If too many events seem to be occurring at a given point, an analyst can decompose a data

conversion (circle). The new data conversions from a parent-child relationship with the

original data conversion : the child circle.

SYSTEM IMPLEMENTATION AND REQUIREMENT
Introduction:
The decision to acquire hardware or software must be handled in the same way as any other

information decision, The variety of sizes and types of computing resources available puts a

burden on the analyst who must select hardware, software and advise the top management

accordingly.

Today, selecting a system is a serious and time-consuming. The time spent on the selection

process is a function of the applications and whether the system is a basic microcomputer or a

mainframe. In either case, planning system selection and acquiring experienced help where

necessary pay off in the long run.

There are various important factors, which should be considered prior to system selection.

They are:

 Define system capabilities that make sense for the college.

 Specify the magnitudes of the problem; that is, clarify section entails a few peripherals

or a major decision concerning the mainframe.

 Hardware and software should be considered as a package.

 Develop a time frame for the selection process.

 Provide user indoctrination. This is crucial, especially for first time users. Selling the

system to the user staff, provide adequate training and creating an environment

conductive to implementation are prerequisites for system acquisition.

The selection process should be viewed as a project and a project team should be formed with

the help of management. The selection process consists of several steps, which are discussed

below:
Requirements analysis: The first step in selection is understanding the user`s requirements

within the framework of the organization`s objectives and the environment in which the

system is being installed.

System specifications: System specification must be clearly defined. These specifications

must reflect the actual applications to be handled by the system and include system

objectives, Flowcharts, input-output requirements, file structure and cost.

Request for proposal: After the requirement analysis and system specifications have been

defined, a request for proposal is prepared and sent to selected vendors for bidding.

Evaluation and validation: The evaluation phase ranks various vendor proposal and

determines the one best suited to the user`s requirements. It looks into items such as price,

availability and technical support. System validation ensures that the vendor can, in fact,

match his/her claims, especially system performance.

Vendor selection: This step determines the vendor with the best combination of reputation,

reliability, service record, training, delivery time, lease/finance terms. The System chosen

goes though contract negotiation before implementation.

Conclusion and future scope:

This project as title “Student management system” is comes under the Relational Database

Management System (RDBMS). This application is developed with the help of java 6.0 and

Microsoft Access. This application can also be run on the network environment so it can be

said as network application.

From a proper analysis of positive points and constraints on the component it can be safely

concluded that the product is a highly efficient GUI based component. This application is

working properly and meeting to all user requirements. This component can be easily plugged

in many other systems.

Nothing is perfect in this world. So, we are also no exception. Although, we have tried our

best to present the information effectively, yet, there can be further enhancement in the

Application. We have taken care of all the critical aspects, which need to take care of during

the development of the Project. Like the things this project also has some limitations and can

further be enhances by someone, because there are certain drawbacks that do not permit the

system to be 100% accurate.

The different areas where we can use this application are:

 Any education institute can make use of it for providing information about student.

 It can be used in offices and modifications can be easily done according to

requirements.

 This application can work on the full web based environment.

Implementation is the stage in the project where the theoretical design is turned into a

working system. The implementation phase constructs, installs and operates the new system.

The most crucial stage in achieving a new successful system is that it will work efficiently

and effectively.

There are several activities involved while implementing a new project. They are

 End user training

  End user Education

 Training on the application software

 System Design

 Parallel Run And To New System

 Post implementation Review

End user Training:

The successful implementation of the new system will purely upon the involvement of the

officers working in that department. The officers will be imparted the necessary training on

the new technology

End User Education:

The education of the end user start after the implementation and testing is over. When

the system is found to be more difficult to under stand and complex, more effort is put to

educate the end used to make them aware of the system, giving them lectures about the new

system and providing them necessary documents and materials about how the system can do

this.

Training of application software:

After providing the necessary basic training on the computer awareness, the users will

have to be trained upon the new system such as the screen flows and screen design type of

help on the screen, type of errors while entering the data, the corresponding validation check

at each entry and the way to correct the data entered. It should then cover information needed

by the specific user or group to use the system.

Post Implementation View:

The department is planning a method to know the states of t he past implementation

process. For that regular meeting will be arranged by the concerned officers about the

implementation problem and success

Coding:
 LOGIN PAGE

<%@include file="template/top.jsp" %>

<%@include file="template/menu_public.jsp" %>

<%@include file="template/body_start.jsp" %>

<form id="form" action="loginbaseselect.jsp">

<table>

<tr>

<td><input type="text" name="uname" id="uname" placeholder="username" required=""/> </td>

</tr>

<tr>

<td><input type="password" name="upass" id="upass" placeholder="password" required=""/></td>

</tr>

<tr>

<td><button class="button" type="submit" id="search-submit">Login</button> </td>

<td><div id="result"></div></td>

</tr>

</table>

</form>
<script type="text/javascript">

<%

if (request.getParameter("login") != null && request.getParameter("login").contentEquals("failed"))

%>

alert("Login Failed !!!");

<% }

%>

<%

if (request.getParameter("login") != null &&

request.getParameter("login").contentEquals("dissabled")) {

%>

alert("User Blocked !!!");

<% }

%>

<%

if (request.getParameter("login") != null &&

request.getParameter("login").contentEquals("unknown")) {
%>

alert("Unknown user !!!");

<% } Online Shopping System Department of Computer Science, CUSAT Page 60

%>

</script>

%@include file="template/body_end.jsp" %

 REGISTRATION

<%@page import="DataBase.DB"%>

<%@page import="java.sql.ResultSet"%>

<%@include file="template/top.jsp" %>

<%@include file="template/menu_public.jsp" %>

<%@include file="template/body_start.jsp" %>

<h2 class="title"><a href="#">Register </a></h2>

<div class="entry">

<form action="dbregister.jsp" onsubmit="return check()">

<table>

<tr>

<td>User Name

</td>
<td><input type="text" required="" name="uname" id="uname" />

</td>

</tr>

<tr>

<td>Password

</td>

<td><input type="password" required="" name="upass" id="upass" />

</td>

</tr>

<tr>

<td>Login Name

</td>

<td><input type="text" required="" name="lname" id="lname" />

</td>

</tr>

<tr>
<td>Email

</td>

<td><input type="email" name="emailid" id="emailid" />

</td>

</tr>

<tr>

<td>Mobile No.

</td>

<td><input type="text" name="mobno" id="mobno" />

</td>

</tr>

<tr>

<td>

</td> Online Shopping System Department of Computer Science, CUSAT Page 63

return null;

}
public static void close() {

try {

con.close();

stmt.close();

rs.close();

} catch (Exception e) {

System.out.println("Exception" + e);

 ANDROID WEB-VIEW ACTIVITY

import com.onlineshopping.activity.R;
SCREEN
LAYOUT
LOGIN FORM
Main Form
User Master
Company Master
Customer Master
Item Master
Purchase Transaction
Sales Transaction
Vehicle Mast
Vendor Master

SOFTWARE TESTING
Introduction:-

Is the menu bar displayed in the appropriate contested some system related features

included either in menus or tools? Do pull –Down menu operation and Tool-bars work

properly? Are all menu function and pull down sub function properly listed ?; Is it possible to

invoke each menu function using a logical assumptions that if all parts of the system are

correct, the goal will be successfully achieved .? In adequate testing or non-testing will leads

to errors that may appear few months later.

Testing is the process of exercising software with the intent of finding errors and ultimately

correcting them. The following testing techniques have been used to make this project free of

errors.

Content Review

The whole content of the project has been reviewed thoroughly to uncover typographical

errors, grammatical error and ambiguous sentences.

Navigation Errors

Different users were allowed to navigate through the project to uncover the navigation errors.

The views of the user regarding the navigation flexibility and user friendliness were taken

into account and implemented in the project.

Unit Testing:-

Focuses on individual software units, groups of related units.

 Unit – smallest testable piece of software.

  A unit can be compiled /assembled / linked/loaded; and put under a test harness.

 Unit testing done to show that the unit does not satisfy the application and /or its

implemented software does not match the intended designed structure.

Integration Testing:-

Focuses on combining units to evaluate the interaction among them

 Integration is the process of aggregating components to create larger components.

 Integration testing done to show that even though components were individually

satisfactory, the combination is incorrect and inconsistent.

This create two problem

1. Time delay between the cause and appearance of the problem.

2. The effect of the system errors on files and records within the system

The purpose of the system testing is to consider all the likely variations to which it will be

suggested and push the systems to limits.

The testing process focuses on the logical intervals of the software ensuring that all

statements have been tested and on functional interval is conducting tests to uncover errors

and ensure that defined input will produce actual results that agree with the required results.

Program level testing, modules level testing integrated and carried out.

There are two major type of testing they are

1) White Box Testing.

 2) Black Box Testing.

White Box Testing

White box some times called “Glass box testing” is a test case design uses the control

structure of the procedural design to drive test case.

Using white box testing methods, the following tests where made on the system

a) All independent paths within a module have been exercised once. In our system, ensuring

that case was selected and executed checked all case structures. The bugs that were prevailing

in some part of the code where fixed

b) All logical decisions were checked for the truth and falsity of the values.

While white-box testing can be applied at the unit, integration and system levels of the

software testing process, it is usually done at the unit level. It can test paths within a unit,

paths between units during integration, and between subsystems during a system–level test.

Though this method of test design can uncover many errors or problems, it might not detect

unimplemented parts of the specification or missing requirements.

Techniques used in white-box testing include: API testing (application programming

interface) – testing of the application using public and private APIs

Code coverage – creating tests to satisfy some criteria of code coverage (e.g., the test designer

can create tests to cause all statements in the program to be executed at least once) Fault

injection methods – intentionally introducing faults to gauge the efficacy of testing strategies

Mutation testing methods

Static testing methods

Code coverage tools can evaluate the completeness of a test suite that was created with any

method, including black-box testing. This allows the software team to examine parts of a

system that are rarely tested and ensures that the most important function points have been

tested. Code coverage as a software metric can be reported as a percentage for:

Function coverage, which reports on functions executed Statement coverage, which reports on

the number of lines executed to complete the test 100% statement coverage ensures that all

code paths, or branches (in terms of control flow) are executed at least once. This is helpful in

ensuring correct functionality, but not sufficient since the same code may process different

inputs correctly or incorrectly.

Black box Testing

Black box testing focuses on the functional requirements of the software. This is black box

testing enables the software engineering to derive a set of input conditions that will fully

exercise all functional requirements for a program. Black box testing is not an alternative to

white box testing rather it is complementary approach that is likely to uncover a different

class of errors that white box methods like..

1) Interface errors

2) Performance in data structure

3) Performance errors
4) Initializing and termination errors

Black-box testing treats the software as a "black box", examining functionality without any

knowledge of internal implementation. The tester is only aware of what the software is

supposed to do, not how it does it. Black-box testing methods include: equivalence

partitioning, boundary value analysis, all-pairs testing, state transition tables, decision table

testing, fuzz testing, model-based testing, use case testing, exploratory testing and

specification-based testing.

Specification-based testing aims to test the functionality of software according to the

applicable requirements. This level of testing usually requires thorough test cases to be

provided to the tester, who then can simply verify that for a given input, the output value (or

behavior), either "is" or "is not" the same as the expected value specified in the test case. Test

cases are built around specifications and requirements, i.e., what the application is supposed

to do. It uses external descriptions of the software, including specifications, requirements, and

designs to derive test cases. These tests can be functional or non-functional, though usually

functional.

Specification-based testing may be necessary to assure correct functionality, but it is

insufficient to guard against complex or high-risk situations.

One advantage of the black box technique is that no programming knowledge is required.

Whatever biases the programmers may have had, the tester likely has a different set and may

emphasize different areas of functionality. On the other hand, black-box testing has been said

to be "like a walk in a dark labyrinth without a flashlight." Because they do not examine the
source code, there are situations when a tester writes many test cases to check something that

could have been tested by only one test case, or leaves some parts of the program untested.

This method of test can be applied to all levels of software testing: unit, integration, system

and acceptance. It typically comprises most if not all testing at higher levels, but can also

dominate unit testing as well.

System Testing:-

Focuses on a complete integrated system to evaluate compliance with specified requirements

(test characteristics that are only present when entire system is run)

 A system is a big component.

 System testing is aimed at revealing bugs that cannot be attributed to a component as such,

to inconsistencies between components or planned interactions between components.

 Concern: issues, behaviors that can only be exposed by testing the entire integrated system

(e.g., performance, security, recovery)

 each form encapsulates (labels, texts, grid etc.). Hence in case of project in V.B. form are

the basic units. Each form is tested thoroughly in term of calculation, display etc.
Regression Testing:-

 Each time a new form is added to the project the whole project is tested thoroughly to

rectify any side effects. That might have occurred due to the addition of the new form.

Thus regression testing has been performed.

MAINTENANCE
INTRODUCTION :-

Software Development has many phases. These phases include Requirements

Engineering, Architecting, Design, Implementation, Testing, Software Deployment,

and Maintenance. Maintenance is the last stage of the software life cycle. After the

product has been released, the maintenance phase keeps the software up to date with

environment changes and changing user requirements. The earlier phases should be

done so that the product is easily maintainable. The design phase should plan the

structure in a way that can be easily altered. Similarly, the 5 implementation phase

should create code that can be easily read, understood, and changed. Maintenance can

only happen efficiently if the earlier phases are done properly. There are four major

problems that can slow down the maintenance process: unstructured code, maintenance

programmers having insufficient knowledge of the system, documentation being

absent, out of date, or at best insufficient, and software maintenance having a bad

image. The success of the maintenance phase relies on these problems being fixed

earlier in the life cycle. Maintenance consists of four parts. Corrective maintenance

deals with fixing bugs in the code. Adaptive maintenance deals with adapting the

software to new environments. Perfective maintenance deals with updating the

software according to changes in user requirements. Finally, preventive maintenance

deals with updating documentation and making the software more maintainable. All

changes to the system can be characterized by these four types of maintenance.

Corrective maintenance is ‘traditional maintenance’ while the other types are

 considered as ‘software evolution.’ As products age it becomes more difficult to keep

them updated with new user requirements. Maintenance costs developers time, effort,

and money. This requires that the maintenance phase be as efficient as possible. There

are several steps in the software maintenance phase. The first is to try to understand the

design that already exists. The next step of maintenance is reverse engineering in

which the design of the product is reexamined and restructured. The final step is to test

and debug the product to make the new changes work properly. This paper will discuss

what maintenance is, its role in the software development process, how it is carried

out, and its role in iterative development, agile development, component-based

development, and open source development.

Software maintenance is widely accepted part of SDLC now a days. It stands for all

the modifications and updations done after the delivery of software product. There are

number of reasons, why modifications are required, some of them are briefly

mentioned below:

 Market Conditions - Policies, which changes over the time, such as taxation and

newly introduced constraints like, how to maintain bookkeeping, may trigger need for

modification.

 Client Requirements - Over the time, customer may ask for new features or functions

in the software.

 Host Modifications - If any of the hardware and/or platform (such as operating

system) of the target host changes, software changes are needed to keep adaptability.
  Organization Changes - If there is any business level change at client end, such as

reduction of organization strength, acquiring another company, organization venturing

into new business, need to modify in the original software may arise.

Types of maintenance :-

In a software lifetime, type of maintenance may vary based on its nature. It may be

just a routine maintenance tasks as some bug discovered by some user or it may be a large

event in itself based on maintenance size or nature. Following are some types of

maintenance based on their characteristics:

 Corrective Maintenance - This includes modifications and updations done in order to

correct or fix problems, which are either discovered by user or concluded by user

error reports.

 Adaptive Maintenance - This includes modifications and updations applied to keep

the software product up-to date and tuned to the ever changing world of technology

and business environment.

 Perfective Maintenance - This includes modifications and updates done in order to

keep the software usable over long period of time. It includes new features, new user

requirements for refining the software and improve its reliability and performance.

 Preventive Maintenance - This includes modifications and updations to prevent

future problems of the software. It aims to attend problems, which are not significant

at this moment but may cause serious issues in future.

 Cost of Maintenance :-

Reports suggest that the cost of maintenance is high. A study on estimating software

maintenance found that the cost of maintenance is as high as 67% of the cost of entire

software process cycle.

On an average, the cost of software maintenance is more than 50% of all SDLC phases.

There are various factors, which trigger maintenance cost go high, such as:

Real-world factors affecting Maintenance Cost

 The standard age of any software is considered up to 10 to 15 years.

 Older software’s, which were meant to work on slow machines with less memory and

storage capacity cannot keep themselves challenging against newly coming enhanced

software’s on modern hardware.

 As technology advances, it becomes costly to maintain old software.

 Most maintenance engineers are newbie and use trial and error method to rectify

problem.

 Often, changes made can easily hurt the original structure of the software, making it

hard for any subsequent changes.

 Changes are often left undocumented which may cause more conflicts in future.

Software-end factors affecting Maintenance Cost

 Structure of Software Program

 Programming Language
  Dependence on external environment

 Staff reliability and availability

Maintenance Activities :-

IEEE provides a framework for sequential maintenance process activities. It can be used in

iterative manner and can be extended so that customized items and processes can be

included.

These activities go hand-in-hand with each of the following phase:

 Identification & Tracing - It involves activities pertaining to identification of

requirement of modification or maintenance. It is generated by user or system may

itself report via logs or error messages. Here, the maintenance type is classified also.

 Analysis - The modification is analyzed for its impact on the system including safety

and security implications. If probable impact is severe, alternative solution is looked

for. A set of required modifications is then materialized into requirement

specifications. The cost of modification/maintenance is analyzed and estimation is

concluded.

 Design - New modules, which need to be replaced or modified, are designed against

requirement specifications set in the previous stage. Test cases are created for

validation and verification.

 Implementation - The new modules are coded with the help of structured design

created in the design step.Every programmer is expected to do unit testing in parallel.

  System Testing - Integration testing is done among newly created modules.

Integration testing is also carried out between new modules and the system. Finally

the system is tested as a whole, following regressive testing procedures.

 Acceptance Testing - After testing the system internally, it is tested for acceptance

with the help of users. If at this state, user complaints some issues they are addressed

or noted to address in next iteration.

 Delivery - After acceptance test, the system is deployed all over the organization

either by small update package or fresh installation of the system. The final testing

takes place at client end after the software is delivered.

Training facility is provided if required, in addition to the hard copy of user manual.

 Maintenance management - Configuration management is an essential part of

system maintenance. It is aided with version control tools to control versions, semi-

version or patch management.

Software Re-engineering :-

When we need to update the software to keep it to the current market, without impacting its

functionality, it is called software re-engineering. It is a thorough process where the design

of software is changed and programs are re-written.

Legacy software cannot keep tuning with the latest technology available in the market. As

the hardware become obsolete, updating of software becomes a headache. Even if software

grows old with time, its functionality does not.

For example, initially Unix was developed in assembly language. When language C came

into existence, Unix was re-engineered in C, because working in assembly language was

difficult.

Other than this, sometimes programmers notice that few parts of software need more

maintenance than others and they also need re-engineering.

Re-Engineering Process :-

 Decide what to re-engineer. Is it whole software or a part of it?

 Perform Reverse Engineering, in order to obtain specifications of existing software.

 Restructure Program if required. For example, changing function-oriented programs

into object-oriented programs.

 Re-structure data as required.

 Apply Forward engineering concepts in order to get re-engineered software.

There are few important terms used in Software re-engineering

Reverse Engineering :-

It is a process to achieve system specification by thoroughly analyzing, understanding the

existing system. This process can be seen as reverse SDLC model, i.e. we try to get higher

abstraction level by analyzing lower abstraction levels.

An existing system is previously implemented design, about which we know nothing.

Designers then do reverse engineering by looking at the code and try to get the design. With

design in hand, they try to conclude the specifications. Thus, going in reverse from code to

system specification.
Program Restructuring :-

It is a process to re-structure and re-construct the existing software. It is all about re-

arranging the source code, either in same programming language or from one programming

language to a different one. Restructuring can have either source code-restructuring and data-

restructuring or both.

Re-structuring does not impact the functionality of the software but enhance reliability and

maintainability. Program components, which cause errors very frequently can be changed, or

updated with re-structuring.

The dependability of software on obsolete hardware platform can be removed via re-

structuring.

Forward Engineering :-

Forward engineering is a process of obtaining desired software from the specifications in

hand which were brought down by means of reverse engineering. It assumes that there was

some software engineering already done in the past.

Forward engineering is same as software engineering process with only one difference – it is

carried out always after reverse engineering.

Component reusability:-

A component is a part of software program code, which executes an independent task in the

system. It can be a small module or sub-system itself.

Example

The login procedures used on the web can be considered as components, printing system in

software can be seen as a component of the software.

Components have high cohesion of functionality and lower rate of coupling, i.e. they work

independently and can perform tasks without depending on other modules.

In OOP, the objects are designed are very specific to their concern and have fewer chances to

be used in some other software.

In modular programming, the modules are coded to perform specific tasks which can be used

across number of other software programs.

There is a whole new vertical, which is based on re-use of software component, and is

known as Component Based Software Engineering (CBSE).

Re-use can be done at various levels

 Application level - Where an entire application is used as sub-system of new

software.

 Component level - Where sub-system of an application is used.

 Modules level - Where functional modules are re-used.

Software components provide interfaces, which can be used to establish

communication among different components.

Reuse Process

Two kinds of method can be adopted: either by keeping requirements same and adjusting

components or by keeping components same and modifying requirements.

 Requirement Specification - The functional and non-functional requirements are

specified, which a software product must comply to, with the help of existing system,

user input or both.

 Design - This is also a standard SDLC process step, where requirements are defined in

terms of software parlance. Basic architecture of system as a whole and its sub-

systems are created.

 Specify Components - By studying the software design, the designers segregate the

entire system into smaller components or sub-systems. One complete software design

turns into a collection of a huge set of components working together.

 Search Suitable Components - The software component repository is referred by

designers to search for the matching component, on the basis of functionality and

intended software requirements..

 Incorporate Components - All matched components are packed together to shape

them as complete software.

DESCRIPTION OF THE NATURE OF THE PHASE:-

This section will cover what the software maintenance phase is about. As briefly seen

in the introduction, software maintenance is not limited to the correction of latent

faults. The term software maintenance usually refers to changes that must be made to
 software after they have been delivered to the customer or user. The definition of

software maintenance by IEEE [1993] is as follows: The modification of a software

product after delivery to correct faults, to improve performance or other attributes, or

to adapt the product to a modified environment. The following subsections will discuss

different types of software maintenance, the significance and the characteristics of

software maintenance.

CONCLUSION:-

Maintenance clearly plays an important role is the life cycle of a software product. As

noted earlier, the cost of maintenance in the United States has been estimated at more

than $70 billion annually for more than ten billion lines of existing code. While

“traditional maintenance” applies only to corrective maintenance – fixing bugs in the

code, the maintenance phase also incorporates three other main aspects that are

considered to be elements of software evolution. Adaptive maintenance serves to

modify the software for use in new environments, such as a new hardware platform or

interfacing with a different database system. Perfective maintenance concerns adding

new functionality to a product, typically as a result of a customer request. Finally,

preventive maintenance increases the maintainability of a system, through updating

documentation or changing the structure of the software. There are a number of models

of maintenance that serve to organize the five main tasks of the phase: isolating and
analyzing the problem, designing a fix, implementing this fix, testing the resulting

system, and updating documentation to reflect the changes made. A number of tools,

such as automated analyzers and configuration management tools, aid in the

accomplishment of these tasks. Maintenance is heavily impacted by the methods used

to develop a product. Thus, different development methods result in different

maintenance procedures. Iterative development results in the creation of a working

product after each iteration. Therefore, maintenance tasks are carried out on each

working product created. This serves to ensure that problems will not go undiagnosed

and unfixed for long. Agile development, a similar method to iterative, considers the

creation of documentation a secondary objective, thus preventive maintenance can

become problematic. However, because of the iterative nature of agile development,

corrective and perfective maintenance are a natural extension of the development life

cycle. Component Based Software Development shifts the focus of the phase to

maintaining the interaction between components rather than at the source code level, as

the maintenance of the specific components falls to their developer. Open source

development blurs the line between maintenance and earlier phases of the software life

cycle due to the typical lack of a definite release date. However, it offers the advantage

of allowing users to double as co developers, resulting in a large debugging team. As

the cost of maintenance has been estimated at 50% of total life cycle costs, it is

apparent that further study into this field will be necessary. Cost savings in this area

can have a large impact on the overall life of a software project. This paper has

presented an overview of this phase of the project life cycle and its role in 38 various

means of development in the hopes of aiding this further study.

 CONCLUSION

This project as title “Car Parking System” is comes under the Relational Database

Management System (RDBMS). This application is developed with the help of JSP 6.0 and

Microsoft Access. This application can also be run on the network environment so it can be

said as network application.

From a proper analysis of positive points and constraints on the component it can be safely

concluded that the product is a highly efficient GUI based component. This application is

working properly and meeting to all user requirements. This component can be easily plugged

in many other systems.

Nothing is perfect in this world. So, we are also no exception. Although, we have tried our

best to present the information effectively, yet, there can be further enhancement in the
Application. We have taken care of all the critical aspects, which need to take care of during

the development of the Project. Like the things this project also has some limitations and can

further be enhances by someone, because there are certain drawbacks that do not permit the

system to be 100% accurate.

The different areas where we can use this application are:

 Any education institute can make use of it for providing information about student.

 It can be used in offices and modifications can be easily done according to

requirements.

 This application can work on the full web based environment.

Now one can easily plan the journey comfortably as the process is efficient and fast with

being easy to access. Reservations can be made through the Indian railways site or at the

ample reservation centers all over the country. Also now there are authorized agencies which

provide reservation facility on behalf of India railways and without waiting in long line one

can easily book a ticket. The booking is done through an ETicket issue which have a PNR

number of which one has to take a print and just have to show at the station. It not only

provide reservation but cancellation can also be done through this system at ease and one can

use a credit card to complete the process. This being a big step in terms of improvement in the

railway system it is

widely accepted across the country.

Our project is only a humble venture to satisfy the needs in a library. Several user friendly

coding have also adopted. This package shall prove to be a powerful package in satisfying

all the requirements of the organization.

 The objective of software planning is to provide a frame work that enables the manger

to make reasonable estimates made within a limited time frame at the beginning of the

software project and should be updated regularly as the project progresses. Last but not

least it is no the work that played the ways to success but

LIMITATIONS OF EXISTING SYSTEM: -

Data redundancy:-

It means that same data fields appear in many different files and often in different formats. In

manual system, it poses quite a big problem because the data has to be maintained in large

volumes but in our system, this problem can be overcome by providing the condition that if

the data entered is duplicate, it will not be entered, otherwise, updating will take place.

Difficulty in accessing the data:-

In manual system, searching information is time consuming but in our system, any

information can be accessed by providing the primary key.

Unsatisfactory security measures:-

In manual system, no security measures were provided but in this system, password security

has been provided. The person can access the system by providing the correct password

otherwise he is denied the access

BIBLIOGRAPHY

1) Head First Java 2nd Edition

2) http://java.sun.com/javase/technologies/desktop/

3) http://www.roseindia.net/jdbc/jdbc-access/CreateTable.shtml

4) http://www.jdbc-tutorial.com/

5) Java and Software Design Concepts by A Press