“VEHICLE SHOWROOM”

1

A Project Report :on

“VEHICLE SHOWROOM”

Submitted to the Bangalore University in partial fulfillment of

the requirement for the award of the degree in

Bachelor of Computer Applications

Submitted by

RAJENDRA BABU USN: 14VFSB7043

SWAROOP DR USN:14VFSB7056

Under the guidance of

Mr. Rajseh H

Ring Road, Marathalli, Bangalore – 560 103.

2

DECLARATION

I hereby declare that the project reported titled “Vehicle Showroom” was prepared by

me during the year 2016-2017and was submitted to the Bangalore University, in partial

fulfillment of the requirements for the award of the Degree in Bachelor of Computer

Applications. I also declare that this project report is original and genuine and it has not

been submitted to any other University for the award of any degree, diploma or other

similar titles or purposes.

Date: 27-04-2017 Signature of the Candidate

Place: Bangalore RAJENDRA BABU

[USN: 14VFSB7043]

SWAROOP DR

USN:14VFSB7056

3

CERTIFICATE

This is to certify that the project reported titled ―VEHICLE SHOWROOM”

Submitted by RAJENDRA BABU [14VFSB7043]. This report is an outcome of

genuine project work and has been submitted in partial fulfillment for the award of

the Degree of Bachelor of Computer Applications, awarded by Bangalore University,

during the academic year 2016-17.

Project Guide Head of the Department

Mr. Rajesh H Mr Nagaraju K

Signature of the Examiners

1. ________________

2. ________________

4

ACKNOWLEDGEMENT

We express our deep sincere thanks to Dr.Mohan Maghnani, Chairman of New Horizon

Educational Institutions for providing the platform and infrastructure to do this project. This

project would not have been possible without the help and co-operation of many. At the outset I

wish to record my profound gratitude to our principal Dr. R. Bodhisatvan

We are extremely thankful to Mr Nagaraju K, Head of the Department, BCA for his unending

support and encouragement during the development of this project.

We would like to acknowledge the interest and the support extended by our project guide Mr.

Rajesh H, Asst. Professor, Department of BCA, to make this project implementation successful.

Above all we would thank God for the blessings and my parents also for their valuable

suggestion and support in my project report

Finally, we extend my deep sense of gratitude to all those who made this project come alive and

encouraged and guided me from the start to finish.

5

ABSTRACT

TITLE : VEHICLE SHOWROOM

The project ―vehicle showroom‖ in which the user can select car of their choice and buy it. The

user will get all specifications about the car with its description and price. To buy the vehicle the

user should register to website otherwise the user can see only about cars and its description.

The project is GUI based project where user can be access easily. After booking the vehicle, it

shows the users details, vehicle details with price and tax and showroom details. When user

login to this website, the users can view car price ,car details , car dealers. The vehicle

showroom responses to the users request and clears their doubts.

6

INDEX

Chapters Page No

CHAPTER 1: INTRODUCTION TO THE PROJECT

1.1.Problem Statement 2

1.1.1. Module Description 3

CHAPTER 2: SYSTEM ANALYSIS

2.1. Requirements Specification 5

2.1.1. Hardware requirements 5

2.1.2. Software requirements 5

2.1.2.1. Introduction to HTML 7

2.1.2.2. Introduction to CSS 13

2.1.2.3. Introduction to PHP 19

2.1.2.4 Introduction to the SQL 23

2.2. Existing System 26

2.3. Proposed System 27

CHAPTER 3: SYSTEM DESIGN

3.1. Table Structure 29

3.2. Data Flow Diagram /Entity Relationship Diagram 32

CHAPTER 4: CODING AND DEVELOPMENT.

4.1. Source Code 38

CHAPTER 5: TESTING AND IMPLEMENTATION.

5.1 Introduction to Testing 83

5.2 Types of testing used in Project 84

CHAPTER 6: CONCLUSION

7

6.1 Future enhancement 89

Appendices

Form Designs/Screenshots 91

Bibliography 98

INTRODUCTION TO PROJECT

8

1. INTRODUCTION TO VEHICLE SHOWROOM:

The project ―vehicle showroom‖ in which the user can select car of their choice and buy it. The

user will get all specifications about the car with its description and price. To buy the vehicle the

user should register to website otherwise the user can see only about cars and its description.

The project is GUI based project where user can be access easily. After booking the vehicle, it

shows the users details, vehicle details with price and tax and showroom details. When user

login to this website, the users can view car price ,car details , car dealers. The vehicle

showroom responses to the users request and clears their doubts.

1.1.Problem statement :

There are a lot of repetitions which can be easily avoided. And hence there is a lot of strain on

the person who are running the hostel and software’s are not usually used in this context. This

particular project deals with the problems on managing a hostel and avoids the problems which

occur when carried manually.

Identification of the drawbacks of the existing system leads to the designing of computerized

System that will be compatible to the existing system with the system which is more user

friendly and more GUI oriented. We can improve the efficiency of the system, thus overcome the

drawbacks of the existing system.

Objective of project :

The main objective ―Prague Stay (hostel)‖ is software developed for managing various activities

in the hostel. For the past few years the numbers of educational institutions are increasing

rapidly. Thereby the numbers of hostels are also increasing for the accommodation of the

9

students studying in this institution. And hence there is a lot of strain on the person who are

running the hostel and software’s are not usually used in this context. This particular project

deals with the problems on managing a hostel and avoids the problems which occur when carried

manually.

2.1.1. MODULE DESCRIPTION:

In our project ―Vehicle Showroom‖ have five modules:

1. Registration and Login module:

In this module the users can register and login into the Prague stay.

2. Vehicle module:

This module is used to view vehicles and its details

3. Order module:

In this module users can view the ordered vehicles list.

4. Dealer module:

This module is used to view the different company cars which is present in

our website.

5. Contact us module:

This module is used to give the feedback or to enquire about vehicles.

10

SYSTEM ANALYSIS

11

2.1. Requirement specifications:

A System Requirements Specification (abbreviated SRS when need to be distinct from

a Software Requirements Specification SRS) is a structured collection of information that

embodies the requirements of a system.

2.1.1.HARDWAREREQUIREMENTS

Processor : X86 Compatible processor with 1.7 GHz Clock speed

RAM : 1GB or more

Hard disk : 20 GB or more

Monitor : VGA/SVGA

Keyboard : 104 Keys

Mouse : 2 buttons/ 3 buttons

2.1.2. SOFTWAREREQUIREMENTS

Front End : HTML,CSS.

Back End : PHP , MySQL

Web server : Xampp

Operating System : Windows XP or Higher

Tool for IDE : Sublime 3

https://en.wikipedia.org/wiki/Software_Requirements_Specification

12

A software requirements specification (SRS) is a description of software to be developed. It lays

out functional and non-functional requirements, and may include a set of use cases that describe

User interaction that the software must provide.[2]

Software requirements specification establishes the basis for an agreement between customers

and contractors or suppliers (in market-driven projects, these roles may be played by the

marketing and development divisions) on what the software product is to do as well as what it is

not expected to do. Software requirements specification permits a rigorous assessment of

requirements before design can begin and reduces later redesign. It should also provide a realistic

basis for estimating product costs, risks, and schedules. Software requirements specification

prevents software projects from failure.[2]

The software requirements specification document enlists enough and necessary requirements

that are required for the project development. To derive the requirements we need to have clear

and thorough understanding of the products to be developed or being developed. This is achieved

and refined with detailed and continuous communications with the project team and customer till

the completion of the software.[2]

PURPOSE OF SRS

There are three major parts in a new system:-

Client

User

Developer

The requirements of the system that will satisfy the needs of the clients and the concerns of the

users have to communicate to the developer. The problem is that, the developer usually doesn’t

13

understand the client’s problem and applications area. This causes a communication gap between

the parties involved in the development project.

The basic purpose of software requirement specification is to bridge this communication gap.

SRS is a medium through which the client and user needs are accurately specified; Indeed, SRS

forms the basis of software development. A good SRS should specify something very hard to

achieve and involving trade-offs and persuasion.

The introduction of software System offers strong and effective features such as providing new

services, performing activation in a different manner to collecting data which were either

impossible or unfeasible without a software system.

2.1.2.1. INTRODUCTION TO HTML

Hypertext Mark-up Language (HTML) is the standard mark-up language for creating

webpagesand web applications With Cascading Style Sheets(CSS) and JavaScript it forms a triad

of cornerstone technologies for the World Wide Web.Web browsers receive HTML documents

from a webserveror from local storage and render them into multimedia web pages. HTML

describes the structure of a web page semantically and originally included cues for the

appearance of the document.[4]

HTML elements are the building blocks of HTML pages. With HTML constructs, imagesand

