Online Vehicle Showroom Thesis

ONLINE VEHICLE SHOWROOM
Session (2013-2015)
Program
Master in Computer Science
Submitted By
Inam Ullah
13-MCS-S-HU-8
Atta-Ur-Rahman
13-MCS-S-HU-3
Supervised By
Mr. Aamir Javed
Lecturer, IT Department
HAZARA UNIVERSITY, MANSEHRA

1
FINAL APPROVAL
This is to certify that we have read the project report titled Online Vehicle Showroom
submitted by the fowling students of MCS 4th semester.
Roll No
Name
Registration No
31048
Inam Ullah
13-MCS-S-HU-8
31040
Atta-Ur-Rahman
13-MCS-S-HU-3
It is our judgment that this project report is of sufficient standard to warrant its
acceptance by the department of Information Technology, Hazara University Mansehra.
COMMITTEE
External Examiner
________________________________
Internal Examiner
________________________________
Supervisor
________________________________
Head of Department
_______________________________
DEDICATION
They fed me when I was hungry, gave me strength when weak, Protected me when in danger,
taught me to walk on my feet, Nursed me when hurt, encouraged me when dejected and helped me
to live honourably in this world, we dedicate this humble effort to our Respected Parents, Family
Members and Teachers with love and gratitude May Allah bless them with a very happy, successful
and a healthy life.
(AMEEN)
DECLARATION
We hereby declare that this software, neither as a whole nor as a part has been copied out
from any source. It is further declared that we developed this software and this report
entirely on the basis of our personal efforts made under the sincere guidance of our
project supervisor.
If any part of this software is proved to be copied or found to be a report of some other,
we shall standby the consequences. No portion of the work presented in this report has
been submitted in support of any application from any other degree of qualification of his
or any other university or institute of learning. We further declare that this software and
all associated documents, reports and records are submitted as partial requirement for the
degree of MCS. We understand and transfer copyrights for these materials to HAZARA
UNIVERSITY MANSEHRA. We shall not sale this software and documents not get any
financial gains from these.
Inam Ullah (31048)

_____________________
Atta-Ur-Rahman
(31040)
_____________________
ACKNOWLEDGMENT
In the great name of ALLAH, the most gracious and the most merciful, Who gifted us
blessings, strength and mental powers, without which we could not complete this project.
Before we get into thick of the things we would like to add a few heart felt words for the
people who were part of this project in numerous ways. People who gave unending
support right from the stage project idea were conceived. In particular we are extremely
indebted our teacher and supervisor of this project Mr. Aamir Javed, and also we are
thankful to our teachers and friends for their support. Vivacious and exuberant approach
always put us on right track. We are extremely thankful to our beloved Parents and family
whose prayers and continuous encouragement made the successful completion of this
project possible.
Inam Ullah
Atta-Ur-Rahman
PREFACE
Computer science and information technology has brought revolutionary changes in
every field of life. Increase processing speed, style etc. are some of the features that are
considered essential for the development of an organization. It is computer which pays a
vital role in achieving these targets. There are different websites that are available today
are the outcome of the needs and requirements of different organization. Online Vehicle
Showroom is one such activity that requires a lot of time and hard work. The wastage of
time in these processes can be greatly reduced only with the help of efficient Website.
So this website for Online Vehicle Showroom will improve the day-to-day work. The
user have no need to visit the showroom for purchasing vehicle but this application will
allow him/her to avail all the purchasing and business deals online. By using this website
user will purchase the products online and payment system will also by online services
and finally the user will get his/her desired product on his/her door step.
PROJECT IN BRIEF
Project Title:
Online Vehicle Showroom.
Organization:
Hazara University Mansehra.
Objectives:
To Develop User Friendly Website.
Developed By:
Inam Ullah and Atta-Ur-Rahman.
Supervised By:
Mr. Aamir Javed.
Tools Used:
C#, ASP.Net, SQL Server (2008).
System Used:
Core 2 duo, 4 GB RAM
Operation System:
Microsoft Windows7.
TABLE OF CONTENTS
CHAPTER 1 INTRODUCTION
1.1 Introduction....................................................................................................................1
1.2 History...........................................................................................................................1
1.2.1 Online purchasing system in Pakistan....................................................................1
1.3 Purpose of Project (Software)........................................................................................1
1.4 Scope..............................................................................................................................2
1.5 Advantages of the Project..............................................................................................2
1.6 Disadvantage of the Manual System.............................................................................3
1.7 Feasibility of project......................................................................................................3
1.8 Gantt Chart for Project Development............................................................................4
1.9 Outputs from the Project................................................................................................4
CHAPTER 2 EXISTING SYSTEM
2.1 Drawback of manual system..........................................................................................5
2.1.1 Data Duplication.....................................................................................................5
2.1.2 Delayed Information...............................................................................................5
2.1.3 Security...................................................................................................................6
2.1.4 Integrity...................................................................................................................6
2.1.5 Common Errors......................................................................................................6
2.1.7 Too Much Paper Work............................................................................................7
2.1.8 Loss and Profit........................................................................................................7
2.1.9 Tedious Information Access....................................................................................7
2.1.10 Backup problem....................................................................................................7
2.1.11 Data Entry.............................................................................................................8
2.1.12 Data recovery........................................................................................................8
2.1.13 Analysis problem..................................................................................................8

2.1.14 Redundancy..........................................................................................................8
2.1.15 In-accurate data.....................................................................................................8
2.1.16 Inflexible Data......................................................................................................8
2.1.17 Difficult to Modify................................................................................................8
CHAPTER 3 PROPOSED SYSTEM
3.1 Proposed system............................................................................................................9
3.2 Objective of the proposed system..................................................................................9
3.2.1 Efficiency and readability.......................................................................................9
3.2.2 Compatibility..........................................................................................................9
3.2.3 Acceptability...........................................................................................................9
3.2.4 Fast retrieval...........................................................................................................9
3.2.5 User friendly.........................................................................................................10
3.2.6 Correctness...........................................................................................................10
3.3 Techniques for Analysis of Online vehicle showroom (SDLC)..................................10
3.4 Preliminary Investigation.............................................................................................11
3.4.1 Review of Documents...........................................................................................12
3.4.2 Interview and Observation....................................................................................12
3.4.3 Questioner.............................................................................................................13
3.5 Process Model..............................................................................................................14
3.5.1 Waterfall model.....................................................................................................14
3.5.1.1 Requirement Analysis and Definition............................................................15
3.5.1.2 Systemand Software Design..........................................................................15
3.5.1.3 Development Phase:......................................................................................16
3.5.1.4 Implementationand Unit Testing...................................................................16
3.5.1.5 Integration and System Testing......................................................................16

3.5.1.6 Operations and Maintenance.........................................................................16
CHAPTER 4 REQUIREMENT ANALYSIS
4.1 Introduction..................................................................................................................17
4.1.1 Feasibility study....................................................................................................17
4.1.1.1 Initial studies..................................................................................................17
4.1.2 Economical Feasibility.........................................................................................17
4.1.3 Technical Feasibility.............................................................................................18
4.1.4 Operational Feasibility..........................................................................................18
4.2 Requirement analysis...................................................................................................19
4.3 Requirement definition................................................................................................19
4.4 Requirement specification...........................................................................................19
4.5 Functional requirement................................................................................................20
4.6 Non-functional requirement.........................................................................................20
4.6.1 Speed.....................................................................................................................20
4.6.2 Security.................................................................................................................20
4.6.3 Usability................................................................................................................20
4.6.4 Efficiency..............................................................................................................20
4.6.5 Reliability..............................................................................................................20
4.6.6 Backup facility......................................................................................................21
4.6.8 Refer images to the operation system...................................................................21
4.6.9 Future Enhancement.............................................................................................21
CHAPTER 5 SYSTEM DESIGN
5.1 Database Design..........................................................................................................22
5.2 Data base Design.........................................................................................................23
5.2.1 Bottom up approach..............................................................................................24

5.2.2 Top down approach...............................................................................................24
5.3 Logical Database Design.............................................................................................24
5.4 Physical data base design.............................................................................................25
5.4.1 Accessories...........................................................................................................25
5.4.2 Admin...................................................................................................................26
5.4.3 Contact..................................................................................................................26
5.4.4 Delivery................................................................................................................26
5.4.5 Employee..............................................................................................................27
5.4.6 FAQs.....................................................................................................................27
5.4.7 Feed Back.............................................................................................................27
5.4.8 Loss and profit......................................................................................................28
5.4.9 Order.....................................................................................................................28
5.4.10 Payment..............................................................................................................28
5.4.11 Product info.........................................................................................................29
5.4.12 Stock...................................................................................................................29
5.4.13 User _registration................................................................................................30
5.5 Logical design..............................................................................................................30
5.5.1 Data Flow Diagrams.............................................................................................30
5.5.1.1 Level 0 data flow diagram.............................................................................30
5.5.1.2 Notations of data flow diagram.....................................................................31
5.5.1.3 Level 1 DFD..................................................................................................32
5.5.1.4 Level 2 DFD..................................................................................................33
5.5.2 Entity Relationship Diagram................................................................................34
5.5.2.1 Admin............................................................................................................34
5.5.2.2 Contact...........................................................................................................34
5.5.2.3 Delivery.........................................................................................................35
5.5.2.4 Employee.......................................................................................................35
5.5.2.5 FAQs..............................................................................................................35
5.5.2.6 Feed Back......................................................................................................36
5.5.2.7 Loss and Profit...............................................................................................36
5.5.2.8 Order..............................................................................................................36
5.5.2.9 Payment.........................................................................................................37
5.5.2.10 Product.........................................................................................................37
5.5.2.11 Stock............................................................................................................37
5.5.2.12 Accessories..................................................................................................38
5.5.2.13 Temporary Table..........................................................................................38
5.5.2.14 User Registration.........................................................................................38
5.6 Database Diagram........................................................................................................39
5.7 Entity Relationship Diagram.......................................................................................40
CHAPTER 6 SYSTEM TESTING
6.1 The place of testing in SDLC......................................................................................41
6.2 System and Software Design.......................................................................................41
6.2.1 Implementation and Unit Testing.........................................................................41
6.2.2 Integration and System Testing.............................................................................42
6.2.3 Operations and Maintenance................................................................................42
6.3 Type of testing.............................................................................................................42
6.3.1 Functional testing..................................................................................................42
6.3.2 Stress testing.........................................................................................................42
6.3.3 Black box testing..................................................................................................43
10
6.3.4 White box testing..................................................................................................43

6.3.5 Beta testing...........................................................................................................43
6.4 Testing of Online vehicle showroom.......................................................................43
6.5.1 Trace ability Matrix............................................................................................43
6.5.2 Test case Description............................................................................................45
CHAPTER 7 OVERVIEW
7.1 Overview......................................................................................................................46
7.2 Main page....................................................................................................................47
7.3 Administrator login......................................................................................................48
7.4 User login.....................................................................................................................48
7.5 Products.......................................................................................................................49
7.6 View product details....................................................................................................50
7.7 Order............................................................................................................................51
7.8 Add to cart....................................................................................................................52
7.9 Registration from.........................................................................................................53
7.10 Success page..............................................................................................................54
7.11 Contact us..................................................................................................................54
7.12 Feed back...................................................................................................................55
CHAPTER 8 CODING
Appendices........................................................................................................................56
REFERENCES
References........................................................................................................................116
11
LIST OF TABLES
Table 5.1: Accessories...26
Table 5.2: Admin...27
Table 5.3: Contact..27
Table 5.4: Delivery27
Table 5.5: Employee..28
Table 5.6: FAQs.28
Table 5.7: Feed Back.28
Table 5.8: Loos and profit..29
Table 5.9: Order.29
Table 5.10: Payment..29
Table 5.11: Product Info30
Table 5.12: Stock...30
Table 5.13: User Registration31
Table 6.1: Trace ability Matrix..42
Table 6.2: Test Case Description...44
12
LIST OF FIGURES
Figure 1.1: Gantt chart.4
Figure 2.1: Data Duplication5
Figure 2.2: Lack of Security6
Figure 2.3: Fire6
Figure 2.4: Repetition of Work7
Figure 2.5: Too much paper work7
Figure 2.6: Loss and Profit...7
Figure 3.1: SDLC...12
Figure 3.2: Waterfall model...15
Figure 5.1: Level 0 DFD32
Figure 5.2: Notations of DFDs
32
Figure 5.3: Level 1 DFD ...33
Figure 5.4: Level 2 DFD34
Figure 5.5: Admin..35
Figure 5.6: Contact.35
Figure 5.7: Delivery...36
Figure 5.8: Employee.36
Figure 5.9: FAQs...36
Figure 5.10: Feed Back..37
Figure 5.11: Loss and Profit...37
Figure 5.12: Order..37
Figure 5.13: Payment.....................................................................................................38
Figure 5.14: Product...38
Figure 5.15: Stock..38
Figure 5.16: Accessories39
Figure 5.17: Temp_Table...39
Figure 5.18: User registration....39
Figure 5.19: Database Diagram.40
13
Figure 5.20: Entity Relationship Diagram.41

Figure 7.1: Home Page..48
Figure 7.2: Administrator Login....49
Figure 7.3: User Login.......49
Figure 7.4: Product.50
Figure 7.5: Product Detail..51
Figure 7.6: Order....52
Figure 7.7: Add to cart..53
Figure 7.8: Registration from.54
Figure 7.9: Success page55
Figure 7.10: Contact us..55
Figure 7.11: Feed Back..56
14
LIST OF ACRONYM
DBMS
Database Management System.
DD
Data Dictionary.
SQL
Structured Query language.
DFD
Data Flow Diagram.
GUI
Graphical User Interface.
ERD
Entity Relationship Diagram.
SDLC
Software Development Life Cycle.
SQA
Software Quality Assurance.
DD
Database Design.
DDS
Data Design System.
LDD
Logical Database Design.
PDD
Physical Data Design.
15
CHAPTER 1
INTRODUCTION
1.1 Introduction
This software is developed for a web application that depicts online vehicles showroom
and booking vehicle. Customer can register to this site and he can book vehicles by
entering his login information. Administrator is main user of this system and can add
employees, and new vehicles details.
This project is developed for vehicle showroom. The project aims to show Online its
records. So all of its paper and manual computer work is to be converted into a database,
which is updateable, modifiable and easy to use.
The basic idea of the database is to provide information and to make it easy to use and to
make fast access to the records. This system will maintain records of the shopping. And
also have queries about customers, Product etc.
The proposed system can be expended to a complete comparison-shopping site. Then
they can check out their whole order at one place.
Therefore the whole online purchasing process will be much easier than it is today. The
goal of this design is to develop efficient software architecture to offer easy online
purchasing.
1.2 History
1.2.1 Online purchasing system in Pakistan.
Pakistan is considered to be worlds 2nd slowest adopter in online system. Most people
are interested to purchase and bought usually books and cloths. Airline tickets, books,
hotel reservations are also commonly done online. In Pakistan, online shoppers look 25%
for computer hardware for clothing 18% and rest 57% are saying that they are not willing
to or plan to make online purchasing in the next two year. The other important factor is
that the most of the people in this region have negative experience in online purchasing.
1.3 Purpose of Project (Software)

The main purpose of this software online vehicle showroom is to develop a user friendly
application for vehicle showroom administrator as well as for customers. This application
allows storing of vehicle information, stock available at different locations, product

payment modes etc.
This project can be useful for users who want online detail about the vehicles. And
further this can be used by any other vehicle showroom.
This software allows the administrator a global scope and the customer with the limited
scope and thus helps in maintaining the security of the records.
1.4 Scope
We describe what features are in the scope of the software and what are not in the scope
of the software to be developed.
This software will consist of some significant modules in order to satisfy the companys
needs as well as the customers.
Registration forms for customers in able to take order.
User authentication to secure the login information of both user and administrator.
Inventory system where the admin can have full control of the information stored in
the database like members and products information and able to view orders
information.
The system can print the profile information of the members for both admin and
ordinary users.
Administrator has full permission to access this software features.
1.5 Advantages of the Project

