Project name Enrollment Number

CERTIFICATE

This is to certify that the project entitled “CAB BOOKING SYSTEM” is a

bonefited report of the work carried out by -------------------------------under the
guidance and supervision for the award of the degree of Bachelor of
Computer Engineering at LDRP Institute of Technology and Research -
Gandhinagar, Gujarat.
To the best of my knowledge and belief, this work embodies the work of candidate
himself/herself, has duly been completed, fulfills the requirement of the ordinance
relating to the Bachelor degree of the university and is up to the standard in respect of
content, presentation and language for being referred to the examiner.

Guide name,

Designation,

CE Department,

LDRP ITR, Gandhinagar

Prof Ashish Patel

H.O.D.

CE Department,

LDRP ITR, Gandhinagar

1
Project name Enrollment Number

-:ACKNOWLEDGEMENT:-

2
Project name Enrollment Number

-:INDEX:-
1) Introduction……………………………………………………….......
Project Profile
Project Summary
Project Purpose
Project Goals
Project Scope

2) Project Management…………………………………………………
Project Planning & Scheduling
Risk Management
Estimation

3) System Requirement Study………………………………………..

User Characteristics
Hardware Requirements
Software Requirements

4) Tools and Technology…………………………………………….......

Technology Study
Feasibility Study

5) System Analysis and Design ………………………………………..

Usecase Diagram
Class Diagram
Activity Diagram
Sequence Diagram
Dataflow Diagram
E-R Diagram

6) Testing ………………………………………………………………………..
Testing Plan
Testing Strategy
Testing Method
Test Class

3
Project name Enrollment Number

7) Screen Shots ………………………………………………………………

8) Conclusion…………………………………………………………………..
Advantages
Limitations
Future Expansions
Conclusions

9) Bibliography………………………………………………………………..

4
Project name Enrollment Number

-:Preface:-

 Project during the study is the bridge between the theoretical and practical knowledge.
The main objective of the project is to get details about the operation process being
carried out within the company. Theory of any subject is important but without its
practical knowledge, it becomes useless.

 Practical training polishes the theoretical aspects of the technical studies. The aim is
to open up the window of project knowledge to a student and give hint of an insight
regarding the operations, processes and trouble shooting of a system.

Objectives of Report

 To develop a system, this can be used for managing the entire data in a
an efficient manner.

 To provide a system that puts the whole system in a single platform.

 To design a system that will have good interface and well documented user guide.

 To understand and enforce the importance of project management aspects, during the
software development.

 To develop a system this can be use for current as well as future aspects of Indian
business for the marketing.

5
Project name Enrollment Number

1…

Introduction

 Project Profile
 Project Summary
 Project Purpose
 Project Goals
 Project Scope

6
Project name Enrollment Number

-:Project Profile:-

Project Title : CAB BOOKING SYSTEM

Organization : LDRP INSTITUTE OF TECHNOLOGY AND

RESEARCH

Tools : Hardware

 Intel Pentium dual core Processor

 256MB RAM

 40 GB HDD

Software

 Operating System :

 Windows XP

 Development :

 HTML,CSS ,JS

 Web Server :

 IIS(Internet Information Server)

Starting Date : 12-06-2024

Ending Date : 18-09-2024

Team Size : 3

Team Members: DHRUV PAREKH

DARPIT PARIKH

KASHYAP KAKADIYA

7
Project name Enrollment Number

Guided By : PROF. JALPA KHAMAR

Submitted To: DEPARTMENT OF COMPUTER ENGINEERING &

INFORMATION TECHNOLOGY,
LDRP INSTITUTE OF TECHNOLOGY & RESEARCH,
GANDHINAGAR

-:Project summary:-
8
Project name Enrollment Number

The Cab Booking System is a digital platform that allows users to easily book, manage, and track cab
rides. It includes features for passengers and drivers, such as real-time cab booking, fare estimation, live
tracking, and secure payments.

Key Features:
 User Registration & Login: Passengers and drivers can sign up via email or phone.
 Cab Booking: Users can book cabs, choose ride options, and get fare estimates.
 Live Tracking: Real-time GPS tracking of cabs with ETA display.
 Payment Integration: Secure online payments or cash options.
 Rating & Feedback: Users rate drivers post-ride.
 Driver Interface: Helps drivers manage bookings and routes.

