VEHICLE SERVICE CENTER

MANAGEMENT SYSTEM

MAJOR PROJECT

Submitted by

A.MONISHA
RollNo:20MCA010

In partial fulfillment of the requirement for

the award of the degree of

MASTER OF COMPUTER APPLICATIONS

Dr. MAHALINGAM COLLEGE OF

ENGINEERING AND TECHNOLOGY
POLLACHI - 642 003
(Approved by AICTE, Affiliated to Anna University and
Accredited by NBA & NAAC with “A++” Grade)

MAY 2022

i
 Dr. MAHALINGAM COLLEGE OF ENGINEERING

AND TECHNOLOGY POLLACHI – 642 003

Department of Computer Applications (MCA)

MAJOR PROJECT

MAY 2022

This is to certify that the project entitled

Vehicle Service Center Management System

Is the bonafide record of project work done by

A.MONISHA

Roll No: 20MCA010

Of Master of Computer Applications during the year 2021-2022

Project Guide Head of the Department

MR. K. MADUSUDANAN MCA., M.Phil., Dr. R. MUTHUSAMI, M.C.A., M.Phil., Ph.D

Assistant Professor/MCA Head &Assistant Professor(ST/MCA)

Submitted for the Project Viva-Voce examination held on

Internal Examiner External Examiner

ii
DECLARATION
 DECLARATION

I affirm that the project work titled “Vehicle Service Center MANAGEMENT
SYSTEM” being submitted in partial fulfillment for the award of Master of Computer
Applications is the original work carried out by me. It has not formed the part of any other
project work submitted for award of any degree or diploma, either in this or any other
University.

(Signature of the Candidate)

A.MONISHA
Roll No: 20MCA010

I certify that the declaration made above by the candidate is true

(Signature of the Guide)

MR. K. MADUSUDANAN MCA., M.Phil.,
Assistant Professor/MCA
ACKNOWLEDGEMENT
 ACKNOWLEDGEMENT

I express my gratitude to Dr. C. RAMASWAMY, M.E., F.I.V., Secretary, NIA

Educational Institutions, Pollachi, for having provided me the facilities to do the project
successfully.

I express my sincere thanks to Dr. A. RATHINAVELU, B.E., M.Tech., Ph.D .,

Principal, Dr. Mahalingam college of Engineering and Technology, Pollachi, for having
provided me the facilities to do the project successfully.

I owe deep sense of gratitude to Dr. R. MUTHUSAMI, M.C.A., M.Phil., Ph.D.,

Head of Department of Computer Applications for appreciating my goal. I express my
sincere thanks to his for his constantan couragement.

I express my thanks to my guide MR. K. MADUSUDANAN MCA., M.Phil., Department of

Computer Applications for his/her valuable guidance and support to meet the successful completion of my
project.

I express my sincere thanks to all staff members of Department of Computer

Applications for their encouragement and valuable guidance throughout this project.

Last but not the least, I would like to thank my family and my friends for putting up
with me spending so much time providing encouragement and valuable suggestions, throughout
the project tenure.

iv
ABSTRACT
 ABSTRACT

In this Project Entitled Named as “vehicle service center” Nowadays many peoples do not spend
more time to purchase services and goods for their daily life. Therefore the buyers would like to purchase
services and goods through online based. To full fill that kind of consumers need and to make
improvements on company’s business activities, the vehicle service center Company decided to improve the
business trend through online. Because the company is keeping their company records in printed papers and
they have found some inconveniences on the traditional paper system to maintain their business. The “Web
based Vehicle Service Management System” is to provide customers to online booking for their vehicle
from their places, With the help of this online system “vehicle service” can able to maintain their
relationship with their customers through this online system and they are able to maintain their day to day
activities such as calculating income and expenditure details, customers details, and service details. So they
introduced the Web based Vehicle Service Management System to solve above problems. This system
development with prototyping is used to develop methodology and design with object oriented concept.
This Web based Vehicle Service Management System was mostly been developed using some modern open
sourced tools and software. The management likes to save the time and decrease the work load by using this
system and may help them to achieve their goal.
TABLE OF CONTENT
 TABLE OF CONTENTS

CHAPTER NO TITLE PAGE NO