other objects, such as interactive forms, may be embedded into the rendered page. It provides a

means to create structured documentsby denoting structural semantics for text such as headings,

paragraphs, lists, links, quotes and other items. HTML elements are delineated by tags, written

using angle brackets. Tags such as <img /> and <input /> introduce content into the page

directly. Others such as <p>...</p> surround and provide information about document text and

may include other tags as sub-elements. Browsers do not display the HTML tags, but use them to

interpret the content of the page. [4]

HTML can embed programs written in a scripting language such as JavaScript which affect the

behaviour and content of web pages. Inclusion of CSS defines the look and layout of content.

14

The World Wide Web Consortium (W3C), maintainer of both the HTML and the CSS standards,

has encouraged the use of CSS over explicit presentational HTML since 1997. [4]

History

In 1980, physicist Tim Berners-Lee, a contractor at CERN, proposed and prototyped ENQUIRE,

a system for CERN researchers to use and share documents. In 1989, Berners-Lee wrote a memo

proposing an Internet-based hypertextsystem. Berners-Lee specified HTML and wrote the

browser and server software in late 1990. That year, Berners-Lee and CERN data systems

engineer Robert Cailliau collaborated on a joint request for funding, but the project was not

formally adopted by CERN. In his personal notes from 1990 he listed "some of the many areas in

which hypertext is used" and put an encyclopaedia first. [4]

The first publicly available description of HTML was a document called "HTML Tags", first

mentioned on the Internet by Tim Berners-Lee in late 1991. It describes 18 elements comprising

the initial, relatively simple design of HTML. Except for the hyperlink tag, these were strongly

influenced by SGMLguide,an in-house Standard Generalized Mark-up Language(SGML)-based

documentation format at CERN. Eleven of these elements still exist in HTML 4. [4]

HTML is a mark-up language that web browsers use to interpret and compose text, images, and

other material into visual or audible web pages. Default characteristics for every item of HTML

mark-up are defined in the browser, and these characteristics can be altered or enhanced by the

web page designer's additional use of CSS. Many of the text elements are found in the 1988 ISO

technical report TR 9537 Techniques for using SGML, which in turn covers the features of early

text formatting languages such as that used by the RUNOFF commanddeveloped in the early

1960s for the CTSS (Compatible Time-Sharing System) operating system: these formatting

commands were derived from the commands used by typesetters to manually format documents.

However, the SGML concept of generalized mark-up is based on elements (nested annotated

ranges with attributes) rather than merely print effects, with also the separation of structure and

mark-up; HTML has been progressively moved in this direction with CSS. [5]

15

Berners-Lee considered HTML to be an application of SGML. It was formally defined as such

by the Internet Engineering Task Force (IETF) with the mid-1993 publication of the first

proposal for an HTML specification, the "Hypertext Mark-up Language (HTML)" Internet Draft

by Berners-Lee and Dan Connolly, which included an SGML Document Type Definition to

define the grammar. The draft expired after six months, but was notable for its acknowledgment

of the NCSA Mosaic browser's custom tag for embedding in-line images, reflecting the IETF's

philosophy of basing standards on successful prototypes.Similarly, Dave Raggett's competing

Internet-Draft, "HTML+ (Hypertext Mark-up Format)", from late 1993, suggested standardizing

already-implemented features like tables and fill-out forms.

After the HTML and HTML+ drafts expired in early 1994, the IETF created an HTML Working

Group, which in 1995 completed "HTML 2.0", the first HTML specification intended to be

treated as a standard against which future implementations should be based.

Further development under the auspices of the IETF was stalled by competing interests. Since

1996, the HTML specifications have been maintained, with input from commercial software

vendors, by the World Wide Web Consortium (W3C).However, in 2000, HTML also became an

international standard (ISO/IEC 15445:2000). HTML 4.01 was published in late 1999, with

further errata published through 2001. In 2004, development began on HTML5 in the Web

Hypertext Application Technology Working Group (WHATWG), which became a joint

deliverable with the W3C in 2008, and completed and standardized on 28 October 2014.[5]

HTML versions timeline

November 24, 1995

HTML 2.0 was published as IETF RFC 1866. Supplemental RFCs added capabilities:

November 25, 1995: RFC 1867 (form-based file upload)

May 1996: RFC 1942(tables)

August 1996: RFC 1980 (client-side image maps)

January 1997: RFC 2070 (internationalization)[4]

January 14, 1997

16

HTML 3.2was published as a W3C Recommendation. It was the first version developed and

standardized exclusively by the W3C, as the IETF had closed its HTML Working Group on

September 12, 1996. [4]

Initially code-named "Wilbur", HTML 3.2 dropped math formulas entirely, reconciled

overlap among various proprietary extensions and adopted most of Netscape's visual mark-up

tags. Netscape's blink element and Microsoft's marquee elementwere omitted due to a mutual

agreement between the two companies. A mark-up for mathematical formulas similar to that

in HTML was not standardized until 14 months later in MathML.

December 18, 1997

HTML 4.0was published as a W3C Recommendation. It offers three variations:

Strict, in which deprecated elements are forbidden

Transitional, in which deprecated elements are allowed

Frameset, in which mostly only frame related elements are allowed.

Initially code-named "Cougar", HTML 4.0 adopted many browser-specific element types and

attributes, but at the same time sought to phase out Netscape's visual mark-up features by

marking them as deprecated in favour of style sheets. HTML 4 is an SGML application

conforming to ISO 8879 – SGML. [4]

April 24, 1998

HTML 4.0was reissued with minor edits without incrementing the version number.

December 24, 1999

HTML 4.01 was published as a W3C Recommendation. It offers the same three variations as

HTML 4.0 and its last errata were published on May 12, 2001.[4]

May 2000

ISO/IEC 15445:2000 ("ISO HTML", based on HTML 4.01 Strict) was published as an

ISO/IEC international standard. In the ISO this standard falls in the domain of the ISO/IEC

JTC1/SC34 (ISO/IEC Joint Technical Committee 1, Subcommittee 34 – Document

description and processing languages).[4]

17

After HTML 4.01, there was no new version of HTML for many years as development of the

parallel, XML-based language XHTML occupied the W3C's HTML Working Group through

the early and mid-2000s. [4]

October 28, 2014

HTML5 was published as a W3C Recommendation.

November 1, 2016

HTML 5.1was published as a W3C Recommendation.

HTML draft version timeline

October 1991

HTML Tags, an informal CERN document listing 18 HTML tags, was first mentioned in

public.

June 1992

First informal draft of the HTML DTD, with seven subsequent revisions (July 15, August 6,

August 18, November 17, November 19, November 20, November 22) [4]

November 1992

HTML DTD 1.1 (the first with a version number, based on RCS revisions, which start with

1.1 rather than 1.0), an informal draft

June 1993

Hypertext Mark-up Language was published by the IETF IIIR Working Group as an Internet

Draft (a rough proposal for a standard). It was replaced by a second version one month later,

followed by six further drafts published by IETF itselfthat finally led to HTML 2.0 in RFC

1866. [4]

November 1993

HTML+ was published by the IETF as an Internet Draft and was a competing proposal to the

Hypertext Mark-up Language draft. It expired in May 1994.

April 1995 (authored March 1995)

18

HTML 3.0 was proposed as a standard to the IETF, but the proposal expired five months

later (28 September 1995) without further action. It included many of the capabilities that

were in Raggett's HTML+ proposal, such as support for tables, text flow around figures and

the display of complex mathematical formulas. [4]

W3C began development of its own Arena browser as a test bed for HTML 3 and Cascading

Style Sheets, but HTML 3.0 did not succeed for several reasons. The draft was considered

very large at 150 pages and the pace of browser development, as well as the number of

interested parties, had outstripped the resources of the IETF. Browser vendors, including

Microsoft and Netscape at the time, chose to implement different subsets of HTML 3's draft

features as well as to introduce their own extensions to it. (see Browser wars). These

included extensions to control stylistic aspects of documents, contrary to the "belief [of the

academic engineering community] that such things as text color, background texture, font

size and font face were definitely outside the scope of a language when their only intent was

to specify how a document would be organized." Dave Raggett, who has been a W3C Fellow

for many years, has commented for example: "To a certain extent, Microsoft built its

business on the Web by extending HTML features." [4]

January 2008

HTML5 was published as a Working Draft by the W3C.

Although its syntax closely resembles that of SGML, HTML5 has abandoned any attempt to

be an SGML application and has explicitly defined its own "html" serialization, in addition to

an alternative XML-based XHTML5 serialization. [4]

2011 HTML5 – Last Call

On 14 February 2011, the W3C extended the charter of its HTML Working Group with clear

