Você está na página 1de 65

PROJECT REPORT

On

Online Cab Booking


Submitted in partial fulfillment of their requirements for the
award of the diploma in

INFORMATION TECHNOLOGY

Under the supervision of


Er.HimanshuKashyap
(Sr. Project Manager-IT)

PNP Intech Learning& Research Center


Lucknow (UP)

Submitted By
Anita Patel

Submitted to
-------------------
Govt. Girls PolytechnicFaizabad

1
ACKNOWLEDGEMENT

I would like to express my deep and sincere gratitude to my supervisor Er.

HimanshuKashyap(PNP Intech Learning & Research Centre)who gave me his full support

and encouraged me to work in an innovative and challenging project for Educational field.

His wide knowledge and logical thinking gave me right direction all the time.

I am deeply grateful my project coordinator for his help and support provided at every step

of the project.

Last but not the least, I thank to all employees of PNP Intech Learning & Research Centre

for their support and co-operation.

Anita Patel

2
PNP/VT17-…..……....

COMPLETION CERTIFICATE

This is to certify that Anita PatelofDIPLOMA (Information Technology)


fromGovt.GirlsPolytechnic Faizabad(Institute) was working on the project entitled “Online Cab
Booking” in PNP Intech Learning & Research Centre. He was engaged with us during 1st June
2017 to 15thJuly2017for a period of 45 days.

He has done an excellent job during his engagement with the Software Development & Testing
Division of the company. He has completed his project during the training tenure. His performance
has been good and satisfactory.

I would like to take this opportunity to express my appreciation to Anita Patelfor his work and
wish him all the very best for his future endeavours.

Regards,
……………………..
___________________
HR-Manager
PNP Intech Learning & Research Center
Lucknow(U.P.)

3
DECLARATION

This is to certify that the project report entitled “Online Cab Booking” is done by me is an

authentic work carried out for the partial fulfillment of the requirements for the award of

the Diploma in “Information Technology” under the guidance of Er. HimanshuKashyap.

The matter embodied in this project work has not been submitted earlier for award of any

degree or diploma to the best of my knowledge and belief.