ABSTRACT V
LIST OF FIGURES viii
LIST OF ABBREVIATIONS ix
LIST OF TABLES x
1 INTRODUCTION 1
1.1 Overview of the project 1
2 SYSTEM ANALYSIS 2
2.1 Existing System 2
2.2 Proposed System 2
3 SYSTEM SPECIFICATION 3

3.1 Hardware Specification 3

3
3.2 Software Specification
3.3 About the software
4 PROJECT DESCRIPTION 7
5.1 Module Description 7

5 System Design 8
5.1 Data Flow Diagram 8
5.2 System Flow Diagram 10
5.3 Entity Relationship Diagram 11

5.4 Use Case Diagram 12

5.5 Table Design 13

vi
6 SYSTEM TESTING 14
6.1 Testing Methodologies 14
6.1.1 Unit Testing 14
6.1.2 Integration Testing 14
6.1.3 Functional Testing 15
6.1.4 System Testing 15
6.1.5 White Box Testing 15
6.1. 6 Black Box Testtin
6.2 Test Cases 16
7 SYSTEM IMPLEMENTATION 18
7.1 System Implementation 18
7.2 System Maintenance 19
8 CONCLUSION AND FUTURE
20
ENHANCEMENTS
8.1 Conclusion 20
8.2 Future Enhancements 20
9 APPENDICES 21
9.1 Source Code 21
9.2 Screen Shots 23
10 BIBLIOGRAPHY 28

vii
LIST OF FIGURES
 LIST OF FIGURES

FIG NO DESCRIPTION PAGENO

5.1 DATA FLOW DIAGRAM 8

5.2 SYSTEM FLOW DIAGRAM 10
5.3 ENTITY RELATIONSHIP DIAGRAM 11
5.4 USECASE DIAGRAM 12

vi
ii
 LIST OF ABBREVATIONS

S.NO DESCRIPTION ABBREVATION

1. CSS Cascading Style Sheet

2. DFD Data Flow Diagram

3. HTML Hyper Text Markup Language

4. ER Entity Relationship

ix
 LIST OF TABLES

TABLE.NO DESCRIPTION PAGE NO

5.5.1 USER 13

5.5.2 ADMIN 13
5.5.3 SERVICE_LIST 13

x
INTRODUCTION
 CHAPTER 1
INTRODUCTION

1.1 OVERVIEW OF THE PROJECT

In this Project Entitled Named as “vehicle service center” Nowadays many peoples do not
spend more time to purchase services and goods for their daily life. Therefore the buyers would
like to purchase services and goods through online based. To full fill that kind of consumers need
and to make improvements on company’s business activities, the vehicle service center
Company decided to improve the business trend through online. Because the company is keeping
their company records in printed papers and they have found some inconveniences on the
traditional paper system to maintain their business. The “Web based Vehicle Service
Management System” is to provide customers to online booking for their vehicle from their
places, With the help of this online system “vehicle service” can able to maintain their
relationship with their customers through this online system and they are able to maintain their
day to day activities such as calculating income and expenditure details, customers details, and
service details. So they introduced the Web based Vehicle Service Management System to solve
above problems. This system development with prototyping is used to develop methodology and
design with object oriented concept. This Web based Vehicle Service Management System was
mostly been developed using some modern open sourced tools and software. The management
likes to save the time and decrease the work load by using this system and may help them to
achieve their goal.

1
SYSTEM STUDY
 CHAPTER 2

SYSTEM STUDY

2.1 EXISTING SYSTEM

In existing manual system of the company maintains their records in log book. The company
divided their manager level into two top level management. They are administrator level, and
Regional level management. The customers make booking through telephone and the
administrator and staff of the company manage their booking record in manually. Then they gave
the information about booking to Branch manager
2.1.1 DRAWBACKS OF EXISTING SYSTEM

1. Hand written contract documents (booking list, payment vouchers, etc.)

2. Inflexibility of finding details of booking.
3. Confidential data is recorded in a log book.
4. No proper customer history and documentation.
5. Calculations are done manually.
6. Complex monitoring of business progress.
7. Poor communication methods with the customers in business.
2.2 PROPOSED SYSTEM