milestones for HTML5. In May 2011, the working group advanced HTML5 to "Last Call",

an invitation to communities inside and outside W3C to confirm the technical soundness of

the specification. The W3C developed a comprehensive test suite to achieve broad

interoperability for the full specification by 2014, which was the target date for

recommendation. In January 2011, the WHATWG renamed its "HTML5" living standard to

"HTML". The W3C nevertheless continues its project to release HTML5.[5]

19

2012 HTML5 – Candidate Recommendation

In July 2012, WHATWG and W3C decided on a degree of separation. W3C will continue the

HTML5 specification work, focusing on a single definitive standard, which is considered as a

"snapshot" by WHATWG. The WHATWG organization will continue its work with HTML5

as a "Living Standard". The concept of a living standard is that it is never complete and is

always being updated and improved. New features can be added but functionality will not be

removed.

In December 2012, W3C designated HTML5 as a Candidate Recommendation. The criterion

for advancement to W3C Recommendation is "two 100% complete and fully interoperable

implementations".

2014 HTML5 – Proposed Recommendation and Recommendation

In September 2014, W3C moved HTML5 to Proposed Recommendation.

On 28 October 2014, HTML5 was released as a stable W3C Recommendation,meaning the

specification process is complete.

XHTML versions

Main article: XHTML

XHTML is a separate language that began as a reformulation of HTML 4.01 using XML 1.0. It

is no longer being developed as a separate standard.[4][8]

XHTML 1.0 was published as a W3C Recommendation on January 26, 2000 and was

later revised and republished on August 1, 2002. It offers the same three variations as

HTML 4.0 and 4.01, reformulated in XML, with minor restrictions. [4][8]

XHTML 1.1 was published as a W3C Recommendation on May 31, 2001. It is based on

XHTML 1.0 Strict, but includes minor changes, can be customized, and is reformulated

using modules in the W3C recommendation "Modularization of XHTML", which was

published on April 10, 2001. [4][8]

XHTML 2.0 was a working draft; work on it was abandoned in 2009 in favour of work

on HTML5and XHTML5. XHTML 2.0 was incompatible with XHTML 1.x and,

20

therefore, would be more accurately characterized as an XHTML-inspired new language

than an update to XHTML 1.x. [4][8]

An XHTML syntax, known as "XHTML5.1", is being defined alongside HTML5 in the

HTML5 draft.\l " [4][8]

2.1.2.2.IntroductionCascading Style Sheets

Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of a

document written in a mark-up language. Although most often used to set the visual style of web

pages and user interfaces written in HTML and XHTML, the language can be applied to any

XML document, including plain XML, SVG and XUL, and is applicable to rendering in speech,

or on other media. Along with HTML and JavaScript, CSS is a cornerstone technology used by

most websites to create visually engaging webpages, user interfaces for web applications, and

user interfaces for many mobile applications. [5]

CSS is designed primarily to enable the separation of document content from document

presentation, including aspects such as the layout, colors, and fonts. This separation can improve

content accessibility, provide more flexibility and control in the specification of presentation

characteristics, enable multiple HTML pages to share formatting by specifying the relevant CSS

in a separate .css file, and reduce complexity and repetition in the structural content. [5]

Separation of formatting and content makes it possible to present the same mark-up page in

different styles for different rendering methods, such as on-screen, in print, by voice (via speech-

based browser or screen reader), and on Braille-based tactile devices. It can also display the web

page differently depending on the screen size or viewing device. Readers can also specify a

different style sheet, such as a CSS file stored on their own computer, to override the one the

author specified. [5]

21

Changes to the graphic design of a document (or hundreds of documents) can be applied quickly

and easily, by editing a few lines in the CSS file they use, rather than by changing mark-up in the

documents.

The CSS specification describes a priority scheme to determine which style rules apply if more

than one rule matches against a particular element. In this so-called cascade, priorities (or

weights) are calculated and assigned to rules, so that the results are predictable.[5]

The CSS specifications are maintained by the World Wide Web Consortium (W3C). Internet

media type (MIME type) text/css is registered for use with CSS by RFC 2318 (March 1998).

The W3C operates a free CSS validation service for CSS documents.[5]

History

CSS was first proposed by HåkonWium Lie on October 10, 1994. At the time, Lie was working

with Tim Berners-Lee at CERN.Several other style sheet languages for the web were proposed

around the same time, and discussions on public mailing lists and inside World Wide Web

Consortium resulted in the first W3C CSS Recommendation (CSS1)being released in 1996. In

particular, Bert Bos' proposal was influential; he became co-author of CSS1 and is regarded as

co-creator of CSS. [5]

Style sheets have existed in one form or another since the beginnings of Standard Generalized

Mark-up Language (SGML) in the 1980s, and CSS was developed to provide style sheets for the

web. One requirement for a web style sheet language was for style sheets to come from different

sources on the web. Therefore, existing style sheet languages like DSSSL and FOSI were not

suitable. CSS, on the other hand, let a document's style be influenced by multiple style sheets by

way of "cascading" styles. [5]

As HTML grew, it came to encompass a wider variety of stylistic capabilities to meet the

demands of web developers. This evolution gave the designer more control over site appearance,

at the cost of more complex HTML. Variations in web browser implementations, such as

ViolaWWW and Worldwide Web, made consistent site appearance difficult, and users had less

control over how web content was displayed. The browser/editor developed by Tim Berners-Lee

had style sheets that were hard-coded into the program. The style sheets could therefore not be

22

linked to documents on the web. Robert Cailliau, also of CERN, wanted to separate the structure

from the presentation so that different style sheets could describe different presentation for

printing, screen-based presentations, and editors.[5][8]

Improving web presentation capabilities was a topic of interest to many in the web community

and nine different style sheet languages were proposed on the www-style mailing list. Of these

nine proposals, two were especially influential on what became CSS: Cascading HTML Style

Sheets and Stream-based Style Sheet Proposal (SSP). Two browsers served as test beds for the

initial proposals; Lie worked with Yves Lafon to implement CSS in DaveRaggett'sArena

browser. Bert Bos implemented his own SSP proposal in the Argo browser. Thereafter, Lie and

Bos worked together to develop the CSS standard (the 'H' was removed from the name because

these style sheets could also be applied to other mark-up languages besides HTML). [5][8]

Lie's proposal was presented at the "Mosaic and the Web" conference (later called WWW2) in

Chicago, Illinois in 1994, and again with Bert Bos in 1995. Around this time the W3C was

already being established, and took an interest in the development of CSS. It organized a

workshop toward that end chaired by Steven Pemberton. This resulted in W3C adding work on

CSS to the deliverables of the HTML editorial review board (ERB). Lie and Boswas the primary

technical staff on this aspect of the project, with additional members, including Thomas Reardon

of Microsoft, participating as well. In August 1996 Netscape Communication Corporation

presented an alternative style sheet language called JavaScript Style Sheets (JSSS). The spec was

never finished and is deprecated.By the end of 1996, CSS was ready to become official, and the

CSS level 1 Recommendation was published in December. [5]

Development of HTML, CSS, and the DOM had all been taking place in one group, the HTML

Editorial Review Board (ERB). Early in 1997, the ERB was split into three working groups:

HTML Working group, chaired by Dan Connolly of W3C; DOM Working group, chaired by

Lauren Wood of Soft Quad; and CSS Working group, chaired by Chris Lilleyof W3C. [5]

The CSS Working Group began tackling issues that had not been addressed with CSS level 1,

resulting in the creation of CSS level 2 on November 4, 1997. It was published as a W3C

Recommendation on May 12, 1998. CSS level 3, which was started in 1998, is still under

development as of 2014. [5]

23

In 2005 the CSS Working Groups decided to enforce the requirements for standards more

strictly. This meant that already published standards like CSS 2.1, CSS 3 Selectors and CSS 3

Text were pulled back from Candidate Recommendation to Working Draft level. [5]

Difficulty with adoption

The CSS 1 specification was completed in 1996. Microsoft's Internet Explorer 3was released in

that year, featuring some limited support for CSS. IE 4 and Netscape 4.x added more support, but

it was typically incomplete and had many bugs that prevented CSS from being usefully adopted.

It was more than three years before any web browser achieved near-full implementation of the

specification. Internet Explorer 5.0 for the Macintosh, shipped in March 2000, was the first

browser to have full (better than 99 per cent) CSS 1 support,surpassing Opera, which had been

the leader since its introduction of CSS support 15 months earlier. Other browsers followed soon

afterwards, and many of them additionally implemented parts of CSS 2.[4]

However, even when later 'version 5' browsers began to offer a fairly full implementation of