Technical Stack:
 Frontend: Mobile apps (iOS/Android) and web interface.
 Backend: APIs for ride management and user data.
 GPS & Maps: Integrated for real-time navigation.

Expected Outcomes:
 Seamless cab booking experience for users.
 Optimized ride allocation for drivers.
 Safe and reliable payment processing.

This system enhances convenience for passengers and helps drivers optimize their operations while
ensuring a secure and transparent platform for all users.

9
Project name Enrollment Number

-:PROJECT PURPOSE:-

1. Facilitating Easy Cab Bookings:

The primary goal is to offer a user-friendly platform for customers to book cabs conveniently from their
mobile devices or desktops. This system simplifies the process of finding available cabs, selecting a ride,
and confirming the booking within a few clicks.

2. Real-Time Cab Availability & Tracking:

It provides real-time information on cab availability, ensuring customers can quickly find rides. After
booking, it offers real-time tracking so passengers can monitor the driver's location and estimated time of
arrival (ETA).

3. Enhanced User Experience:

By offering a seamless and efficient interface, the system enhances the overall user experience,
eliminating the need for manual cab-hailing and reducing waiting times.

4. Cost Estimation & Fare Transparency:

The system provides accurate fare estimates before booking, ensuring pricing transparency for the users.
This allows customers to compare costs for different routes or types of rides (e.g., economy, luxury) and
make informed decisions.

5. Efficient Fleet Management:

For cab operators, the system helps manage fleets efficiently. It tracks vehicle locations, driver availability,
and ride schedules, making it easier to manage dispatching and allocation of resources.

6. Driver & Customer Management:

It streamlines the process of managing both drivers and customers. Drivers are assigned rides
automatically or manually by the system, and customer profiles are stored to provide personalized services
(e.g., ride history, payment methods).

7. Safe and Secure Payments:

The system integrates multiple payment options, including credit/debit cards, mobile wallets, and cash,
making the transaction process secure and convenient for both drivers and passengers.

8. Rating & Feedback System:

To maintain service quality, the system allows passengers to rate drivers and provide feedback, ensuring
accountability and continuous improvement in the service.

9. Promotions & Discounts:

The system can incorporate dynamic pricing, loyalty programs, and promotional offers to attract and retain
customers, providing a competitive edge in the market.

10
Project name Enrollment Number

10. Data Analytics & Reporting:

The system collects and analyzes data on bookings, ride patterns, customer preferences, and driver
performance. These insights help operators optimize their services, improve customer satisfaction, and
make data-driven decisions for future growth.

11. Safety & Emergency Features:

It includes safety features such as driver background checks, panic buttons, and route monitoring to ensure
the security of both drivers and passengers.

1. Admin Module

11
Project name Enrollment Number

2. General user Module

 Now we explain each module in detail ….

1. Admin-Module :-

Manage (add, update and delete) the users.

Manage the site, Information.

12
Project name Enrollment Number

2…

Project
Management

 Project Planning and scheduling

 Risk Management
 Estimation

13
Project name Enrollment Number

-:Project Planning and

Scheduling:-

Project Development Approach and Justification:-

 The Project Development approach I have used in our system is the Conventional
Software Engineering approach.
 Project Activities :-

 The major activity in the project includes the following tasks:

 To determine the methodology for the construction of the project.
 To determine the model of the software through which the project will be
identified.
 Determining the first face goals from the aim of the project.
 Designing the software development life cycle for the project.
 Identify the number of phases in the software development life cycle of the
project.

 Project Management:-

 Planning, scheduling and tracking of project:-

 The project planning consists of:

 Selection of Suitable software development model.
 Risk Management Plan, which involves the risk identification and risk
assessments.
 Project Scheduling, which involves the identification of tasks and duration.

14
Project name Enrollment Number

-:Timeline Chart:-

 When creating a software project schedule, the planner begins with a set of tasks. If
automated tools are used, the work breakdown is input as a task network or task
outline. Effort, duration, and start date are then input for each task. In addition, tasks
may be assigned to specific individuals.
 As a consequence of this input, a timeline chart, also called a Gantt chart is generated.
 A Timeline Chart can be developed for the entire project. Timeline Charts depicts a