In this Project Entitled Named as “vehicle service center” Nowadays many peoples do not
spend more time to purchase services and goods for their daily life. Therefore the buyers would
like to purchase services and goods through online based. To full fill that kind of consumers need
and to make improvements on company’s business activities, the vehicle service center
Company decided to improve the business trend through online. Because the company is keeping
their company records in printed papers and they have found some inconveniences on the
traditional paper system to maintain their business.

2
SYSTEM SPECIFICATION
 CHAPTER 3
SYSTEM SPECIFICATION
3.1 HARDWARE SPECIFICATION

 Processor : Pentium-IV
 Memory : 256 MB Ram
 Processor speed : 2.66 GHz

3.2 SOFTWARE SPECIFICATION

 Operating System : Windows 10

 Front-End : HTML,CSS,C#
 Back-End : C#

3.3 ABOUT THE SOFTWARE

FRONT END-ASP.NET

THE VISUAL STUDIO .NET FRAMEWORK

The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet.
OBJECTIVES OF .NET FRAMEWORK
1. To provide a consistent object-oriented programming environment whether object codes is
stored and executed locally on Internet-distributed, or executed remotely.
2. To provide a code-execution environment to minimizes software deployment and
guarantees safe execution of code.
3. Eliminates the performance problems.
There are different types of application, such as Windows-based applications and Web-
based applications. To make communication on distributed environment to ensure that code
be accessed by the .NET Framework can integrate with any other code.
3
COMPONENTS OF .NET FRAMEWORK

THE COMMON LANGUAGE RUNTIME (CLR)

The common language runtime is the foundation of the .NET Framework. It manages
code at execution time, providing important services such as memory management, thread
management, remoting and also ensures more security and robustness. The concept of code
management is a fundamental principle of the runtime. Code that targets the runtime is
known as managed code, while code that does not target the runtime is known as unmanaged
code.
THE .NET FRAME WORK CLASS LIBRARY

It is a comprehensive, object-oriented collection of reusable types used to develop

applications ranging from traditional command-line or graphical user interface (GUI)
applications to applications based on the
Latest innovations provided by ASP.NET, such as Web Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load the common
language runtime into their processes and initiate the execution of managed code, thereby
creating a software environment that can exploit both managed and unmanaged features. The
.NET Framework not only provides several runtime hosts, but also supports the development of
third-party runtime hosts.
Internet Explorer is an example of an unmanaged application that hosts the runtime (in
the form of a MIME type extension). Using Internet Explorer to host the runtime to enables
embeds managed components or Windows Forms controls in HTML document

PROBLEM ANALYSIS
FEATURES OF THE COMMON LANGUAGE RUNTIME
The common language runtime manages memory; thread execution, code execution, code
safety verification, compilation, and other system services these are all run on CLR.
4
  Security
 Robustness
 Productivity
 Performance

SECURITY
The runtime enforces code access security. The security features of the runtime thus
enable legitimate Internet-deployed software to be exceptionally feature rich. With regards to
security, managed components are awarded varying degrees of trust, depending on a number of
factors that include their origin to perform file-access operations, registry-access operations, or
other sensitive functions.

ROBUSTNESS
The runtime also enforces code robustness by implementing a strict type- and code-
verification infrastructure called the common type system (CTS). The CTS ensures that all
managed code is self-

Describing. The managed environment of the runtime eliminates many common software issues.

PRODUCTIVITY
The runtime also accelerates developer productivity. For example, programmers can
write applications in their development language of choice, yet take full advantage of the
runtime, the class library, and components written in other languages by other developers.

PERFORMANCE

The runtime is designed to enhance performance. Although the common language runtime
provides many standard runtime services, managed code is never interpreted. A feature called
just-in-time (JIT) compiling enables all managed code to run in the native machine language of
the system on which it is executing. Finally, the runtime can be hosted by high-performance,
server-side applications, such as Microsoft® SQL Server™ and Internet Information Services
(IIS).

5
DATA ACCESS WITH ADO.NET
As you develop applications using ADO.NET, you will have different requirements for
working with data. You might never need to directly edit an XML file containing data - but it is
very useful to understand the data architecture in ADO.NET.
ADO.NET offers several advantages over previous versions of ADO:
 Interoperability
 Maintainability
 Programmability