CSS, they were still incorrect in certain areas and were fraught with inconsistencies, bugs and

other quirks. The inconsistencies and variation in feature support made it difficult for designers

to achieve a consistent appearance across browsers and platforms, leading to the use of

workarounds such as CSS hacks and filters. [5]

Problems with browsers' patchy adoption of CSS, along with errata in the original specification,

led the W3C to revise the CSS 2 standard into CSS 2.1, which moved nearer to a working

snapshot of current CSS support in HTML browsers. Some CSS 2 properties that no browser

successfully implemented were dropped, and in a few cases, defined behaviors were changed to

bring the standard into line with the predominant existing implementations. CSS 2.1 became a

Candidate Recommendation on February 25, 2004, but CSS 2.1 was pulled back to Working

Draft status on June 13, 2005, and only returned to Candidate Recommendation status on July

19, 2007. [5]

In addition to these problems, the .css extension was used by a software product used to convert

PowerPoint files into Compact Slide Show files, so some web servers served all .css as mime

type application/x-point plus rather than text/css. [4]

24

Variations

CSS has various levels and profiles. Each level of CSS builds upon the last, typically adding new

features and typically denoted as CSS 1, CSS 2, CSS 3, and CSS 4. Profiles are typically a subset

of one or more levels of CSS built for a particular device or user interface. Currently there are

profiles for mobile devices, printers, and television sets. Profiles should not be confused with

media types, which were added in CSS 2.[4]

CSS 1

The first CSS specification to become an official W3C Recommendation is CSS level 1,

published on December 17, 1996. HåkonWium Lie and Bert Bos are credited as the original

developers. Among its capabilities are supports for

Font properties such as typeface and emphasis[5]

Color of text, backgrounds, and other elements[5]

Text attributes such as spacing between words, letters, and lines of text[5]

Alignment of text, images, tables and other elements[5]

Margin, border, padding, and positioning for most elements[5]

Unique identification and generic classification of groups of attributes [4]

The W3C no longer maintains the CSS 1 Recommendation.[5]

CSS 2

CSS level 2 specification was developed by the W3C and published as a recommendation in

May 1998. A superset of CSS 1, CSS 2 includes a number of new capabilities like absolute,

relative, and fixed positioning of elements and z-index, the concept of media types, support for

aural style sheets (which were later replaced by the CSS 3 speech modules)and bidirectional text,

and new font properties such as shadows. [5]

The W3C no longer maintains the CSS 2 recommendation.

CSS 2.1

CSS level 2 revision 1, often referred to as "CSS 2.1", fixes errors in CSS 2, removes poorly

supported or not fully interoperable features and adds already implemented browser extensions

25

to the specification. To comply with the W3C Process for standardizing technical specifications,

CSS 2.1 went back and forth between Working Draft status and Candidate Recommendation

status for many years. CSS 2.1 first became a Candidate Recommendation on February 25, 2004,

but it was reverted to a Working Draft on June 13, 2005 for further review. It returned to

Candidate Recommendation on 19 July 2007 and then updated twice in 2009. However, because

changes and clarifications were made, it again went back to Last Call Working Draft on 7

December 2010. [5][8]

CSS 2.1 went to Proposed Recommendation on 12 April 2011. After being reviewed by the W3C

Advisory Committee, it was finally published as a W3C Recommendation on 7 June 2011.

CSS 2.1 was planned as the first and final revision of level 2—but low priority work on CSS 2.2

began in 2015. [5]

CSS 3

"CSS3" redirects here. For other uses, see CSS3 (disambiguation).

Unlike CSS 2, which is a large single specification defining various features, CSS 3 is divided

into several separate documents called "modules". Each module adds new capabilities or extends

features defined in CSS 2, preserving backward compatibility. Work on CSS level 3 started

around the time of publication of the original CSS 2 recommendation. The earliest CSS 3 drafts

were published in June 1999. [5][8]

Due to the modularization, different modules have different stability and statuses. As of June

2012, there are over fifty CSS modules published from the CSS Working Group., and four of

these have been published as formal recommendations:[5][8]

2012-06-19: Media Queries

2011-09-29: Namespaces

2011-09-29: Selectors Level 3

2011-06-07: Color

Some modules have Candidate Recommendation (CR) status and are considered moderately

stable. At CR stage, implementations are advised to drop vendor prefixes.[5][8]

26

CSS 4

There is no single, integrated CSS4 specification,because it is split into separate modules.

However, there are "level 4" modules.[5][8]

Because CSS3 split the CSS language's definition into modules, the modules have been allowed

to level independently. Most modules are level 3—they build on things from CSS 2.1. A few

level-4 modules exist (such as Image Values, Backgrounds & Borders,or Selectors), which build

on the functionality of a preceding level-3 module. Other modules defining entirely new

functionality, such as Flex box, have been designated as "level 1".[5]

The CSS Working Group sometimes publishes ―Snapshots‖, a collection of whole modules and

parts of other drafts that are considered stable, interoperable implemented and hence ready to

use. So far, four such best current practices document have been published as Notes, in 2007,

2010,2015. and 2017.[5]

2.1.2.3. Introduction to PHP:

PHP is a server-side scripting language designed primarily for web development but also used as

a general-purpose programming language. Originally created by RasmusLerdorf in 1994, the

PHP reference implementation is now produced by The PHP Development Team. PHP originally

stood for Personal Home Page, but it now stands for the recursive acronymPHP: Hypertext Pre-

processor.[1]

PHP code may be embedded into HTML or HTML5 mark-up, or it can be used in combination

with various web template systems, web content management systems and web frameworks.

PHP code is usually processed by a PHP interpreter implemented as a module in the web server

or as a Common Gateway Interface (CGI) executable. The web server software combines the

results of the interpreted and executed PHP code, which may be any type of data, including

images, with the generated web page. PHP code may also be executed with a command-line

interface(CLI) and can be used to implement standalonegraphical applications.[1]

27

The standard PHP interpreter, powered by the Zend Engine, is free software released under the

PHP License. PHP has been widely ported and can be deployed on most web servers on almost

every operating system and platform, free of charge.[2]

The PHP language evolved without a written formal specification or standard until 2014, leaving

the canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to create a

formal PHP specification.[3]

HISTORY

RasmusLerdorf(left), who wrote the original Common Gateway Interface (CGI) component,

together with AndiGutmans (middle) and Zeev Suraski(right), who rewrote the parser that

formed PHP 3.[2]

PHP development began in 1995 when RasmusLerdorfwrote several Common Gateway Interface

(CGI) programs in C, which he used to maintain his personal homepage. He extended them to

work with web forms and to communicate with databases, and called this implementation

"Personal Home Page/Forms Interpreter" or PHP/FI.[3]

PHP/FI could help to build simple, dynamic web applications. To accelerate bug reporting and to

improve the code, Lerdorf initially announced the release of PHP/FI as "Personal Home Page

Tools (PHP Tools) version 1.0" on the Usenetdiscussion group

comp.infosystems.www.authoring.cgi on June 8, 1995. This release already had the basic

functionality that PHP has as of 2013//en.wikipedia.org/w/index.php?title=PHP&action=edit.

This included Perl-like variables, form handling, and the ability to embed HTML. The syntax

resembled that of Perl but was simpler, more limited and less consistent.[3]

Lerdorf did not intend the early PHP to become a new programming language, but it grew

organically, with Lerdorf noting in retrospect: "I don’t know how to stop it, there was never any

intent to write a programming language […] I have absolutely no idea how to write a

programming language, I just kept adding the next logical step on the way." A development team

began to form and, after months of work and beta testing, officially released PHP/FI 2 in

November 1997.[3]

28

The fact that PHP lacked an original overall design but instead developed organically has led to

inconsistent naming of functions and inconsistent ordering of their parameters. In some cases,

the function names were chosen to match the lower-level libraries which PHP was "wrapping",

while in some very early versions of PHP the length of the function names was used internally as

a hash function, so names were chosen to improve the distribution of hash values.[2]

PHP 3 and 4

Zeev Suraski and AndiGutmans rewrote the parserin 1997 and formed the base of PHP 3,

changing the language's name to the recursive acronymPHP: Hypertext Pre-processor.

Afterwards, public testing of PHP 3 began, and the official launch came in June 1998. Suraski

and Gutmans then started a new rewrite of PHP's core, producing the Zend Engine in 1999. They

also founded Zend Technologies in Ramat Gan, Israel. [2]

On May 22, 2000, PHP 4, powered by the Zend Engine 1.0, was released. As of August 2008

this branch reached version 4.4.9. PHP 4 is no longer under development nor will any security

updates be released.[3]

PHP 5

On July 13, 2004, PHP 5 was released, powered by the new Zend Engine II. PHP 5 included new