part of a software project schedule
 All project tasks are listed in the left-hand column. The horizontal bars indicate the
duration of each task. When multiple bars occur at the same time on the calendar, task
concurrency is implied. The diamonds indicate milestones, which indicate the place
where our project reach.
 Once the information necessary for the generation of a timeline chart has been input,
the majority of software project scheduling tools produce project tables a tabular
listing of all project task, their planned and actual start and end table dates and variety
of related information, enable the project manager to track progress.

15
Project name Enrollment Number

Week 1 to 3:

Work Tasks
Week1 Week Week 3
2
Study

Study of HTML

 Study of Data base system

with the language study.

Milestone:

Study of project has been started

Set up of Environment
 Installing req. s/w and o/s

Milestone: Req. s/w is

Installed.

16
Project name Enrollment Number

Week 4 to 8:

Week 4
Work Tasks Week 5 Week 6 Week 7 Week 8

Defining Scope
and Objectives

 Preparing project
definition
 Defining feature of
product

Milestone: Project

Defined.

Requirement &
System Analysis

Milestone :

Analysed System.

System Designing

 Define flow of
project.
 Flowchart
Development.

Milestone:

Designing Is done.

17
 Project name Enrollment Number

Week 9 to 14:

Work Tasks Week10 Week11 Week12 Week13 Week14

Week 9

Coding

 Coding for creating

different forms like
admin, faculty, student,

Milestone:

Coding is done.

Testing

 White box testing

 Black box testing

Milestone:

Testing is Completed.

18
Project name Enrollment Number

Documentation

Milestone:

Documentation is Completed.

-:Project Scheduling:-

 Generalized project scheduling tools and technique can be applied with little
modification to software projects.

19
Project name Enrollment Number

 Program evolution and review techniques (PERT) and critical path method (CPM)
are two project scheduling method that can be applied to software development.
Both techniques are driven by information already developed in earlier project
planning activities:

 Estimate of effort.
 A decomposition of the product function.
 The selection of appropriate process model and task set.
 Decomposition of tasks.

-:Risk Management:-

 Identifying risk and drawing up plans to minimize their effect on the project is called
risk management. Risk may threaten the project, the software that is being developed
or the organization. These categories of risk can be defined as follow:

20
Project name Enrollment Number

1. Project Risks are risks, which affect the project schedule or resources.

2. Product Risks are risks, which affect quality or performance of the software being
developed.

3. Business Risks are risks which affect the organization developing

the software.

Risks Risk Type Description

Technology Business The underlying technology

on which the system is
built is superseded by new
technology.

Requirement Project and Product There will be a larger no.

Change of changes to the
requirements than
anticipated.

Management Project There will be a change of

change organization management
with different priorities.

Hardware Project Hardware that is essential

unavailability to the project will not be
delivered on schedule.

Specification Project and Product Specification of essential

delay interface are not available
on schedule

Size under Project and Product The size of the system is

estimated under estimated

(Table) Risk Management

Risk Identification:-

21
Project name Enrollment Number

 The followings are the possible risks, which is associated with project. We have
identified mainly technical and project risks.

Technical Risks:-

 Our software doesn’t work on all operating system.

 It cannot work if proper system is not installed.

Project Risks:-

 Scope might have been wrongly defined and the project might go in the wrong
direction.
 The time limits might not have been properly calculated as per the scope. If the
project was not properly scheduled, or if the scope was ill defined, it might not be
possible to finish the project at the right time.
 Scope creep could occur. The expectations and requirements have increased or may
be changed.
 Certain technical problems have remained unsolved.

Risk Analysis and Planning:-

 To handle the risks we have prioritized it. The damaging risks can be handled first and
then most likely risks. Since the risk related to the schedule slippage arise primarily
due to the intangible nature of the software, so we had to do the visibility of software
requirements documentation and reviewing the relevant documents during the
developments. Every phase can be broken into the reasonably sized tasks and
milestones can be scheduled for these tasks.

 In this process each identified risk is considered in turn and a judgment made about
the probability and the seriousness of the risk.
The probability of the risk might be assessed as very low (less than 10%), low (10-
25%), moderate (25-50%), high (50-75%) or very high (greater than 75%).
The effects of the risk might be assessed as catastrophic, serious, tolerable or
insignificant.