MySQL Server:
Databases are a great way to store information they can store your personal contact list,
your financial records, your household inventory, or even a listing of your favorite websites.
Databases are able to store large amounts of useful information in a logical structure that allows
for quick retrieval in any user defined format. Community libraries are renowned for their use of
large database systems to store the mass amounts of usable information that they collect and
share.

6
PROJECT DESCRIPTION
 CHAPTER 4
PROJECT DESCRIPTION
4.1 MODULES DESCRIPTION
MODULES:
1. ADMIN MODULE
2. USER MODULE
4.1.1 ADMIN MODULE:

1.REGISTER:
1.This module for the purpose of providing authentication to the user and an
organization by the way of different login method.
1. Monitor user log detail
2. This module track and store the user id and phone number.
2. LOGIN:
The Registered User Can be Allowed to view inner details for which he
Permitted.
3. SERVICE ADD

This feature allows to add new service in service add and view
the details of the service by logging in using their unique Login id and
password.

4.1.2 USER DETAILS:

1. REGISTER:
This module is used for customer book the service. User can entroll the
name and email to the booking service, and book the service it will going to
a mail to the admin It includes user id, customer name, mobile number,
address, e- mail id etc.
2. VIEW THE SERVICE:
The customer can view the service and price and select the service they want to use
for their vehicle

7
SYSTEM DESIGN
 CHAPTER 5
SYSTEM DESIGN

5.1 DATA FLOW DIAGRAM

Data flow diagrams are directed graphs in which the nodes specify processing activities
and arches that specify the data items transmitted between processing nodes. It is a
representation because it is used to convey the flow of data and the processes involved in a
problem.
A data flow diagram can be used to represent data flow between individual statements or
block statements in a routine, data flow between sequential routines, between concurrent
processes or data flow in a distributed computing system, where each node represents a
geographically remote processing unit.

Level 0:

ADMIN Vehicle service user

center

Fig No: 5.1

8
Level 1:

user Invalid Failure Error

message Report

valid

View service

Select
service

Result
Report

Fig No: 5.2

Level 2:
Customer Customer details Take service
Registration

View service Service report

Admin login admin details order

Edit service View order

Fig No: 5.3 Order report

9
5.2 SYSTEM FLOW DIAGARM

Start

user admin

login no registration
login

Profile view
Service provider

Service List Order views

View the selected mail

service
Fig No: 5.4
logout logout

10
 5.3 ENTITY RELATIONSHIP DIAGRAM

passwo
rd
email
cust_id
login Vehicle item name
brands service_id
username email
Vehicle
type

vehicle amount
user Fig No: 5.5 admin
phone
17

orders
Take Service_list
service

Service_id
amount

Cust_id

Fig 5.5

11
5.4USECASE DIAGRAM

REGISTRATIO
N

LOGIN

SERVICE
USER ADMIN

ORDER

MAIL

Fig No: 5.6

12
5.5 TABLE DESIGN
5.5.1 Table Name: USER
Key :Primary Key(cust_id)

NAME NULL/NOTNULL TYPE KEY

Cust_id NOTNULL varchar (50) PRIMARYKEY

Name NULL varchar (50)

Email NULL varchar (50)

Password NULL varchar (50)

Vehicletype NULL varchar (20)

Brand NULL varchar (50)

5.5.2 Table Name: ADMIN

NAME NULL/NOTNULL TYPE KEY

Serviceid NOTNULL INT Foregin key

cust_id NULL VARCHAR(50) Foregin key
Amount NULL Int
Item_name NULL VARCHAR(500)
Email NULL VARCHAR(500)

5.5.3 Table Name: SERVICE_LIST

Key : primary key (serviced)
NAME NULL/NOTNULL TYPE KEY

Serviceid NOTNULL INT Primary key

cust_id NULL VARCHAR(50) Foregin key
Amount NULL Int

13
TESTING
 CHAPTER 6
TESTING

The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub assemblies, assemblies and/or a finished product. It is the
process of exercising software with the intent of ensuring that the software system meets its
requirements and user expectations and does not fail in an unacceptable manner. There are
various types of test. Each test type addresses a specific testing requirement.

6.1 TESTING METHODOLOGIES