features such as improved support for object-oriented programming, the PHP Data Objects

(PDO) extension (which defines a lightweight and consistent interface for accessing databases),

and numerous performance enhancements. In 2008 PHP 5 became the only stable version under

development. Late static binding had been missing from PHP and was added in version 5.3.[3]

Many high-profile open-source projects ceased to support PHP 4 in new code as of February 5,

2008, because of the GoPHP5 initiative, provided by a consortium of PHP developers promoting

the transition from PHP 4 to PHP 5. [3][8]

Over time, PHP interpreters became available on most existing 32-bit and 64-bit operating

systems, either by building them from the PHP source code, or by using pre-built binaries. For

the PHP versions 5.3 and 5.4, the only available Microsoft Windows binary distributions were

32-bit x86 builds, requiring Windows 32-bit compatibility mode while using Internet

Information Services (IIS) on a 64-bit Windows platform. PHP version 5.5 made the 64-bit x86-

64 builds available for Microsoft Windows.[2]

29

PHP 6 and Unicode

PHP has received criticism due to lacking native Unicode support at the core language level,

instead only supporting byte strings. In 2005, a project headed by Andrei Zmievski was initiated

to bring native Unicode support throughout PHP, by embedding the International Components

for Unicode (ICU) library, and representing text strings as UTF-16 internally. Since this would

cause major changes both to the internals of the language and to user code, it was planned to

release this as version 6.0 of the language, along with other major features then in

development.[2][7]

However, a shortage of developers who understood the necessary changes, and performance

problems arising from conversion to and from UTF-16, which is rarely used in a web context, led

to delays in the project.As a result, a PHP 5.3 release was created in 2009, with many non-

Unicode features back-ported from PHP 6, notably namespaces. In March 2010, the project in its

current form was officially abandoned, and a PHP 5.4 release was prepared containing most

remaining non-Unicode features from PHP 6, such as traits and closure re-binding. Initial hopes

were that a new plan would be formed for Unicode integration, but as of 2014 none have been

adopted. [3][7]

PHP 7

During 2014 and 2015, a new major PHP version was developed, which was numbered PHP 7.

The numbering of this version involved some debate. While the PHP 6 Unicode experiment had

never been released, several articles and book titles referenced the PHP 6 name, which might

have caused confusion if a new release were to reuse the name. After a vote, the name PHP 7

was chosen. [3][7]

The foundation of PHP 7 is a PHP branch that was originally dubbed PHP next generation

(phpng). It was authored by Dmitry Stogov, XinchenHui and Nikita Popov, and aimed to

optimize PHP performance by refactoring the Zend Engine to use more compact data structures

with improved cache locality while retaining near-complete language compatibility. As of 14

July 2014//en.wikipedia.org/w/index.php?title=PHP&action=edit, Word Press-based

benchmarks, which served as the main benchmark suite for the phpng project, showed an almost

100% increase in performance. Changes from phpng are also expected to make it easier to

improve performance in the future, as more compact data structures and other changes are seen

30

as better suited for a successful migration to a just-in-time(JIT) compiler. Because of the

significant changes, the reworked Zend Engine is called Zend Engine 3, succeeding Zend Engine

2 used in PHP 5. [2][7]

Because of major internal changes in phpng, it must receive a new major version number of

PHP, rather than a minor PHP 5 release, according to PHP's release process. Major versions of

PHP are allowed to break backward-compatibility of code and therefore PHP 7 presented an

opportunity for other improvements beyond phpng that require backward-compatibility breaks,

including wider use of exceptions, reworking variable syntax to be more consistent and

complete, and the deprecation or removal of various legacy features.PHP 7 also introduced new

language features, including return type declarations for functions, which complement the

existing parameter type declarations, and support for the scalar types (integer, float, string, and

boolean) in parameter and return type declarations.[2][7]

Syntax :

<html>

<head>

<title>PHP Test </title>

</head>

<body>

<?php echo “<p> Hello World </p>”; ?>

</body></html>

2.1.2.4: Introduction to MYSQL:

MySQL is written in Cand C++. Its SQL parser is written in yacc, but it uses a home-brewed

lexical analyser. MySQL works on many system platforms, including AIX, BSDi, FreeBSD, HP-

UX, eComStation, i5/OS, IRIX, Linux, macOS, Microsoft Windows, NetBSD, Novell NetWare,

OpenBSD, Open Solaris, OS/2Warp, QNX, Oracle Solaris, Symbian, SunOS, SCO Open Server,

SCO UnixWare, Sanos and Tru64. A port of MySQL to OpenVMS also exists.[1]

31

The MySQL server software itself and the client libraries use dual-licensing distribution. They

are offered under GPL version 2, beginning from 28 June 2000 (which in 2009 has been

extended with a FLOSS License Exception)or to use a proprietary license.[1][9]

Support can be obtained from the official manual. Free support additionally is available in

different IRC channels and forums. Oracle offers paid support via its MySQL Enterprise

products. They differ in the scope of services and in price. Additionally, a number of third party

organisations exist to provide support and services, including Maria DB and Percona.[1]

MySQL has received positive reviews, and reviewers noticed it "performs extremely well in the

average case" and that the "developer interfaces are there, and the documentation (not to mention

feedback in the real world via Web sites and the like) is very, very good". It has also been tested

to be a "fast, stable and true multi-user, multi-threaded sql database server". [1]

Features

MySQL is offered under two different editions: the open source MySQL Community Server and

the proprietary Enterprise Server.MySQL Enterprise Server is differentiated by a series of

proprietary extensions which install as server plugins, but otherwise shares the version

numbering system and is built from the same code base. [1][9]

Major features as available in MySQL 5.6:

A broad subset of ANSI SQL 99, as well as extensions

Cross-platform support

Stored procedures, using a procedural language that closely adheres to SQL/PSM

Triggers

Cursors

Updatable views

Online DDL when using the InnoDB Storage Engine.

Information schema

Performance Schema that collects and aggregates statistics about server execution and

query performance for monitoring purposes.

32

A set of SQL Mode options to control runtime behaviour, including a strict mode to

better adhere to SQL standards.[1][9]

X/Open XA distributed transaction processing(DTP) support; two phase commit as part

of this, using the default InnoDB storage engine

Transactions with save points when using the default InnoDB Storage Engine. The NDB

Cluster Storage Engine also supports transactions.

ACID compliance when using InnoDB and NDB Cluster Storage Engines

SSL support

Query caching

Sub-SELECTs (i.e. nested SELECTs)

Built-in replication support (i.e., master-master replication and master-slave replication)

with one master per slave, many slaves per master.Multi-master replication is provided in

MySQL Cluster, and multi-master support can be added to uncluttered configurations

using Galera Cluster.

Full-text indexing and searching

Embedded database library

Unicode support

Partitioned tables with pruning of partitions in optimizer

Shared-nothing clustering through MySQL Cluster

Multiple storage engines, allowing one to choose the one that is most effective for each

table in the application.

Native storage engines InnoDB, MyISAM, Merge, Memory (heap), Federated, Archive,

CSV, Black hole, NDB Cluster.

Commit grouping, gathering multiple transactions from multiple connections together to

increase the number of commits per second.

33

The developers release minor updates of the MySQL Server approximately every two months.

The sources can be obtained from MySQL's website or from MySQL's GitHub repository, both

under the GPL license. [1][9]

Limitations

When using some storage engines other than the default of InnoDB, MySQL does not comply

with the full SQL standard for some of the implemented functionality, including foreign key

references and check constraints.

Up until MySQL 5.7, triggers are limited to one per action / timing, meaning that at most one

trigger can be defined to be executed after an INSERT operation and one before INSERT on the

same table. No triggers can be defined on views.*

MySQL database's inbuilt functions like UNIX_TIMESTAMP () will return 0 after 03:14:07

UTC on 19 January 2038.[1][9]

Syntax:

Mysql_connect (server name, user name, password)

2.2. Existing System:

• Lack of security of data.

• More man power.

• Time consuming.

• Consumes large volume of pare work.

• Needs manual calculations.

• No direct role for the higher officials.

• Damage of machines due to lack of attention.

34

To avoid all these limitations and make the working more accurately the system needs to be

computerized.

2.3. Proposed System

The aim of proposed system is to develop a system of improved facilities. The proposed system

can overcome all the limitations of the existing system. The system provides proper security and

reduces the manual work.

ADVANTAGES OF THE PROPOSED SYSTEM :

The system is very simple in design and to implement. The system requires very low system

resources and the system will work in almost all configurations. It has got following features

• Security of data.

• Ensure data accuracy’s.

• Proper control of the higher officials.

• Reduce the damages of the machines.