22
Project name Enrollment Number

Risks Probability Effects

Organizational Very low Catastrophic

financial
problems force
reductions in
project budget

Key staff are ill at Moderate Serious

critical times in
project

Software Very low Serious

component which
should be re-used
contain defect
which limit their
functionality

Changes to the Very low Serious

requirements
which require
major design
rework as
proposed

The organization Very low Tolerable

is restructured so
the different
management are
responsible for
the project

The database Very low Serious

used in system
cannot process as
many transaction
per second as
expected

23
Project name Enrollment Number

3…

System
Requirement Study

24
Project name Enrollment Number

 User Characteristics
 Hardware Requirement
 Software Requirement

25
Project name Enrollment Number

-:USER CHARACTERISTICS:-
 Our project is the college based project (ASK LDRP) this site can be used by
different type of users. We can deal in project with various institutes users, general
users, admin, faculties, and students.

-:HARDWARE REQUIREMENT:-
 As we are preparing a computerized system, obviously the most basic hardware need of
the system is a computer. The minimum requirement is as follows.

 450 MHz Processor

 512 MB RAM

 10 GB HDD

 CD-ROM or DVD-ROM Drive

 Super VGA Monitors (800*600)

 Ms Mouse Pointer

-:SOFTWARE REQUIREMENT:-
26
Project name Enrollment Number

 TOOLS:-

 Administrator (Front End Tools):

 Dreamweaver

 Customer/Client:
 Notepad ++

 Database Management System:

 Server Express Edition 2005
 Internet Information Server

 Others Tools:

 XML
 MS-Office 2007, MS-Office 2003
 Enterprise Architect for Documentation

27
Project name Enrollment Number

4…

Tools &
Technology

 Technology study
 Feasibility Study

28
Project name Enrollment Number

HTML:
 Hyper Text Markup Language (HTML) is the main markup language for
creating web pages and other information that can be displayed in a web
browser.
 HTML is written in the form of HTML elements consisting of tags enclosed
in angle brackets (like <html>), within the web page content. HTML tags most
commonly come in pairs like <h1> and </h1>, although some tags, known
as empty elements, are unpaired, for example <img>. The first tag in a pair is
the start tag, the second tag is the end tag (they are also called opening tags
and closing tags). In between these tags web designers can add text,
tags, comments and other types of text-based content.
 The purpose of a web browser is to read HTML documents and compose them
into visible or audible web pages. The browser does not display the HTML
tags, but uses the tags to interpret the content of the page.
 HTML elements form the building blocks of all websites. HTML
allows images and objects to be embedded and can be used to create PHP
interactive forms. It provides a means to create structured documents by
denoting structural semantics for text such as headings, paragraphs, lists, links,
quotes and other items. It can embed scripts written in languages such
as JavaScript which affect the behavior of HTML web pages.

 Feasibility Study:-
In the conduct of the feasibility study, we consider seven distinct, but inter-related types of
feasibility .They are:-
1. Technical feasibility

2. Operational feasibility
3. Economic feasibility
4. Social feasibility
5. Management feasibility
6. Legal feasibility
7. Time feasibility

29
Project name Enrollment Number

 TECHNICAL FEASIBILITY

This is concerned with specifying and software that will successful satisfy the user
requirement the technical needs of the system may vary considerably, but might include:
 The facility to produce outputs in given time.
 Response time under certain conditions.
 Ability to process a certain volume of tasks at a particular speed.
 Facility to communicate data to distant location
In examining technical feasibility, configuration of the system is given more importance
than the actual make of hardware .The configuration should give the complete picture
about the system’s requirements:-
At the feasibility stages, it is desirable that two or three different configuration will be
pursued that satisfy the key technical requirement but which represent different levels of
ambition and cost. Investigation of these technical alternatives can be aided by approaching a
range of supplies for preliminary discussion out of all types of feasibility. Technical
feasibility generally is the most difficult to determine.
 OPERATIONAL FEASIBILITY
It is mainly related to human organizational and political aspects .The points to be
considered are:
1. What change will be brought with the system?
2. What organizational structures are distributed?
3. What new skills will be required? Do the existing staff members have these skills?
4. If not, can they be trained in due course of time?

