A Project Report on “ONLINE CAR SHOWROOM
MANAGEMENT”
Submitted to the Bangalore University in partial fulfillment
of the requirement for the award of the degree in
Bachelor of Computer Applications
Submitted by BALAKRISHNA .P USN:17VFSB7008
Under the guidance of Ms. ANJANA S MURTHY Asst. Professor
Ring Road, Marathalli, Bangalore – 560 103
DECLARATION
I hereby declare that the project report entitled “ONLINE CAR SHOWROOM MANAGEMENT ” was prepared by me during the year 2019-2020 and 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: Signature of the Candidate
Place: NewHorizonCollege BALAKRISHNA. P
(Marathalli) [USN: 17VFSB7008] CERTIFICATE
This is to certify that the project report entitled “ONLINE CAR SHOWROOM MANAGEMENT ” Submitted by BALAKRISHNA. P [17VFSB7008]. 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 2017-18.
ProjectGuide Head of theDepartment Ms. ANJANA S MURTHY Mr. Nagaraju K
Signature of theExaminers
1.
2. 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 MrNagaraju K, Head-Computer science 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 Mrs. Anjana S Murthy, Asst. Professor, Department of Computer Science, 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 projectreport
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.
4
5
INDEX CHAPTER CONTENTS PAGE NO. 01. INTRODUCTION 1-3 1.1 Abstract 1 1.2 Problem Statement 2 1.3 Module Description 3 02. SYSTEM ANALYSIS 5-31 2.1 Introduction to System Analysis 5 2.1.1 Existing System 5 2.1.2 Proposed System 6 2.2 Software Requirement 8 Specification(SRS) 2.3 Hardware Requirements 9 2.4 Software Requirements 9 2.5 Introduction to HTML 10 2.6 Introduction to JavaScript 13 2.7 Introduction to Servlet 18 2.8 Introduction to Java Server page(JSP) 22 2.9 Introduction to My SQL 31 03. SYSTEM DESIGN 33-53 3.1 Table Structure 33 3.2 Data Flow Diagram 37 3.3 Form Design 43 04. CODING AND DEVELOPMENT 54-102 4.1 Source Code 54 05. TESTING AND IMPLEMENTATION 103- 105 5.1 Introduction to Testing 103 5.2 Types of Testing 104 06. CONCLUSION AND FUTURE 106 ENHANCEMENT 07. BIBLIOGRAPHY 107
6
1. INTRODUCTION TO THE PROJECT
1.1. Abstract:-
Vehicle showroom Management System Project provides solution for showrooms for organizing data using software application. This web application helps administrator to update data in step by step process while selling vehicle to customer. Using this system management team can update customers information, vehicle information, payment details, Insurance details, take orders..Etc. Vehicle showroom software is presently used in car showrooms for computerizing entire system. This software package includes inventory management module, daily management details, image uploads, sales reports. There is no other scripting or server end management for this system.
1.2. Problem Statement:- For most people a car is a very important purchase decisions and with modern lifestyles it has become a necessity. Today people have many choices when it comes to cars but the basic experience is about the same. All cars are equally reliable and offer material standards matching their class. This makes it easy for consumers to purchase a car without even seeing it. In some places it is not possible to view a car at the showroom before purchase due to non – availability of showroom cars or delays in production. This system will allow users to easily purchase cars from dealers on a web – based interface. The car manufacturer will be required to upload all the promotional material for the car such as pictures, videos, interviews, etc. All details about features, specifications and models will also be available. Links to reviews by external reviewers can be accessed by users. Besides the promotional photos the manufacturer will be required to take photos of the different colors of the car in a prescribed background, so as to allow users to compare the car with other cars. Users will be able to see pictures of each trim level of the car and this will help them make an informed choice. After choosing a car, the user will be allocated a sales representative at their closest dealership. Users will then have the option to opt for exchange offers where they sell their current car to the dealership for discounts on the new car. The dealership will request specific photos and video clips to ascertain the quality of the car and set a buyback price accordingly. The user will also have the option to finance their purchase with the dealership’s partner banks. After all these formalities are completed an official order will be placed and computerized receipts
7 will be generated. This makes it easy for consumers to purchase a car without even seeing it. In some places it is not possible to view a car at the showroom before purchase due to non – availability of showroom cars or delays in production.
1.3. Modules Description:-
1. LOGIN
2. SIGNUP
3. HOME
4. BRANDS
5. CONTACT
6. ADMIN
7. CARS
8. ADD STOCK
9. ORDERS
1. LOGIN
- Here the user can log into their account.
2. SIGNUP
- Here the user can register new account.
3. HOME
- Here the user can look into various options and menus.
4. BRANDS
- Here the user can select among different brands.
5. CONTACT
- Here the user contact or leave a message for the admin.
6. ADMIN
- Here the admin can perform various operations.
8
7. CARS
- Here the admin can look into stock.
8. ADD STOCK
- Here the admin new stock of cars.
9. ORDERS
- Here the admin can look all the bookings.
9
2.System Analysis
2.1.1 Existing System
The existing system of car booking is solely done at the car showroom. Due to space constraints, car showrooms are generally placed at the outskirts of the city and new customers will have to make repeated journeys to complete all the formalities. Human error is prevalent in this system because sales representatives try to make the task easier by filling in some parts of the form without troubling the customer. A new customer is constantly anxious about the car delivery and also has to search different avenues for bank loans and selling their old car.
2.1.1 Proposed System This system will make the whole process user friendly. Dealerships need not be placed close to the customers as customers only need to visit it once to collect the car. Users can check the system at any time to prevent errors and sales representatives need not be troubled about keeping the customer informed. All bank formalities and car exchanges can be completed via the system itself. Advantages
. It provides a direct connection with the donors. . It also provides the important facts. . It also provides details of upcoming camps. . It is easy to use. . Admin can view request report which can be helpful for decision making.
2.2. Software Requirements specification
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
10
2.3. Hardware requirements
Processor : Intel
Ram : 512 or More
Hard Disc : 40 GB or More
Monitor : LCD or LED
Keyboard : RS/32 or USB/normal
Mouse : compatible mouse
2.4. Software Requirement Specification
Front End : HTML,CSS.
Back End : PHP ,My Sql
Web server : Xampp
Operating System : Windows 7
Tool for IDE : Sublime 2
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] 11
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]
2.4.1. 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 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.5. INTRODUCTION TO HTML
Hypertext Mark-up Language (HTML) is the standard mark-up language for creating webpage sand 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 web server or 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, images and other objects, such as interactive forms, may be embedded into the rendered page. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other
12 items. HTML elements are delineated by tags, written using angle brackets. Tags such as and introduce content into the page directly. Others such as
...
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 behavior and content of web pages. Inclusion of CSS defines the look and layout of content. 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 hypertext system. 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 encyclopedia 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 SGML guide, 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 command developed 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
13 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]
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 HTML 3.2was published as a W3C Recommendation. It was the first version developed and standardized
14 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 element were 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 favor 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]
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. 15
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)
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
16 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]
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
17 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]
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]
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]
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, therefore, would be more accurately characterized as an XHTML-inspired new language than an update to XHTML 1.x. [4]
An XHTML syntax, known as "XHTML5.1", is being defined alongside HTML5 in the HTML5 draft.\l " [4]
18
2.5.1. INTRODUCTION Cascading 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]
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
19
CSS was first proposed by Håkon Wium 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 Viola WWW 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 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]
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 Dave Raggett's Arena 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]
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
20
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 Lilley of 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 were started in 1998, are still under development as of 2014. [5]
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]
2.6. INTRODUCTION 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 Rasmus Lerdorf 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 acronym PHP: 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 stand alone graphical applications.[1]
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
21
PHP interpreter as a de facto standard. Since 2014 work has gone on to create a formal PHP specification.[3]
HISTORY Rasmus Lerdorf(left), who wrote the original Common Gateway Interface (CGI) component, together with Andi Gutmans (middle) and Zeev Suraski (right), who rewrote the parser that formed PHP 3.[2]
PHP development began in 1995 when Rasmus Lerdorf wrote 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 Use net discussion 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]
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
22
Zeev Suraski and Andi Gutmans rewrote the parser in 1997 and formed the base of PHP 3, changing the language's name to the recursive acronym PHP: 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]
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]
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]
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 23 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] 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]
The foundation of PHP 7 is a PHP branch that was originally dubbed PHP next generation (phpng). It was authored by Dmitry Stogov, Xinchen Hui 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 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]
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]
24
2.7. INTRODUCTION MySQL
MySQL is written in C and 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]
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]
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 organizations 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]
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
25
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.
A set of SQL Mode options to control runtime behaviour, including a strict mode to better adhere to SQL standards.[1]
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
26
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, cMerge, 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.
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]
27
3 . System Design
3.1 Table description
Admin
Column Type Null Constraints Details
Primary This contains the admin_id int(11) No key/auto unique id increment
admin_name varchar(200) No NULL This contains the name
admin_pass varchar(200) No NULL This contains the password
Car
Column Type Null Constraints Details
Primary key/auto This contains the chassis_number int(11) No increment chassis number
This contains the model model int(11) No NULL number
color varchar(20) Yes NULL This contains the color
28
Customer
Column Type Null Constraints Details
Primary This contains the unique c_id int(11) No key/auto customer id increment
name varchar(30) No NULL This contains the name
email varchar(250) No NULL This contains the email id
pass varchar(250) No NULL This contains the password
phone varchar(100) No NULL This contains the phone number
address varchar(20) No NULL This contains the address
Dealership
Column Type Null Constraints Details Primary This contains the unique d_id int(11) No key/auto dealer id increment
name varchar(30) No NULL This contains the name
Manufacturer
Column Type Null Constraints Details Primary This contains the unique m_id int(11) No key/auto id increment
name varchar(25) No NULL This contains the name
29
Model
Column Type Null Constraints Details Primary This contains the model model int(11) No key/auto number increment This contains the unique model m_id int(11) No NULL id
name varchar(20) No NULL This contains the model name year year(4) No NULL This contains the model year This contains the basic basic_spec varchar(200) No NULL specification.
Sale2
Column Type Null Constraints Details Primary This contains the unique sale_id int(11) No key/auto sales id increment
This contains the unique customer_id int(11) No NULL customer id
carmodel varchar(100) No NULL This contains the car model ordertime datetime No NULL This contains the order time.
30
Data flow diagram
31
3.3 Form Design
1. LOGIN
2. SIGNUP
32
3. HOME
4. BRANDS
33
5. CONTACT
6. ADMIN
34
7. CARS
35
8. ADD STOCK
36
9. ORDERS
4.1 SOURCE CODE
37
INDEX.PHP
div class="header">