`
Anita Patel

4
TABLE OF CONTENT

I. Declaration
II. Certificate
III. Acknowledgement
1. Introduction…………………………………………………………………………..…........7-12
1.1 Overview of Organization
1.2 Objectives
1.3 Existing System Description
1.4 Proposed System
1.5 Tools Used
2. System Analysis…………………………………………………………………...............13-24
2.1 Idenification of need
2.2 SDLC Phases
2.2.1 Feasibility Study
2.2.2 Report Approval
2.2.3 System Analysis
2.2.4 System Design
2.2.5 Coding
2.2.6 Testing
2.2.7 Implementation
2.2.8 Maintenance
2.3 Process Description
2.4 Project Model Used
2.5 Data Flow Diagram
3. Software Requirement
Specification………….…………………………………………………………….………..25-26
3.1 Hardware Requirement
3.2 Software Requirement
3.3 Support Maintenance
4. System Design Approach…………………………………………………………………27-28
4.1 Top-Down Designing
4.2 Bottom –Up Designing
4.3 Following Approach

5
5. Low Level Design………………………………………………………………………………………29

5.1 Description of Classes and Methods

6. Data Modeling………………………………………………………………………..25-27
6.1 List of Tables
6.2 Structure of Tables
7. Testing…………………………………………………………………………… 28-31
8. Input-Output Forms………………………………………………………………………….…32-54
8.1 Modularization Details
8.2 User Screenshots
8.3 Admin Screenshots
9. Future Scope……………………………………………………………………………….…55
10. Conclusion……………………………………………..……………………………..60

6
INTRODUCTION

Firstly,Online Cab Booking System specializing in Hiring cabs to customers. It is an online


system through which customers can view available cabs; register the cabs, view profile
and book cabs.Cab booking service is a majortransport service provided by the various
transport operators in a particular city. Mostly peoples use cabservice for their daily
transportations need. The company must be aregistered and fulfils all the requirements
and security standards set bythe transport department.

Online Cab Booking System is a web based platform that allows your customers to book
their taxi's and executive taxis all online from the comfort of their own home or office. The
platform should offer an administration interface where the taxi company can manage the
content, and access all bookings and customer information. More and more Taxi companies
are looking for integrated taxi booking systems as it makes life much easier for (1) The
traveller - this is highly important and in today's internet age people should be able to book
taxis online without having to pick up the phone and (2) the taxi company as all their
bookings are now managed via an automated system which means they have an electronic
record of future and historic bookings

A Cab Booking/Hiring is a system that can be used temporarily for a period of time with a
fee. Hiring a car assists people to get around even when they do not have access to their
ownpersonal vehicle or don't own a vehicle at all. The individual who want to hire/rent a
car must first contact the cab hiring company for the desire vehicle. This can be done
online. At this point, this person has to supply some information such as: dates of rental,
and type ofcar. After these details are worked out, the individual renting the car must
present a valid Identification Card. Most companies throughout the industry make a profit
based of the type of cars. The hiring cabs are categorized into economy, compact, compact
premium; premium and luxury & customers are free to choose any car of their choice based
on their purse and availability of such car atthe time of reservation.

The following Online Cab Booking having the following services:-

1. Enhance Business Processes: To be able to use internet technology to project the rental
company to the global world instead of limiting their services to their localdomain alone,
thus increase their Return onInvestment (ROI).

2. Traveller’s registration: A registration portal to hold traveller’s details, monitor


theirtransaction and used same to offer better and improve services to them.

7
3. Group bookings: Allows the customer to book space for a group in the case of weeding or
corporate parties or meetings.

4. Eco-friendly: The monitoring of the vehicle activity and the overall business becomes
easy and includes the least of paper work.

5. Availability: The software acts as an office that is open 24/7.

6. Efficient: It increases the efficiency of the management at offering quality services to the
customers.

7. User friendly: It provides custom features development and support with the software’s.

8. Security: The subsystem should provide a high level of security and integrity of the data
held by the system, only authorized personnel of the company can gain access to the
company’s secured page on the system; and only users with valid password and username
can login to viewuser’s page.

Overview of Organization

PNP Intech is a complete IT solutions company, providing software development, Website


development, Training and IT services. We are an entity that is focused to provide 100%
satisfaction to our client and anticipate that we will be your preference if when you are
going to promote your business as well as company. We provide the latest technology and
most innovative solutions, allowing us to give our customers the best service possible. We
develop web-sites and web based applications, our area of expertise includes Web Design

8
&Maintenance, Flash based Websites, Web application development, E-commerce, 2D-3D
animation, Search Engine Optimization(SEO), Content Writing.

PROBLEM DEFINITION

In this section we shall discuss the limitation and drawback of the existing system that
forced us to take up this project. Really that work was very typical to manage the daily
errors free records and adding or removing any node from server. This problem produces a
need to change the existing system. Some of these shortcomings are being discussed below:

 Low Functionality

With the existing system, the biggest problem was the low functionality. The
problem faced hampered the work. For small task like adding any new node to
server or deleting a node or keeping daily record we have to appoint minimum two
or three employee.

 Erroneous Input and Output

In the existing system, humans performed all the tasks. As in the human tendency,
error is also a possibility. Therefore, the inputs entered by the person who is
working in the Company, in the registers may not be absolutely foolproof and may
be erroneous. As a result of wrong input, the output reports etc.will also be wrong
which would in turn affect the performance.

 Portability Problem

System that existed previously was manual. As a result, the system was less
portable. One has to carry the loads of many registers to take the data from one
place to another. A big problem was that the system was less flexible and if we
wanted to calculate yearly or monthly maintenance report or efficiency report, then
it was a big headache.

9
 Security-

Security concerns were also one of the motives of the Company for the need of
software. In the registers, the data is not secure as anybody can tamper with the
data written in the registers. While in this software, just a password makes it
absolutely secure from the reach of unauthorized persons.

 Data Redundancy

In the case of manual system, the registers are maintained in which, a lot of data is
written.

 Processing Speed

In manual system maintaining a register and performing the necessary calculation


has proved to be a troublesome job, which takes a lot of time and may affect the
performance of the Company. But with this software we can have all the tasks
performed in a fraction of second by a single click thus making the troublesome job
much easier.

 Manual Errors

When a number of tough tasks are prepared by the humans like preparation of
reports, performing long calculation then some human error are obvious due to a
number of factors like mental strain, tiredness etc. But as we all know that computer
never get tired irrespective of the amount of work it has to do. So this software can
nullify the probability of manual error that improve the performance.

 Complexity in Work

In manual system whenever a record is to be updated or to be deleted a lot of


cutting and overwriting needs to be done on the registers that are concerned that
are deleted or updated record, which makes the work very complex.

10
PROPOSED SYSTEM

The development of this new system contains the following activities, which try to develop
on-line application by keeping the entire process in the view of database integration
approach.
 Secure registration and profile management facilities for Customers.

 Browsing through the e-Mall to see the items that are there in each category of
products like Apparel, Kitchen accessories, Bath accessories, Food items etc.

 Creating a Shopping cart so that customer can Shoppe ‘n’ no. of items and checkout
finally with the entire shopping cart

 Customers should be able to mail the Shop about the items they would like to see in
the Shop

 Secured mechanism for checking out from the Shop( Credit card verification
mechanism)

 Updates to customers about the Recent Items in the Shop.

 Uploading ‘Most Purchased’ Items in each category of products in the Shop like
Apparel, Kitchen accessories, Bath accessories, Food items etc.

11
SYSTEM ANALYSIS

Identification of needs:-

Social and economic factor: a wave of social and economic changes often follows in the
wake of the new technology. New opportunities may arise to improve on a production
process or to do something that was not previously possible. Changes in the ways
individuals are organized into groups may then be necessary, and the new groups may
complete for economic resources with established units.
Technological factor: people have never before in a time when the scope of scientific
inquiry was so broad, so when the speed of applying the new technology accounts for many
changes in the organization.
High level decisions and operating processes: in response to technological, socio-
economical factors, top level managers may decide to recognize operations and introduce
new products. To deal with these needs, people commonly seek new modified information
to support the decision. When that happens, then they obtain turn to a computer system for
help the information users and data processing specialist then work together to complete a
series of steps in a system study to produce output results to satisfy information needs.

Feasibility Study: -

Feasibilitystudyisthesecondstepofthesystem development lifecycle.Thingsare always easy


at the beginning in any software process. In fact nothing is infeasible with unlimited time
and resources. But it is not the fact. So, practically we have to do in limited resources in a
restricted time margin. So for the system to be feasible, following points we have to
consider.

12
The feasibility study is conducted to check whether the candidate system is feasible. The
system which is selected to be the best against the criteria is thereafter designed and
developed. The feasibility study takes in to consideration, the risks involved in the project
development beforehand. Therefore in this phase we have to do feasibility study which is
the test of the website according to its workability, impact on the organization, ability to
meet user need and effective use of resources. We do the feasibility study for website to
analyze the risks, costs and benefits relating to economics, technology and user
organization. There are several types of feasibility depending on the aspect they cover.
Import of these includes:

1. Problem Statement:

To develop a completeBandhan which is a web based application which handles


inquiry regarding the different product available on the website .This enhances the
working ability and reduces the required resources and manpower; also give new
and refreshing look to the interface.

2. Technical Feasibility:
 The current system is built on user interface environment using SQL SERVER 2005 and
ASP.Net which will provide a good and enhanced working environment.
 Provides a user friendly environment.
 Windows OS and ASP.NET software are easily available and easyto Interact.

3. BehaviouralFeasibilty:
During the onsite review of the current system the client showed a positive approach
towards the change over. Any further change in the current system will be accepted
smoothly, as this new developing system is based on GUI interface.

13
4. Alternate Solution:
Right now we are implementing this system using MS SQL SERVER2005 as backend. It can
be structured using MS access or ORACLE8 or above.

5. Risk Analysis :

Risk identification:
Technical risk: - In this project, the only risk can arise if some change occurs in the
technical requirements of the management. As per the requirement, we have taken
ASP.NET as technology for system development.

Software Tools:-

Technology used inOnline Matrimonial Portal:


 Server Side : ASP.Net 4.5 , C# 5.0
 Client Side : Java Script
 Layout : HTML,CSS
 Database : MS-SQL

Platform:-

 Frontend : MSVisual Studio 2012


 Backend : MS-SQL Server 2008 R2

Software Requirement:-

 Operating system : Windows XP/7/8/8.1/10


 Language used : C# with .NET Framework
 Database : MS-SQL Server 2008 R2
 Browser : Internet Explorer
 For Documentation : Microsoft Word 2007/10/13

14
Hardware Tools:-

 System : IBM compatible PC’s

 Processor : Core 2 Duo Processor

 RAM : 2 GB RAM

 HDD : 160 GB

 Output device : : Monitor, Laser Printer

 Input device : Keyboard, Mouse

 LAN connection (Wired)

Request Approval:-
Request approval is the third phaseofsystem development lifecycle. Request approval is
the phase in whichalltherequirementswhichwouldbeprovide in the system arestated. The
request approval is a sort of agreement between theclient and the companywhich is
buildingthis software. Both the parties should be mutuallyagreed on the stated
requirements.

SystemAnalysis:-
System analysisisthephasefollowingthephaseoftherequestapproval.In this phasewetend to
analyzetheoverallsystemwhichwehavetobuild.Systemanalysisis the crucial part in SDLC.

SystemDesign:-
System design means thedesigningofthesystem. TheSystemcanbedone in eitherof the
following twoways:-

 Logical System Design


 Physical System Design

15
Coding:-

Codingisthephasein which
adevelopercodesusinganyprogramminglanguages.Codingconstitutes only20 %of
thewholeproject and which is easiertowrite.Thecodingwork is also done in the
teams;development of thesystem is usuallydoneunderthemmodularprogrammingstyle,
which can beeither top-down approachor bottom-up approach.

Testing:-

Testingisthephasein which thesystemthat has been developed is tested. Testing


comprises ofthe 60%ofthe overalldevelopment of the system. Testingofthesystem is
important because testing aims to uncover thedifferenterrors in thesystem.
Therearevarious different testingtechniques that can beusedforthetestingofthesystem.

Implementation:-

Implementation process involved theinstallationofsoftwareon user’s side.

Process actuallydepends on typeofasystem&various.Optingforsuitableconversionapproach


is astep implementation. The conversion processes are as follows:-

 Parallel Conversion
 Direct Conversion Approach
 Pilot Conversion Approach
 PhaseIn Conversion Approach

Maintenance: -
Merelydevelopingthesystemisnotimportantbutalsomaintenanceis
important.Thecompanythat has
builtthesystemprovidesforsometimefreeofcostmaintenancetotheclient and after that
period it is usuallyapaid service.

16
Process Description:-

Gantt charts mainly used to allocate resources to activities. The resources allocated to
activities include staff, hardware, and software. Gantt charts (named after its developer
Henry Gantt) are useful for resource planning. A Gantt chart is special type of bar chart
where each bar represents an activity. The bars are drawn along a timeline. The length of
each bar is proportional to the duration of the time planned for the corresponding activity.
Gantt chart is a project scheduling technique. Progress can be represented easily in a Gantt
chart, by coloring each milestone when completed. The project will start in the month of
January and end after 4 months at the beginning of April.

17
PROJECT MODEL USED
Iterative Enhancement Model:-

This model has the same phases as the waterfall model, but with fewer restrictions.

Generally the phases occur in the same order as in the waterfall model, but they may be
conducted in several cycles.
Useable product is released at the end of the each cycle, with each release providing

additional functionality. Customers and developers specify as many requirements as
possible and prepare a SRS document. Developers and customers then prioritize these
18
requirements. Developers implement the specified requirements in one or more cycles
of design, implementation and test based on the defined priorities.

The procedure itself consists of the initialization step, the iteration step, and the
Project Control List. The initialization step creates a base version of the system. The
goal for this initial implementation is to create a product to which the user can react. It
should offer a sampling of the key aspects of the problem and provide a solution that is
simple enough to understand and implement easily. To guide the iteration process, a
project control list is created that contains a record of all tasks that need to be
performed. It includes such items as new features to be implemented and areas of
redesign of the existing solution. The control list is constantly being revised as a result
of the analysis phase.
The iteration involves the redesign and implementation of iteration is to be simple,
straightforward, and modular, supporting redesign at that stage or as a task added to
the project control list. The level of design detail is not dictated by the iterative
approach. In a light-weight iterative project the code may represent the major source
of documentation of the system; however, in a critical iterative project a
formal Software Design Document may be used. The analysis of iteration is based upon
user feedback, and the program analysis facilities available.

PHASES:-

Incremental development slices the system functionality into increments (portions).


In each increment, a slice of functionality is delivered through cross-discipline work, from
the requirements to the deployment. The unified process groups increments/iterations
into phases: inception, elaboration, construction, and transition.
 Inception identifies project scope, requirements (functional and non-functional) and
risks at a high level but in enough detail that work can be estimated.
 Elaboration delivers a working architecture that mitigates the top risks and fulfills the
non-functional requirements.

19
 Construction incrementally fills-in the architecture with production-ready code
produced from analysis, design, implementation, and testing of the functional
requirements.
 Transition delivers the system into the production operating environment.

Data Flow Diagram

Introduction:-
DFD is anacronym for thewordDataFlowDiagram. DFD is pictorial representation of
thesystem. DFD is agraphical representation ofthe―flow‖of data through the information
system. DFD arealso used forthe visualization ofdata processing (structured design). ADFD
provides no information about thetimings of theprocess,orabout whetherprocess will
operate in parallel or sequence. DFD is an important technique for modeling system’s high-
level detailbyshowing how input dataistransformedtooutput results
throughasequenceoffunctionaltransformations. DFD revealrelationships among between
the various components in aprogram or system.Thestrength of DFD lies in the fact that

20
usingfewsymbolswe are able to express program design in an easiermanner. ADFD can
beusedstorepresentthe following:-

External Entitysendingandreceivingdata.
Process that changethedata.
Flow ofdatawithin the system.
Data Storagelocations.

UsesofDFD:-

Themain uses of data flow diagrams areasfollows:-


DFD is amethodofchoiceforrepresentation of showingof information througha system
because of thefollowingreasons:-

 DFDs areeasierto understand bytechnical and non-technicalaudiences.

 DFDs can
provideahighlevelsystemoverview,completewithboundariesandconnections to
othersystem.
 DFDs can provideadetailedrepresentation of system components.

0-Level DFD:-

Reg./login Reg./login
Online
Customer Matrimoni Admin
Accept/ Accept/
Reject al Portal reject

SOFTWAREREQUIREMENT SPECIFICATION

21
A requirements specification for a software system is a complete description of the
behavior of a system to be developed and it includes a set of use cases that describe all the
interactions the users will have with the software. In addition to use cases, the SRS also
contains non-functional requirements.

Non-functional requirements are requirements which impose constraints on the design or


implementation (such as performance engineering requirements, quality standards, or
design constraints).Requirements are a sub-field of software engineering that deals with
the elicitation, analysis, specification, and validation of requirements for software.

The software requirement specification document enlists all necessary requirements for
project development. To derive the requirements we need to have clear and thorough
understanding of the products to be developed. This is prepared after detailed
communications with project team and the customer.

SUPPORTANDMAINTENANCE:-

One year free support for rectifying system bugs including front end and beck end will be
provided. During warranty period Software Engineers will be responsible for removing
bugs and improving it. After one year support can be extended @ 20% of the total product
deployment cost.

SYSTEM DESIGN APPROACH

Top – Down designing:

22
The top - down designing approach started with major components of the system. It is a
stepwise refinement which starts from an abstract design, in each steps the design is
refined two or more concrete levels until we reach a level where no – more refinement is
possible or not needed.

Bottom – Up designing:

In bottom – up designing the most basic and primitive components are designed first, and
we proceed to higher level components. We work with layers of abstractions and
abstraction are implemented until the stage is reached where the operations supported by
the layer is complete.

Approach we are following:

23
In this project we are following Mixed Approach i.e. A combination of top – down and
bottom – up. We are developing some of the components using top – down designing
approach (e.g. the WebPages) and the some components in bottom – up designing
approach (e.g. the middle tier classes).

Low Level Design

Description: Low Level Design creation is one of the most important activities in the
development of any software product. The low level design document gives the design of
the actual software application. Low level design document is based on High Level Design
document. It defines internal logic of every sub module. A good low level design document
will make the application very easy to develop by the developer. An effective design
document results in very low efforts in developing a Software product.

Each project's low level design document should provide a complete and
detailed specification of the design for the software that will be developed in the project,
including the classes, member and non-member functions, and associations between
classes that are involved.

The low level design document should contain a listing of the declarations of all the classes,
non-member-functions, and class member functions that will be defined during the
subsequent implementation stage, along with the associations between those classes and
any other details of those classes (such as member variables) that are firmly determined by
the low level design stage. The low level design document should also describe the classes,
function signatures, associations, and any other appropriate details, which will be involved
in testing and evaluating the project according to the evaluation plan defined in the
project's requirements document.

24
TESTING

Testing is the integral part of any System Development Life Cycle insufficient and
interested application tends to crash and result in loss of economic and manpower
investment besides user’s dissatisfaction and downfall of reputation.

“Software Testing can be looked upon as one among much process, an organization
performs, and that provides the last opportunity to correct any flaws in the developed
system. Software Testing includes selecting test data that have more probability of giving
errors.” The first step in System testing is to develop the plan that all aspect of system
.Complements, Correctness, Reliability and Maintainability.

Software is to be tested for the best quality assurance, an assurance that system meets the
specification and requirement for its intended use and performance.
System Testing is the most useful practical process of executing the program with the
implicit intention of finding errors that makes the program fail.

Types of Testing:

Black Box (Functional) Testing:

Testing against specification of system or component. Study it by examining its inputs and
related outputs. Key is to devise inputs that have a higher likelihood of causing outputs that
reveal the presence of defects. Use experience and knowledge of domain to identify such
test cases. Failing this a systematic approach may be necessary. Equivalence partitioning is
where the input to a program falls into a number of classes, e.g. positive numbers vs.
negative numbers. Programs normally behave the same way for each member of a class.

25
Partitions exist for both input and output. Partitions may be discrete or overlap. Invalid
data (i.e. outside the normal partitions) is one or more partitions that should be tested.
Internal System design is not considered in this type of testing. Tests are based on
requirements and functionality.
This type of test case design method focuses on the functional requirements of the
software, ignoring the control structure of the program. Black box testing attempts to find
errors in the following categories:

 Incorrect or missing functions.

 Interface errors.

 Errors in data structures or external database access.

 Performance errors.

 Initialization and termination errors.

White Box (Structural) Testing:

Testing based on knowledge of structure of component (e.g. by looking at source code).


Advantage is that structure of code can be used to find out how many test case need to be
performed. Knowledge of the algorithm (examination of the code) can be used to identify
the equivalence partitions. Path testing is where the tester aims to exercise every
independent execution path through the component. All conditional statements tested for
both true and false cases. If a unit has n control statements, there will be up to 2n possible
paths through it. This demonstrates that it is much easier to test small program units than
large ones. Flow graphs are a pictorial representation of the paths of control through a
program (ignoring assignments, procedure calls and I/O statements). Use flow graph to
design test cases that execute each path. Static tools may be used to make this easier in
programs that have a complex branching structure. Tools support. Dynamic program
analysers instrument a program with additional code. Typically this will count how many

26
times each statement is executed. At end print out report showing which statements have
and have not been executed. Problems with flow graph derived testing:
 Data complexity could not take into account.
 We cannot test all paths in combination.
 In really only possible at unit and module testing stages because beyond that
complexity is too high.
This testing is based on knowledge of the internal logic of an application’s code. Also
known as a Glass Box Testing .Internal software and code working should be known for
this type of testing. Tests are based on coverage of code statements, branches, paths,
conditions.

Unit Testing:

Unit testing concentrates on each unit of the software as implemented in the code. This is
done to check syntax and logical errors in programs. At this stage, the test focuses on each
module individually, assuring that it functions properly as a unit. In our case, we used
extensive white-box testing at the unit testing stage.
A developer and his team typically do the unit testing do the unit testing is done in parallel
with coding; it includes testing each function and procedure.

Incremental Integration Testing:

Bottom up approach for testing i.e. continuous testing of an application as new


functionality is added; Application functionality and modules should be independent
enough to test separately done by programmers or by testers.

Integration Testing:

27
Testing of integration modules to verify combined functionality after integration .Modules
are typically code modules, individual applications, client and server and distributed
systems.

Functional Testing:

This type of testing ignores the internal parts and focus on the output is as per
requirement or not .Black box type testing geared to functionality requirements of an
application.

System Testing:

Entire system is tested as per the requirements. Black box type test that is based on overall
requirement specifications covers all combined parts of a system.

End-to-End Testing:

Similar to system testing ,involves testing of a complete application environment in a


situation that mimics real-world use, such as interacting with a database ,using network
communications, or interacting with hardware, applications, or system if appropriate.

Regression Testing:

Testing the application as a whole for the modification in any module or


functionality.Difficult to cover all the system in regression testing so typically automation
tools are used for these testing types.

28
Acceptance Testing:

Normally this type of testing is done to verify if system meets the customer specified
requirements. User or customers do this testing to determine whether to accept
application.

Performance Testing:

Term often used interchangeably with “stress” and “load” testing, To check whether system
meets performance requirements, Used different performance and load tools to do this.

Alpha Testing:

In house virtual user environment can be created for this type of testing. Testing is done at
the end of development .Still minor design changes may be made as a result of such testing.

Beta Testing:

Testing typically done by end-users or others. This is final testing before releasing
application for commercial purpose.

Description Of Classes and Methods :

Datamanager class and Method:

using System;

29
usingSystem.Collections.Generic;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Data.SqlClient;
usingSystem.Configuration;
usingSystem.Data;

/// <summary>
/// Summary description for dbmanager
/// </summary>
public class dbmanager
{
publicdbmanager()
{
//
// TODO: Add constructor logic here
//
}
SqlConnection con = new
SqlConnection(ConfigurationManager.ConnectionStrings["bandhan"].ToString());

publicbooliud(string query)
{
SqlCommandcmd = new SqlCommand(query, con);

try
{
con.Open();
cmd.ExecuteNonQuery();
return true;
}
catch (Exception)
{
return false;
}
finally
{
con.Close();
}

publicDataTableselectcmd(string query)
{
DataTabledt = new DataTable();
SqlDataAdapter da = new SqlDataAdapter(query, con);
da.Fill(dt);
returndt;
}

30
}

EmailSender.cs

using System;
usingSystem.Collections.Generic;
usingSystem.Linq;
usingSystem.Web;
using System.Net; // for network
usingSystem.Net.Mail; //for mail

/// <summary>
/// Summary description for EmailSender
/// </summary>
public class EmailSender
{
publicEmailSender()
{
//
// TODO: Add constructor logic here
//
}
public string SendTO { get; set; }
public string Subject { get; set; }
public string MessageBody { get; set; }
public string SendToCC { get; set; }
public string UserName { get; set; }
public string Password { get; set; }

publicboolSendMyEmail()
{
SmtpClient client = new SmtpClient();
MailMessagemsg = new MailMessage();
MailAddress from = new MailAddress(UserName);
MailAddress to = new MailAddress(SendTO);

//network string start here

NetworkCredentialnc = new NetworkCredential(UserName, Password);

client.EnableSsl = true;
client.Host = "Smtp.gmail.com";

31
client.UseDefaultCredentials = false;
client.Port = 587;
client.Credentials = nc;

//mail setting start here

msg.From = from;
msg.Subject = Subject;
msg.To.Add(to);
msg.Body = MessageBody;
msg.IsBodyHtml = true;
if (SendToCC != null)
{
MailAddresstocc = new MailAddress(SendToCC);
msg.CC.Add(tocc);
}

client.Send(msg);
return true;

}
}

32
User Screenshots:
HomePage:

33
Admin Screenshots:

Addlocation.aspx:

Addroute.aspx:

34
35
Admin.aspx:

36
CODINGS:-
Home.aspx

<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master"


AutoEventWireup="true" CodeFile="home.aspx.cs" Inherits="home" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<div id="outer">
<link href="css/Home.css" rel="stylesheet" />
</div>
</asp:Content>

Aboutus.aspx

<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master"


AutoEventWireup="true" CodeFile="aboutus.aspx.cs" Inherits="aboutus" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">


</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<div id="aboutus"></div>
</asp:Content>

Login.aspx :
<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master"
AutoEventWireup="true" CodeFile="ContactUs.aspx.cs" Inherits="ContactUs" %>

37
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
<style type="text/css">
.auto-style1 {
width: 100%;
}
.auto-style2 {
height: 56px;
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">

<div id="outer">
<div id="contact"><h2 style="text-align:center;">--Contact--</h2>
<p style="text-align:center;">Name-Anita Patel</p>
<p style="text-align:center;">Address-Varannasi</p>
<p style="text-align:center;">Mobile no-7565945148</p>
<p style="text-align:center;">Email ID-patelanita812@gmail.com</p>

</div>
<div id="query"><h2 style="text-align:center;">--Query Form--</h2>
<table class="auto-style1">
<tr>
<td>&nbsp;&nbsp;&nbsp; Name<asp:TextBox ID="TextBox1" runat="server"
style="margin-left: 70px"></asp:TextBox>
</td>
<td>Email&nbsp;
<asp:TextBox ID="TextBox2" runat="server" TextMode="Email"></asp:TextBox>
</td>
38
</tr>
<tr>
<td class="auto-
style2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<asp:TextBox ID="TextBox5" runat="server"
style="margin-left: 45px"></asp:TextBox>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;</td>
<td class="auto-
style2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp; Subjet<asp:TextBox ID="TextBox4" runat="server" style="margin-left:
29px" Width="133px"></asp:TextBox>
</td>
</tr>
<tr>
<td>Mobile No. <asp:TextBox ID="TextBox7" runat="server" style="margin-left: 29px"
Width="133px"></asp:TextBox>
</td>
<td>&nbsp;</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>
<asp:Button ID="Button1" runat="server" Text="send" OnClick="Button1_Click" />
</td>
</tr>
</table>

</div>
39
<div id="map"></div>
</div>
<link href="css/contactUs.css" rel="stylesheet" />
</asp:Content>

Contact.aspx :

<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master"


AutoEventWireup="true" CodeFile="ContactUs.aspx.cs" Inherits="ContactUs" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">


<style type="text/css">
.auto-style1 {
width: 100%;
}
.auto-style2 {
height: 56px;
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">

<div id="outer">
<div id="contact"><h2 style="text-align:center;">--Contact--</h2>
<p style="text-align:center;">Name-Anita Patel</p>
<p style="text-align:center;">Address-Varannasi</p>
<p style="text-align:center;">Mobile no-7565945148</p>
<p style="text-align:center;">Email ID-patelanita812@gmail.com</p>

40
</div>
<div id="query"><h2 style="text-align:center;">--Query Form--</h2>
<table class="auto-style1">
<tr>
<td>&nbsp;&nbsp;&nbsp; Name<asp:TextBox ID="TextBox1" runat="server"
style="margin-left: 70px"></asp:TextBox>
</td>
<td>Email&nbsp;
<asp:TextBox ID="TextBox2" runat="server" TextMode="Email"></asp:TextBox>
</td>
</tr>
<tr>
<td class="auto-
style2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Message&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<asp:TextBox ID="TextBox5" runat="server"
style="margin-left: 45px"></asp:TextBox>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;</td>
<td class="auto-
style2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp; Subjet<asp:TextBox ID="TextBox4" runat="server" style="margin-left:
29px" Width="133px"></asp:TextBox>
</td>
</tr>
<tr>
<td>Mobile No. <asp:TextBox ID="TextBox7" runat="server" style="margin-left: 29px"
Width="133px"></asp:TextBox>
</td>
41
<td>&nbsp;</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>
<asp:Button ID="Button1" runat="server" Text="send" OnClick="Button1_Click" />
</td>
</tr>
</table>

</div>
<div id="map"></div>
</div>
<link href="css/contactUs.css" rel="stylesheet" />
</asp:Content>

Howwework.aspx :

<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master"


AutoEventWireup="true" CodeFile="howwework.aspx.cs" Inherits="howwework" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">


<style type="text/css">
.auto-style1 {
width: 100%;
}
</style>
</asp:Content>

42
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<div id="how we work">
<h1>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; How We
work&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </h1>
<table class="auto-style1">
<tr>
<td>&nbsp;seach<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
<br />
</td>
</tr>
<tr>
<td>Bookcab<asp:TextBox ID="TextBox6" runat="server"></asp:TextBox>
<br />
</td>
</tr>
<tr>
<td>Confern booking<asp:TextBox ID="TextBox3" runat="server" style="margin-top:
0px"></asp:TextBox>
<br />
</td>
</tr>
<tr>
<td>Car will to you <asp:TextBox ID="TextBox4" runat="server"></asp:TextBox>
<br />
</td>
</tr>
<tr>
<td>
43
<br />
You will reach<asp:TextBox ID="TextBox7" runat="server"></asp:TextBox>
</td>
</tr>
</table>
</div>
</asp:Content>

Searchcab.aspx :

<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master"


AutoEventWireup="true" CodeFile="serch.aspx.cs" Inherits="serch" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">


<style type="text/css">
.auto-style1 {
width: 100%;
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<div id="search">
<h1>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Serch</h1>
<table class="auto-style1">
<tr>

44
<td>
<br />
From&nbsp;&nbsp;
<asp:DropDownList ID="DropDownList4" runat="server">
</asp:DropDownList>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
To<asp:DropDownList ID="DropDownList3" runat="server">
</asp:DropDownList>
</td>
<asp:DropDownList ID="DropDownList2" runat="server">
</asp:DropDownList>
</tr>
<tr>
<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
nbsp;&nbsp;
<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;
<asp:Button ID="Button2" runat="server" Text="serch" />
</td>
</tr>
</table>
45
</div>
</asp:Content>

Bookcab.aspx :

<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master"


AutoEventWireup="true" CodeFile="Bookcar.aspx.cs" Inherits="Bookcar" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">


<style type="text/css">
.auto-style1 {
width: 100%;
}
.auto-style2 {
height: 42px;
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<div id="BookCab">
<h1>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; BookCab</h1>
<table class="auto-style1">
<tr>
<td>From&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

46
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp; Check Availibity<asp:TextBox ID="TextBox5"
runat="server"></asp:TextBox>

<br />

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;
<asp:DropDownList ID="DropDownList1" runat="server"
OnSelectedIndexChanged="DropDownList1_SelectedIndexChanged">
</asp:DropDownList>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp; </td>
</tr>
<tr>
<td class="auto-style2">
<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Name<asp:TextBox ID="TextBox1"
runat="server"></asp:TextBox>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile<asp:TextBox
ID="TextBox2" runat="server"></asp:TextBox>
47
</td>
</tr>
<tr>
<td>&nbsp;&nbsp;&nbsp;&nbsp; Pickup Address<asp:TextBox ID="TextBox3"
runat="server"></asp:TextBox>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<br />
</td>
</tr>
<tr>
<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email<asp:TextBox ID="TextBox4"
runat="server"></asp:TextBox>
<br />
</td>
</tr>
<tr>
<td>
<br />
BookCab<asp:Button ID="Button3" runat="server" Text="Button" />
</td>
</tr>
</table>
</div>
</asp:Content>

Admin Code:

48
Addlocation.aspx:
<%@ Page Title="" Language="C#" MasterPageFile="~/admin/adminmaster.master"
AutoEventWireup="true" CodeFile="addlocation.aspx.cs" Inherits="admin_addlocation"
%>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">


<style type="text/css">
.auto-style1 {
width: 100%;
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<h1> Add Location</h1>
<table class="auto-style1">
<tr>
<td>
<br />
Location<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
</td>
</tr>
<tr>
<td>
<br />
<asp:Button ID="Button1" runat="server" Text="Add" />
</td>
</tr>
</table>

49
<br />
</div>
</asp:Content>

Addroute.aspx:

<%@ Page Title="" Language="C#" MasterPageFile="~/admin/adminmaster.master"


AutoEventWireup="true" CodeFile="addroute.aspx.cs" Inherits="admin_addroute" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">


<style type="text/css">
.auto-style1 {
width: 100%;
}
.auto-style2 {
height: 49px;
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<h1>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp; AddRoute</h1>
<div id="add route">
<table class="auto-style1">
<tr>
<td class="auto-
style2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
nbsp;&nbsp; From&nbsp; <asp:DropDownList ID="DropDownList1" runat="server">

50
</asp:DropDownList>
<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n
bsp;&nbsp; To&nbsp;&nbsp;&nbsp;
<asp:DropDownList ID="DropDownList2" runat="server">
</asp:DropDownList>
</td>
</tr>
<tr>
<td>&nbsp;</td>
</tr>
<tr>
<td>
<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <asp:Button
ID="Button2" runat="server" Text="Button" />
</td>
</tr>
</table>
</div>
</asp:Content>

Admincontactus.aspx:

<%@ Page Title="" Language="C#" MasterPageFile="~/admin/adminmaster.master"


AutoEventWireup="true" CodeFile="admincontactus.aspx.cs"
Inherits="admin_admincontactus" %>

51
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<asp:GridView ID="GridView1" runat="server" AllowPaging="True"
AutoGenerateColumns="False" BackColor="White" BorderColor="#CC9966"
BorderStyle="None" BorderWidth="1px" CellPadding="4" DataKeyNames="adminEmail"
DataSourceID="SqlDataSource1">
<Columns>
<asp:CommandFieldShowDeleteButton="True" />
<asp:BoundFieldDataField="adminEmail" HeaderText="adminEmail" ReadOnly="True"
SortExpression="adminEmail" />
<asp:BoundFieldDataField="adminPassword" HeaderText="adminPassword"
SortExpression="adminPassword" />
<asp:CheckBoxFieldDataField="adminStatus" HeaderText="adminStatus"
SortExpression="adminStatus" />
<asp:BoundFieldDataField="adminCount" HeaderText="adminCount"
SortExpression="adminCount" />
<asp:BoundFieldDataField="adminlastDateTime" HeaderText="adminlastDateTime"
SortExpression="adminlastDateTime" />
<asp:BoundFieldDataField="adminlogoutDateTime" HeaderText="adminlogoutDateTime"
SortExpression="adminlogoutDateTime" />
</Columns>
<FooterStyleBackColor="#FFFFCC" ForeColor="#330099" />
<HeaderStyleBackColor="#990000" Font-Bold="True" ForeColor="#FFFFCC" />
<PagerStyleBackColor="#FFFFCC" ForeColor="#330099" HorizontalAlign="Center" />
<RowStyleBackColor="White" ForeColor="#330099" />
<SelectedRowStyleBackColor="#FFCC66" Font-Bold="True" ForeColor="#663399" />
<SortedAscendingCellStyleBackColor="#FEFCEB" />
<SortedAscendingHeaderStyleBackColor="#AF0101" />
<SortedDescendingCellStyleBackColor="#F6F0C0" />
52
<SortedDescendingHeaderStyleBackColor="#7E0000" />
</asp:GridView>
<asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="<%$
ConnectionStrings:myconnection %>" DeleteCommand="DELETE FROM [adminlogin]
WHERE [adminEmail] = @adminEmail" InsertCommand="INSERT INTO [adminlogin]
([adminEmail], [adminPassword], [adminStatus], [adminCount], [adminlastDateTime],
[adminlogoutDateTime]) VALUES (@adminEmail, @adminPassword, @adminStatus,
@adminCount, @adminlastDateTime, @adminlogoutDateTime)" SelectCommand="SELECT
* FROM [adminlogin]" UpdateCommand="UPDATE [adminlogin] SET [adminPassword] =
@adminPassword, [adminStatus] = @adminStatus, [adminCount] = @adminCount,
[adminlastDateTime] = @adminlastDateTime, [adminlogoutDateTime] =
@adminlogoutDateTime WHERE [adminEmail] = @adminEmail">
<DeleteParameters>
<asp:Parameter Name="adminEmail" Type="String" />
</DeleteParameters>
<InsertParameters>
<asp:Parameter Name="adminEmail" Type="String" />
<asp:Parameter Name="adminPassword" Type="String" />
<asp:Parameter Name="adminStatus" Type="Boolean" />
<asp:Parameter Name="adminCount" Type="Int32" />
<asp:Parameter Name="adminlastDateTime" Type="String" />
<asp:Parameter Name="adminlogoutDateTime" Type="String" />
</InsertParameters>
<UpdateParameters>
<asp:Parameter Name="adminPassword" Type="String" />
<asp:Parameter Name="adminStatus" Type="Boolean" />
<asp:Parameter Name="adminCount" Type="Int32" />
<asp:Parameter Name="adminlastDateTime" Type="String" />
<asp:Parameter Name="adminlogoutDateTime" Type="String" />
<asp:Parameter Name="adminEmail" Type="String" />
</UpdateParameters>
53
</asp:SqlDataSource>
</asp:Content>

Alllogin.aspx:

<%@ Page Title="" Language="C#" MasterPageFile="~/admin/adminmaster.master"


AutoEventWireup="true" CodeFile="All login.aspx.cs" Inherits="admin_All_login" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">


</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False"
CellPadding="4" DataKeyNames="loginemail" DataSourceID="SqlDataSource1"
ForeColor="#333333" GridLines="None" AllowPaging="True">
<AlternatingRowStyleBackColor="White" ForeColor="#284775" />
<Columns>
<asp:BoundFieldDataField="loginemail" HeaderText="loginemail" ReadOnly="True"
SortExpression="loginemail" />
<asp:BoundFieldDataField="loginpassword" HeaderText="loginpassword"
SortExpression="loginpassword" />
<asp:CheckBoxFieldDataField="loginstatus" HeaderText="loginstatus"
SortExpression="loginstatus" />
<asp:BoundFieldDataField="logincount" HeaderText="logincount"
SortExpression="logincount" />
<asp:BoundFieldDataField="lastlogindatatime" HeaderText="lastlogindatatime"
SortExpression="lastlogindatatime" />
<asp:BoundFieldDataField="lastlogoutdatatime" HeaderText="lastlogoutdatatime"
SortExpression="lastlogoutdatatime" />

54
</Columns>
<EditRowStyleBackColor="#999999" />
<FooterStyleBackColor="#5D7B9D" Font-Bold="True" ForeColor="White" />
<HeaderStyleBackColor="#5D7B9D" Font-Bold="True" ForeColor="White" />
<PagerStyleBackColor="#284775" ForeColor="White" HorizontalAlign="Center" />
<RowStyleBackColor="#F7F6F3" ForeColor="#333333" />
<SelectedRowStyleBackColor="#E2DED6" Font-Bold="True" ForeColor="#333333" />
<SortedAscendingCellStyleBackColor="#E9E7E2" />
<SortedAscendingHeaderStyleBackColor="#506C8C" />
<SortedDescendingCellStyleBackColor="#FFFDF8" />
<SortedDescendingHeaderStyleBackColor="#6F8DAE" />
</asp:GridView>
<asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="<%$
ConnectionStrings:myconnection %>" SelectCommand="SELECT * FROM [login]"
DeleteCommand="DELETE FROM [login] WHERE [loginemail] = @loginemail"
InsertCommand="INSERT INTO [login] ([loginemail], [loginpassword], [loginstatus],
[logincount], [lastlogindatatime], [lastlogoutdatatime]) VALUES (@loginemail,
@loginpassword, @loginstatus, @logincount, @lastlogindatatime, @lastlogoutdatatime)"
UpdateCommand="UPDATE [login] SET [loginpassword] = @loginpassword, [loginstatus]
= @loginstatus, [logincount] = @logincount, [lastlogindatatime] = @lastlogindatatime,
[lastlogoutdatatime] = @lastlogoutdatatime WHERE [loginemail] = @loginemail">
<DeleteParameters>
<asp:Parameter Name="loginemail" Type="String" />
</DeleteParameters>
<InsertParameters>
<asp:Parameter Name="loginemail" Type="String" />
<asp:Parameter Name="loginpassword" Type="String" />
<asp:Parameter Name="loginstatus" Type="Boolean" />
<asp:Parameter Name="logincount" Type="Int32" />
<asp:Parameter Name="lastlogindatatime" Type="String" />
55
<asp:Parameter Name="lastlogoutdatatime" Type="String" />
</InsertParameters>
<UpdateParameters>
<asp:Parameter Name="loginpassword" Type="String" />
<asp:Parameter Name="loginstatus" Type="Boolean" />
<asp:Parameter Name="logincount" Type="Int32" />
<asp:Parameter Name="lastlogindatatime" Type="String" />
<asp:Parameter Name="lastlogoutdatatime" Type="String" />
<asp:Parameter Name="loginemail" Type="String" />
</UpdateParameters>
</asp:SqlDataSource>
</asp:Content>
FUTURE SCOPE

Improvements in design can be made using:


 Flash
 Photoshop
 New features can be added, like:
 Improved validation
 Provision of discounts and offers
 Generation of reports
 Provision of print-out(s) to buyer
 Refund of the money if the order is cancelled within a specific time period
 Larger collection of products

56
CONCLUSION:
ACHIEVEMENTS:
The program achieved the main requirement which was to develop a website meant
forBandhan shopping. Given the amount of time on hand, and given the basic knowledge of
the front end & back end used, the site satisfies most of the basic requirements that it was
supposed and planned to fulfill, like, providing facilities for authentication, registration,
searching for products, using a shopping cart, placing orders, cancellation of orders,
calculation of total payable amount, providing options for means of payment, addition of
new products to the site, managing the delivery of products, a very basic view of account
details, and extraction of information from the database using queries, where the database
is created in MS SQL & is connected to the design of site using SqlDataSource, and the web
site has been designed using ASP.NET with all the coding done in Visual C#.

During the development of the project, not only did we learn the basic concept
behindBandhan shopping, but we also learnt many basic features and concepts of
ASP.NET& SQL and how the ASP.NET technology can enable one to develop web sites
and applications with very little hassle. The development period did give me some
confidence to put together some sites in my spare time!

The entire project was like a challenge to me. The concept itself was interesting, and it was
aggravated by the fact that it was my first-ever experience with Practical Training. Most of
the time was consumed by the development of logic and its application in the correct
manner. There were matters of concerns, and numerous new ideas coming up, time and
again, but at the end of it all, the problems, their solutions & the new ideas played a major
role in helping me develop a broad outlook towards how things work in the real world, and
everything I gained in the 30-day period, will certainly help me with the projects in the real
software world in the time to come.

57
LIMITATIONS:
The major limitation of the project is that the site is not connected to any financial
institution which almost all such sites are (unless they don’t provide for ‘credit card’ as a
means of payment) because credit card is undoubtedly the dominant method of payment
used to shopBandhan. However, in the project, the credit card is taken as a mode of
payment just to show how the credit card information is entered whenBandhan shopping
is carried out. Once the user enters his credit card details on shopping bazaar, a message is
displayed, that the details have been verified and his order has been registered if the details
are entered in the correct format (an arbitrary format is used with shopping bazaar). The
actual sites are connected to a financial institution and follow the code format used by
different credit card companies like, MasterCard, Visa etc. When a user enters a valid credit
card type and corresponding number & CVV, then, a modem sends out these details to the
institution. If funds are available, the transaction is approved almost instantaneously and
the ordered goods are delivered within a specified time frame.

APPENDICS:-

Introduction to Visual Studio.net


Visual studio.net is a complete set of development tools for building ASP Web applications,
XML Web services, desktop applications, and mobile applications. Visual Basic .Net, visual
c++.NET all use the same integrated development environment (IDE), which allows
them to share tools facilitates in the creation of mixed – language solutions. In addition,
these languages leverage the functionality of the .NET Framework, which provides access
to key technologies that simplify the development of ASP Web applications and XML Web
services.
Architecture is explained form bottom to the top in the following discussion:
VB C++ C# Jscript

Visual Studio 2012

58
At the bottom of the architecture is common language Runtime. The common language
runtime loads and executes code that targets the runtime. This code is therefore called
managed code.
.NET Framework provides a rich set of class libraries. These include base classes, like
networking and input/output classes, a data library for data access, and classes for use by
programming tools, such as debugging services.
ADO.NET is Microsoft’s ActiveX Data Object (ADO) model for the .NET Framework.
ADO.NET is intended specifically for developing web applications.
The 4th layer of the framework consists of the windows application model and, in parallel,
the web application model. The Web application model-in the slide presented as ASP .NET
–includes Web Forms and Web Services .ASP.NET comes with built in Web forms controls,
which are responsible for generating the user interface. They mirror typical HTML widgets
like text boxes or buttons.
One of the obvious themes of .NET is unification and interoperability between various
programming languages. In order to achieve this; certain rules must be laid and all the
languages must follow these rules.
The CLR and the .NET Frameworks in general, however, are designed in such a way that
code written in one language can not only seamlessly be used by another language. Hence
ASP.NET can be programmed in any of the .net compatible language whether it is VB.NET,
C#, Managed C++ OR JSCRIPT.NET.

The .NET Framework


The .NET Framework is a multi-language environment for building, deploying, and running
XML Web services and applications . It consists of three main parts:
Common Language Runtime Despite its name , the runtime actually has a role in both
component is running , the runtime is responsible for managing memory , allocation ,
starting up and stopping threads and processes , and enforcing security policy , as well as
satisfying any dependencies that the component might have on other components .
The Common Language Runtime is the execution engine for .NET Framework applications.
It provides a number of services, including the following:

59
 Code management – loading and execution.

 Application memory isolation.

 Verification of type safety.

 Conversion of (platform-independent code generated by compilers) to native,


platform-dependent code.

 Access to metadata, which is enhanced type information.

 Managing memory for managed objects.

 Enforcement of code access security.

 Exception handling, including cross-language exceptions.

 Interoperation between managed code, com objects, and pre-existing dlls


(unmanaged code and data).

 Automation of object layout.

ADO.NET

ADO.NET is a set of libraries included with the Microsoft .NET Framework that help you
communicate with various data stores from .NET applications. The ADO.NET libraries
include classes for connecting to a data source, submitting queries, and processing results.
You can also use ADO.NET as a robust, hierarchical, disconnected data cache to work with
data off line. The central disconnected object, the DataSet, allows you to sort, search, filter,
store pending changes, and navigates through hierarchical data. The Dataset also includes a
number of features that bridge the gap between traditional data access and XML
development. Developers can now work with XML data through traditional data access
interfaces and vice-versa.

Microsoft Visual Studio .NET includes a number of data access features you can use to build
data access applications. Many of these features can save you time during the development
process by generating large amounts of tedious code for you. Other features improve the

60
performance of the applications you build by storing metadata and updating logic in your
code rather than fetching this information at run time. Believe it or not, many of Visual
Studio .NET’s data access features accomplish both tasks.

Microsoft SQL SERVER

Microsoft® SQL Server™ 2000 is designed to work effectively as:


A central database on a server shared by many users who connect to it over a network. The
number of users can range from a handful in one workgroup, to thousands of employees in
a large enterprise, to hundreds of thousands of Web users.
A desktop database that services only applications running on the same desktop.

Server Database Systems


Server-based systems are constructed so that a database on a central computer, known as a
server, is shared among multiple users. Users access the server through an application:

61
In a multi tier system, such as Windows® DNA, the client application logic is run in two or
more locations.A thin client is run on the user's local computer and is focused on displaying
results to the user.
The business logic is located in server applications running on a server. Thin clients
request functions from the server application, which is itself a multithreaded application
capable of working with many concurrent users. The server application is the one that
opens connections to the database server.
This is a typical scenario for an Internet application. For example, a multithreaded server
application can run on a Microsoft® Internet Information Services (IIS) server and service
thousands of thin clients running on the Internet or an intranet. The server application uses
a pool of connections to communicate with one or more instances of SQL Server 2000. The
instances of SQL Server 2000 can be on the same computer as IIS, or they can be on
separate servers in the network.
In a two-tier client/server system, users run an application on their local computer, known
as a client application, that connects over a network to an instance of SQL Server 2000
running on a server computer. The client application runs both business logic and the code
to display output to the user, so this is sometimes referred to as a thick client.

Advantages of Server Database System


 Having data stored and managed in a central location offers several advantages:
 Each data item is stored in a central location where all users can work with it.
 Business and security rules can be defined one time on the server and enforced equally
among all users.
 A relational database server optimizes network traffic by returning only the data an
application needs.
 Hardware costs can be minimized.
 Maintenance tasks such as backing up and restoring data are simplified because they can
focus on the central server.

62
Advantages of SQL Server 2000 as a Database Server
Microsoft SQL Server 2000 is capable of supplying the database services needed by
extremely large systems. Large servers may have thousands of users connected to an
instance of SQL Server 2000 at the same time. SQL Server 2000 has full protection for these
environments, with safeguards that prevent problems, such as having multiple users trying
to update the same piece of data at the same time. SQL Server 2000 also allocates the
available resources effectively, such as memory, network bandwidth, and disk I/O, among
the multiple users. Extremely large Internet sites can partition their data across multiple
servers, spreading the processing load across many computers, and allowing the site to
serve thousands of concurrent users.
Multiple instances of SQL Server 2000 can be run on a single computer. For example, an
organization that provides database services to many other organizations can run a
separate
instance.

Advantages of Server Database System


 Having data stored and managed in a central location offers several advantages:
 Each data item is stored in a central location where all users can work with it.
 Business and security rules can be defined one time on the server and enforced
equally among all users.
 A relational database server optimizes network traffic by returning only the data an
application needs.
 Hardware costs can be minimized.
 Maintenance tasks such as backing up and restoring data are simplified because
they can focus on the central server.

63
Advantages of SQL Server 2000 as a Database Server
Microsoft SQL Server 2000 is capable of supplying the database services needed by
extremely large systems. Large servers may have thousands of users connected to an
instance of SQL Server 2000 at the same time. SQL Server 2000 has full protection for these
environments, with safeguards that prevent problems, such as having multiple users trying
to update the same piece of data at the same time. SQL Server 2000 also allocates the
available resources effectively, such as memory, network bandwidth, and disk I/O, among
the multiple users. Extremely large Internet sites can partition their data across multiple
servers, spreading the processing load across many computers, and allowing the site to
serve thousands of concurrent users.
Multiple instances of SQL Server 2000 can be run on a single computer. For example, an
organization that provides database services to many other organizations can run a
separate instance.

64
BIBLIOGRAPHY

1) Asp .NET 1.1 with Visual C# .NET 2003 by Wrox publication.


2) Web application development with c# by Microsoft press no.-70-315
3) www.startvbdotnet.com: - tutorial for asp.net with c#
4) www.quickstart.com: - tutorial for asp.net
5) www.asp.net.com :-tutorial for asp.net

65