Generally Project will not be rejected simply because of Operational infeasibility but
such consideration is likely to critically affect the nature and scope of the eventual
recommendation. This feasibility study is carried out by a small group of people who are
familiar with information system techniques who understand the parts of the business that
are relevant to the project and are skilled in system analysis and design process.

 ECONOMIC FEASIBILITY
Economic analysis is the most frequently used technique for evaluation the effectiveness
of a proposed system. More commonly known as Cost/benefits analysis: the procedure is
to determine the benefits and savings that are expected from a proposed system and
compare them with costs. If benefits outweigh costs, a decision is token to design and
implement the system. Otherwise further justification or alternative in the proposed
system will have to be made if it is to have a chance of being approved. This is an
ongoing effort that improves in accuracy at each of the system life cycle.

30
Project name Enrollment Number

 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 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 FEASIBLE
Legal feasible is 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.

31
Project name Enrollment Number

5…

System Analysis
 Use Case Diagram
 Class Diagram
 Activity Diagram
 Sequence Diagram
 Dataflow Diagram
 E-R Diagram

-:System Design:-
32
Project name Enrollment Number

The next phase in the System Development life cycle is a system design.
The designing part begins after the analysis of the system and is aimed at defining
how to do the things. Any design has to be constantly evaluated to ensure that it
meets the requirements, is practical and workable in the given environment. If there are
a number of alternatives, then all alternatives are evaluated and the best possible
solution is implemented.

 Approaches to Design:-
There are two main approaches to design, which are:

1) Data Centered Approach.

2) Process Centered Approach.
In both the approaches, the other factor cannot be ignored i.e. process cannot be
ignored in data centered approach and vice versa. The data centered approach starts
from data structures first and then the processes and the process centric approach
aim at defining all the processes first and data structure at the end. Both the
approaches have their advantages and disadvantages.

We use the Data Centered approach in the design of the system. The Data-Flow
Diagram and the Entity-Relationship diagram form the basic input to the design phase.
The Data Centered approach is the principal of Object Oriented Design where a
collection of data elements and its associated characteristics (processes) are defined
as objects.

-:USECASE dIAGRAM:-

33
Project name Enrollment Number

-:CLASS DIAGRAM :-

34
Project name Enrollment Number

-:SEQUENCE DIAGRAM
:-
35
Project name Enrollment Number

-:DATA FLOW DIAGRAM

(DFD):-

36
Project name Enrollment Number

-:CONTEXT LEVEL DIAGRAM

37
Project name Enrollment Number

-:FIRST LEVEL DFD:-

38
Project name Enrollment Number

39
Project name Enrollment Number

-:ENTITY RELATIONSHIP
DIAGRAM:-

40
Project name Enrollment Number

6…

Testing

 Testing Plan
 Testing Strategy
 Testing Methods

41
Project name Enrollment Number

-:TESTING PLAN:-

 Development of a complex client/server three tier application requires that a

methodology be developed for more effective application or software testing and
quality assurance. Testing is made to find errors in the application. The strategy
adopted for the testing in our application.

-:TESTING STRATEGY:-

“Testing cannot show the absence of defect. It can only show that software

errors are present.”

 Testing is the process of executing a program with the explicit intention of finding
errors that is, making the program fail. Testing is very crucial and most expensive
phase of the software development. Before delivering the system, the process of
rigorous testing is done to check that software works as it is expected and meets its
specifications. For that two testing strategies are there Code Testing & Specification
Testing. We have used both of them at different levels of code development.

 TESTING (WHITE BOX TESTING)

 The code-testing strategy examines the logic of the program. To follow this testing
method, test cases should be developed that result in executing every instruction in the
program or module; that is, every path through the program is tested. A path is a
specific combination of conditions that is handled by the program.
This testing is used at initial stage of the development, as code volume is very less at
this stage. It checks only the aspects are implemented correctly or not.

But this strategy does not indicate the code meets its specifications nor does it
determine weather all aspects are even implemented. So with this, another strategy is
also used.

42
Project name Enrollment Number

 SPECIFICATION TESTING (BLACK BOX TESTING)

 In this strategy, the specifications stating what the program should do and how it