6.1.1. Unit Testing
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program input produces valid outputs. All decision branches and
internal code flow should be validated. It is the testing of individual software units of the
application .it is done after the completion of an individual unit before integration. This is a
structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform
basic tests at component level and test a specific business process, application, and/or system
configuration. Unit tests ensure that each unique path of a business process performs accurately
to the documented specifications and contains clearly defined inputs and expected results.
6.1.2. Integration Testing
Integration tests are designed to test integrated software components to determine if they
actually run as one program. Testing is event driven and is more concerned with the basic
outcome of screens or fields. Integration tests demonstrate that although the components were
individually satisfaction, as shown by successfully unit testing, the combination of components is
correct and consistent. Integration testing is specifically aimed at exposing the problems that
arise from the combination of components.
14
6.1.3. Functional Testing
Functional tests provide a systematic demonstration that functions tested are available as
specified by the business and technical requirements, system documentation, and user manuals.
6.1.4. System Testing
System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system testing is the
configuration oriented system integration test. System testing is based on process descriptions
and flows, emphasizing pre-driven process links and integration points.
6.1.5. White Box Testing
White Box Testing is a testing in which the software tester has knowledge of the inner
workings, structure and language of the software, or at least its purpose. It is used to test areas
that cannot be reached from a black box level.

6.1.6. Black Box Testing

Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the software
under test is treated, as a black box, cannot “see” into it. The test provides inputs and responds to
outputs without considering how the software works.

15
6.2 TEST CASES 16
Test Case Test Case Expected Actual Test case
Id Name Outcome Result
1 Login Grant User Test case
access to successfully pass
the login into
applicable the
Main submission
system of correct
login
credentials.
2 Add New If service id Test case
service service entered pass
successfully already
added to the exists in the
system system,
Error
Message is
displayed
.If the
service id
of the new
service is
successfully
added.
3 Email The Email Successfully Test case
contains at added the pass
least one mail id
special
character .
Its empty it
will show
message

17
SYSTEM IMPLEMENTATION
 CHAPTER 7
SYSTEM IMPLEMENTATION
7.1 SYSTEM IMPLEMENTATION PROCEDURES
Implementation is the stage of the project, when the theoretical design is turned into a
working system. System is the major factor. Impact on existing practices shift to user
department. If the implementation stage is not carefully, planned and controlled. Thus, it cannot
be considered to be the more crucial stage in achieving a successful new confidence that the
system will work more effectively.
The implementation stage is a system project in its own right. It involves careful
planning, investigation of the current system and its constraints on implementation, design of
methods to achieve the change our procedures, and evaluation of change over methods.

The implementation plan consists of the following sample steps.

➢ Testing the developed system with sample data.

➢ Detection and correction of errors.

➢ Making necessary changes in the system.

➢ Checking the reports with that of the existing system.

➢ Training and involvement of user personnel.

➢ Installation of hardware and software utilities.

The implementation of the system is easy for any system environment as the software is
portable one.

IMPLEMENTATION PROCEDURES
The implementation phase is less creative than system design. A system project may be
dropped at any time prior to implementation, although it becomes more difficult when it goes the
design phase.

18
7.2 SYSTEM MAINTENANCE
The implementation view of software requirements presents the real world manifestation of
processing function and information structures. In some case, a physical representation is
developed as the first step in software design.
The analyst must recognize the constraints imposed by predefined system elements in and
consider the implementation view of function and information when such view is appropriate.

Implementation Plan
System implementation is the process of making the newly designed system fully
operational. The system is implemented after careful testing. Implementation is a stage in the
project where theoretical design is turned into working system in order to maximize efficiency
and productivity. The most critical stage in achieving a new system is in getting the approval
from the system manager. The newly designed system put into work process, after the testing is
over. The system will be implemented in phase along with existing system and it take over
happens when the full testing is defined to be perfect, till then the parallel run is done.

Implementation procedures are

➢ Implementation simply means converting a new computer system to replace an existing one.

➢ Implementation of computer system to replace a manual system.

After the data has been initially set, the system is ready for use. The change over from the
existing system to new system is a step-by-step process.

19
CONCLUSION AND FUTURE ENHANCEMENT
 CHAPTER 8
CONCLUSION AND FUTURE ENHANCEMENT

8.1 CONCLUSION