• Minimize manual data entry.

• Minimum time needed for the various processing.

• Greater efficiency.

• Better service.

• User friendliness and interactive.

• Minimum time required.

36

SYSTEM DESIGN

3.1. TABLE DESCRIPTION:

ADMIN LOGIN :

SL NO FIELD NAME DATATYPE CONSTRAINT DESCRIPTION

1 Admin id Varchar (20) Primary key Id of the admin

37

2 Password Varchar(20) Null Password of the admin

SHOWROOM:

FIELD NAME DATATYPE CONSTRAINT DESCRIPTION

Showroom id Int (10) Primary key Id of the showroom

Showroom

name

Varchar(255) Null Name of the

showroom

Address Varchar(255) Null Address of showroom

Contact no Int (255) Null Contact no of

showroom

Pin code Int(10) Null Pin code of showroom

DEALER :


Dealer Id Int(10) Primary Id of the dealer

Dealer name Varchar(255) Null Name of the dealer

Company name Varchar(255) Null Name of company

Contact no int(255) Null Contact no of dealer

Address Varchar(255) Null Address of the dealer

VEHICLE:


38

Vehicle Id Int(10) Primary Id of the Vehicle

Vehicle name varchar(210) Null It specifies name of the

vehicle

Vehicle cost Int(10) Null Cost number of the

vehicle

Vehicle model Varchar(100) Null Model of the vehicle

Vehicle type Varchar(150) Null Type of the vehicle

TAX:


Tax Id Int(10) Primary Id no of tax

Tax price Int(50) Null Tax of the vehicle

Tax

description

Varchar(255) Null Information about

tax

39

3.2. E-R DIAGRAM

An entity-relationship diagram is a graphical depiction of organizational system elements and

the association among the elements .E-R diagram can help define system boundaries.

The elements that make up a system are referred to a entities. A Relationship is the

association that describes the interaction between entities.

An E-R diagram may all so indicate the cardinalityof a relationship .Cardinality is the

number of instances of one entity that can, or must, be associated with each instance of

another entity.

In general we may speak of one-to-one (1:1), one-to-many (1:

N), or many -to-many (N: N) relationship.

The E-R notation also allow for distinguishing different types of entities .An entity is

an object or concept about which some information is stored.

: Fundamental entity

An entity that is areal thing .E.g.: person, place, or thing

: Associative entity

40

Used for something that is created that joins two entities .E.g.: A receipt that exists

when a customer and a salesperson complete transaction.

: Attributive entity

Used for data that is independent up on a fundamental entity and is useful for

describing attributes .E.g.: In identify a specific copy of a movie title when a video store

has multiple copies of each movie.

: Entity

:Weakentity

An entity types that do not have key attributes of their own .

41

:Attribute

It is a property or characteristic of an entity.

: Key attribute

An attribute that uniquely identifies an entity .It is unique distinguishing characteristic of

the entity.

: Multi value attribute .

It is an attribute that can have more than one value

: Derived attribute

An attribute that is based on another attribute .

42

: Relationship

It specifies how to entities share information in the database.

: Identifying relationship

Specifies the relationship between a weak entity and a specific entity from another entity .

There are several different styles used to draw E-R diagrams . The Kendall and Kendal