should perform under various conditions are examined. Test cases are developed
for each condition or combination of conditions
 The analyst does not look into the program to study the code and is not concerned
about weather every instruction or path through the program is tested. This is
more efficient method, since it focuses on the way software is expected to be used.

-:TESTING METHOD:-

 Different types of testing method are used,

 UNIT TESTING:-
 In it analyst tests the program making up a system. The software units in a
system are the modules and routines that are assembled and integrated to
perform a specific function.
 It focuses on modules, independently of one another, to locate errors. This
enables the tester to detect errors in coding and logic that are contained within
the module alone.

 Bottom-Up Unit Testing:-

 It can be performed from the bottom up, starting with the smallest and lowest-
level modules and proceeding one at a time. For each module in bottom-up
testing, a short program executes the module and provides the needed data, so
that the module is asked to perform the way it will when embedded within the
larger system.

 Top-Down Unit Testing:-

 As the name implies, begins with the upper-level modules. However, since the
detailed activities usually performed in lower-level routines are not provided,

43
Project name Enrollment Number

stubs are written. A sub is a module can be called by the upper-level module
and that, when reached properly, will return a message to the calling module,
indicating a proper interaction occurred.

 SYSTEM TESTING:-
 System testing does not test the software per se but rather the integration of
each module in the system. It also tests o find discrepancies between the
system and its original objective, current specifications and system
documentation.
 The primary concern is the compatibility of individual modules. Analysts are
trying to find areas where modules have been designed with different
specifications.
 Test cases are designed to test the system and according to the submitted test
cases test data are determined and then he system is tested according to
different test objectives.

44
Project name Enrollment Number

7…

Screen
Shots

45
Project name Enrollment Number

-:SCREEN SHOTS AND USER MANUAL:-

 The system must be user friendly and user interface is the key point of success of
system. How the user can interact with system depends on features and design of the
system.
 .Net technology provides us rich GUI, so here we had designed all pages with Visual
Basic.net controls.
 The points that we have to keep in mind are:
 Design of all forms with system must follow some sort of uniform method. e. g. Font
size of form must be same in all forms. Command button and text box should have
same size as possible.

 Color is center of attraction but while designing the real management system, the
color of almost form must be light and same.
 Size of form and sequence of forms cannot be ignored.
 Minimum action should reflect optimum output.
 Since message box and tool tip text provide user friendly environment, so they are
suggested.
 Complexity must be less.

Some special type of input data format should be specified if required

46
Project name Enrollment Number

General Home Page:-

 This is the first page anyone can see when enter into site where he/she can see only
general information like how many colleges are there, what are the rules and about
contact person.
 To enter into the site he/she has to provide the Username and password after that they
can see further information.

47
Project name Enrollment Number

48
Project name Enrollment Number

49
Project name Enrollment Number

50
Project name Enrollment Number

8…

Conclusion

 Advantages
 Limitations
 Future Expansions
 Conclusions

51
Project name Enrollment Number

-:ADVANTAGES OF THE SITE:-

 This is a digital world. This site gives you a virtual ride in the history of Ahmedabad .

-:LIMITATIONS OF THE SITE:-

 Due to the time limitations I can’t make the dynamic site.

 Geolocation is impossible for this site.
 I am going to improve this in future and I will try to solve this and will trying to
remove limitations from the site.

-:FUTURE ENHANCEMENTS:-

 In the future I want to implement this site for the different cities.
 This is just difficult but I will go into that direction try to increase the functionality of
the site.

-:CONCLUSIONS:-
 During the period of project I came to know the practical aspects of Web-Site
development that sound our knowledge in HTML5 and CSS3.
 HTML5 and CSS3 are brand new technology and I will improvement my skill in
these fields.

52
Project name Enrollment Number

9…

Bibliography

-:REFERENCE BOOKS:-
 The Ultimate HTML4 Code Book

53
Project name Enrollment Number

By- Karl Moore

 THE COMLETE REFRENCE WITH HTML4
By- Syngress Press

-:WEBSITES:-
 www.google.com

 www.codeproject.com

 www.startvndotnet.com

 www.vbcity.com

 msdn2.microsoft.com

 www.codeguru.com

54