The forthcoming automated system on single pc will cover all mentioned flaws of manual
system making it more.
Secure.
Easy to handle.
Less resource required.
Less chance of error occurring.
Supportive for user.
1.6 Disadvantage of the Manual System

Some disadvantage of the manual system nowadays manual system includes:
Data isolation.
Poor Security.
Integrity.
Duplication.
More chances of error.
Difficult to maintain.
Inconsistency.
Data are not shared to other mean data are distributed.
1.7 Feasibility of project

A successful completion and adoption of the automated system will definitely make the
work easier around its field by maintaining all record about user product records and
services. The existing system will be replaced by automated system.
All the information are kept and derived manually. The automated system will be able to
meet all the requirement like ease of use, easy to maintain, security etc. record and
information will be kept and upgraded safely and data will be processed faster in
purposed automated system. It will provide us the following advantages.
1. Avoid the fraud.
2. Technical problem.
3.
Operational problem.
3
4. Administrator will be the only user of the system and will have full authority and
privileges.
Administrator of the system will be able to maintain system, upgrade record so on. The
administrator of the system will be able to move all around the system controlling all
activities by having complete privileges/rights.
1.8 Gantt Chart for Project Development

Following grant chart shows the sequence of phases and progress of project graphically.
Finish Line
Installation andTraining
Progress
Implementation
Development
Design
Analysis
1 Feb-15 Feb
16 Feb-28 Feb 1 Mar-15 Mar
Time
Figure 1.1: Gantt chart
1.9 Outputs from the Project
Software.
Database.
Project Documentation.
16 Mar-31 Mar
1 Apr-5 Apr
CHAPTER 2
EXISTING SYSTEM
Study of present system is a basic step in developing the new system, by this study we
will be able to find out the drawbacks of present system which we will be removed in
new system and will improve the good features of present system in new system.
So a thorough study of the present system was conducted to completely understand the
working nature of present system. No Online Software was developed for vehicle
showroom, therefore a generalized study was conducted.
Present system is working manually in registers, pads and files etc.
So the present system has many of the drawbacks i.e. time consuming, not secure, not
reliable and efficient etc. The present system do not provide the facility of online
purchasing of the product. It may lead to errors so handling such type of information
manually at a time is very difficult, may lead to errors and very time consuming so we
decided that it is time to computerize the existing / present system to save their time and
get the desired information with in second. The following drawback in the present system
were found, which compelled us to develop a software.
2.1 Drawback of manual system

2.1.1 Data Duplication
The same data gets repeated again and again since the workers find it difficult to keep a
section of records of the documents, information and transactions.
For example:
a. Registers are used in which data can be written again and again.
Figure 2.1: Data Duplication

2.1.2 Delayed Information
As data is stored manually, if reports or results or other sorts of information is needed, it
takes a lot of time to process the data and find the desired information.
2.1.3 Security
The security of the manual system is very poor because the registers can be lost or stolen
at any time, it may be possible that any miss-haps occur such as the department building
get fire in that situation entire information will be lost.
For Example:
a. If someone steals the shop, data will be lost.
Figure 2.2: Lack of Security

b. In case of fire.
Figure 2.3: Fire

2.1.4 Integrity
The integrity of the current system is also worst because anyone can change the data in
the computers intentionally or unintentionally.
2.1.5 Common Errors
When entering data customers might have accidentally switched details and data since it
is hand written.
2.1.6 Repetition of Work
If there are any changes to be made, the data will have to be entered again. At times the
worker would forget to make the changes or forget that they had already altered it and
might do it again, its time consuming.
Figure 2.4: Repetition of Work

2.1.7 Too Much Paper Work
Since everything and every detail are written down manually in paper there will be too
much paper work!
Figure 2.5: Too much paper work

2.1.8 Loss and Profit
The present system is not able to generate the proper reports of Loss and Profit.
Figure 2.6: Loss and Profit

2.1.9 Tedious Information Access
In the existing form of system it is very difficult to access information quickly. If we want
to retrieve any record of an employee, it is tedious and difficult, so details were collected
that explained the nature of project request.
2.1.10 Backup problem
In the existing system there is always a risk of deliberate or accidental destruction of
recorded data. One such information is damaged there remain no backup copies to be
used in future. So it become difficult to recover the required information once destroyed
in the manual system.
2.1.11 Data Entry

The data entry and retrieval is difficult to manage in manual work.
2.1.12 Data recovery
Error that occurs accidentally and which remain unknown leads to erroneous result which
take months to correct.
2.1.13 Analysis problem
As data store in different files and registers and different files and registers have to be
open for managing information. So it was very difficult to analyse the data in the manual
system.
2.1.14 Redundancy
As information about the customer and user are recorded in registers, therefore
redundancy occur.
2.1.15 In-accurate data
More writing work is involved in maintaining the record of different entities. Therefore,
there are more chances of man-oriented errors and mistakes, which result in an inaccurate
and unreliable source of information.
2.1.16 Inflexible Data
Data which is stored in the current system in such a way that it is not in a very useful
form and thus cannot be used in many different ways easily.
2.1.17 Difficult to Modify
The data stored in any computer can be required to be modified at any time, but in current
system, the data cannot be easily modified unless some procedure is followed.
CHAPTER 3
PROPOSED SYSTEM
3.1 Proposed system

Computerization of the system involves the study of present system along with all of its
weakness and drawback, and then suggesting a suitable computer based system.
After analyzing the present system and finding its shortcoming, it is necessary to
eliminate its deficiencies in order to define the objective and design of the proposed
system. New system has brought some changes in the existing system but mostly the
structure and number of fields and data codes are same as in the traditional purchasing
system. But some changes have been made to make system more efficient and some
modification are based on new requirement.
In the proposed system, input forms have become different and the proposed system
online purchasing will be window based. This system will provide the facility to
customer to buy the product online. Customer will see different categories of products.
3.2 Objective of the proposed system

It is important to establish some objective of the proposed system should meet.
3.2.1 Efficiency and readability
The news should be efficient and it should have an edge over the present system and
order to make data reliable, several data validation checks should be provide in the
system.
3.2.2 Compatibility
Compatibility in data design, entry and processing with the present system.
3.2.3 Acceptability
The system should be acceptable to the organization. It should satisfy the previous and
new objectives in a better way.
3.2.4 Fast retrieval

File access and retrieval of information including the generation of reports and queries
should be fast, to do so, fields in which search have been perform should be indexed so as
to reduced time for accessing the desired information.
3.2.5 User friendly
System should be user friendly, that user can easily operate the system.
3.2.6 Correctness
The new system should be error free. The output of produced by the new system should
be satisfactory, in addition to that it should be comprehensive database of insertion,
modification and retrieving of data.
3.3 Techniques for Analysis of Online vehicle showroom (SDLC)

SDLC is the process of analyzing the information needs of an organization and
developing a conceptual model that reflects those satisfy user needs in terms of
performance, completeness, integrity, constraints and other factors. It is a process for
continuously improving the quality of product. It is basically the frame work for the task
that are required to build a high quality software this show us to approach that we are
going to select develop a software.
10
Software Development Life Cycle (SDLC)

Planning
System Definition
Request, Collection and