The package was designed in such a way that future modifications can be
done easily. The following conclusions can be deduced from the development of the
project.

 Automation of the entire system improves the efficiency

 It provides a friendly graphical user interface which proves to be better when
compared to the existing system.
 It gives appropriate access to the authorized users depending on their permissions.
 It effectively overcomes the delay in communications.
 Updating of information becomes so easier.
 System security, data security and reliability are the striking features.
 The System has adequate scope for modification in future if it is necessary.

8.2. FUTURE ENHANCEMENT

In future we can make the payment through online. Then we can send an alert message
for the customer one who books. While developing “VEHICLE SERVICE CENTER
MANAGEMENT SYSTEM” keeping in the mind all the given and possible condition is found
to be working efficiently. The system is implemented successfully. It can be changed and it can
be updated according to the needs of the user in future. The drawback is that there is no mobile
app interaction; in future we can develop it.
The coding pattern is kept as dynamic as possible with minimum amount of static
values to make it easier for future extensions. As the current system is expected to add more
functionality and dependency according to requirement changes and technology, proper coding
standards and working platform have been kept in mind to produce a quality product.

20
APPENDIX
 CHAPTER 9
APPENDIX
9.1SOURCE CODE
1. Index.php

@model IEnumerable<VechileService_Assignment.Models.ServiceName>
@{
ViewBag.Title = "Index";
}
<div>
<br />
<a href="/Home/Index">
<img src="~/image/backarrow.png"width="30"height="30"/>
</a>
</div>
<h2>Index</h2>
<div>
<ul class="nav navbar-nav" style="float:right !important">
<p>
<a href="/Home/Index">
<img src="~/image/Profile.jpg" width="50" height="50" />
</a>
@Html.ActionLink("Ordered Services", "AdmincsView", "ServiceNames", new {
@class = "btn btn-primary" })
</p>
</ul>
</div
<p>
@Html.ActionLink("Create New", "Create", "Home", new { @class = "btn btn-primary"
})
</p>
<table class="table">
<tr>
<th>
@Html.DisplayNameFor(model => model.Itemname)
</th>
<th>
@Html.DisplayNameFor(model => model.Amount)
</th>
<th></th>
</tr>
@foreach (var item in Model)
{
<tr> 21
 <td>
@Html.DisplayFor(modelItem => item.Itemname)
</td>
<td>
@Html.DisplayFor(modelItem => item.Amount)
</td>
<td>
@Html.ActionLink("Edit", "Edit", new { id = item.ID },new { @class = "btn btn-
success" }) |
@Html.ActionLink("Details", "Details", new { id = item.ID }, new { @class = "btn
btn-primary" }) |
@Html.ActionLink("Delete", "Delete", new { id = item.ID }, new { @class = "btn btn-
danger" })
</td>
</tr>
}
</table>

22
9.2 SCREEN SHOT

Fig 9.1 Home page

Fig 9.2 User Registration

23
Fig 9.3 User Profile

Fig 9.4 Service List

24
Fig 9.5Admin Login

25
Fig 9.6 Admin Page

Fig 9.7 Admin Area

26
Fig 9.8 Mail send

27
BIBLIOGRAPHY
 CHAPTER 10
BIBLIOGRAPHY

10.1 RFERENCED BOOKS

1. Jeffrey R.Shapiro “ASP.NET: The Complete Reference” Tata McGraw-Hill
Publishing Company Limited, 2002.
2. Dave Mercer”ASP.NET: Beginner’s guide” Tata McGraw -Hill Publishing
Company Limited, 2002.
3. Roger S .Pressman ”Software Engineering’‘ McGraw-Hill Publications
4. Eilas M.Awad ”System Analysis And Design” Galogoeia publications(p)Ltd, l992,2’
Edition.
5. “The Language of SQL Kindle Edition” by Larry Rock off
6. “Microsoft ASP.NET and AJAX: Architecting Web Applications”, by Dino
Esposito
7. “ASP.NET 3.5 Unleashed”, by Stephen Walther

10.2 REFERENCED WEB SITES

1. http://www.sourcefordgde.com
2. http://www.jfree.org/
3. http://www.networkcomputing.com/
4. http://www.tutorialpoint/c#.com
5. www.Tenders.com

28