text which uses ('row's Foot notation .Cardinality can be shown using" tick marks" and " crew's

feet " super imposed on the relationship lines.

1 1 or more 0, 1, or more

43

0 or 1one to many

E-R DIAGRAM

Admin

Admin id Password

Dealer

Dealer id

Company name Contact number

Dealer name

Address

Add

Showroom

Save

Showroom id Showroom name

Address State

Pin code

Vehicle

Supply

Select

Vehicle id Vehicle name

Vehicle cost Vehicle type

44

CODING AND DEVELOPMENT

4.1. Source Code:

Admin Login:

<?php

session_start();

include("dbconnection.php");

?>

<script type="application/javascript">

function validation()

{

Contact no Vehicle status Vehicle model

Tax

Vehicle Tax

Tax id Tax price

Tax description

45

var alphaExp = /^[a-zA-Z]+$/;

if(document.admin.adminname.value == "")

{

alert("Please enter name");

document.admin.adminname.focus();

return false;

}

else if(!document.admin.adminname.value.match(alphaExp))

{

alert("Admin name is not valid...");

document.admin.adminname.value = "";

document.admin.adminname.focus();

return false;

}

else if(document.admin.username.value == "")

{

alert("Please enter username");

document.admin.username.focus();

return false;

}

46

else if(document.admin.password.value == "")

{

alert("Password should not be empty");

document.admin.password.focus();

return false;

}

else if(document.admin.password.value.length <8)

{

alert("Password should not be less than 8 characters");


return false;

}

else if(document.admin.password.value != document.admin.cpassword.value)

{

alert("Password and confirm password not matching.");


return false;

}

else if(document.admin.contno.value == "")

{

alert("Contact Number should not be empty...");

47

document.admin.contno.focus();

return false;

}

else if(isNaN(document.admin.contno.value))

{

alert("Contact Number not valid...");


return false;

}

else if(document.admin.contno.value.length <9)

{

alert("Contact number should not be less than 8");


return false;

}

else

{

return true;

}

}

</script>

48

<?php

$date=date("Y-m-d");

if($_SESSION["setid"] == $_POST["setid"])

if(isset($_POST["submit"]))

{

if(isset($_GET[editid]))

{

$result = mysqli_query($con,"UPDATE admin SET

adminname='$_POST[adminname]',username='$_POST[username]',password='$_POST[passwo

rd]',contactnumber='$_POST[contno]',status='$_POST[status]' where

adminid='$_GET[editid]'");

if(!$result)

{

$res = "<br>Failed to update record";

}

else

{

$res = "<br>Record updated successfully...";

}

}

else

49

{

$result=mysqli_query($con,"INSERT INTO

admin(adminname,username,password,contactnumber,createdat,status)

values('$_POST[adminname]','$_POST[username]','$_POST[password]','$_POST[contno]','$dat

e','$_POST[status]')");

if(!$result)

{

$res = "failed to insert record";

}

else

{

$res = "Record inserted successfully...";

}

}

}

$_SESSION["setid"] = rand();

$sql = "SELECT * FROM admin where adminid='$_GET[editid]'";

$seleditquery = mysqli_query($con,$sql);

$rseditfetch = mysqli_fetch_array($seleditquery);

50

?>

<?php

include("header.php"); //Developed by www.freestudentprojects.com

?>

<div id="templatemo_main">

<div id="sidebar" class="float_l">

<?php

include("menusidebar.php");

?>

</div>

<div id="content" class="float_r">

<h1>Add Administrator</h1>

<form name="admin" method="post" action="" onsubmit="return validation()">

<input type="hidden" name="setid" value="<?php echo $_SESSION[setid]; ?>" />

<TABLE width="372" border=1 color=black class="tftable">

<tr><td colspan="2"><?php echo $res; ?></td></tr>

<tr><th>ADMINNAME:</th><td><input type=text name=adminname value="<?php echo

$rseditfetch["adminname"]; ?>" ></td></tr>

51

<tr><th>USERNAME:</th><td><input type=text name=username value="<?php echo

$rseditfetch["username"]; ?>" ></td></tr>

<tr><th>PASSWORD:</th><td><input type=password name=password value="<?php echo

$rseditfetch["password"]; ?>" ></td></tr>

<tr><th>CONFIRMPASSWORD:</th><td><input type=password name=cpassword

value="<?php echo $rseditfetch["password"]; ?>" ></td></tr>

<tr><th>CONTACTNUMBER</th><td><input type=text name=contno value="<?php echo

$rseditfetch["contactnumber"]; ?>" ></td></tr>

<tr><th>STATUS:</th><td>

<select name=status>

<option>Select</option>

<?php

$arr = array("Enabled","Disabled");

foreach($arr as $value)

{

if($value== $rseditfetch["status"])

{

52

echo "<option value='$value' selected>$value</option>";

}

else

{

echo "<option value='$value'>$value</option>";

}

}

?>

</select>

</td></tr>

<tr ><td colspan=2 ><center><input type=submit value=SUBMIT

name=submit></center></td></tr>

</table>

</form>

</div>

<div class="cleaner"></div>

</div>

53

<?php

include("footer.php");

?>

Index Page

<?php



?>



<?php


?>

</div>


<div id="slider-wrapper">

<div id="slider" class="nivoSlider">

<img src="images/slider/car1.gif" alt="" />

54

<a href="#"><img src="images/slider/car2.jpg" alt="" title="Best-In-Class Highway Fuel

Economy" /></a>

<img src="images/slider/car3.jpg" alt="" />

<img src="images/slider/car4.jpg" alt="" title="#htmlcaption" />

</div>

<div id="htmlcaption" class="nivo-html-caption">

<strong>User friendly advanced technology</strong>

</div>

</div>

<script type="text/javascript" src="js/jquery-1.4.3.min.js"></script>

<script type="text/javascript" src="js/jquery.nivo.slider.pack.js"></script>

<script type="text/javascript">

$(window).load(function() {

$('#slider').nivoSlider();

});

</script>

<h1>New Vehicles</h1>

<?php

$sql = ("SELECT * FROM vehicle order by vehid desc LIMIT 0 , 9 ");

$result = mysql_query($sql);

55

$count = 1;

while($rs = mysql_fetch_array($result))

{

$sql1 = "SELECT * FROM images where vehid='$rs[vehid]' order by

rand() limit 1";

$result1 = mysql_query($sql1);

$rs1 = mysql_fetch_array($result1);

if($count== 1 || $count == 2)

{

echo "<div class='product_box'>";

}

else

{

echo "<div class='product_box no_margin_right'>";

$count=1;

}

?>

<h3><?php echo $rs['vehname']; ?></h3>

<a href="vehicledetail.php?vid=<?php echo $rs[vehid];?>">

<?php

56

if(mysql_num_rows($result1) == 1)

{

echo "<img src='imgvehicle/$rs1[imagepath]'

alt='$rs1[imagename]' width='200' height='150' />";

}

else

{

echo "<img src='images/vehiclebg.jpg' alt='<?php

$rs1[imagename]; ?>' width='200' height='150' />";

}

?>

</a>

<p>Model: <?php echo substr($rs['vehmodel'],0,20);; ?></p>

<p>Type: <?php echo $rs['vehtype']; ?></p>

<p class="product_price">Rs. <?php echo $rs['vehcost']; ?></p>

<a href="buyvehicle.php?vid=<?php echo $rs[vehid];?>" class="addtocart"></a>

<a href="vehicledetail.php?vid=<?php echo $rs[vehid];?>" class="detail"></a>

</div>

<?php

$count++;

}

?>

57


</div>



<?php


?>

Dealer:

<?php

session_start();


?>

<script type="application/javascript">

function validation()

{

var alphaExp = /^[a-zA-Z]+$/;

if(document.dealer.companyname.value == "")

{

alert("Please enter first name");

document.dealer.companyname.focus();

58

return false;

}

else if(document.dealer.fname.value == "")

{

alert("Please enter first name");

document.dealer.fname.focus();

return false;

}

else if(!document.dealer.fname.value.match(alphaExp))

{

alert("First name is not valid...");

document.dealer.fname.value = "";

document.dealer.fname.focus();

return false;

}

else if(document.dealer.lname.value == "")

{

alert("Please enter last name");

document.lname.focus();

return false;

}

59

else if(!document.dealer.lname.value.match(alphaExp))

{

alert("Last name is not valid...");

document.dealer.lname.value = "";

document.dealer.lname.focus();

return false;

}

else if(document.dealer.username.value == "")

{

alert("Please enter Email ID");

document.dealer.username.focus();

return false;

}

else if(document.dealer.password.value == "")

{

alert("Password should not be empty");

document.dealer.password.focus();

return false;

}

else if(document.dealer.password.value.length <8)

60

{

alert("Password should not be less than 8 characters");

document.dealer.password.focus();

return false;

}

else if(document.dealer.password.value != document.dealer.cpassword.value)

{

alert("Password and confirm password not matching.");

document.dealer.newpassword.focus();

return false;

}

else if(document.dealer.address.value == "")

{

alert("Please enter Address");

document.dealer.address.focus();

return false;

}

else if(document.dealer.contno.value == "")

{

alert("Contact Number should not be empty...");

document.dealer.contno.focus();

61

return false;

}

else if(isNaN(document.dealer.contno.value))

{

alert("Contact Number not valid...");


return false;

}

else if(document.dealer.contno.value.length <9)

{

alert("Contact number should not be less than 8");


return false;

}

else

{

return true;

}

}

</script>

<?php

62

$date=date("Y-m-d");

if($_SESSION["setid"] == $_POST["setid"])

{

if(isset($_POST["submit"]))

{

if(isset($_GET['editid']))

{

if($_FILES['compimg']['name'] != "")

{

$imgname = rand().$_FILES['compimg']['name'];

move_uploaded_file($_FILES['compimg']['tmp_name'],"imgcompany/".

$imgname);

$result = mysql_query($con,"INSERT INTO images(imagepath)

values('$imgname')") or mysqli_error($con);

$imgid = mysql_insert_id($con);

}

else

{

$imgid = $_POST[compimg1];

}

$dt = date("Y-m-d");

63

$result = mysql_query($con,"UPDATE dealer SET

adminid='$_SESSION[adminid]',imgid='$imgid',companyname='$_POST[companyname]',fnam

e='$_POST[fname]',lname='$_POST[lname]',username='$_POST[username]',password='$_POS

T[password]',contactnumber='$_POST[contno]',address='$_POST[address]',createdat='$dt',statu

s='$_POST[status]' where dealerid='$_GET[editid]'");

if(!$result)

{

$resi=1;

$res = "<br>Failed to update record";

}

else

{

$resi=1;

$res = "<br><strong>Record updated successfully...</strong>";

}

}

else

{

if($_FILES['compimg']['name'] != "")

{

$imgname = rand().$_FILES['compimg']['name'];

move_uploaded_file($_FILES['compimg']['tmp_name'],"imgcompany/".

$imgname);

64

$result = mysqli_query($con,"INSERT INTO images(imagepath)

values('$imgname')") or mysqli_error($con);

$imgid = mysqli_insert_id($con);

}

$dt = date("Y-m-d");

$result=mysqli_query($con,"INSERT INTO

dealer(adminid,imgid,companyname,fname,lname,username,password,contactnumber,address,cr

eatedat,status)

values('$_SESSION[adminid]','$imgid','$_POST[companyname]','$_POST[fname]','$_POST[lna

me]','$_POST[username]','$_POST[password]','$_POST[contno]','$_POST[address]','$dt','$_PO

ST[status]')");

if(!$result)

{

$resi=1;

$res = "failed to insert record";

}

else

{

$resi=1;

$res = "<strong>Record inserted successfully...</strong>";

}

}

65

}

}

$_SESSION["setid"] = rand();

$sql = "SELECT * FROM dealer where dealerid='$_GET[editid]'";

$seleditquery = mysqli_query($con,$sql);

$rseditfetch = mysqli_fetch_array($seleditquery);

?>

<?php


?>



<?php


?>

</div>


<h1>Add Dealer</h1>

66

<form name="dealer" method="post" action="" onsubmit="return validation()"

enctype="multipart/form-data">

<input type="hidden" name="setid" value="<?php echo $_SESSION[setid]; ?>" />

<TABLE width="491" border=1 color=black class="tftable">

<?php

if($resi == 1)

{

?>

<tr>

<td colspan="2" align="center">

<?php

echo $res;

?></td>

</tr>

<?php

}

?>

<tr>

<th>COMPANY NAME:</th><td><input type=text name=companyname value="<?php echo

$rseditfetch["companyname"]; ?>" ></td></tr>

67

<tr>

<th>FIRST NAME:</th><td><input type=text name=fname value="<?php echo

$rseditfetch["fname"]; ?>" ></td></tr>

<tr>

<th>LAST NAME:</th><td><input type=text name=lname value="<?php echo

$rseditfetch["lname"]; ?>" ></td></tr>

<tr>

<th>USER NAME:</th><td><input type=text name=username value="<?php echo

$rseditfetch["username"]; ?>" ></td></tr>

<tr><th>PASSWORD:</th><td><input type=password name=password value="<?php echo

$rseditfetch["password"]; ?>" ></td></tr>

<tr>

<th>CONFIRM PASSWORD:</th><td><input type=password name=cpassword value="<?php

echo $rseditfetch["password"]; ?>" ></td></tr>

<tr><th>ADDRESS:</th><td><textarea name="address"><?php echo $rseditfetch["address"];

?></textarea></td></tr>

68

<tr>

<th>CONTACT NUMBER</th><td><input type=text name=contno value="<?php echo

$rseditfetch["contactnumber"]; ?>" ></td></tr>

<tr>

<th>UPLOAD LOGO</th><td>

<input type="hidden" name="compimg1" id="compimg" value="<?php echo

$rseditfetch[imgid]; ?>" >

<input type="file" name="compimg" id="compimg" ><br />

<?php

$sqlimg = "SELECT * FROM images where imgid='$rseditfetch[imgid]'";

$selqueryimg = mysql_query($con,$sqlimg);

$rsimg = mysql_fetch_array($selqueryimg);

?>

<img src="imgcompany/<?php echo $rsimg[imagepath]; ?>" />

</td></tr>

<tr><th>STATUS:</th><td>

<select name=status>

<option>Select</option>

69

<?php

$arr = array("Enabled","Disabled");

foreach($arr as $value)

{

if($value== $rseditfetch["status"])

{

echo "<option value='$value' selected>$value</option>";

}

else

{

echo "<option value='$value'>$value</option>";

}

}

?>

</select>

</td></tr>

<tr ><td colspan=2 >

<center><input type=submit value=SUBMIT name=submit></center>

</td></tr>

70

</table>

</form>

</div>



<?php


?>

Vehicle :

<?php


?>



<?php


?>

</div>

71


<h1> Vehicles</h1>

<?php

if(isset($_GET['did']))

{

$sql = "SELECT * FROM vehicle where dealerid='$_GET[did]' order by vehid desc";

}

else if(isset($_GET['searchid']))

{

$sql = "SELECT * FROM `vehicle` WHERE `vehname` LIKE '%$_GET[searchid]%' OR

`vehmodel` LIKE '%$_GET[searchid]%' order by vehid desc";

}

else

{

$sql = "SELECT * FROM vehicle order by vehid desc";

}

$result = mysql_query($sql);

if(mysql_num_rows($result) == 0)

{

echo "<h2>No vehicles found</h2>";

}

72

$count = 1;

while($rs = mysql_fetch_array($result))

{

$sql1 = "SELECT * FROM images where vehid='$rs[vehid]' order by

rand() limit 1 ";

$result1 = mysql_query($sql1);

$rs1 = mysql_fetch_array($result1);

if($count== 1 || $count == 2)

{

echo "<div class='product_box'>";

}

else

{

echo "<div class='product_box no_margin_right'>";

$count=1;

}

?>

<h3><?php echo $rs['vehname']; ?></h3>

<a href="vehicledetail.php?vid=<?php echo $rs[vehid];?>">

<?php

73

if(mysql_num_rows($result1) == 1)

{

echo "<img src='imgvehicle/$rs1[imagepath]'

alt='$rs1[imagename]' width='200' height='150' />";

}

else

{

echo "<img src='images/vehiclebg.jpg' alt='<?php

$rs1[imagename]; ?>' width='200' height='150' />";

}

?>

</a>

<p>Model: <?php echo $rs['vehmodel']; ?></p>

<p>Type: <?php echo $rs['vehtype']; ?></p>

<p class="product_price">Rs. <?php echo $rs['vehcost']; ?></p>

<a href="buyvehicle.php?vid=<?php echo $rs['vehid'];?>" class="addtocart"></a>

<a href="vehicledetail.php?vid=<?php echo $rs['vehid'];?>" class="detail"></a>

</div>

<?php

$count++;

}

?>

74


</div>



<?php


?>

75

TESTING AND IMPLEMENTATION

76

5.1. Introducing to Testing:

The purpose of testing is to discover errors. Testing is the process of trying to discover every

conceivable fault or weakness in a work product. It provides a way to check the functionality of

components, sub assemblies, assemblies and/or a finished product It is the process of exercising

software with the intent of ensuring that the Software system meets its requirements and user

expectations and does not fail in an unacceptable manner. There are various types of test. Each

test type addresses a specific testing requirement. [6]

5.2 TYPES OF TESTS

Unit testing Unit testing involves the design of test cases that validate that the internal program logic is

functioning properly, and that program inputs produce valid outputs. All decision branches and

internal code flow should be validated. It is the testing of individual software units of the

application .it is done after the completion of an individual unit before integration. This is a

structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform

basic tests at component level and test a specific business process, application, and/or system

configuration. Unit tests ensure that each unique path of a business process performs accurately

77

to the documented specifications and contains clearly defined inputs and expected results.

[6][10]

Integration testing

Integration tests are designed to test integrated software components to determine if they actually

run as one program. Testing is event driven and is more concerned with the basic outcome of

screens or fields. Integration tests demonstrate that although the components were individually

satisfaction, as shown by successfully unit testing, the combination of components is correct and

consistent. Integration testing is specifically aimed at exposing the problems that arise from the

combination of components. [6][10]

Functional test

Functional tests provide systematic demonstrations that functions tested are available as

specified by the business and technical requirements, system documentation, and user manuals.

Functional testing is centred on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures : interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key functions, or

special test cases. In addition, systematic coverage pertaining to identify Business process flows;

data fields, predefined processes, and successive processes must be considered for testing.

78

Before functional testing is complete, additional tests are identified and the effective value of

current tests is determined. [6][10]

System Test System testing ensures that the entire integrated software system meets requirements. It tests a

configuration to ensure known and predictable results. An example of system testing is the

configuration oriented system integration test. System testing is based on process descriptions and

flows, emphasizing pre-driven process links and integration points.

White Box Testing

White Box Testing is a testing in which in which the software tester has knowledge of the inner

workings, structure and language of the software, or at least its purpose. It is purpose. It is used to test

areas that cannot be reached from a black box level. [6][10]

Black Box Testing

Black Box Testing is testing the software without any knowledge of the inner workings,

structure or language of the module being tested. Black box tests, as most other kinds of tests,

must be written from a definitive source document, such as specification or requirements

document, such as specification or requirements document. It is a testing in which the software

under test is treated, as a black box .you cannot ―see‖ into it. The test provides inputs and

responds to outputs without considering how the software works. [6][10]

Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test phase of the software

lifecycle, although it is not uncommon for coding and unit testing to be conducted as two distinct

phases. [6][10]

Test strategy and approach Field testing will be performed manually and functional tests will be written in detail.

79

Test objectives

All field entries must work properly.

Pages must be activated from the identified link.

The entry screen, messages and responses must not be delayed.

Features to be tested

Verify that the entries are of the correct format

No duplicate entries should be allowed

All links should take the user to the correct page.

Integration Testing

Software integration testing is the incremental integration testing of two or more integrated

software components on a single platform to produce failures caused by interface defects. The

task of the integration test is to check that components or software applications, e.g. components

in a software system or – one step up – software applications at the company level – interact

without error.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.

[6][10]

AcceptanceTesting:

User Acceptance Testing is a critical phase of any project and requires significant participation

by the end user. It also ensures that the system meets the functional requirements.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.

[6]

81

CONCLUSION

6. CONCLUSION

To conclude the description about the project. The project, developed using HTML, CSS with

PHP and SQL SERVER is based on the requirement specification of the user and the analysis of

the existing system, with flexibility for future enhancement.

PRAGUE STAY is very useful for hostel allotment and fee calculation. This hostel management

software is designed for people who want to manage various activities in the hostel. For the past

few years the numbers of educational institutions are increasing rapidly. Thereby the numbers of

hostels are also increasing for the accommodation of the students studying in this institution.

And hence there is a lot of strain on the person who are running the hostel and software’s are not

usually used in this context. This particular project deals with the problems on managing a hostel

and avoids the problems which occur when carried manually.

Identification of the drawbacks of the existing system leads to the designing of computerized

system that will be compatible to the existing system with the system which is

more user friendly and more GUI oriented.

82

6.1 SCOPE FOR FUTURE DEVELOPMENT

The following are the future scope for the project.

Employee payroll

Providing feedback

Online payment

Students Attendance

83

APPENDICES

7. APPENDICES

Form design:

Home page :

84

User Login:

Admin Login:

85

Register page:

86

Profile Updating:

Room details:

87

Change Password:

88

User’s Login details:

Add Course:

89

Add Rooms:

Vacate Room:

90

Dashboard:

91

BIBLIOGRAPHY

8. BIBLIOGRAPHY:

8.1 BOOK REFERENCES:

1. Luke Welling,‖PHP and MySQL Web Development‖.

2. PHP solution: Dynamic Web Design Made Easy, second edition.

92

3. Larry Ullman’s,‖PHP For The Web: Visual Quick Start Guide‖

4. Thomas Powell, ‖HTML & CSS: The complete reference, fifth edition‖

5. Eric A. Meyer, ―CSS Pocket Reference: Visual Presentation for the Web‖, fourth edition.

6. Ian Sommerville-SoftwareEngineering,9th

Edition, Pearson Education Ltd,2010

8.2 WEBSITES:

7. http://www.w3schools.com/php.net/

8. http://www.stackoverflow.com

9. http://www.mysql.com

10. http://www.softwaretestinghelp.com

http://www.w3schools.com/php.net/

http://www.stackoverflow.com/

“VEHICLE SHOWROOM”

Documents

Transcript of “VEHICLE SHOWROOM”