Analysis of System
Design
Conceptual Design
Logical Design
Physical Design
Implementation
Data Loading
Testing
Maintenance
Feedback
SDLC (SOFTWARE DEVELOPMENT LIFE CYCLE

Figure 3.1: SDLC
3.4 Preliminary Investigation

In preliminary investigation, we carried out evaluation of the project request being
proposed. Information was collected that just permits to evaluate the merit of the project
request and make an informal judgment about the feasibility of the proposed project in
order to carry out a preliminary investigation.
11
The data collected through preliminary investigation (analysis) was conducted through
following two methods.
3.4.1 Review of Documents
First of all brief information was obtained about the online vehicle showroom by
studying different documents. During this process the following information was
obtained.
How it operates? How information comes and how it is processed? And where the
information is transferred after processing? These details were gathered and studied by
examining the Organizational charts and written operating procedures. The operating
procedures describes how the data collecting process should operate and identify the most
important steps involved in receiving, managing and dispatching the data.
3.4.2 Interview and Observation
For making software for online vehicle showroom, first we met the owner. We also
contacted some other showroom in the local area to develop the software more
generalized and flexible. They gave us all the related data vehicle showroom
He gives us the detailed study of the flow of data. We found him very cooperative as a
friend. We met him several times and discussed various issues regarding all processes of
online vehicle showroom.
Whenever we faced problem regarding the working nature of online vehicle showroom,
we consulted the owner either by phone or we met him face by face.
By conducting this technique, we found the following necessary information regarding
Vehicle showroom.
The buying and selling is available 24 hours.
Having different model i.e. old or new.
Having different categories i.e. Small, medium and large.
Having product as well as purchasers and order details.
The customer see online details of the required item, and in the case of
availability the customer order.
12
The purchaser things (vehicles) will be deliver according to the customer

address.
The customer will pay the payment any payment of method (debt card, easy
paisa).
The process will be continued in this manner.
3.4.3 Questioner
As this is another important technique for analysis of system in Software Development
Life Cycle, we have also created a questionnaire to extract some necessary information
regarding.
Analysis conducted for showroom
Q1: Have you any computer skill?
Yes
No
Q2: What type of vehicle you sell?
Honda
(new /used)
Suzuki
(new/used)
Toyota
(new/used)
All companies
(new/used)
Other
(new /used)
Q3: Now a days which company vehicle customers demands?
Honda
(new/used)
Suzuki
(new/ used)
Toyota
(new/used)
13
All companies
(new/ used)
Others
(new/used)
Q4: What is the daily or monthly progress of the showroom?
Loss
Profit
Q5: Is the present system is fulfill your requirement?
Yes
No
Q6: Are you selling vehicle on lease?
Yes
No
Q7: In case of loss of record any backup to recover?
Yes
No
Q8: If you selling on lease what is the leasing return criterion?
3/6/9/12other month debit.
Installment per month.
None of them.
Q9: What are the reasons due to which you computerize the present system?
Ans: Because computerize system will fulfill all the requirement of user, it is to restore
the backup and also time saving.
14
3.5 Process Model

3.5.1 Waterfall model
The waterfall model is a sequential software development process, in which progress is
seen as flowing steadily downwards (like a waterfall) through the phases of Conception,
Initiation, Analysis, Design (validation), Construction, Testing and maintenance.
Figure 3.2: Waterfall model

The unmodified waterfall model". Progress flows from the top to the bottom, like a
waterfall.
The waterfall development model has its origins in the manufacturing and construction
industries, highly structured physical environments in which after-the-fact changes are
prohibitively costly, if not impossible. Since no formal software development
methodologies existed at the time, this hardware-oriented model was simply adapted for
software development.
The first formal description of the waterfall model is often cited to be an article published
in 1970 by Winston W. Royce (19291995), although Royce did not use the term
"waterfall" in this article. Royce was presenting this model as an example of a flawed,
non-working model (Royce 1970). This is in fact the way the term has generally been
used in writing about software developmentas a way to criticize a commonly used
software practice.
15
3.5.1.1 Requirement Analysis and Definition

All possible requirements of the system to be developed are captured in this phase.
Requirements are set of functionalities and constraints that the end-user (who will be
using the system) expects from the system. The requirements are gathered from the enduser by consultation, these requirements are analysed for their validity and the possibility
of incorporating the requirements in the system to be development is also studied.
Finally, a Requirement Specification document is created which serves the purpose of
guideline for the next phase of the model.
3.5.1.2 System and Software Design
Before a starting for actual coding, it is highly important to understand what we are going
to create. The requirement specifications from first phase are studied in this phase and
system design is prepared. System Design helps in specifying hardware and system
requirements and also helps in defining overall system architecture. The system design
specifications serve as input for the next phase of the model.
3.5.1.3 Development Phase:
In this stage of SDLC the actual development starts and the product is built. The
programming code is generated as per DDS (Data Design System) during this stage. If
the design is performed in a detailed and organized manner, code generation can be
accomplished without much trouble.
3.5.1.4 Implementation and Unit Testing
On receiving system design documents, the work is divided in modules/units and actual
coding is started. The system is first developed in small programs called units, which are
integrated in the next phase. Each unit is developed and tested for its functionality; this is
referred to as Unit Testing. Unit testing mainly verifies if the modules/units meet their
specifications.
3.5.1.5 Integration and System Testing
As specified above, the system is first divided in units which are developed and tested for
their functionalities. These units are integrated into a complete system during Integration
16
phase and tested to check if all modules/units coordinate between each other and the
system as a whole behaves as per the specifications. After successfully testing the
software, it is delivered to the customer.
3.5.1.6 Operations and Maintenance
This phase of "The Waterfall Model" is virtually never ending phase (Very long).
Generally, problems with the system developed (which are not found during the
development life cycle) come up after its practical use starts, so the issues related to the
system are solved after deployment of the system. Not all the problems come in picture
directly but they arise time to time and needs to be solved, hence this process is referred
as Maintenance.
CHAPTER 4
REQUIREMENT ANALYSIS
17
4.1 Introduction
This involves understanding the problem, establishing the services, which the system
should provide the constraints under which meet operation.
It is the process of translating the ideas about the system to be developed, in the mind of
client mind the actual users, in to more formal ways, it is communicating between
customer and software development team. Without preparing the requirement
specification the process of developing software with all of its functionality look quite
impossible.
There are four principle stages in the requirement engineering process.
Feasibility study.
Requirement analysis.
Requirement definition.
Requirement specification.
4.1.1 Feasibility study

4.1.1.1 Initial studies
They study will decide if the proposed system will be cost effective from a business
point of view and if it can be developed in the given budgetary and time constraints.
During the process collected information, examine the projects feasibility and answers
the question whether the system will be beneficial for vehicle showroom for this purpose
the following three tests of feasibility were studied.
Economic Feasibility.
Technical Feasibility.
Operational Feasibility.
17
4.1.2 Economical Feasibility

The bottom line in many projects is economic feasibility. Economical feasible solution
means that is this solution is cost effective for the business? It means that if the expanses
on the project are less than the benefits produced by the project or not.
Before selection of an alternative solution to the system, costs cant evaluate the practical
cost of the system. As soon as the requirements of new system are defined and a solution
to problem is selected, cost-benefit analysis of each alternative can be evaluated and
feasible solution can be selected. Software is economically feasible and it is cheap.
The tools being used for the development at the Front-End is ASP.NET, with C# and at
the back end tool is Microsoft SQL. No other expensive tools, software, hardware or
consultancy is required, so the project is very much feasible economically i.e. Financial
benefits must equal or exceed the financial costs. In order to do so the following steps can
be considered:
Estimate of hardware and software can be made and must have alternate
solution for providing economical feasibility.
The evaluation of benefits will be higher than the estimated total cost. Since
project proposal for vehicle showroom passes all these feasibility tests,
therefore, it is considered as an economically feasible system.
4.1.3 Technical Feasibility

As ASP.NET with C# and SQL server 2008 are database based applications and most of
the users now-a-days are well familiar with the use of these, so there is no need of any
special skills required by the users or making them aware of the system. On the other
hand the system does not have any extra ordinary technical requirements. So the project
is technical feasible too.
Software is easy to operate on and user can easily understand the operations of the
software and proper help is also provided for the user.
Technical feasibility concerns around the current system technology i.e. Software and
Hardware and to what extent it can support the proposed system. It also involves the
financial consideration to accommodate the technical enhancements.
18
System can be expanded whenever required.
There are technical guarantees of accuracy, reliability, ease of access and high data
security.
4.1.4 Operational Feasibility
Proposed system is operationally feasible in showroom because it fulfils the
requirements, as it is more efficient, accurate and reliable.
ASP.NET with C# and SQL server 2008 will be operationally feasible because it will be
efficient, accurate, and reliable and provides more facilities any other available system.
The proposed system will be user friendly and easy to understand, so users would be able
to understand and use this system easily, no high computer knowledge would be required
for it.
This project is operationally feasible for the following reasons:
This project will fulfil end-users requirements.
The project is functionally acceptable to end-user.
This system will work successfully whenever developed and installed.
The system is integrated with other system that is already in use.
The accessibility of records will not be lost.
Performance will not be slow in any section.
4.2 Requirement analysis

The requirements are gathered from the end-user by consultation, these requirements are
analysed for their validity and the possibility of incorporating the requirements in the
system to be development is also studied. Finally, a Requirement Specification document
is created which serves the purpose of guideline for the next phase of the model.
Without preparing the requirement specification the process of developing software with
all of its functionality look quite impossible.
19
4.3 Requirement definition

All the requirement gathered during requirement definition stage were narrated for first
approval. In this stage we also define what the administrator can do and what is the
function that it can perform.
4.4 Requirement specification

Out of various alternative, structured language is used to write down functional
requirement structured language. Which is a restricted specify requirements.
4.5 Functional requirement

1. User or customer requirement
The system will be able to handle the data base of online purchasing vehicle. User will be
able to retrieve this data base using the unique identification. User can also edit his data
can make change has data, there will be complete record of all products.
2. Loss and profit information
The system can keep the record of loss and profit of online purchasing.
3. Retrieval of information from DB
The system must have an effective and fast retrieval of the required information from the
data base.
4.6 Non-functional requirement

4.6.1 Speed
The system must have complete all queries and all other data transfer processes within
second and define redundancy to speed up the quires.
4.6.2 Security
Only authorize personnel should be able to access the data base for their defined usage.
20
4.6.3 Usability
All the options should be provided in clickable from avoid wasting time in writing
commands.
4.6.4 Efficiency
The proposed system should much more efficient and helpful to check the information.
4.6.5 Reliability.
The system should be reliable enough that it provides the correct result as expected.
4.6.6 Backup facility
System should be capable of backup and restoring information (if the system crashes etc.
4.6.7 Maintainability
Developed system should be maintainable that it is allow the change to be made. Code
should be documented properly.
4.6.8 Refer images to the operation system
Referring all images to the operating system instead of storing them in data base.
4.6.9 Future Enhancement
There should be extensible support for future enhancement in the data base.
21
CHAPTER 5
SYSTEM DESIGN
22
Design is a decision making activity. Design works is a base for the proceeding activities
in the development good design lead to efficient software. System design is the phase
where quality is fostered in software development.
Hence good development work depends upon good quality of design. Design changes
customer, s requirement into representation of software. Software or system is unable
without a good design and fails when changes are made into it.
So the designing is the basic building block of any software. The design depends upon
the study and understanding of the present system and the vision and approach of the
software designer for the proposed system. The design can be divided into three parts.
5.1 Database Design
Input Design.
Output Design.
In the designing phase of online vehicle showroom, the activities included many
important designing aspects; Viewed from a purely functional point of view, most of the
computer system will perform three task
Presentation logic.
Business logic.
Data service.
5.1.1 Presentation logic

The presentation phase comprises the entire user interface. Not only this phase allow the
user to interact with the application, input data, and view the result of request, it manages
the manipulation and formatting of data once it arrives at the client.
5.1.2 Business logic
Business logic, which is the true that govern application processing, connect the user at
one end with the data at the other. The function that these rules govern closely mimic
everyday business tasks, and can be single task, or a series of tasks.
5.1.3 Data service logic
It handles the storage and retrieval of data while maintaining integrity of data.
5.2Conceptual database design
Tells the user exactly.
22
What the system will do.
Describe the function of the systems.
The system will work in the following areas.
Unique authorized access to all registered users.
Purchasing the products.
The system is defined by its boundaries, entities, attributes, and relationship.
Conceptual design describes each of these system aspects by answering the

following.
Where will data come from?
(1) Input
The input to the system comes from administration of the vehicle showroom.
(2) Output
The output coming from the magnitudes displaying in different form.
What will happen to do the data in the system?
The following describe format will be used for input and outputs. Accuracy of the data is
dependent upon connection. Speed gateway, device type flow of data depend upon the
member of the user accessing database.
5.2 Data base Design

It means the design of a data base model that will support the operations and objectives.
Database design is a creative process of transforming:
The description of solution.
Designer of the database should satisfy the user.
To represent the data and the relationships between data required by all major application
areas and user groups.
To provide a data model that support any transactions required on the data.
23
The two main approaches to the design of a data base system are referred to as the top
down and bottom up approaches.
5.2.1 Bottom up approach
The bottom up approach begins at the fundamental level of attributes, which are grouped
into entities and relationships. As the process continues we identify and add new
relationships between entities. The process of normalization also represents a bottom up
approach to design. This approach is suitable for simple databases having a small number
of attributes. Normalization involves the identification of the required attributes and their
subsequent decomposition into normalized tables.
5.2.2 Top down approach
It is suitable for designing complex databases. It stars with the development of data
models that contain a few high level entities and then identify lower level entities,
attributes and their relationships. It uses ER model, which shows the entities and their
relationships.
In our project we have used the top down approach.
The Top down database design approach is composed of two major phases:
Logical database design.

Physical database design.
5.3 Logical Database Design

The steps involved in this design are:
Step 1: Build Local Conceptual Data Model from user view.
Build a local conceptual data model of an enterprise for a specific user view.
1. Identify entity types
Identify the main entity types in the user view of the enterprise. Document entity types.
2. Identify relationship types
Identify the important relationships that exist between the entity types that we have
identified. Determine the cardinality. Document relationship types. Use entity
relationship (ER) modelling when necessary.
24
3. Associate attributes with entity or relationship types

Associate attributes with the appropriate entity or relationship types. Identify
simple/composite attributes, single-valued/multi-valued attributes and derived attributes.
Document attributes.
4. Determine attribute domains
Determine domains for the attributes in the local conceptual model. Documents attribute
domains.
5. Determine candidate and primary key attributes
Identify the candidate key (S) for each entity and if there is more than one candidate key,
choose one to be the primary key. Document primary and candidate keys for each strong
entity.
6. Specialize/generalize entity types (optional step)
Identify super class and subclass entity types, where appropriate.
7. Draw entity relationship diagram
Draw an entity relationship diagram that is a conceptual representation of a user view
of the enterprise.
8. Review local conceptual data model with user
Review the local conceptual data modal with the user to ensure that the modal is a true
representation of the user view of the enterprise.
5.4 Physical data base design

The data access database is stored in table that contain field, data type and value.
The table used in this database are following.
5.4.1 Accessories
25
Table 5.1: Accessories

5.4.2 Admin
Table 5.2: Admin

5.4.3 Contact
Table 5.3: Contact

5.4.4 Delivery
Table 5.4: Delivery
26
5.4.5 Employee
Table 5.5: Employee

5.4.6 FAQs
Table 5.6: FAQs

5.4.7 Feed Back
Table 5.7: Feed Back
27
5.4.8 Loss and profit
Table 5.8: Loss and profit

5.4.9 Order
Table 5.9: Order

5.4.10 Payment
Table 5.10: Payment

28
5.4.11 Product info
Table 5.11: Product Info

5.4.12 Stock
Table 5.12: Stock
29
5.4.13 User _registration
Table 5.13: User Registration
5.5 Logical design

The primary objective of architectural design is to develop a modular program structure
and represent the control relationship between them.
5.5.1 Data Flow Diagrams
5.5.1.1 Level 0 data flow diagram
Data Flow Diagrams (DFDs) graphically characterize data process and flows in a
business system. Here data flow diagrams have been used to depict the broadest possible
overview of system inputs, process and outputs. Also a series of layered data flow
diagrams have been used to represent and analyse detailed procedures within this large
system. Therefore by using combinations of only four symbols, we have created a
pictorial depiction of process that will eventually provide solid system concepts and
documentation.
The four basic symbols used in the data flow diagram are as under:
30
31
Login
Login
Confirmation
Confirmation
Figure 5.1: Level 0 DFD
5.5.1.2 Notations of data flow diagram

There are following notations of Data Flow Diagrams.
Figure 5.2: Notations of DFDs
32
5.5.1.3 Level 1 DFD
33
5.5.1.4 Level 2 DFD
34
5.5.2 Entity Relationship Diagram

The object relationship pair is the cornerstone of the data model. These pairs can be
represented graphically using the entity relationship diagram (ERD). Peter Chen
originally proposed the entity relationship diagram for the design of the relational
database system. The primary purpose of the entity relationship diagram is to represent
the data objects in the form of relationships. Data objects, attributes, relationships and
various type indicators are the primary components of entity relationship diagram. It has
following features. Data objects are represented by a labeled rectangle.
Relationships are indicated with a labeled line connecting objects. In some variations of
entity relationship diagram relationships are represented by special diamond symbol,
mostly for junctions.
5.5.2.1 Admin
Admin id
Emails
Password
Admin
Figure 5.5: Admin

5.5.2.2 Contact
Name
Mob No
Email
Con ID
Contact
35
Figure 5.6: Contact

5.5.2.3 Delivery
D address
Pro _id
D _id
User reg id
Date
Name
Teacher Name
D source
Delivery
Figure 5.7: Delivery

5.5.2.4 Employee
CNIC
Designation
Gender
Mob No
Name
Address
Teacher Name
Salary
Emp_ID
Employee
Figure 5.8: Employee
36
5.5.2.5 FAQs
Faq_ID
Answer
Question
FAQs
Figure 5.9: FAQs

5.5.2.6 Feed Back
Fb_ID
Fb Answer
Fb Question
Feed Back
Figure 5.10: Feed Back

5.5.2.7 Loss and Profit
Pro_ID
Loss_Amount
Lp_ID
Profit_Amount
Loss and Profit
Figure 5.11: Loss and Profit
37
5.5.2.8 Order
User_Name
Pro_Name
User_ID
Pro_Price
Pro_ID
Pro_Image
Teacher Name
Qty
Order_ID
Date
Order
Figure 5.12: Order
5.5.2.9 Payment
Pro_ID
User Reg_ID
Pay_Date
Pay_ID
Payment
Figure 5.13: Payment
38
5.5.2.10 Product
Image
Pro_Name
Description
Pro_ID
Pro_price
Size
Teacher Name
Qty
Cat_ID
Color
File_Path
File_Name
Released
Product
Figure 5.14: Product

5.5.2.11 Stock
Stock_ID
Pro_ID
Stock
Figure 5.15: Stock
39
Qty
5.5.2.12 Accessories
Name
Acc_ID
Product ID
Acc_Price
Description
Accessories
Figure 5.16: Accessories

5.5.2.13 Temporary Table
Session ID
Temp_Tbl_ID
Product ID
Pro_Name
Pro_Price
Temp_Table
Figure 5.17: Temp_Table

5.5.2.14 User Registration
User_Reg_ID
Gender
User_CNIC
Email
User_Name
Password
Address
Mob_No
Tel_No
User Registration
Figure 5.18: User Registration
40
5.6 Database Diagram

Figure 5.19: Database Diagram
5.7 Entity Relationship Diagram
41
Figure 5.20: Entity Relationship Diagram
42
CHAPTER 6
SYSTEM TESTING
43
To developing software there is a tendency to push the end product out of door as soon
as possible. Most of the time, software project are not estimated properly and tend to run
behind schedule. System testing is essential step for development of a reliable and error
free system. Testing is a process of executing a program with explicit intension of finding
errors but this does not mean to embarrass the programmer or fail the product but positive
intension to remove as many problems from the system. A test case is a set of data items
that the system process as normal input. Good testing involves much more than just
running the program a few time to see whether it work.
A successful test is the one that find error. So some people ignore this important phase.
But our project online vehicle showroom has been thoroughly tested by us.
6.1 The place of testing in SDLC

Testing has in important place in SDLC (software development life cycle). The SQA
(software quality assurance) team should be involved in the early phases of the project.
This will make them the aware of the requirement and techniques that are been followed
enabling them to develop an appropriate test strategy.
6.2 System and Software Design

Before a starting for actual coding, it is highly important to understand what we are going
to create. The requirement specifications from first phase are studied in this phase and
system design is prepared. System Design helps in specifying hardware and system
requirements and also helps in defining overall system architecture. The system design
specifications serve as input for the next phase of the model.
6.2.1 Implementation and Unit Testing
On receiving system design documents, the work is divided in modules/units and actual
coding is started. The system is first developed in small programs called units, which are
integrated in the next phase. Each unit is developed and tested for its functionality, this is
referred to as Unit Testing. Unit testing mainly verifies if the modules/units meet their
specifications.
41
6.2.2 Integration and System Testing

As specified above, the system is first divided in units which are developed and tested for
their functionalities. These units are integrated into a complete system during Integration
phase and tested to check if all modules/units coordinate between each other and the
system as a whole behaves as per the specifications. After successfully testing the
software, it is delivered to the customer.
6.2.3 Operations and Maintenance
This phase of "The Waterfall Model" is virtually never ending phase (Very long).
Generally, problems with the system developed (which are not found during the
development life cycle) come up after its practical use starts, so the issues related to the
system are solved after deployment of the system. Not all the problems come in picture
directly but they arise time to time and needs to be solved; hence this process is referred
as Maintenance.
6.3 Type of testing

A will organized testing strategy should include following type testing:
6.3.1 Functional testing
This is referred to white box testing. It is done at a high level and takes individually
tested feature and places them together in small applications and test cases to test whether
they work to gather in small application.
6.3.2 Stress testing
This is a type of testing that is dread by developer because the kinds of bugs, it reveals
are different for them to simulate and fix. Stress testing is useful in identifying memory
leaks, garbage collection, thread execution, scalability and other issues that are not easy
to produce.
42
6.3.3 Black box testing

In this type of testing a software component is tested is treated like opaque box. This test
designer focus on determining how well the component conform to the published
requirement for the component, instead of worrying about the implementation details.
6.3.4 White box testing
In this type of testing
software component is treated as transparent box. Test designer
can peek into the box and again knowledge about the implementation.
6.3.5 Beta testing
The process of distribution a prerelease version of a product to a subset of its intended
audience for the purpose of obtaining feedback.
6.4 Testing of Online vehicle showroom

The testing of online Vehicle Showroom is done through all stages of black box testing
and white box testing. In the evaluation phase the system is reviewed to see whether the
objective of the system is accomplished or not.
A major factor during evaluation phase the system is to evaluate the system with
perspective of the user because he/ she is eventually being the one who use it.
Testing of purchasing online vehicle showroom is follow.
Trace ability Test Matrix.
Test Case Description.
GUI Test Plan.
6.5.1 Trace ability Matrix

Test case ID
Test
Result
Test 1
Verify that user get error message on wrong password.
Test has passed

successfully
43
Test2
Verify that users can access all the edit boxes.
Test has passed

successfully
Test3
Test 4
Verify that user cannot access the administrator
Test has passed
functionally if login as customer.
successfully
Verify that user get error message on wrong entries.
Test has passed

successfully
Test5
Verify that product is updated.
Test has passed

successfully
Test 6
Test7
Test8
Verify that shopping cart becomes empty while
Test has passed
attempting for new order.
successfully
Verify that user can view only index page user is not
Test has passed
login.
successfully
Verify that the order is placed.
Test has passed

successfully
Test 10
Verify that user can access home page.
Test has
successfully
Test 11
Test12
Verify that user get error message on wrong user name
Test has passed
and password.
successfully
Verify that user get error message on wrong entries.
Test has passed

successfully
Test 13
Verify that if we deliver something on current date or
Test has passed
future date the process go forwarded successfully and if
successfully
we go past date they give us error.

Test 14
Verify that all over the process are working true.
Test has passed

successfully
Table 6.1: Trace ability Matrix
44
6.5.2 Test case Description
Test case ID
Test 3
Test Engineer: Mr. Aamir Javed
Test date
1 march 2015 Test case version : Vr :1.0
Objective: Verify that user cannot access the administrator functionality if login as
customer.
Module /version:
Online vehicle showroom
Environment :
Window7
Pre- Requisite:
Method
Administrator functionality only get if user login as administrator
1.open the login page

2.enter the name for the administrator
3.enter the true password for administrator
Test case ID
Test 4
Test date
Test engineer : Mr. Aamir Javed
3 -march -2015
Test case version : vr :1.1
Objective:
Verify that user get error message on wrong entries
Version/module:
Online vehicle showroom
Environment:
Window 7
Pre-Requisite :
User must have to make all entries according to system requirement
Method
1. Check the field on from and enter data according to the mentioned fields.
Table 6.2: Test Case Description
45
CHAPTER 7
OVERVIEW
46
7.1 Overview
It is particularly important first to design how the system will look and inspire the user
before designing the software structure. The most critical and creative aspect of
development is to design the user interface. User interface design determines how the
system will look the user from outside. The basic design principle, consider the user
interface design, are the following. The interface describe how the software communicate
with the system that inter operate with it and with human who use it. An interface implies
of flow of the information for interface design.
The interface design create in effective communicate medium between human and a
computer. Following are set of design principle. The design identifier interface object
action and then create a screen layout that formats the basic for the user interface
prototype. User interface begin with the identification of the user, task and the
environment requirement. User interface for software should be design in such a way that
is friendly to the user, easy to use and easy to understand. It should provide high quality
interface between the users in the system. The results produce by our software should be
consistence.
In the designing the user interface it has been kept in mind that on technical personnel
will operate the system with very little or no technical knowledge, therefore the user
interface has been designed is user friendly as possible that facilitate easy and quick entry
of input data. Controls that has been used and designing the screen are:
1. Main page.
2. Administrator Login.
3. User Login.
4. Product page.
5. View product details.
6. Order.
7. Add to cart.
8. Registration from.
9. Success page.
10. Contact us.
11. Feedback.
46
7.2 Main page
Figure 7.1: Home Page
47
7.3 Administrator login

In this from the administrator will enter user name and password to access the main menu
of the administrator from. The purpose of this from is to provide the security to
administration operation. Only the administrator has the privileges to the data base.
Figure 7.2: Administrator login
7.4 User login

In this from the user will enter user name and password to give your order.
Figure 7.3: User Login
48
7.5 Products
There is list of product available and also all of the description of the product and
category. If we want to buy a product, you simply click on the product, and the selected
product will show you more details about product.
Figure 7.4: Product
49
7.6 View product details
50
In this table all of details of the product along with its specification and price are
available
here.
51
7.7 Order
In this page we have all the details about the product by which the customer order.
Figure 7.6: Order
52
7.8 Add to cart

There is list of product name, category name, price and description. User will see the
product list and then he/ she will press add to cart button.
Figure 7.7: Add to cart
53
7.9 Registration from

There is a registration form for those who have not an account. In order to make a new
account user should have to give its complete information i.e. name. Contact and address
etc. text boxes and buttons are used to gather the information.
Figure 7.8: Registration from
54
7.10 Success page

This page will appear when the user succeeds in purchasing product.
Figure 7.9: Success page
7.11 Contact us
In this form the developer contact is available for any problem. There is Name, email,
and phone no of owner are available.
55
Figure 7.10: Contact us
7.12 Feed back

In this form the customer give the feedback about the product.
Figure 7.11: Feed Back
56
CHAPTER 8
CODING
57
Appendices
Accessories
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Accessories.aspx.cs"
Inherits="OnlineVehicleShowroom.Admin.Accessories" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.0
Transitional//EN"
<html xmlns="http://www.w3.org/1999/xhtml">
<head id="Head1" runat="server">
<title>Accessories</title>
<link href="~/Styles/Site.css" rel="stylesheet" type="text/css" />
</head>
<body>
<form id="form1" runat="server">
<div>
<div class="headrr">
<h1>
Online Vehicle Showroom - ( Accessories Form )
</h1>
<div class="loginDisplay">
<div class="clear hideSkiplink">
</div>
<asp:Menu ID="NavigationMenuuu" runat="server" CssClass="menu"
EnableViewState="false" IncludeStyleBlock="false" Orientation="Horizontal">
<Items>
<asp:MenuItem NavigateUrl="~/Admin/Admin_Dashboard.aspx"
Text="Admin Dashboard"/>
</Items>
</asp:Menu>
</div> 
</div> 
</div>
<div class="all" style="border: 2px solid white; width: 79.7%;">
<br />
<div id="Acc_grid_h1">
<h1><b>Accessories Form</b></h1>
<br />
<%--UpdateCommand="UPDATE
[User_Registration]
Set
[User_Name]=@User_Name, [User_CNIC]=@User_CNIC, [User_Gender]=@User_Gender,
[Email]=@Email,
[Password]=@Password,
[User_Tel_No]=@User_Tel_No,
[User_Mob_No]=@User_Mob_No,
[User_Address]=@User_Address,
[User_Country]=@User_Country
Where
[User_Reg_ID]=@User_Reg_ID"
DeleteCommand="DELETE
from
[User_Registration]
Where
[User_Reg_ID]=@User_Reg_ID"--%>
56
<Items>
</Items>
</asp:Menu>
</div> 
</div>
<div class="maiiiii" style=" border: 2px solid white; width: 79.67%; margin-left: 10%;
background: white;">
<br />
<h1 style="margin-left: 12%;"><b>Admin Form</b></h1>
<div id="grid_add">
<div class="gridview">
<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False"
AutoGenerateDeleteButton="True" AutoGenerateEditButton="True"
DataKeyNames="Admin_ID" DataSourceID="SqlDataSource1" Height="31px"
Width="424px">
<Columns>
<asp:BoundField DataField="Admin_ID" HeaderText="Admin_ID"
InsertVisible="False" ReadOnly="True" SortExpression="Admin_ID" />
<asp:BoundField DataField="Admin_Name" HeaderText="Admin_Name"
SortExpression="Admin_Name" />
<asp:BoundField DataField="Password" HeaderText="Password"
SortExpression="Password" />
</Columns>
<%--UpdateCommand="UPDATE [Admin] Set [Admin_Name]=@Admin_Name,
[Password]=@Password Where [Admin_ID]=@Admin_ID" DeleteCommand="DELETE from
[Admin] Where [Admin_ID]=@Admin_ID"--%>
</asp:GridView>
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
ConnectionString="<%$
ConnectionStrings:OnlineVehicleShowroomDBConnectionString %>"
SelectCommand="SELECT * FROM [Admin]" UpdateCommand="UPDATE [Admin]
Set
[Admin_Name]=@Admin_Name,
[Password]=@Password
Where
[Admin_ID]=@Admin_ID"
from
[Admin]
Where
[Admin_ID]=@Admin_ID"></asp:SqlDataSource>
</div>
<div id="Admin_add">
<div id="lblEmail"> <asp:Label ID="txtAdminName" runat="server" Text="Name
"></asp:Label></div>
<div id="txtemal"> <asp:TextBox ID="txtEmail" runat="server"></asp:TextBox>
</div>
<br />
<div id="lblPass"> <asp:Label ID="Label2" runat="server" Text="Password
"></asp:Label> </div>
<div id="txtPass"><asp:TextBox ID="txtPassword" runat="server"></asp:TextBox>
</div>
<br /><br />
59
<div id="btnAd"><asp:Button ID="btnAdd" runat="server" Text="ADD"

onclick="btnAdd_Click" /></div>
</div>
</div>
<br /><br /><br /><br />
</div>
<%--footer starts--%>
<div class="footer">
<p><b> Developed by Inam ullah & Atta ur rehman .</b></p>
<div class="social">
<asp:HyperLink ID="HyperLink1" runat="server"
ImageUrl="~/Admin/img/facebook.JPG" NavigateUrl="#">HyperLink
<asp:Image ID="Image17" runat="server" />
</asp:HyperLink>
ImageUrl="~/Admin/img/twitter.JPG" NavigateUrl="#">HyperLink
</asp:HyperLink>
ImageUrl="~/Admin/img/li.JPG" NavigateUrl="#">HyperLink
</asp:HyperLink>
</div>
</div> <%--Ends footer--%>
</form>
</body>
</html>
Admin Dashboard
<%@
Page
Language="C#"
CodeBehind="Admin_Dashboard.aspx.cs"
Inherits="OnlineVehicleShowroom.Admin.WebForm1" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
AutoEventWireup="true"
1.0
<head runat="server">
<title>Admin Dashboard</title>
</head>
<body>
60
Transitional//EN"
<div>
<h1>
Online Vehicle Showroom - ( Admin Dashboard )
</h1>
<div id="aa" style="margin-left: 80%; margin-top: -5%;"><h2>
<asp:Label ID="lblWelcome" runat="server" Text=""
Font-Bold="True" Font-Italic="True" ForeColor="White"></asp:Label>
</h2></div>
<br />
<a href="../Default.aspx" style="color:White; margin-left: 90%;"
id="A1"><b>Logout</b></a>
<%--<Items>
<asp:MenuItem NavigateUrl="~/Default.aspx" Text="Logout"/>
</Items>--%>
</div>
<Items>
Text="Dashboard"/>
</Items>
</asp:Menu>
</div> 
<%--main area starts--%>
<div class="all" style="border: 2px solid black; width: 79.7%;">
<h2><b>Welcome to Admin Dashboard of Online Vehicle Showroom!</b></h2>
<div id="move">
<div id="one">
<asp:Image ID="Image1" runat="server" Height="37px"
ImageUrl="~/Admin/img/admin.JPG" Width="42px" />
<a href="../Admin/Admin.aspx" id="AdminLink">Admin</a>
<br /><br />
ImageUrl="~/Admin/img/user_reg.JPG" Width="42px" />
<a href="../Admin/User_Reg.aspx" id="UserRegLink">User Registration</a>
<br /><br />
ImageUrl="~/Admin/img/products.JPG" Width="42px" />
<a href="../Admin/Products.aspx" id="ProductsLink">Products</a>
61
<br /><br />

<%--<asp:Image ID="Image4" runat="server" Height="37px"
ImageUrl="~/Admin/img/catagory.JPG" Width="42px" />
<a href="../Admin/Catagories.aspx" id="CatagoryLink">Catagories</a>--%>
ImageUrl="~/Admin/img/contact.JPG" Width="42px" />
<a href="../Admin/Contacts.aspx" id="ContactLink">Contacts</a>
<br /><br />
</div>
<div id="two">

ImageUrl="~/Admin/img/delivery.JPG" Width="42px" />
<a href="../Admin/Delivery.aspx" id="DeliveryLink">Delivery</a>
<br /><br />
ImageUrl="~/Admin/img/emplyee.JPG" Width="42px" />
<a href="../Admin/Employee.aspx" id="EmployeeLink">Employee</a>
<br /><br />
ImageUrl="~/Admin/img/faqs.JPG" Width="42px" />
<a href="../Admin/Faqs.aspx" id="FaqsLink">Faqs</a>
<br /><br />
ImageUrl="~/Admin/img/feedback.JPG" Width="42px" />
<a href="../Admin/Feedback.aspx" id="FeedbackLink">Feedback</a>
</div>
<div id="three">

ImageUrl="~/Admin/img/loss_profit.JPG" Width="42px" />
<a href="../Admin/Loss_Profit.aspx" id="LostProfitLink">Loss & Profit</a>
<br /><br />
ImageUrl="~/Admin/img/orders.JPG" Width="42px" />
<a href="../Admin/Orders.aspx" id="OrdersLink">Orders</a>
<br /><br />
ImageUrl="~/Admin/img/payments.JPG" Width="42px" />
<a href="../Admin/Payments.aspx" id="PaymentsLink">Payments</a>
<br /><br />
ImageUrl="~/Admin/img/accessories.JPG" Width="42px" />
62
<a href="../Admin/Accessories.aspx" id="AccessoriesLink">Accessories</a>

</div>
<div id="four">

ImageUrl="~/Admin/img/stock.JPG" Width="42px" />
<a href="../Admin/Stock.aspx" id="StockLink">Stock</a>
<br /><br />
</div>
</div>
<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
</div> <%--main area ends--%>
</asp:HyperLink>
</asp:HyperLink>
</asp:HyperLink>
</div>
</div>
</div>
</form>
</body>
</html>
Contact
63
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Contacts.aspx.cs"

Inherits="OnlineVehicleShowroom.Admin.Contacts" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
1.0
Transitional//EN"
<title>Contacts</title>
</head>
<body>
<div>
<h1>
Online Vehicle Showroom - ( Admin Form )
</h1>
</div>
<Items>
</Items>
</asp:Menu>
</div> 
</div>
<br />
<div id="cntact_grid_h1">
<h1><b>Contact Details Form</b></h1>
<br />
DataKeyNames="Contact_ID" DataSourceID="SqlDataSource1">
<Columns>
<asp:BoundField DataField="Contact_ID" HeaderText="Contact_ID"
InsertVisible="False" ReadOnly="True" SortExpression="Contact_ID" />
<asp:BoundField DataField="Name" HeaderText="Name"
SortExpression="Name" />
<asp:BoundField DataField="Email" HeaderText="Email" SortExpression="Email"
/>
<asp:BoundField DataField="Contact_No" HeaderText="Contact_No"
SortExpression="Contact_No" />
<%--<asp:BoundField DataField="Message" HeaderText="Message"
SortExpression="Message" />--%>
</Columns>
</asp:GridView>
64
SelectCommand="SELECT * FROM [Contact]" UpdateCommand="UPDATE
[Contact] Set [Name]=@Name, [Email]=@Email, [Contact_No]=@Contact_No Where
[Contact_ID]=@Contact_ID"
from
[Contact]
Where
[Contact_ID]=@Contact_ID"></asp:SqlDataSource>
</div>
<br /><br />
<div id="add_contact">
<asp:Label ID="Label1" runat="server" Text="Name" FontBold="True"></asp:Label> <br />
<asp:TextBox ID="txtName" runat="server" Width="175px"></asp:TextBox>
<br />
<asp:Label ID="Label2" runat="server" Text="Email" FontBold="True"></asp:Label> <br />
<asp:TextBox ID="txtEmail" runat="server" Width="174px"></asp:TextBox>
<br />
<%-<asp:Label ID="Label3" runat="server" Text="Subject" FontBold="True"></asp:Label> <br />
<asp:TextBox ID="txtSubject" runat="server"></asp:TextBox>
<br />--%>
<asp:Label ID="Label4" runat="server" Text="Contact_No" FontBold="True"></asp:Label> <br />
<asp:TextBox ID="txtContact" runat="server" Width="174px"></asp:TextBox>
<br /><br />
<asp:Button ID="btnAdd" runat="server" Text="ADD" Font-Bold="True"
Height="31px" onclick="btnAdd_Click" Width="59px" />
</div>
<br /><br /><br />

</div>
</asp:HyperLink>
</asp:HyperLink>
65
</asp:HyperLink>
</div>
</form>
</body>
</html>
Delivery
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Delivery.aspx.cs"
Inherits="OnlineVehicleShowroom.Admin.Delivery" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
1.0
Transitional//EN"
<title>Delivery Form</title>
</head>
<body>
<div>
<h1>
Online Vehicle Showroom - ( Delivery Form )
</h1>
</div>
<Items>
</Items>
</asp:Menu>
</div> 
</div>
<br />
<div id="Delivery_grid_h1">
<h1><b>Delivery Form</b></h1>
<br />
66
DataKeyNames="Delivery_ID,Pro_ID" DataSourceID="SqlDataSource1"
Height="114px">
<Columns>
<asp:BoundField DataField="Delivery_ID" HeaderText="Delivery_ID"
ReadOnly="True" SortExpression="Delivery_ID" />
<asp:BoundField DataField="User_CNIC" HeaderText="User_CNIC"
SortExpression="User_CNIC" />
<asp:BoundField DataField="Pro_ID" HeaderText="Pro_ID"
SortExpression="Pro_ID" ReadOnly="True" />
<asp:BoundField DataField="Pro_Name" HeaderText="Pro_Name"
SortExpression="Pro_Name" />
<%-- <asp:BoundField DataField="Delivery_City" HeaderText="Delivery_City"
SortExpression="Delivery_City" />
<asp:BoundField DataField="Delivery_Village" HeaderText="Delivery_Village"
SortExpression="Delivery_Village" />--%>
<asp:BoundField DataField="Delivery_Source" HeaderText="Delivery_Source"
SortExpression="Delivery_Source" />
<asp:BoundField DataField="Delivery_Address" HeaderText="Delivery_Address"
SortExpression="Delivery_Address" />
<asp:BoundField DataField="Date" HeaderText="Date" SortExpression="Date"
/>
</Columns>
</asp:GridView>
<%--SelectCommand="SELECT * FROM [Delivery]" UpdateCommand="UPDATE
[Delivery]
Set
[Pro_ID]=@Pro_ID,
[User_Reg_ID]=@User_Reg_ID,
[Delivery_Address]=@Delivery_Address,
[Date]=@Date,
[Delivery_Source]=@Delivery_Source
Where
[Delivery_ID]=@Delivery_ID"
from
[Delivery]
Where
[Delivery_ID]=@Delivery_ID"></asp:SqlDataSource>
--%>
SelectCommand="SELECT * FROM [Delivery_Details_View]"
from
[Delivery]
Where
[Delivery_ID]=@Delivery_ID"></asp:SqlDataSource>
</div>
<%--<div id="delivery_Add">
<asp:Label ID="Label2" runat="server" Text="Product ID"></asp:Label><br />
<asp:TextBox ID="txtProID" runat="server"></asp:TextBox>
<br />
<asp:Label ID="Label1" runat="server" Text="User Registration
ID"></asp:Label><br />
<asp:TextBox ID="txtUserRegID" runat="server"></asp:TextBox>
<br />
<asp:Label ID="Label3" runat="server"
Address"></asp:Label><br />
<asp:TextBox ID="txtDelivAdrs" runat="server"></asp:TextBox>
<br />
<br />
<br />
<br />
67
Text="Delivery
<br />
<asp:Label ID="Label6" runat="server" Text="Date"></asp:Label><br />
<asp:TextBox ID="txtDate" runat="server"></asp:TextBox>
<br />
/>
<asp:Label ID="Label7" runat="server" Text="Delivery Source"></asp:Label><br

<asp:TextBox ID="txtDelivSource" runat="server"></asp:TextBox>
<br /><br />
<div id="btnAdDelivery">
onclick="btnAdd_Click" />
</div>
</div>--%>
<br /><br /><br /><br />
</div>
<p><b> Developed by Inam ullah &Atta ur rehman.</b></p>
</asp:HyperLink>
</asp:HyperLink>
</asp:HyperLink>
</div>
</form>
</body>
</html>
Employee from
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Employee.aspx.cs"
Inherits="OnlineVehicleShowroom.Admin.Employee" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
1.0
<title>Employee</title>
</head>
68
Transitional//EN"
<body>
<div>
<h1>
Online Vehicle Showroom - ( Employee Form )
</h1>
</div>
<Items>
</Items>
</asp:Menu>
</div> 
</div>
<br />
<div id="Emp_grid_h1">
<h1><b>Employee Details Form</b></h1>
<br />
DataKeyNames="Emp_ID" DataSourceID="SqlDataSource1">
<Columns>
<asp:BoundField DataField="Emp_ID" HeaderText="Emp_ID"
InsertVisible="False"
ReadOnly="True" SortExpression="Emp_ID" />
<asp:BoundField DataField="Emp_Name" HeaderText="Emp_Name"
SortExpression="Emp_Name" />
<asp:BoundField DataField="Emp_Gender" HeaderText="Emp_Gender"
SortExpression="Emp_Gender" />
<asp:BoundField DataField="Emp_CNIC" HeaderText="Emp_CNIC"
SortExpression="Emp_CNIC" />
<asp:BoundField DataField="Emp_Designation"
HeaderText="Emp_Designation"
SortExpression="Emp_Designation" />
<asp:BoundField DataField="Emp_Mob_No" HeaderText="Emp_Mob_No"
SortExpression="Emp_Mob_No" />
<asp:BoundField DataField="Emp_Address" HeaderText="Emp_Address"
SortExpression="Emp_Address" />
<asp:BoundField DataField="Emp_Salary" HeaderText="Emp_Salary"
SortExpression="Emp_Salary" />
</Columns>
</asp:GridView>
69
SelectCommand="SELECT * FROM [Employee]" UpdateCommand="UPDATE
[Employee]
Set
[Emp_Name]=@Emp_Name,
[Emp_Gender]=@Emp_Gender,
[Emp_CNIC]=@Emp_CNIC,
[Emp_Designation]=@Emp_Designation,
[Emp_Mob_No]=@Emp_Mob_No,
[Emp_Address]=@Emp_Address,
[Emp_Salary]=@Emp_Salary Where [Emp_ID]=@Emp_ID" DeleteCommand="DELETE from
[Employee] Where [Emp_ID]=@Emp_ID"></asp:SqlDataSource>
</div>
<div id="Add_Emp">
<asp:Label ID="Label1" runat="server" Text="Name"></asp:Label> <br />
<asp:TextBox ID="txtEmpName" runat="server"></asp:TextBox>
<br />
<asp:Label ID="Label2" runat="server" Text="Gender"></asp:Label> <br />
<asp:TextBox ID="txtGender" runat="server"></asp:TextBox>
<br />
<asp:Label ID="Label3" runat="server" Text="CNIC"></asp:Label> <br />
<asp:TextBox ID="txtCNIC" runat="server"></asp:TextBox>
<br />
<asp:Label ID="Label4" runat="server" Text="Designation"></asp:Label> <br />
<asp:TextBox ID="txtDesignation" runat="server"></asp:TextBox>
<br />
<asp:Label ID="Label5" runat="server" Text="Mobile No"></asp:Label> <br />
<asp:TextBox ID="txtMobNo" runat="server"></asp:TextBox>
<br />
<asp:Label ID="Label6" runat="server" Text="Address"></asp:Label> <br />
<asp:TextBox ID="txtAddress" runat="server"></asp:TextBox>
<br />
<asp:Label ID="Label7" runat="server" Text="Salary"></asp:Label> <br />
<asp:TextBox ID="txtSalary" runat="server"></asp:TextBox>
<br /><br />
</div>
<br /><br /><br />
</div>
70

</asp:HyperLink>
</asp:HyperLink>
</asp:HyperLink>
</div>
</form>
</body>
</html>
FAQs
<%@ Page Language="C#" AutoEventWireup="true"
Inherits="OnlineVehicleShowroom.Admin.Faqs" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
CodeBehind="Faqs.aspx.cs"
1.0
Transitional//EN"
<title>Faqs</title>
</head>
<body>
<div>
<h1>
Online Vehicle Showroom - ( Faqs )
</h1>
</div>
<Items>
</Items>
</asp:Menu>
</div> 
71
</div>
<br />
<h1><b>Faqs Form</b></h1>
<br />
<%--UpdateCommand="UPDATE [Admin] Set [Email]=@Email,
[Password]=@Password Where [Admin_ID]=@Admin_ID" DeleteCommand="DELETE from
[Admin] Where [Admin_ID]=@Admin_ID"--%>
DataKeyNames="Faq_ID" DataSourceID="SqlDataSource1">
<Columns>
<asp:BoundField DataField="Faq_ID" HeaderText="Faq_ID" ReadOnly="True"
SortExpression="Faq_ID" />
<asp:BoundField DataField="Faq_Question" HeaderText="Faq_Question"
SortExpression="Faq_Question" />
<asp:BoundField DataField="Faq_Answer" HeaderText="Faq_Answer"
SortExpression="Faq_Answer" />
</Columns>
</asp:GridView>
SelectCommand="SELECT * FROM [Faqs]" UpdateCommand="UPDATE [Faqs] Set
[Faq_Question]=@Faq_Question, [Faq_Answer]=@Faq_Answer Where [Faq_ID]=@Faq_ID"
DeleteCommand="DELETE from [Faqs] Where [Faq_ID]=@Faq_ID"></asp:SqlDataSource>
<br /><br />
<div id="add_faqs">
<div id="lbl_Ques"><asp:Label ID="Label1" runat="server" Text="Question"
Font-Bold="True"></asp:Label> </div>
<div id="txt_Ques"> <asp:TextBox id="txtQues" TextMode="multiline"
Columns="70"
Rows="3" runat="server" /> </div>
<br />
<div id="lbl_Ans"> <asp:Label ID="Label2" runat="server" Text="Answer"
Font-Bold="True"></asp:Label> </div>
<div id="txt_Ans"> <asp:TextBox id="txtAns" TextMode="multiline"
Columns="70"
Rows="3" runat="server" /> </div>
<br />
<div id="btnAdd_Faqs">
Height="27px" onclick="btnAdd_Click1" Width="58px" />
</div>
</div>
<br /><br /><br />
</div>
72
<p><b> Developed by Inam ullah&Atta ur rehman .</b></p>
</asp:HyperLink>
</asp:HyperLink>
</asp:HyperLink>
</div>
</form>
</body>
</html>
Feed back
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Feedback.aspx.cs"
Inherits="OnlineVehicleShowroom.Admin.Feedback" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
1.0
Transitional//EN"
<title>Feedback</title>
</head>
<body>
<div>
<h1>
Online Vehicle Showroom - ( Feedback Form )
</h1>
</div>
<Items>
73
</Items>
</asp:Menu>
</div> 
</div>
<br />
<h1 style="margin-left:16%;"><b>Feedbacks Form</b></h1>
<br /><br />
<div id="feedback_grid">

DataKeyNames="FB_ID" DataSourceID="SqlDataSource1">
<Columns>
<asp:BoundField DataField="FB_ID" HeaderText="FB_ID"
InsertVisible="False"
ReadOnly="True" SortExpression="FB_ID" />
<asp:BoundField DataField="User_Name" HeaderText="User_Name"
SortExpression="User_Name" />
<asp:BoundField DataField="FB_Title" HeaderText="FB_Title"
SortExpression="FB_Title" />
<asp:BoundField DataField="FB_Description" HeaderText="FB_Description"
SortExpression="FB_Description" />
</Columns>
</asp:GridView>
<%-UpdateCommand="UPDATE [Employee] Set [Emp_Name]=@Emp_Name,
[Emp_Gender]=@Emp_Gender,
[Emp_CNIC]=@Emp_CNIC,
[Emp_Designation]=@Emp_Designation,
[Emp_Mob_No]=@Emp_Mob_No,
[Emp_Address]=@Emp_Address,
[Emp_Salary]=@Emp_Salary
Where
[Emp_ID]=@Emp_ID"
from
[Employee]
Where
[Emp_ID]=@Emp_ID"--%>
SelectCommand="SELECT * FROM [Feedback]" UpdateCommand="UPDATE
[Feedback]
Set
[Pro_Name]=@Pro_Name,
[User_Name]=@User_Name,
[FB_Title]=@FB_Title,
[FB_Description]=@FB_Description
Where
[FB_ID]=@FB_ID"
from
[Feedback]
Where
[FB_ID]=@FB_ID"></asp:SqlDataSource>
</div>
<br /><br /><br />
74
</div>
</asp:HyperLink>
</asp:HyperLink>
</asp:HyperLink>
</div>
</form>
</body>
</html>
Loss & profit

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Loss_Profit.aspx.cs"
Inherits="OnlineVehicleShowroom.Admin.Loss_Profit" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
1.0
Transitional//EN"
<title>Loss & Profit Form</title>
</head>
<body>
<div>
<h1>
Online Vehicle Showroom - ( Loss & Profit Form )
</h1>
</div>
<Items>
75
</Items>
</asp:Menu>
</div> 
</div>
<br />
<div id="LP_Grid_h1">
<h1><b>Loss & Profit Details Form</b></h1>
<br />
DataKeyNames="LP_ID" DataSourceID="SqlDataSource1" Height="130px"
Width="337px">
<Columns>
<asp:BoundField DataField="LP_ID" HeaderText="LP_ID" InsertVisible="False"
ReadOnly="True" SortExpression="LP_ID" />
SortExpression="Pro_ID" />
<asp:BoundField DataField="Loss_Amount" HeaderText="Loss_Amount"
SortExpression="Loss_Amount" />
<asp:BoundField DataField="Profit_Amount" HeaderText="Profit_Amount"
SortExpression="Profit_Amount" />
</Columns>
</asp:GridView>
<%--UpdateCommand="UPDATE [Delivery] Set [Pro_ID]=@Pro_ID,
[User_Reg_ID]=@User_Reg_ID,
[Delivery_Address]=@Delivery_Address,
[Delivery_City]=@Delivery_City, [Delivery_Village]=@Delivery_Village, [Date]=@Date,
[Delivery_Source]=@Delivery_Source
Where
[Delivery_ID]=@Delivery_ID"
DeleteCommand="DELETE from [Delivery] Where [Delivery_ID]=@Delivery_ID"--%>
SelectCommand="SELECT * FROM [Lost_Profit]" UpdateCommand="UPDATE
[Lost_Profit]
Set
[Pro_ID]=@Pro_ID,
[Loss_Amount]=@Loss_Amount,
[Profit_Amount]=@Profit_Amount Where [LP_ID]=@LP_ID" DeleteCommand="DELETE
from [Lost_Profit] Where [LP_ID]=@LP_ID"></asp:SqlDataSource>
</div>
<div id="LP_ADD">
<asp:Label ID="Label1" runat="server" Text="Product ID"></asp:Label><br />
<asp:TextBox ID="txtProID" runat="server" Height="24px"></asp:TextBox>
<br />
<asp:Label ID="Label2" runat="server" Text="Loss Amount"></asp:Label><br />
<asp:TextBox ID="txtLossAmount" runat="server" Height="24px"></asp:TextBox>
<br />
<asp:Label ID="Label3" runat="server" Text="Profit Amount"></asp:Label><br />
<asp:TextBox ID="txtProfitAmount" runat="server" Height="24px"></asp:TextBox>
<br /><br />
76
<div id="btnAdd_LP">
onclick="btnAdd_Click" />
</div>
</div>
<br /><br /><br /><br />
</div>
</asp:HyperLink>
</asp:HyperLink>
</asp:HyperLink>
</div>
</form>
</body>
</html>
Order from
Inherits="OnlineVehicleShowroom.Admin.Orders" %>
CodeBehind="Orders.aspx.cs"
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
1.0
<title>Orders</title>
</head>
<body>
<div>
<h1>
77
Transitional//EN"
Online Vehicle Showroom - ( Orders Form )

</h1>
</div>
<Items>
</Items>
</asp:Menu>
</div> 
</div>
<br />
<center>
<h1><b>Order Details From</b></h1>
</center>
/>

DataSourceID="SqlDataSource1" DataKeyNames="Order_ID,User_Reg_ID,Pro_ID"
onselectedindexchanged="GridView1_SelectedIndexChanged">
<Columns>
<asp:BoundField DataField="Order_ID" HeaderText="Order_ID"
SortExpression="Order_ID" ReadOnly="True" />
<asp:BoundField DataField="User_Reg_ID" HeaderText="User_Reg_ID"
SortExpression="User_Reg_ID" ReadOnly="True" />
<asp:BoundField DataField="Cmp_Name" HeaderText="Cmp_Name"
SortExpression="Cmp_Name" />
<asp:BoundField DataField="Size" HeaderText="Size" SortExpression="Size" />
<asp:BoundField DataField="Color" HeaderText="Color" SortExpression="Color"
<asp:BoundField DataField="Model" HeaderText="Model"

SortExpression="Model" />
<asp:BoundField DataField="Pro_Price" HeaderText="Pro_Price"
SortExpression="Pro_Price" />
<asp:BoundField DataField="Date" HeaderText="Date" SortExpression="Date"
/>
</Columns>
</asp:GridView>
78
SelectCommand="SELECT * FROM [order_details_view]"></asp:SqlDataSource>
<br /><br /><br />

</div>
</asp:HyperLink>
</asp:HyperLink>
</asp:HyperLink>
</div>
</form>
</body>
</html>
Payment form
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Payments.aspx.cs"
Inherits="OnlineVehicleShowroom.Admin.Payments" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
1.0
<title>Payments</title>
</head>
<body>
79
Transitional//EN"
<div>
<h1>
Online Vehicle Showroom - ( Payments Form )
</h1>
</div>
<Items>
</Items>
</asp:Menu>
</div> 
</div>
<br />
<div id="">
<h1><b>Payments Details Form</b></h1>
<br />
DataKeyNames="Pay_ID,Pro_ID" DataSourceID="SqlDataSource1">
<Columns>
<asp:BoundField DataField="Pay_ID" HeaderText="Pay_ID"
ReadOnly="True" SortExpression="Pay_ID" />
<asp:BoundField DataField="Bank_Name" HeaderText="Bank_Name"
SortExpression="Bank_Name" />
<asp:BoundField DataField="Account_No" HeaderText="Account_No"
SortExpression="Account_No" />
<asp:BoundField DataField="Pay_Date" HeaderText="Pay_Date"
SortExpression="Pay_Date" />
</Columns>
</asp:GridView>

80
[Payments_Details_View]"></asp:SqlDataSource>
SelectCommand="SELECT
FROM
</div>
<br /><br /><br />
</div>
<p><b> Developed by Inam ullah& Atta ur rehman .</b></p>
</asp:HyperLink>
</asp:HyperLink>
</asp:HyperLink>
</div>
</form>
</body>
</html>
Product list
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Products.aspx.cs"
Inherits="OnlineVehicleShowroom.Admin.Products" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
1.0
<title>Products</title>
</head>
<body>
<div>
<h1>
Online Vehicle Showroom - ( Products List )
</h1>
81
Transitional//EN"
</div>
<Items>
</Items>
</asp:Menu>
</div> 
</div>
<br />
<h1><b>Products Form</b></h1>
ImageUrl="~/Admin/img/Add.png" Width="42px" />
<a href="../Admin/Products_Add.aspx" id="A1">Add Products</a
<br />
/>

DataKeyNames="Pro_ID" DataSourceID="SqlDataSource1">
<Columns>
<asp:BoundField DataField="Pro_ID" HeaderText="Pro_ID" InsertVisible="False"
ReadOnly="True" SortExpression="Pro_ID" />
<%--<asp:BoundField DataField="Cat_ID" HeaderText="Cat_ID"
SortExpression="Cat_ID" />--%>
<asp:BoundField DataField="Cmp_Name" HeaderText="Cmp_Name"
SortExpression="Cmp_Name" />
<asp:BoundField DataField="Pro_Price" HeaderText="Pro_Price"
<asp:BoundField DataField="Description" HeaderText="Description"
SortExpression="Description" />
<asp:BoundField DataField="Size" HeaderText="Size" SortExpression="Size" />
<asp:BoundField DataField="Color" HeaderText="Color" SortExpression="Color"
<asp:BoundField DataField="Model" HeaderText="Model"

SortExpression="Model" />
<asp:BoundField DataField="FileName" HeaderText="FileName"
SortExpression="FileName" />
<asp:BoundField DataField="FilePath" HeaderText="FilePath"
SortExpression="FilePath" />
</Columns>
</asp:GridView>
82
SelectCommand="SELECT * FROM [Products]" UpdateCommand="UPDATE
[Products]
Set
[Pro_Name]=@Pro_Name,
[Cmp_Name]=@Cmp_Name,
[Pro_Price]=@Pro_Price, [Description]=@Description, [Size]=@Size, [Color]=@Color,
[Model]=@Model,
[FileName]=@FileName
Where
[Pro_ID]=@Pro_ID"
from
[Products]
Where
[Pro_ID]=@Pro_ID"></asp:SqlDataSource>
<%--<br /><br /><br /><br />--%>
<%--<div id="Add_Products">
<asp:Label ID="Label1" runat="server" Text="Product Name"></asp:Label><br />
<asp:TextBox ID="txtProName" runat="server" Height="25px"
Width="250px"></asp:TextBox>
<br />
<asp:Label ID="Label2" runat="server" Text="Catagory ID"></asp:Label><br />
<asp:TextBox
ID="txtCatID"
runat="server" Height="25px"
<br />
<asp:Label ID="Label3" runat="server" Text="Company ID"></asp:Label><br />
<asp:TextBox ID="txtCmpID" runat="server" Height="25px"
<br />
<asp:Label ID="Label4" runat="server" Text="Product Price"></asp:Label><br />
<asp:TextBox ID="txtProPrice" runat="server" Height="25px"
<br />
<asp:Label ID="Label5" runat="server" Text="Description"></asp:Label><br />
<asp:TextBox ID="txtDescription" runat="server" Height="25px"
<br />
<asp:Label ID="Label6" runat="server" Text="Product Image"></asp:Label><br />
<asp:FileUpload ID="FileUpload1" runat="server" Height="25px"
Width="250px"/>
<br />
<asp:Label ID="Label7" runat="server" Text="Size"></asp:Label><br />
<asp:TextBox
ID="txtSize"
runat="server"
Height="25px"
<br />
<asp:Label ID="Label8" runat="server" Text="Color"></asp:Label><br />
<asp:TextBox
ID="txtColor"
runat="server"
Height="25px"
<br />
<asp:Label ID="Label9" runat="server" Text="Model"></asp:Label><br />
<asp:TextBox ID="txtModel" runat="server" Height="26px"
<br /><br />
83
onclick="btnAdd_Click" Height="26px" Width="57px" />

</div>--%>
<br /><br /><br /><br />
</div>
<p><b> Developed by Inam ullah& Atta ur rehman .</b></p>
</asp:HyperLink>
</asp:HyperLink>
</asp:HyperLink>
</div>
</form>
</body>
</html>
Add product
<%@
Page
Language="C#"
CodeBehind="Products_Add.aspx.cs"
Inherits="OnlineVehicleShowroom.Admin.Add_Products" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
1.0
<head runat="server">
<title>Add Products</title>
</head>
<body>
<div>
<h1>
Online Vehicle Showroom - ( Products Form )
</h1>
84
Transitional//EN"

</div>
<Items>
<asp:MenuItem NavigateUrl="~/Admin/Products.aspx" Text="Products"/>
</Items>
</asp:Menu>
</div> 
<br /><br /><br />
<center><asp:Label ID="lblSuccessMsg" runat="server" Font-Bold="True"
Font-Size="Larger"></asp:Label>
<br /><br />
</center>
<div id="Add_Products">
<asp:Label ID="Label1" runat="server" Text="Product Name"></asp:Label><br />
<asp:TextBox ID="txtProName" runat="server" Height="25px"
<br />
<asp:Label ID="Label3" runat="server" Text="Company Name"></asp:Label><br
/>
<asp:TextBox
<br />
ID="txtCmpName"
runat="server"
Height="25px"
<asp:Label ID="Label4" runat="server" Text="Product Price"></asp:Label><br />

<asp:TextBox ID="txtProPrice" runat="server" Height="25px"
<br />
<asp:Label ID="Label5" runat="server" Text="Description"></asp:Label><br />
<asp:TextBox ID="txtDescription" runat="server" Height="25px"
<br />
<asp:Label ID="Label6" runat="server" Text="Product Image"></asp:Label><br />
<asp:FileUpload ID="FileUpload1" runat="server" Height="25px"
Width="250px"/>
<br />
<asp:Label ID="Label7" runat="server" Text="Size"></asp:Label><br />
<asp:TextBox
ID="txtSize"
runat="server"
Height="25px"
<br />
<asp:Label ID="Label8" runat="server" Text="Color"></asp:Label><br />
85
<asp:TextBox
<br />
ID="txtColor"
runat="server"
Height="25px"
<asp:Label ID="Label9" runat="server" Text="Model"></asp:Label><br />

<asp:TextBox ID="txtModel" runat="server" Height="26px"
<br /><br />
onclick="btnAdd_Click" Height="26px" Width="57px" />
</div>
<br /><br />

</div>
<p><b> Developed by Inam ullah& Atta er rehman .</b></p>
</asp:HyperLink>
</asp:HyperLink>
</asp:HyperLink>
</div>
</div>
</form>
</body>
</html>
Stock
86

Inherits="OnlineVehicleShowroom.Admin.Stock" %>
CodeBehind="Stock.aspx.cs"
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
1.0
Transitional//EN"
<title>Stock</title>
</head>
<body>
<div>
<h1>
Online Vehicle Showroom - ( Admin Form )
</h1>
</div>
<Items>
</Items>
</asp:Menu>
</div> 
</div>
<br />
<div id="stock_grid_h1">
<h1><b>Stock Details Form</b></h1>
<br />
DataKeyNames="Stock_ID" DataSourceID="SqlDataSource1" Width="316px">
<Columns>
<asp:BoundField DataField="Stock_ID" HeaderText="Stock_ID"
InsertVisible="False" ReadOnly="True" SortExpression="Stock_ID" />
<asp:BoundField DataField="qty" HeaderText="qty" SortExpression="qty" />
</Columns>
</asp:GridView>
87
SelectCommand="SELECT * FROM [Stock]" UpdateCommand="UPDATE [Stock]
Set
[Pro_ID]=@Pro_ID,
[qty]=@qty
Where
[Stock_ID]=@Stock_ID"
from
[Stock]
Where
[Stock_ID]=@Stock_ID"></asp:SqlDataSource>
</div>
<div id="Add_stock">
<asp:Label ID="Label1" runat="server" Text="Product ID"></asp:Label> <br />
<asp:TextBox ID="txtProID" runat="server" Width="184px"></asp:TextBox>
<br /><br />
<asp:Label ID="Label2" runat="server" Text="Quantity"></asp:Label> <br />
<asp:TextBox ID="txtQty" runat="server" Width="184px"></asp:TextBox>
<br /><br />
</div>
<br /><br /><br />
</div>
</asp:HyperLink>
ImageUrl="~/Admin/img/twitter.JPG" NavigateUrl="#">HyperLink <asp:Image
ID="Image18" runat="server" />
</asp:HyperLink>
ImageUrl="~/Admin/img/li.JPG" NavigateUrl="#">HyperLink <asp:Image
ID="Image19" runat="server" />
</asp:HyperLink>
</div>
</form>
</body>
</html>
User registration
88
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="User_Reg.aspx.cs"

Inherits="OnlineVehicleShowroom.Admin.User_Reg" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
1.0
Transitional//EN"
<title>User Registration</title>
</head>
<body>
<div>
<h1>
Online Vehicle Showroom - ( User Registration Form )
</h1>
</div>
<Items>
</Items>
</asp:Menu>
</div> 
</div>
<br /><br /><br />
<div id="User_reg_grid">
AutoGenerateEditButton="True"
DataKeyNames="User_Reg_ID" DataSourceID="SqlDataSource1" Width="97px"
AutoGenerateDeleteButton="True" Height="119px">
<Columns>
<asp:BoundField DataField="User_Reg_ID" HeaderText="User_Reg_ID"
InsertVisible="False" ReadOnly="True" SortExpression="User_Reg_ID" />
<asp:BoundField DataField="User_Gender" HeaderText="User_Gender"
SortExpression="User_Gender" />
<asp:BoundField DataField="Email" HeaderText="Email"
SortExpression="Email" />
<asp:BoundField DataField="Password" HeaderText="Password"
SortExpression="Password" />
89
<asp:BoundField DataField="User_Tel_No" HeaderText="User_Tel_No"

SortExpression="User_Tel_No" />
<asp:BoundField DataField="User_Mob_No" HeaderText="User_Mob_No"
SortExpression="User_Mob_No" />
<asp:BoundField DataField="User_Address" HeaderText="User_Address"
SortExpression="User_Address" />
<%-- <asp:BoundField DataField="User_Country" HeaderText="User_Country"
SortExpression="User_Country" />--%>
</Columns>
</asp:GridView>
SelectCommand="SELECT * FROM [User_Registration]"
UpdateCommand="UPDATE
[User_Registration]
Set
[User_Name]=@User_Name,
[User_CNIC]=@User_CNIC,
[User_Gender]=@User_Gender,
[Email]=@Email,
[Password]=@Password, [User_Tel_No]=@User_Tel_No, [User_Mob_No]=@User_Mob_No,
[User_Address]=@User_Address
Where
[User_Reg_ID]=@User_Reg_ID"
from
[User_Registration]
Where
[User_Reg_ID]=@User_Reg_ID"></asp:SqlDataSource>
</div>
<br /><br /><br />

</div>
</asp:HyperLink>
</asp:HyperLink>
</asp:HyperLink>
</div>
</form>
</body>
</html>
Front end
Admin login
90
<%@
Page
Title=""
Language="C#"
MasterPageFile="~/Site.Master"
CodeBehind="admin_login.aspx.cs"
Inherits="OnlineVehicleShowroom.admin_login" %>
<asp:Content ID="Content1" ContentPlaceHolderID="HeadContent" runat="server">
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="MainContent" runat="server">
<div class="row" style="border: 2px solid white; width: 40%; margin-left: 25%;">
<div class="col-md-8">
<div id="kk" style="margin-left: 40%;"><h3>Admin Login</h3></div>
<form name="sentMessage" id="contactForm" novalidate>

<br>
<div id="dd" style="margin-left: 40%;">
<div class="control-group form-group">
<div class="controls">
<label>Admin Name:</label>
<asp:TextBox ID="txtAdminName" runat="server" width =
"130%"></asp:TextBox>
</div>
</div>
<label>Password:</label>
<asp:TextBox ID="txtPassword" TextMode="Password" runat="server"
width = "130%"></asp:TextBox>
</div>
</div>
<asp:Button ID="btnLogin" class="btn btn-primary" runat="server"
Text="Login"
onclick="btnLogin_Click" />
</div>
</form>
<br />
<div style="margin-left: 20%; color:Red">
<asp:Label ID="lblError" runat="server" Font-Bold="True" Font-Italic="True"
Font-Size="Medium"></asp:Label>
</div>
</div>
</div>
</asp:Content>
91
<%@
Page
Title=""
Language="C#"
CodeBehind="checkout_delivery.aspx.cs"
Inherits="OnlineVehicleShowroom.confirm_order" %>
</asp:Content>

<%-- Container Starts--%>
<div class="container">

<div class="row">
<div class="col-lg-12">
<h1 class="page-header">Checkout Section
<small>Entere Delivery Address</small>
</h1>
<ol class="breadcrumb">
<li><a href="Default.aspx">Home</a>
</li>
<li class="active">Checkout</li>
</ol>
</div>
</div>





<div class="row">
<h2 style="color: blue">Delivery Address</h2>
<small style="color: green">Enter the Address where you want to recieve the
product</small>
<br><br>
<%-- Height="33px" Width="321px"--%>
<%--<div class="control-group form-group">
<label>Product Name:</label> <br />
<asp:DropDownList ID="txtProName" runat="server"
DataSourceID="SqlDataSource1" DataTextField="Pro_Name"
DataValueField="Pro_Name" Height="33px" Width="321px">
</asp:DropDownList>
runat="server"
<asp:RequiredFieldValidator ID="RequiredFieldValidator2"
ControlToValidate="txtProName" ErrorMessage="Please select the

product"></asp:RequiredFieldValidator>
92
[Products]"></asp:SqlDataSource>
SelectCommand="SELECT [Pro_Name] FROM
<p class="help-block"></p>
</div>
</div>--%>
<label>User CNIC:</label> <br />
<asp:TextBox ID="txtUsrCNIC" runat="server" Height="33px"
<p style="color: green;">*Like 1360344556786</p>
runat="server"
ControlToValidate="txtUsrCNIC" ErrorMessage="Please enter your
CNIC No"></asp:RequiredFieldValidator>
</div>
<%--<asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server"
ControlToValidate="YourTextBox" ValidationExpression="\d">
ErrorMessage="Numeric Only Please"
</asp:RegularExpressionValidator>
<asp:RegularExpressionValidator ID="regexpName" runat="server"
ErrorMessage="This expression does not validate."
ControlToValidate="txtName"
ValidationExpression="^[a-zA-Z'.\s]{1,40}$" />--%>
</div>
<label>Delivey Source:</label> <br />
<asp:TextBox ID="txtDelivSource" runat="server" Height="33px"
<p style="color: green;">*Purchaser / Reciever</p>
runat="server"
ControlToValidate="txtDelivSource" ErrorMessage="Please enter the
delivery source"></asp:RequiredFieldValidator>
ErrorMessage="Please enter the valid expression."
ControlToValidate="txtDelivSource"
ValidationExpression="^[a-zA-Z''-'\s]{1,40}$" />
</div>
<p style="color: red;"><b>*Enter the source who will recieve the product
( Purchaser / Reciever )</b></p>
</div>
<label>Delivey Address:</label> <br />
<asp:TextBox ID="txtAddress" runat="server" Width="43%"
Height="64px"
TextMode="multiline" Columns="70"
Rows="3"></asp:TextBox>
<p style="color: green;">*Your complete address as mentioned in NIC
card.</p>
93
<asp:RequiredFieldValidator ID="RequiredFieldValidator4" runat="server"

ControlToValidate="txtAddress" ErrorMessage="Please enter your
address"></asp:RequiredFieldValidator>
</div>
</div>
<asp:Label runat="server" ID="lblError" Font-Bold="True"
ForeColor="Red"></asp:Label>
<label>Date:</label> <br />
<asp:TextBox ID="txtDate" runat="server" type="date" Height="33px"
<p style="color: green;">*Please select the Date.</p>
runat="server"
ControlToValidate="txtAddress" ErrorMessage="Please select

date"></asp:RequiredFieldValidator>
</div>
<p style="color: red;"><b>*The purchased vehicle will be delivered to
you after 3 days.</b></p>
</div>
runat="server"
<asp:Button ID="btnDelivAdrsSubmit" class="btn btn-primary"
Text="Submit" onclick="btnDelivAdrsSubmit_Click" />

</form>
</div>
</div>

<hr />
<%--<a href="Default.aspx" class="btn btn-success" style="margin-left: 82.5%; color:
white;"><b>Succeed</b></--%>
</div>
<%--/Container--%>
</asp:Content>
94
<%@
Page
Title=""
Language="C#"
CodeBehind="checkout_payments.aspx.cs"
Inherits="OnlineVehicleShowroom.payments" %>
</asp:Content>
<div class="row">
<h1 class="page-header">Checkout Section
<small>Entere Payment Details to complete the checkout section
successfully</small>
</h1>
</li>
<li class="active">Checkout</li>
</ol>
</div>
</div>

<%--payments--%>
<div class="row">
<h2 style="color: blue"><b>Payment Details</b></h2>
<small style="color: brown">Enter the payment details to get the product
successfully</small>
<br /><br /><br />
<form name="payment" id="contactForm" novalidate>
<label>User CNIC:</label> <br />
<asp:TextBox ID="txtCNIC" runat="server" Height="33px"
runat="server"
ControlToValidate="txtCNIC" ErrorMessage="Please enter your CNIC
No"></asp:RequiredFieldValidator>
</div>
</div>
<%--<div class="control-group form-group">
<label>Product Name:</label> <br />
<asp:DropDownList ID="txtProID" runat="server" Height="33px"
Width="321px"
DataSourceID="SqlDataSource1" DataTextField="Pro_Name"
DataValueField="Pro_Name">
</asp:DropDownList>
<p style="color: green;">*Please select Product</p>
95

SelectCommand="SELECT [Pro_Name] FROM
[Products]"></asp:SqlDataSource>
</div>
</div>--%>
<label>Bank Name:</label> <br />
<asp:TextBox ID="txtBnkName" runat="server" Height="33px"
<p style="color: green;">*Enter Bank Name</p>
runat="server"
ControlToValidate="txtBnkName" ErrorMessage="Please enter Bank
Name"></asp:RequiredFieldValidator>
ErrorMessage="This expression does not validate."
ControlToValidate="txtBnkName"
ValidationExpression="^[a-zA-Z'.\s]{1,40}$" />
</div>
</div>
<label>Account No:</label> <br />
<asp:TextBox ID="txtAcntNo" runat="server" Height="33px"
<p style="color: green;">*Enter your Account No</p>
runat="server"
ControlToValidate="txtAcntNo" ErrorMessage="Please enter your
Account No"></asp:RequiredFieldValidator>
</div>
</div>
<asp:Label ID="lblError" runat="server" Font-Bold="True"
ForeColor="Red"></asp:Label>
<br />
<label>Date:</label> <br />
<asp:TextBox ID="txtDate" type="Date" runat="server"
Height="33px" Width="321px"></asp:TextBox>
<p style="color: green;">*Please select Date</p>
runat="server"
ControlToValidate="txtDate" ErrorMessage="Please select Date"
></asp:RequiredFieldValidator>
</div>
</div>
96
<div id="success"></div>
<asp:Button ID="btnPaySubmit" class="btn btn-primary" runat="server"
Text="Proceed" onclick="btnPaySubmit_Click" />
</form>
</div>
</div>

</div>
</asp:Content>
Contac us
<%@
Page
Title=""
Language="C#"
CodeBehind="contact.aspx.cs"
Inherits="OnlineVehicleShowroom.contact" %>
</asp:Content>
<div class="row">
<h1 class="page-header">Contact Us
</h1>
</li>
<li class="active">Contact</li>
</ol>
</div>
</div>

<center>
<div class="row">

<div>
<h2><b>Contact Details</b></h2>
<p class="lead">Welcome to the Contact Us page of the Online Vehicle
Showroom.</p>
<%-- <asp:DataList runat="server" ID="one" DataKeyField="Contact_ID"
DataSourceID="SqlDataSource1">
97
<ItemTemplate>
%>' />
Contact_ID:
<asp:Label ID="Contact_IDLabel" runat="server"
Text='<%# Eval("Contact_ID") %>' />
<br />
Name:
<asp:Label ID="NameLabel" runat="server" Text='<%# Eval("Name")
<br />
Email:
<asp:Label ID="EmailLabel" runat="server" Text='<%# Eval("Email") %>' />
<br />
Contact_No:
<asp:Label ID="Contact_NoLabel" runat="server"
Text='<%# Eval("Contact_No") %>' />
<br />
<br />
</ItemTemplate>
</asp:DataList>
SelectCommand="SELECT [Contact_ID], [Name], [Email], [Contact_No] FROM
[Contact]">
</asp:SqlDataSource>
--%>
<p><i class="fa fa-phone"></i>

<abbr title="Phone">P</abbr>: +92331 9081 498</p>
<p><i class="fa fa-envelope-o"></i>
<abbr title="Email">E</abbr>: <a
href="https://www.facebook.com/hamza.javed.338">Hamzajaved960@gmail.com</a>
</p>
<p><i class="fa fa-envelope-o"></i>
<abbr title="Email">E</abbr>: <a
href="https://www.linkedin.com/profile/public-profile-settings?trk=prof-edit-editpublic_profile">Linkedin Profile</a>
</p>
<p><i class="fa fa-clock-o"></i>
<abbr title="Hours">H</abbr>: Monday - Saturday: 9:00 AM to 10:00
PM</p>
<abbr title="Hours">Vecands</abbr>: Sunday- Of</p>
<%--<ul class="list-unstyled list-inline list-social-icons">
<li>
98
<a href="https://www.facebook.com/hamza.javed.338"><i class="fa fafacebook-square fa-2x"></i></a>

</li>
<li>
<a href="#"><i class="fa fa-linkedin-square fa-2x"></i></a>
</li>
<li>
<a href="#"><i class="fa fa-twitter-square fa-2x"></i></a>
</li>
<li>
<a href="#"><i class="fa fa-google-plus-square fa-2x"></i></a>
</li>
</ul>--%>
</div>
</div>

</center>
</asp:Content>
Site. Master
<%@ Page Title="Home Page" Language="C#" MasterPageFile="~/Site.master"
CodeBehind="Default.aspx.cs" Inherits="OnlineVehicleShowroom._Default" %>
<asp:Content
ID="HeaderContent"
runat="server"
ContentPlaceHolderID="HeadContent">
</asp:Content>
<asp:Content ID="BodyContent" runat="server" ContentPlaceHolderID="MainContent">
<%--Slider Place Image--%>

<div style="margin-top: -3%; margin-left: -1.5%;">
ImageUrl="~/images/j5.jpg" Width="1366px" />
</div>


<div class="row">
<h1 class="page-header">
<b>Welcome to Online Vehicle Showroom !</b>
</h1>
</div>
<div class="panel panel-default">
99
<div class="panel-heading">
<h4><i class="fa fa-fw fa-check"></i> Services</h4>
</div>
<div class="panel-body">
<p>Online Vehicle Showroom is most efficient site.Our customers buy
vehicles from us so easily. We provide our best services and delightfull
atmosphere
More</a>
to our customers so that they should feel like a at home</p>

<a href="#" class="btn btn-default" style="color: White;">Learn
</div>
</div>
</div>
<h4> <i class="fa fa-fw fa-gift"></i> Free & Open Source </h4>
</div>
<p>We provide Free and open source friendly environment to our
respected customers.
They can use and watch our Online Vehicle Showroom with no risks.
Thats why Online Vehicle Showrrom is known to be the best client side
website.</p>
More</a>
</div>
</div>
</div>
<%--<asp:Calendar runat="server"></asp:Calendar>--%>
<h4><i class="fa fa-fw fa-compass"></i> Easy to Use</h4>
</div>
<p>Online Vehicle Showroom is such an exciting client side website that
ofers
shop from here
More</a>
so many ofers to avail and use in relax manner. Meanwhile you can either
or get any information by just one click on given options.</p>
</div>
</div>
</div>
</div>


100


<div class="row">
<h2 class="page-header">All Products</h2>
</div>
<div class="col-md-4 col-sm-6">
<a href="product_details.aspx">
<img class="img-responsive img-portfolio img-hover"
src="images/Army%20Bullet%20Proof%20Keap.jpg" alt="" />
</a>
</div>
<a href="product_catagories.aspx">
src="images/Black%20Heavy%20Bike.jpeg" alt="" />
</a>
</div>
src="images/Black%20BMW.JPG" alt="" />
</a>
</div>
src="images/Niazi%20Express.jpg" alt="" />
</a>
</div>
src="images/Grayish%20BMW.jpg" alt="" />
</a>
</div>
src="images/Star%20Coch.jpg" alt="" />
</a>
</div>
</div>
<hr /><hr />

</div>

</asp:Content>
Faqs
<%@
Page
Title=""
Language="C#"
CodeBehind="faq.aspx.cs"
Inherits="OnlineVehicleShowroom.faq" %>
</asp:Content>
101

<div class="row">
<h1 class="page-header">FAQs
<small>You can read this for help, if you found any problem here.</small>
</h1>
</li>
<li class="active">FAQs</li>
</ol>
</div>
</div>

<div class="row">
<div class="panel-group" id="accordion">

SelectCommand="SELECT [Faq_Question], [Faq_Answer] FROM
[Faqs]"></asp:SqlDataSource>
<asp:DataList
<ItemTemplate>
<ul>
ID="DataList"
runat="server"
<li> <asp:Label runat="server" Font-Bold="True"><

%#Eval("Faq_Question") %></asp:Label> </li>
<asp:Label runat="server" Font-Italic="True"><
%#Eval("Faq_Answer")%></asp:Label>
<br /> <br />
</ul>
</ItemTemplate>
</asp:DataList>
</div>

</div>

</div>

</div>

</asp:Content>
102
<%@
Page
Title=""
Language="C#"
CodeBehind="product_catagories.aspx.cs"
Inherits="OnlineVehicleShowroom.product_catagories" %>
</asp:Content>
<br />

<%--<div id="Cat_Heading" style="margin-left: 10%;">
<h1>Catagories</h1>
</div>--%>
<%--Catagories section--%>
<%--<div>
SelectCommand="SELECT * FROM [Catagory]">
<div id="all_cats" style="margin-left: 10%;">
<section>
<div>
<asp:ListView ID="ListView1" runat="server" DataKeyNames="Cat_ID"

GroupItemCount="4" DataSourceID="SqlDataSource3">
<EmptyDataTemplate>
<table >
<tr>
<td>No data was returned.</td>
</tr>
</table>
</EmptyDataTemplate>
<EmptyItemTemplate>
<td/>
</EmptyItemTemplate>
<GroupTemplate>
<tr id="itemPlaceholderContainer" runat="server">
<td id="itemPlaceholder" runat="server"></td>
</tr>
</GroupTemplate>
<ItemTemplate>
<td id="Td1" runat="server">
<table>
<tr>
103
border="1" />
<td>
<a href="/products.aspx?Cat_ID=<%#Eval("Cat_ID") %>">
<image src="images/cat.gif" width="130" height="85"
</a>
</td>
</tr>
<tr>
<td>
<br />
<b> <%#Eval("Cat_Name")%> </b>
<br />
</td>
</tr>
<tr>
<td> </td>
</tr>
</table>
</p>
</td>
</ItemTemplate>
<LayoutTemplate>
<table style="width:100%;">
<tbody>
<tr>
<td>
<table id="groupPlaceholderContainer" runat="server"
style="width:100%">
<tr id="groupPlaceholder"></tr>
</table>
</td>
</tr>
<tr>
<td></td>
</tr>
<tr></tr>
</tbody>
</table>
</LayoutTemplate>
</asp:ListView>
</div>
</section>
</div>
</div>--%>
<br />

<div id="Pro_Heading" style="margin-left: 10%;">
<h1>Products</h1>
<small>Please select your favourite vehicle and shop it now.</small>
</div>
<br />
104
<br />
<div id="All_products" style="margin-left: 10%;">
<section>
<div>
<asp:ListView ID="productList" runat="server" DataKeyNames="Pro_ID"
GroupItemCount="4" DataSourceID="SqlDataSource2"
onselectedindexchanged="productList_SelectedIndexChanged">
<EmptyDataTemplate>
<table >
<tr>
<td>No data was returned.</td>
</tr>
</table>
<EmptyItemTemplate>
<td/>
</EmptyItemTemplate>
<GroupTemplate>
<tr id="itemPlaceholderContainer" runat="server">
<td id="itemPlaceholder" runat="server"></td>
</tr>
</GroupTemplate>
<ItemTemplate>
<td id="Td1" runat="server">
<table>
<tr>
<td>
<asp:ImageButton ID="ImageButton2" runat="server" ImageUrl='<
%# Eval("FilePath") %>'
PostBackUrl='<%# Eval("Pro_ID", "product_details.aspx?Pro_ID={0}")
%>' width="210" height="155"
border="1" BorderStyle="Inset" /><br />
</td>
</tr>
<tr>
<td>
<b>Name: </b> <%#Eval("Pro_Name")%>
<br />
<b>Price: </b> <%#Eval("Pro_Price")%>
</span>
<br />
<a href="/product_details.aspx?Pro_ID=<%#Eval("Pro_ID") %>">
<span class="ProductListItem">
<b>View Details<b>
</span>
</a>
</td>
</tr>
<tr>
<td> </td>
</tr>
</table>
</p>
</td>
</ItemTemplate>
105
<LayoutTemplate>
<table style="width:100%;">
<tbody>
<tr>
<td>
<table id="groupPlaceholderContainer" runat="server"
style="width:100%">
<tr id="groupPlaceholder"></tr>
</table>
</td>
</tr>
<tr>
<td></td>
</tr>
<tr></tr>
</tbody>
</table>
</LayoutTemplate>
</asp:ListView>

SelectCommand="SELECT * FROM [Products]"></asp:SqlDataSource>
</div>
</section>
</div>

<br />
</asp:Content>
Product Details
<%@
Page
Title=""
Language="C#"
CodeBehind="product_details.aspx.cs"
Inherits="OnlineVehicleShowroom.product_details" %>
</asp:Content>
<div class="row">
<h1 class="page-header">Product Details
</h1>
106
</li>
<li class="active"><a href="product_catagories.aspx">Back</a></li>
</ol>
</div>
</div>

<%--Orignal Code by help from Wingtip Toys for getting Product Details--%>
<%--<div>
<asp:FormView ID="productDetail" runat="server" RenderOuterTable="False"
<ItemTemplate>
<div>
<h2><%#Eval("Pro_Name") %></h2>
</div>
<br />
<table>
<tr>
<td>
<img src='<%# Eval("FilePath") %>' style="border:solid; height:300px"
alt="<<%#Eval("Pro_Name") %>"/>
</td>
<td> </td>
<td style="vertical-align: top; text-align:left;">
<b>Description:</b><br /><%#Eval("Description")%><br
/><span><b>Price:</b> <%#
Eval("Pro_Price",
"{0:##0.00}"
)
%></span><br />
<span><b>Product Number:</b> <%#Eval("Pro_ID")
%></span><br /></td>
</tr>
</table>
</ItemTemplate>
</asp:FormView>
<div>
%>"

ConnectionStrings:OnlineVehicleShowroomDBConnectionString
SelectCommand="SELECT [Pro_ID], [Pro_Name], [Description], [Pro_Price],

[FilePath], [Size], [Color], [Model] FROM [Products] WHERE ([Pro_ID] = @Pro_ID)">
<SelectParameters>
<asp:QueryStringParameter Name = "Pro_ID" QueryStringField =
"Pro_ID" Type="Decimal" />
</SelectParameters>
</div>
</div>--%>
<%--Orignal Code by help from ShoppingCart Example for getting Product Details--%>
<div>
<div>
107
<asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="<%$

SelectCommand="SELECT [Pro_ID], [Pro_Name], [Cmp_Name], [Pro_Price],
[Description], [Size], [Color], [Model], [FileName], [FilePath] FROM [Products] WHERE
([Pro_ID] = @Pro_ID)">
<SelectParameters>
<asp:QueryStringParameter Name = "Pro_ID" QueryStringField = "Pro_ID"
Type="Decimal" />
</SelectParameters>
</div>
<%--<div>
<asp:SqlDataSource ID="SqlDataSource2" runat="server" ConnectionString="<%$
SelectCommand="SELECT [Pro_ID], [Pro_Name], [Cmp_ID] [Description],
[Pro_Price], [FilePath], [Size], [Color], [Model] FROM [Products] WHERE ([Pro_ID] =
@Pro_ID)">
<SelectParameters>
<asp:QueryStringParameter Name = "Pro_ID" QueryStringField = "Pro_ID"
Type="Decimal" />
</SelectParameters>
</div>--%>
<asp:Repeater ID="repAccordian" runat="server" ClientIDMode="Static"
DataSourceID="SqlDataSource1" OnItemCommand="repAccordian_ItemCommand">
<ItemTemplate>
<div>
<h2><%#Eval("Pro_Name") %></h2>
</div>
<asp:Image ID="Image1" runat="server" ImageUrl='<%# Eval("FilePath") %>'
/><br />
<asp:Label ID="ImageUrlLabel" runat="server" Text='<%# Eval("FilePath")
%>' Visible="False"></asp:Label><br />
<b>Product ID:</b>
<asp:Label ID="lblProID" runat="server" Text='<%# Eval("Pro_ID") %>'>
</asp:Label><br />
<b>Name:</b>
<asp:Label ID="lblProName" runat="server" Text='<%# Eval("Pro_Name")
%>'> </asp:Label><br />
<b>Company Name:</b> <br />
<asp:Label ID="lblCmpName" runat="server" Text='<%# Eval("Cmp_Name")
%>'> </asp:Label><br />
<b>Price:</b>
<asp:Label ID="lblProPrice" runat="server" Text='<%# Eval("Pro_Price",
"{0:##0.00}" ) %>'></asp:Label><br />
<b>Size:</b>
108
<asp:Label ID="SizeLabel" runat="server" Text='<%# Eval("Size")

%>'></asp:Label><br />
<b>Model:</b>
<asp:Label ID="ModelLabel" runat="server" Text='<%# Eval("Model")
<b>Color:</b>
<asp:Label ID="ColorLabel" runat="server" Text='<%# Eval("Color")
<b>Description:</b>
<asp:Label ID="DescriptionLabel" runat="server" Text='<%#
Eval("Description") %>'></asp:Label><br />
<br />
<asp:Button ID="Button2" Text="Add To Cart" runat="server"
BackColor="Brown" CommandName="AddCart"
Font-Bold="True" ForeColor="White" Height="38px"
Width="102px"/>
<br />
<br />
</ItemTemplate>
</asp:Repeater>
<br />
</div>
OnClick="cart"/>
<%--<asp:Button ID="Button1" runat="server" Text="Add To Cart"
<a href="/shopping_cart.aspx?Pro_ID=<%#Eval("Pro_ID") %>" OnClick="cart">

<b>Add To Cart</b>
</a>--%>
<br />
<br />
<br />
</div>
<%--<script>
function cart() {
document.cookie = "aaa";
109
}
</script>--%>
</div> 

</asp:Content>
Registration
<%@
Page
Title=""
Language="C#"
CodeBehind="registration.aspx.cs"
Inherits="OnlineVehicleShowroom.registration" %>
</asp:Content>
<div class="row">
<h1 class="page-header">Registration
<small>User Registration</small>
</h1>
</li>
<li class="active">Registration</li>
</ol>
</div>
</div>




<div class="row">
<label>Full Name:</label> <br />
<asp:TextBox ID="txtName" runat="server" style="width:
50%;"></asp:TextBox>
<p style="color: green;">*Enter your Full Name</p>
ErrorMessage="<b>Error ! Invalid format</b>"
ControlToValidate="txtName"
110
ControlToValidate="txtName" ErrorMessage="Please enter the Full
Name"></asp:RequiredFieldValidator>
</div>
</div>
<label>CNIC:</label> <br />
<asp:TextBox ID="txtCNIC" runat="server" style="width:
runat="server"
ControlToValidate="txtCNIC" ErrorMessage="Please enter the CNIC
No"></asp:RequiredFieldValidator>
</div>
</div>
<label>Gender:</label> <br />
<asp:TextBox ID="txtGender" runat="server" style="width:
<p style="color: green;">*Male / Female</p>
runat="server"
ControlToValidate="txtGender" ErrorMessage="Please enter
Gender"></asp:RequiredFieldValidator>
<asp:RegularExpressionValidator ID="RegularExpressionValidator1"
runat="server" ErrorMessage="<b>Error ! Invalid format</b>"
ControlToValidate="txtGender"
</div>
</div>
<label>Email:</label> <br />
<asp:TextBox ID="txtEmail" runat="server" type="email" style="width:
<p style="color: green;">*Like abc@abc.com</p>
runat="server"
ControlToValidate="txtEmail" ErrorMessage="Please enter
Email"></asp:RequiredFieldValidator>
</div>
</div>
<label>Password:</label> <br />
<asp:TextBox ID="txtPassword" type="password" runat="server"
style="width: 50%;"></asp:TextBox>
<p style="color: green;">*Your secret password with numbers, chars,
uper & lower case.</p>
111
runat="server"
ControlToValidate="txtPassword" ErrorMessage="Please enter

Password"></asp:RequiredFieldValidator>
</div>
</div>
<label>Phone Number:</label> <br />
<asp:TextBox ID="txtPhNo" runat="server" style="width:
</div>
</div>
<label>Mobile Number:</label> <br />
<asp:TextBox ID="txtMobNo" runat="server"
style="width:

ControlToValidate="txtMobNo" ErrorMessage="Please enter the
Mobile Number"></asp:RequiredFieldValidator>
</div>
</div>
<label>Address:</label> <br />
<asp:TextBox ID="txtAddress" runat="server" style="width: 50%;"
></asp:TextBox>
<p style="color: green;">*Your complete address as mentioned in NIC
card.</p>
ControlToValidate="txtAddress" ErrorMessage="Please enter the
Address"></asp:RequiredFieldValidator>
</div>
</div>
<%-- background-color: #47A447; --%>
<asp:Button ID="btnRegister" runat="server" Text="Sign Up"
onclick="btnRegister_Click" BackColor="Brown" ForeColor="White"
Height="38px"
Width="90px"/>
</form>
<br /><br /><br />
</div>
</div>

</asp:Content>
112
<%@
Page
Title=""
Language="C#"
CodeBehind="shopping_cart.aspx.cs"
Inherits="OnlineVehicleShowroom.shopping_cart" %>
</asp:Content>

<div class="row">
<h1 class="page-header">Shopping Cart
</h1>
</li>
<li class="active">Shopping Cart</li>
</ol>
</div>
</div>

<br /><br /><br />
<asp:Label ID="Lblss" runat="server" Text=""></asp:Label>
<br />
<asp:Button ID="Button1" runat="server" Text="get session data"
onclick="Button1_Click" />
<br /><br /><br /><br /><br />
<asp:GridView ID="GridView1" runat="server" Width="664px" style="left: 24px;
position: relative; top: 16px"
Height="16px" CellPadding="4" BackColor="White" BorderColor="White"
BorderStyle="None"
BorderWidth="1px" PageSize="15"
AutoGenerateColumns="False"
DataSourceID="SqlDataSource1"
onselectedindexchanged="GridView1_SelectedIndexChanged">
<FooterStyle BackColor="#99CCCC" ForeColor="#003399" />
<RowStyle BackColor="White" ForeColor="#003399" />
<SelectedRowStyle BackColor="#E0E0E0" Font-Bold="True"
ForeColor="#CCFF99" BorderColor="White" />
<PagerStyle BackColor="#99CCCC" ForeColor="#003399" HorizontalAlign="Left"
/>
<HeaderStyle BackColor="#003399" Font-Bold="True" ForeColor="#CCCCFF" />
<Columns>
<asp:BoundField DataField="Pro_ID" HeaderText="Product ID"
113
<asp:BoundField DataField="Pro_Name" HeaderText="Product Name"
<asp:BoundField DataField="Pro_Price" HeaderText="Product Price"
</Columns>
<EmptyDataTemplate>
<asp:Label ID="Label1" runat="server" Text="Label"><b>Your Cart is empty !
Please go back to shop now.</b></asp:Label>
</asp:GridView>
<%--UpdateCommand="UPDATE
[Faqs]
Set
[Faq_Question]=@Faq_Question,
[Faq_Answer]=@Faq_Answer Where [Faq_ID]=@Faq_ID" DeleteCommand="DELETE from
[Faqs] Where [Faq_ID]=@Faq_ID"
--%>
SelectCommand="SELECT [Pro_ID], [Pro_Name], [Pro_Price] FROM [tempTable]">
<br /><br /><br /><br /><br /><br />
<asp:Button ID="btnOrder" runat="server" Text="Order Now"

onclick="btnOrder_Click" Font-Bold="True" />
</div>
</asp:Content>
<label>Feedback Title:</label> <br />
<asp:TextBox ID="txtFbTitle" runat="server" Width="50%"
Height="28px" ></asp:TextBox>
</div>
</div>
<label>Description:</label> <br />
<asp:TextBox ID="txtDescription" runat="server" Width="50%"
Height="64px"
TextMode="multiline" Columns="70"
114
Rows="3"></asp:TextBox>
</div>
</div>
<div id="success"></div>
<asp:Button ID="btnSubmit" runat="server" Text="Submit"
onclick="btnSubmit_Click" BackColor="#999999" Font-Bold="True"
Height="29px" Width="70px" />
</form>
<br /><br />
</div>
</div>

</asp:Content>
REFERENCES
115
References
Ariffin A.M. and Norshuhada, S. (2008). Usable but not entertaining eLearning
materials. In Proceedings of World Conference on e-Learning in Corporate,
Government, Healthcare, and Higher Education (e-Learn), USA. AACE.
www.softdevteam.com/ Incremental- lifecycle.asp.
Practitioner's Approach. Boston: McGraw Hill. pp. 41 42. ISBN 9780073375977.

What is waterfall model - advantages, disadvantages and when to use it.
Modelviewcontroller Wikipedia, the free encyclopedia.
http://www.w3schools.com/jsref/default.asp, Date accessed: 5 Sep 2011
Skinner, Jon. "Sublime Text". Sublime HQ Pty Ltd. Retrieved 19 August 2011.
Skinner, Jon. "Sublime Blog". Sublime Blog. Sublime HQ Pty Ltd. Retrieved 19
August 2011.
116

Online Vehicle Showroom Thesis

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Online Vehicle Showroom Thesis

Uploaded by

Copyright:

Available Formats

ONLINE VEHICLE SHOWROOM

HAZARA UNIVERSITY, MANSEHRA

Inam Ullah (31048)

Online Vehicle Showroom.

Hazara University Mansehra.

To Develop User Friendly Website.

Inam Ullah and Atta-Ur-Rahman.

Mr. Aamir Javed.

C#, ASP.Net, SQL Server (2008).

Core 2 duo, 4 GB RAM

2.1.13 Analysis problem..................................................................................................8

3.5.1.5 Integration and System Testing......................................................................16

5.2.1 Bottom up approach..............................................................................................24

6.3.4 White box testing..................................................................................................43

Figure 5.20: Entity Relationship Diagram.41

Database Management System.

Structured Query language.

Data Flow Diagram.

Graphical User Interface.

Entity Relationship Diagram.

Software Development Life Cycle.

Software Quality Assurance.

Data Design System.

Logical Database Design.

Physical Data Design.

1.3 Purpose of Project (Software)

allows storing of vehicle information, stock available at different locations, product

Registration forms for customers in able to take order.

Administrator has full permission to access this software features.

1.5 Advantages of the Project

Less resource required.

Less chance of error occurring.

Supportive for user.

1.6 Disadvantage of the Manual System

1.7 Feasibility of project

1.8 Gantt Chart for Project Development

16 Feb-28 Feb 1 Mar-15 Mar

Figure 1.1: Gantt chart

1.9 Outputs from the Project

2.1 Drawback of manual system

Figure 2.1: Data Duplication

Figure 2.2: Lack of Security

Figure 2.3: Fire

Figure 2.4: Repetition of Work

Figure 2.5: Too much paper work

Figure 2.6: Loss and Profit

2.1.11 Data Entry

3.1 Proposed system

3.2 Objective of the proposed system

3.2.4 Fast retrieval

3.3 Techniques for Analysis of Online vehicle showroom (SDLC)

Software Development Life Cycle (SDLC)

Request, Collection and

SDLC (SOFTWARE DEVELOPMENT LIFE CYCLE

3.4 Preliminary Investigation

The buying and selling is available 24 hours.

Having different model i.e. old or new.

Having different categories i.e. Small, medium and large.

Having product as well as purchasers and order details.

The purchaser things (vehicles) will be deliver according to the customer

The process will be continued in this manner.

Q2: What type of vehicle you sell?

Q3: Now a days which company vehicle customers demands?