Apollo Tyre

PROJECT REPORT
ON
APOLLO TYRE
PROJECT REPORT SUBMITTED IN PARTIAL
FULFILLMENT OF THE REQUIREMENT OF
BACHELOR OF BUSINESS ADMINISTRATION
Under the guidance of
MR. AMANDEEP SINGH
(Assistant Professor)
By:
SRI GURU TEGH BAHADUR INSTITUTE OF

MANAGEMENT &INFORMATION TECHNOLOGY
(Affiliated to GGSIP University Delhi)
(2012-2015)
DECLARATION
I hereby declare that the project work entitled APOLLO TYRE

submitted to the Guru Gobind Singh Indrapratha University is a
record of an original work done by me under the guidance of
Mr. AMANDEEP SINGH, faculty member, Sri Guru Tegh Bahadur
Institute of Management & Information Technology.
.............................................
Signature of the scholar
Place: Delhi
Date:
CERTIFICATE
This is to certify that SHUBHAM TYAGI student of Sri Guru Tegh
Bahadur Institute of Management & Information Technology of course
BBA Batch (2011-2014), has completed her research work titled
APOLLO TYRE under my guidance and supervision .The work
submitted is genuine and authentic.
.
Signature of Director
Prof. (Dr) P.L. Sethi
.
Signature of H.O.D
Dr Bipasha Chaudhary
...
Signature of Guide
Ms. AMANDEEP SINGH
Assistant Professor
....
Place: Delhi
Signature of Scholar
Date:
ACKNOWLEDGEMENT
With profound sense of gratitude and regard, I express my sincere thanks
to my guide and mentor Mr. AMANDEEP SINGH for his valuable
guidance and the confidence she instilled in me, that helped me in the
successful completion of this project report. Without her help, this project
would have been a distant affair, her thorough understanding of the
subject and professional guidance was indeed of immense help to me. I
am also thankful to my HOD Ms. Bipasha Chaudhary.
I am also greatly thankful to the faculty members of our institute who cooperated with me and gave me their valuable time.
..
Signature of the scholar
Place: Delhi
Date:
CONTENTS
S. No.
1
Title
Page No.
INTRODUCTION
1.1.
What is html?
1.2.
Advantages of html
1.3.
Disadvantages of html
1.4
Need for system
SYSTEM REQUIREMENT ANALYSIS
2.1.
Project Category
2.2.
Methodology adopted for project
2.3.
Design Constraints
2.4
Software System Attributes
2.5
Features of the system
2.6
System Requirements
SYSTEM ANALYSYS & METHODOLOGY ADOPTED
15
3.1.
Use Case Diagrams
16
3.2
Data Flow Diagram
19
3.2.
Entity Relationship Diagram
21
3.3
Normalization
24
SOFTWARE DESIGN
26
TEST REPORT
29
5.1
Unit Testing
30
5.2
Integration Testing
31
5.3
Functional Testing
31
5.4
System Testing
31
ROLES & RESPONSIBILITIES
34
CONCLUSION & ACHIEVEMENTS
36
APPENDIX
Screen shots
Coding
37
BIBLIOGRAPHY
73
LIST OF FIGURE
Figure
No.
Title
Page No.
Water Fall Model
Use Case Diagram
19
DFD
20
Layout Design
28
Home page.html
38
Header logo.html
29
Header.html
30
Presence.html
44
Sustainability.html
46
10
Products.html
33
11
Corporate social responsbilities.html
52
12
Tyre care.html
55
13
Safety at apollo.html
58
14
Tyre markings.html
61
15
Maintenance.html
64
16
Buying guide.html
69
CHAPTER- 1
INTRODUCTION
CHAPTER - 1
INTRODUCTION
1.1. What is html?
Hyper text markup language is the main markup language for displaying
web pages and other information that can be displayed in a web browser.
HTML is written in the form of HTML elements consisting of tags
enclosed in angle brackets (like <html>), within the web page content.
HTML tags most commonly come in pairs like <h1> and </h1>, although
some tags, known as empty elements, are unpaired, for example <img>.
The first tag in a pair is the start tag, the second tag is the end tag (they
are also called opening tags and closing tags). In between these tags web
designers can add text, tags, comments and other types of text-based
content.
1.2. Advantages of html

The basic format that is utilized on the World Wide Web is HTML. To
display web pages with a broad range of colors, shapes and objects,
HTML is used. In developing, the following the advantages of using
HTML:
1.
Usage is easy.
2.
Syntax is loose (Flexibility help complying with standards).
3.
If not all, it is supported on almost all browsers.
4.
Flexibility is high in HTML.
5.
If not on all websites, it has been established on most websites and

is used widely.
6.
It can also be used increasingly for data storage as it is like XML

syntax.
1.3. Disadvantages of html

1.
It can created only static and plain pages
2.
Need to write lot of code
3.
Security features are not good
4.
If we need to write long code for making a webpages than it

produce some complexity
1.4
Need for system
The system has been prepared towards the fulfillment of the goals of
Bachelor of Business Administration. The project has been prepared
considering all the relevant aspects stated. The project is an approach to
provide knowledge in an easy to access manner. The website thus created
is easy to operate and provides a fair degree of knowledge regarding the
subject as well.
Our project is an attempt to provide some knowledge regarding the topic
in an easy to access and a convenient way. Also it provides information
that easily understandable.
The main objectives of this project are as follows:
1. Understand the importance of the web as a medium of
communication
2. Understand the principles of creating an effective web page,

including as in depth consideration of information architecture.
3. Become familiar with graphic design principles that relates to web
design and learn how to implement these theories into practices.
4. Develop skills in analyzing the usability of a website.
5. Learn the language of the web: HTML & CSS.
6. Be able to embed social media content into web pages.
7. Implement and understand how to interpret basic web analytics.
CHAPTER-2
SYSTEM
REQUIREMENT
ANALYSIS
CHAPTER - 2
SYSTEM REQUIREMENT ANALYSIS
2.1. Project Category
The main aim to design this project is to provide graphical user interface
that helps the user to access information without any complexity and with
minimum operation. We categorize this project for commercial usage.
This document also describes the various interfaces i.e. the hardware,
software and the user interfaces. Along with that the document also
describes the various functions and some general constraints. This project
is cost efficient as well as highly optimized as per the requirement of user.
Assumptions and Dependencies:

We assume all users have basic knowledge. We also assume that the users
will be given software training, documentation and reference material
Future:
The doors for the amendments and improvements are always wide to any
system. In order to get better services out of it; desire modification can be
made to the system without much effort. As and when required new
modules can easily be incorporated into existing system. But this is sure
that provided system does not show any problem.
2.2. Methodology adopted for project

Methodology is generally a guideline system for solving a problem, with
specific components such as phases, tasks, methods, techniques and tools.
It can be defined also as follows:
1.
"The analysis of the principles of methods, rules, and postulates

employed by a discipline";
2.
"The systematic study of methods that are, can be, or have been
applied within a discipline"
3.
"The study or description of methods".
A methodology can be considered to include multiple methods, each as

applied to various facets of the whole scope of the methodology.
We adopted methodology of water fall model:
Fig. 1: Water Fall Model
The waterfall model is a sequential design process, often used in

software development processes, in which progress is seen as flowing
steadily downwards ( like a waterfall ) through the phases of
Conception, Initiation, Analysis, Design, Construction, Testing,
Production/Implementation, and Maintenance.
The waterfall development model originates in the manufacturing and
construction industries; highly structured physical environment in which
after the fact changes are prohibitively costly, if not impossible. Since no
formal software development methodologies existed at the time, this
hardware-oriented model was simply adapted for software development.
The first known presentation describing use of similar phases in software
engineering was held by Herbert D. Benington at Symposium on
advanced programming methods for digital computers on 29 June 1956.
This presentation was about the development of software for SAGE. In
1983 the paper was republished with a foreword by Benington pointing
out that the process was not in fact performed in a strict top down
fashion, but depended on a prototype.
2.3. Design Constraints

In our professional training design phase we have come across
following constraints:
Technology-We have used html for our project. Regarding it we
have to be careful about following things:o Fonts-We have to use fonts that are properly visible.
o Forms-Number of forms used in our project are need to be
less to avoid complexity
o GUI- User interface should be easy to operate.
Requirements-While designing we need to change design of project
according to requirements of library
Policies of institute- according to new policies of institute. We need
to change our modules
2.4 Software System Attributes

There are following software system attributes:
Maintainability
Our
software
is
maintainable
according
toenvironmental changes
Dependability
Our software is dependable on adobe, dream weaver
and vvscipt
Performance
Our software performs in a efficient manner i.e.; it is
User friendly
Lines Of Code
2.5 Features of the system

Sends e-mails (if enabled and internet is available) to the newly
registered members of the system as a notification and also sends
e-mails in different modules.
Maximum amount of training is required to use the system.
Saves the errors occurred in the system in a file that can be used to
troubleshoot the problems.
It is very user friendly
2.6
System Requirements
To be used effectively, all computer software needs certain hardware components or

software resources to be present on computer the perquisites are known as system
requirements. The MIS project requires a certain minimum system requirement
HARDWARE
128 MB of RAM or higher recommended (64 MB minimum supported).
Super VGA (1024 X768) or higher resolution video adapter and monitor.
Keyboard and Microsoft mouse or compatible pointing device.
SOFTWARE
OS: Windows XP minimum or higher.
Internet Explorer 8
LANGUAGE
Hyper Text Mark up Language(HTML)
Technologies used:
FRONT END:
User interface or that part of a software of website that a user sees on the
screen, and acts on to enter commands or to access other parts of the
software or website is known as front end.
HTML/FRONT PAGE
It is front page of the website
Features
Some of the features in the last version of FrontPage include:
FrontPage 2003 consists of a Split View option to allow the user to code
in Code View and preview in Design View without the hassle of
switching from the Design and Code View tabs for each review.
Dynamic Web Templates (DWT) were included for the first time in
FrontPage 2003 allowing users to create a single template that could be
used across multiple pages and even the whole Web site.
Interactive Buttons give users a new easy way to create Web graphics for
navigation and links, eliminating the need for a complicated imageediting package such as adobe Photoshop.
The accessibility checker gives the user the ability to check if their code
is standards-compliant and that their Web site is easily accessible for
people with disabilities. An HTML optimizer is included to aid in
optimizing code to make it legible and quicker to process.
Intellisense, which is a form of auto completion , is a key feature in
FrontPage 2003 that assists the user while typing in Code View. When
working in Code View, Intelligence will suggest tags and/or properties for
the code that the user is entering which significantly reduces the time to
write code. The Quick Tag Editor shows the user the tag they are
currently in when editing in Design View. This also includes the option to
edit the specific tag/property from within the Tag Editor.
Code Snippets give users the advantage of creating snippets of their
commonly used pieces of code allowing them to store it for easy access
whenever it is next needed.
FrontPage 2003 includes support for programming in ASP.Net a server
side, scripting language that adds interactivity to Web sites and Web
pages.
FrontPage 2003 includes support for macros in VBA
SCRIPTING LANGUAGE
A scripting language or script language is a programming language
thatsupports the writing of scripts. Environments that can be automatedthrough
scripting include software applications, web pages within a webbrowser, the
shells of operating systems (OS), and several generalpurpose and domain-
specific languages such as those for embeddedsystems. Scripting is usually a

property of the primary implementations ofa language, rather than a language
per se, although many languages arenot very suited to this kind of
implementation. Forexample, C++ interpreters do exist, but C++ is generally
not considered ascripting language, as not only are these implementations
rarely used, butthe time taken to write a script in C++ would be far in advance
of thatrequired to write in a language like Python.
Typically, a scripting language is characterized by the following

properties:
Ease of use. Scripting languages are intended to be very fast to pick up
and author programs in. This generally implies relatively simple syntax
&semantics.
OS facilities - especially file system and related, built in with easy

interfaces. Scripting is usually aimed at desktop, limiting the portability
needs of the pre-built libraries.
Interpreted from source code - to give the fastest turnaround from script
to execution. On a desktop, the performance of even a slow interpreter is
often non-problematic. In comparison, non-scripting languages intended
for large programs are often precompiled in at least some sense for
superior performance.
Relatively loose structure. It would be difficult to use java as a scripting
language due to the rules about which classes exist in which files contrast to Python, where it's possible to simply define some functions in
a file.
VBSCRIPT
VBScript (Visual Basic Scripting Edition) is an ActiveScripting language
developed by Microsoft that is modeled on VisualBasic. It is designed as a
lightweight language with a fast interpreter foruse in a wide variety of
Microsoft environments. VBScript usesthe Component Object Model to access
elements of the environmentwithin which it is running; for example, the
FileSystemObject (FSO) isused to create, read, update and delete files
JAVA SCRIPT
A scripting language developed by Netscape to enable Web authors todesign
interactive sites. Although it shares many of the features andstructures of the
full Java language, it was developed independently.Java script can interact with
HTML source code, enabling Web authors tospice up their sites with dynamic
content. JavaScript is endorsed by anumber of software companies and is an
open language that anyone canuse without purchasing a license. It is supported
by recent browsers fromNetscape and Microsoft, though Internet Explorer
supports only a subset,which Microsoft calls Jscript.
BACK END:
Back end languages are the languages used to write the parts of theprogram
used to interact with the hardware. Thus game engines, browserengines and so
forth are often written in C++ because first it is acompiled language which
provides straightforward tools for modellingany device logically you don't
already have a driver for and because it hasmany features of data security
which make it easier to keep track of manyvariables.
DATABASE
Databaseare designed to offer an organized mechanism for storing,
managing and retrieving information. They do so through the use of
tables. If youre familiar with spreadsheets like Microsoft Excel, youre
probably already accustomed to storing data in tabular form. Its not

much of a stretch to make the leap from spreadsheets to databases.
CHAPTER-3
SYSTEM ANALYSYS &
METHODOLOGY
ADOPTED
CHAPTER - 3
SYSTEM ANALYSYS & METHODOLOGY
ADOPTED
This chapter will focus on the design of the system using diagrams to
illustrate graphically certain sections of the software system.
3.1. Use Case Diagrams
A use case diagram at its simplest is a representation of a user's
interaction with the system and depicting the specifications of a use case.
A use case diagram can portray the different types of users of a system
and the various ways that they interact with the system. This type of
diagram is typically used in conjunction with the textual use case and will
often be accompanied by other types of diagrams as well.
While a use case itself might drill into a lot of detail about every
possibility, a use-case diagram can help provide a higher-level view of the
system. It has been said before that "Use case diagrams are the blueprints
for your system". They provide the simplified and graphical
representation of what the system must actually do.
Use case diagrams depict:
Use cases. A use case describes a sequence of actions that provide
something of measurable value to an actor and is drawn as a
horizontal ellipse.
Actors. An actor is a person, organization, or external system that
plays a role in one or more interactions with your system. Actors
are drawn as stick figures.
Associations. Associations between actors and use cases are

indicated in use case diagrams by solid lines. An association exists
whenever an actor is involved with an interaction described by a
use case. Associations are modeled as lines connecting use cases
and actors to one another, with an optional arrowhead on one end
of the line. The arrowhead is often used to indicating the direction
of the initial invocation of the relationship or to indicate the
primary actor within the use case. The arrowheads are typically
confused with data flow and as a result I avoid their use.
System boundary boxes (optional). You can draw a rectangle
around the use cases, called the system boundary box, to indicates
the scope of your system. Anything within the box represents
functionality that is in scope and anything outside the box is not.
System boundary boxes are rarely used, although on occasion I
have used them to identify which use cases will be delivered in
each major release of a system.
Packages (optional). Packages are UML constructs that enable
you to organize model elements (such as use cases) into groups.
Packages are depicted as file folders and can be used on any of the
UML diagrams, including both use case diagrams and class
diagrams. I use packages only when my diagrams become
unwieldy, which generally implies they cannot be printed on a
single page, to organize a large diagram into smaller ones.
Use case Diagram :
OWNER
CUSTOMER
HOME
VISION
PRESENCE
FEEDBACK
Fig- 2 Use case diagram
3.2. Data Flow Diagram

A data flow diagram (DFD) is a graphical representation of the "flow" of
data through an information system, modeling itsprocess aspects. Often
they are a preliminary step used to create an overview of the system
which can later be elaborated. DFDs can also be used for
the visualization of data processing (structured design).
A DFD shows what kinds of information will be input to and output from
the system, where the data will come from and go to, and where the data
will be stored. It does not show information about the timing of
processes, or information about whether processes will operate in
sequence or in parallel (which is shown on a flowchart).
It is common practice to draw the context-level data flow diagram first,
which shows the interaction between the system and external agents
which act as data sources and data sinks. This helps to create an accurate
drawing on the context diagram. The system's interactions with the
outside world are modelled purely in terms of data flows across
the system boundary. The context diagram shows the entire system as a
single process, and gives no clues as to its internal organization.
Fig. 3: DFD
This context-level DFD is next "exploded", to produce a Level 1 DFD

that shows some of the detail of the system being modeled. The Level 1
DFD shows how the system is divided into sub-systems (processes), each
of which deals with one or more of the data flows to or from an external
agent, and which together provide all of the functionality of the system as
a whole. It also identifies internal data stores that must be present in order
for the system to do its job, and shows the flow of data between the
various parts of the system.
Data flow diagrams were proposed by Larry Constantine, the original

developer of structured design, based on Mattew and Peter"data flow
graph" model of computation.
3.3. Entity Relationship Diagram

It is a detailed logical representation of data for an organization and uses
three main constructs.
An entity may be defined as a thing which is recognized as being capable
of an independent existence and which can be uniquely identified. An
entity is an abstraction from the complexities of a domain. When we
speak of an entity, we normally speak of some aspect of the real world
which can be distinguished from other aspects of the real world.[4]
An entity may be a physical object such as a house or a car, an event such
as a house sale or a car service, or a concept such as a customer
transaction or order. Although the term entity is the one most commonly
used, following Chen we should really distinguish between an entity and
an entity-type. An entity-type is a category. An entity, strictly speaking, is
an instance of a given entity-type. There are usually many instances of an

entity-type. Because the term entity-type is somewhat cumbersome, most
people tend to use the term entity as a synonym for this term.
Entities can be thought of as nouns. Examples: a computer, an employee,
a song, a mathematical theorem.
A relationship captures how entities are related to one another.
Relationships can be thought of as verbs, linking two or more nouns.
Examples: an ownsrelationship between a company and a computer,
a supervises relationship between an employee and a department,
a performs relationship
between
an
artist
and
song,
a proved relationship between a mathematician and a theorem.

The
model's
linguistic
aspect
described
above
is
utilized
in
the declarative database query language ERROL, which mimics natural

language constructs. ERROL's semantics and implementation are based
on reshaped relational algebra (RRA), a relational algebra which is
adapted to the entityrelationship model and captures its linguistic aspect.
Entities and relationships can both have attributes. Examples:
an employee entity might have a Social Security Number (SSN) attribute;
the proved relationship may have adate attribute.
Every entity (unless it is a weak entity) must have a minimal set of
uniquely identifying attributes, which is called the entity's primary key.
Entityrelationship diagrams don't show single entities or single instances
of relations. Rather, they show entity sets and relationship sets. Example:
a particular song is an entity. The collection of all songs in a database is
an entity set. The eaten relationship between a child and her lunch is a
single relationship. The set of all such child-lunch relationships in a
database is a relationship set. In other words, a relationship set

corresponds to a relation in mathematics, while a relationship corresponds
to a member of the relation.
Certain cardinality constraints on relationship sets may be indicated as
well.
Entities
It is a fundamental thing about which data may be maintained. Each
entity has its own identity.
Entity Type is the description of all entities to which a common definition
and common relationships and attributes apply.
3.4
Normalization
Normalization usually involves dividing a database into two or more

tables and defining relationships between the tables. The objective is to
isolate data so that additions, deletions, and modifications of a field can
be made in just one table and then propagated through the rest of the
database via the defined relationships.
There are three main normal forms, each with increasing levels of
normalization:
First Normal Form (1NF): Each field in a table contains different
information.
Second Normal Form (2NF): Each field in a table that is not a
determiner of the contents of another field must itself be a function of the
other fields in the table.
Third Normal Form (3NF): No duplicate information is permitted.
CHAPTER-4
SOFTWARE DESIGN
CHAPTER - 4
SOFTWARE DESIGN
Software design is the process by which an agent creates a specification
of a software artifact, intended to accomplish goals, using a set of
primitive components and subject to constraints. Software design may
refer to either "all the activities involved in conceptualizing, framing,
implementing, commissioning, and ultimately modifying complex
systems" or "the activity following requirements specification and
beforeprogramming, as ... a stylized software engineering process."
Software design usually involves problem solving and planning
a software solution.
This
includes
both
low-level
component
and algorithm design and high-level, architecture design.

Software design is the process of implementing software solutions to one
or more set of problems. One of the important parts of software design is
the software requirements analysis (SRA). It is a part of the software
development
process that
lists specifications used
in software
engineering. If the software is "semi-automated" or user centered,

software design may involve user experience design yielding a story
board to help determine those specifications. If the software is
completely automated (meaning no user or user interface), a software
design may be as simple as a flow chart or text describing a planned
sequence of events. There are also semi-standard methods like Unified
Modeling Language and Fundamental modeling concepts. In either case,
some documentation of the plan is usually the product of the design.
Furthermore, a software design may beplatform-independent or platformspecific, depending on the availability of the technology used for the
design.
Software design can be considered as creating a solution to a problem in

hand with available capabilities. The main difference between Software
analysis and design is that the output of a software analysis consist of
smaller problems to solve. Also, the analysis should not be very different
even if it is designed by different team members or groups. The design
focuses on the capabilities, and there can be multiple designs for the same
problem depending on the environment that solution will be hosted. They
can be operations systems, webpages, mobile or even the new cloud
computing paradigm. Sometimes the design depends on the environment
that it was
developed, whether
if
it
is created from with
reliable frameworks or implemented with suitable design patterns.

When designing software, two important factors to consider are its
security and usability.
HOME page>> welcome to your site
On clicking the home page a page will open which will tell about the site
and training
At homepage we will find the links of
Home
Vision And Values
Presence
Sustainability
Products
Feedback
LAYOUT OF THE PROJECT
T
PSV
CEH
onESruiO
Y
oseM
vA
m
R
iLdts
Em
urTaeo
ci
noH
C
intc
A
sae
tm
R
Eyebn
nid
tl
iV
ta
yl
u
e
s
Fig. 5: Layout Plan
CHAPTER-5
TEST REPORT
CHAPTER - 5
TEST REPORT
Executing a program with the intent of finding errors is called testing.
Testing is vital to the success of any system. Testing is done at different
stages within the development phase. System testing makes a logical
assumption that if all parts of the system are correct, the goals will be
achieved successfully. Inadequate testing or no testing at all leads to
errors that may come up after a long time when correction would be
extremely implementation. The testing of the system was done on both
artificial and live data. In order to test data test cases are developed.
Following are the various methods that are employed for testing:
5.1. Unit Testing

In unit testing the module is tested independently. It is done to test that
the module does satisfy the functional specification. This is done to check
syntax and logical errors in programs. At the time of preparation of
technical specifications, unit test data was also prepared. The coding for
that program was considered after verifying its output against this test
data.
Following are the unit testing methods:
In Conditional Testing, the logical conditions that are given in the
module were checked to see whether they satisfy the functionality
of the module. This is done by using the test data was prepared.
In Loop Testing, different loops in the module like nested loops

were tested using the data. Attempts to execute the loops to their
maximum range are done.
5.2 Integration Testing

In Integration testing whole system was checked when all the
individual modules were integrated together in order to test
whether the system is performing as according to the
requirements specified. Interface errors if any were corrected.
Test data was prepared was fed into the system to check whether
the system fails to detects an error.
5.3.
Functional Testing
This is done for each module/sub module of the system.
Functional testing serve as a means of validating whether the
functionality of the system confers the original user requirement
i.e. does the module do what it was supposed to do? Separate
schedules were made for functional testing. It involves
preparation of test data, writing of test cases, testing for
conformance to test cases and preparation of bugs listing for
non-conformities.
5.4. System Testing

System testing is done when the entire system has been fully
integrated. The purpose of the system testing is to test how the
different modules interact with each other and whether the entire
system provides the functionality that was expected.
System testing consists of the following steps:
Program Testing
System Testing
System Documentation
User Acceptance Testing
CHAPTER-6
ROLES AND
RESPONSIBILITIES
CHAPTER 6
ROLES & RESPONSIBILITIES
Being the leader of my team I was given the following responsibilities:
Divide the work among the team members.
I was involved in requirement gathering with other team members .
I was responsible for coding, designing , implementation and unit

testing of modules.
I was involved in combining all modules of the professional

training website
CHAPTER-7
CONCLUSION AND
ACHIEVEMENT
CHAPTER - 7
CONCLUSION & ACHIEVEMENTS
The reason to have professional training system is to providing
professional courses, vocational training ,improve skills through internet
and institutions itself. it also saves time of students who do not want to
waste time going here and there.
The project is still going on. We have released the first stable version as
per our project schedule & the work on the next version is in progress.
Achievements
The project has been an excellent learning opportunity for me and
has helped me in understanding and developing a live project.

Technical Knowledge is something one can always get sitting at
home and devouring books. But being a part of a team which is working
on a deliverable Live Project means a lot more other things apart from the
technical knowledge gained.
I learnt to implement hardware devices in the system.
I learned its the team work and working in tandem with the team,
complimenting the team efforts that hold more priority than individual
skills.
I learned how important deadlines are, and that clients are like
gods, we just have to provide them what they want .The ultimate goal is
to meet clients requirements.
I learned to take responsibilities and to handle the work pressure.
CHAPTER-8
APPENDIX
CHAPTER 8
APPENDIX
FIG 8.1- HOMEPAGE.HTML
<html>
<head>
<title>apollo tyre</title>
</head>
<FRAMESET ROWS="24%,*">
<FRAMESET COLS="22%,*">
<FRAME SRC="LINKS HEADER.html" scrolling="no" noresize
name="CONTENTS" target="_self">
<FRAME SRC="HEADER.html" scrolling="no" noresize name="HEADING">
</FRAMESET>
<FRAMESET COLS="22%,*">
<FRAME SRC="LINKS PAGE.html" target="main" scrolling="no" noresize
name="LINK">
<FRAME name="main" SRC="MAIN PAGE CONTENTS.HTML"
scrolling="auto" noresize>
</FRAMESET>
</FRAMESET>
</html>
<html>
<head>
<title>LINKS </title>
</head>
<body background="Yellow.jpg">
<img src="apolloLogo.png" width="254" height="105" >

</BODY>
</html>
<html>
<head>
<title>header</title>
</head>
<body background = "red.jpg">
<div align="center">
<font face= "Matura MT Script Capitals" size="36" color="white">APOLLO
TYRES</font>
</div>
</body>
</html>
FIG 8.2- PRESENCE.HTML
<html>
<head>
<title>PRESENCE</title>
</head>
<body background="YELLOW.jpg" >
<BR>
<h1 align ="left"><font color =
"PURPLE"><marquee><u>PRESENCE</marquee></u></h1></font><br>
<center><img src="presence.jpg" align="CENTER"></center>

<br>
</font>
</body>
</html>
FIG 8.3- SUSTAINABILITY.HTML
<html>
<head>
<title>SUSTAINABILITY</title>
</head>
<BR>
"PURPLE"><marquee><u>Sustainability</marquee></u></h1></font><br>
<center><img src="sustaianability.jpg" align="CENTER"></center>

<FONT COLOR ="PURPLE" TYPE ="MONOTYPE COROSIVA" SIZE ="5" ><p
ALIGN ="left">
<br><br>
As an organisation, Apollo Tyres is committed towards creating values for its
stakeholder. And the crucial link here is building a sustainable business, driven by
strategic growth and responsible actions.
<br><br>
Apollo Tyres believes that to truly move up the value chain, it is critical to use fewer
natural resources to produce more. For a growing organisation, with a long-term focus
and commitment, it is critical to safeguard resources for the future even as it creates
value today. At Apollo, emphasis is laid on using natural resources cautiously and
with care.
<br><br>
In 2011, the company published its 1st Sustainability Report as per Global Reporting
Initiative Version 3. The disclosures and identified gaps have further enabled the
company to better define and evolve its internal systems relating to environmental and
social aspects. Bulk of this work pertains to energy, water, health and safety issues
across operations.
<br><br>
The companys systems and processes have made it possible for it to report at Level B
and the company is positive about achieving Level A across its operations in the
next 2 years.
<br>
<br>
</font>
</body>
</html>
FIG 8.4 - PRODUCTS.HTML
<html>
<head>
<title>SUSTAINABILITY</title>
</head>
<BR>
"PURPLE"><marquee><u>Sustainability</marquee></u></h1></font><br>
<center><img src="sustaianability.jpg" align="CENTER"></center>

ALIGN ="left">
<br><br>
As an organisation, Apollo Tyres is committed towards creating values for its
stakeholder. And the crucial link here is building a sustainable business, driven by
strategic growth and responsible actions.
<br><br>
Apollo Tyres believes that to truly move up the value chain, it is critical to use fewer
natural resources to produce more. For a growing organisation, with a long-term focus
and commitment, it is critical to safeguard resources for the future even as it creates
value today. At Apollo, emphasis is laid on using natural resources cautiously and
with care.
<br><br>
In 2011, the company published its 1st Sustainability Report as per Global Reporting
Initiative Version 3. The disclosures and identified gaps have further enabled the
company to better define and evolve its internal systems relating to environmental and
social aspects. Bulk of this work pertains to energy, water, health and safety issues
across operations.
<br><br>
The companys systems and processes have made it possible for it to report at Level B
and the company is positive about achieving Level A across its operations in the
next 2 years.
<br>
<br>
</font>
</body>
</html>
FIG 8.5- CORPORATE SOCIAL RESPONSIBILITIES.HTML
<html>
<head>
<title>csr</title>
</head>
<BR>
<h1 align ="left"><font color = "PURPLE"><marquee><u>CORPORATE SOCIAL
RESPONSIBILITIES</marquee></u></h1></font><br>
<img src="OVERVIEW.JPG">
ALIGN ="left">
<br>
<h2>Overview</H2>
Apollo Tyres Ltd's corporate social responsibility (CSR) philosophy stems from its
vision statement of "...continuously enhancing stakeholder value". The overall aim is
to add value to the lives of stakeholders, through not-for-profit initiatives, with the
objective of ensuring that all programmes and initiatives remain sustainable and
relevant. The company believes that if undertaken in the right spirit and process,
social initiatives can be a long term risk mitigator and help manage key business and
operational challenges. This framework clearly revolves around the principle of 3 Is
i.e. Involve, Influence andImpact stakeholders. Apollo Tyres Foundation is the body
which works dedicatedly towards achievement of these goals.
<BR><BR><BR>
<TABLE WIDTH="99%">
<TR>
<TD WIDTH="33%"><font color = "PURPLE" SIZE="5"><CENTER><a
href="health.html">HEALTH</a></CENTER></FONT></TD>
href="environment.html">ENVIRONMENT</a></CENTER></FONT></TD>
href="community.html">COMMUNITY</a></CENTER></FONT></TD>
</font>
</body>
</html>
FIG 8.6- TYRE CARE.HTML
<html>
<head>
<title>TYRE CARE</title>
</head>
<BR>
<h1 align ="left"><font color = "PURPLE"><marquee><u>TYRE
CARE</marquee></u></h1></font><br>
<img src="HEADER.JPG">
ALIGN ="left">
<br>
<h2>Overview</H2>
While it's common to overlook those four circles of rubber that your car rests on,
performing a few simple checks can yield better fuel economy and improved vehicle
handling.
<BR><BR>
Ensuring proper tyre care is important for many reasons other than reducing the
potential of a flat tyre or a blowout. In order to achieve optimum handling from your
vehicle, from everyday driving to making emergency maneuvers, tyre pressure needs
to be at the proper inflation level. Even a tyre that doesn't appear to be low on air can
result in reduced vehicle handling and excessive tread wear.
<BR><BR>
Although there is no alternative to using an air pressure gauge to check the inflation
levels, here are some indicators that can help quickly predict the health of your tyres.
<BR><BR>
<UL>
<LI>When driving down a straight, level road, check to see if the car pulls to one side
or the other. While this "pulling" may be caused by improper alignment, it may also
indicate a tyre issue especially if you are certain that the alignment is correct or if
the vehicle recently had an alignment service.
</LI><BR>
<LI>If the centre section of the tread is smooth, your tyres may be over-inflated.
Likewise, if the outside sections or edges of the tyre tread are worn or rounded, your
tyres may be under-inflated over a period of time and need attention.
</LI><BR>
<LI>Pay attention for any squealing sounds when turning a corner at normal speeds.
While this could be symptoms of other problems, they are frequently signs of
improperly inflated tyres.
</LI>
<BR>
</UL>
<BR><BR><BR>
<center><TABLE WIDTH="80%">
<TR>
href="Safety at Apollo.html">Safety at Apollo</a></CENTER></FONT></TD>
href="Tyre Markings.html">Tyre Markings</a></CENTER></FONT></TD>
href="Maintenance.html">Maintenance</a></CENTER></FONT></TD>
href="Buying Guide.html">Buying Guide</a></CENTER></FONT></TD>
</table>
</center>
</font>
</body>
</html>
FIG 8.7- SAFETY AT APOLLO.HTML
<html>
<head>
<title>SAFETY AT APOLLO</title>
</head>
<BR>
<img src="header_safetyat_apollo.JPG">
ALIGN ="left">
<br>
<h2>Safety at Apollo</H2>
<img src="safe_drive_logo.png"><br><br>
Safety is an inherent attribute of our products at Apollo. We also carry out activities to
inform and educate customers about the importance of tyre care and maintenance
under the Apollo Safe Drive initiative.
With customer safety at the core of our actions, Apollo Tyres is also a member of
TyreSafe a leading tyre safety organisation, dedicated to raising awareness about
the dangers associated with defective or illegal tyres.
<BR><BR><BR>
<TR>
<TD WIDTH="20%"><font color = "PURPLE" SIZE="5"><CENTER><a href="tyre
care.html">Overview</a></CENTER></FONT></TD>
</table>
</center>
</font>
</body>
</html>
FIG 8.8- TYRE MARKINGS.HTML
<html>
<head>
<title>TYRE MARKINGS</title>
</head>
ALIGN ="left">
<br>
<h2>Tyre Markings</H2>
<img src="tyre_ranking.png"><br><br>
This identifies the section width of the tyre, which is the measurement of the tyre
sidewall in millimeters - from where it touches the rim to where the tread begins.
<br><br>1 inch = 25.4 millimeters
<BR><BR><BR>
<TR>
</table>
</center>
</font>
</body>
</html>
FIG 8.9- MAINTAINENCE.HTML
<html>
<head>
<title>MAINTENANCE</title>
</head>
ALIGN ="left">
<br>
<h2>Maintenance</H2>
<h3> Air Pressure</h3>
The manufacturer of your vehicle specifies the suitable pressure to be maintained and
is measured in PSI or BAR pressure. It is important to check tyre pressure regularly.
Air from a tyre generally escapes at the rate of up to 2 pounds of air every month.
Loss of air pressure from a tyre is pronounced during warm weather, so more regular
checks are needed when temperatures rise.<br><br>
<b>Benefits of correct air pressure:</b>
<ul>
<li><b>Safety:</b> Tyres that are under inflated can overheat; and over inflated tyres
can lead to poor vehicle handling on the road.</li><br>
<li><b>Economy:</b> Over or under inflated tyres suffer more damage than those
with the correct pressure and need to be replaced more frequently. Vehicles with
under-inflated tyres have increased rolling resistance and require more fuel to
maintain the same speed.</li><br>
<li><b>Environment:</b> Correct tyre pressures help maintain optimum fuel
efficiency. This can equate to lower carbon dioxide (CO2) emissions from your
vehicle than those from a vehicle with incorrect tyre pressure. Thus by maintaining
the recommended air pressure in your tyres you contribute towards a cleaner
environment.</li>
</ul>
<b>Role of Valves:</b>
<ul>
<li>Valves help maintain tyre pressure and permit air to be added or

removed.</li><br>
<li>The valve in your wheel is a small but very important part of your vehicle as far
as safety and tyre life is concerned. It holds the pressure inside the tyre assembly and
is the access point to adjust your tyre pressure. A valve cap in good condition is also
essential as it provides a secondary seal and prevents dirt from getting inside. It is
recommended to have the valves replaced every time your tyres are
changed.</li><br>
</ul>
<h3>Alignment</h3>
If your car feels as though it's pulling to the left or right even though youre
steering in a straight line it could suggest a problem with your wheel alignment.
Incorrect alignment can result in rapid and irregular tyre wear and can even affect the
handling and safety of the vehicle.<br><br>
<b>Benefits of correct wheel alignment:</b><br>
<ul><li>30% increase in tyre mileage on an average</li><br>
<li>2% increase in fuel economy</li><br>
<li>Alignment ensures a vehicle is stable at high speeds</li><br>
<li>A vehicle that is properly aligned handles better and is safer to drive</li>
</ul>
<br>
Wheel alignment can be affected by driving against a pavement, hitting a pothole in
the road or by excessive wear to steering or suspension components. Alignment of
wheels and tyres to the specification required by your vehicle is an important way to
guarantee a smooth ride and to get the most out of your tyres.
<br><br>
The direction and angle at which tyres are set are both equally important. Wheel
alignment or 'tracking' involves checking the direction and angle against vehicle
manufacturers' specifications. These are often described as toe in, toe out, positive
camber or negative camber.
<br><br>
"Toe" refers to whether the front of the tyres are closer or further apart than the rear of
the tyres. Different types of vehicles need different toe settings to allow for the way
wheels pull either towards each other or apart.
<br><br>
"Camber" is the inward or outward tilt of a tyre. The camber is set by the vehicle
manufacturer, and can be affected by potholes in the road and may need to be adjusted
periodically.
<br><br>
Correct wheel alignment is achieved by adjusting a cars suspension and steering
components to ensure the wheels are perfectly aligned to deliver the least wear on the
tyres.
<h3>Balancing</h3>
One of the easiest ways to tell when something is not right with your tyres is from
behind the steering wheel. Vibration through the steering wheel can mean that a wheel
is out of balance, this results in premature wearing of suspension and steering
components, rotating parts and tyres.
<br><br>
Tiny weights are used to counterbalance the heaviest part of the tyre and wheel
assembly.
<br><br>
If these weights become loose, the wheel will wobble more at higher speeds
which will increase tyre wear and is potentially unsafe.
<br><br>
In such a situation you should have your wheels balanced on a wheel balancing
machine. The machine rotates the tyre and wheel assembly and automatically
calculates the weight and location of the balance counter weight.
<br><br>
Balanced wheels in a vehicle deliver a smoother ride and better wear from your tyres,
again saving you time and money.
<br><br>
<h3>Tread Wear</h3>
You must ensure that the tyres you are driving on have more than 1.6 mm of tread on
them.<br><br>
Most new tyres have about 8 mm of tread pattern when manufactured but as tyres
wear their ability to disperse water reduces. Tyres should be replaced before the tread
wears down to the level of the Tread Wear Indicators. This can be checked easily with
the help of a tread depth gauge or visiting your nearest Apollo dealer.<br><br>
Tread Wear Indicators are moulded into all major grooves of tyres in at least four
positions around the tyre. These indicators sit at least 1.6 mm above the bottom of the
grooves and should be examined regularly and should be replaced when at the
wearing limit.
<BR><BR><BR>
<center>
<TABLE WIDTH="100%">
<TR>
</table>
</center>
</font>
</body>
</html>
FIG 8.10- BUYING GUIDE.HTML
<html>
<head>
<title>Buying Guide</title>
</head>
ALIGN ="left">
<img src="header_buying.jpg">
<br>
<h2>Buying Guide</H2>
Tyres can be selected by keeping some of the following parameters in mind.
<ul><li><b>Original Size: </b>Every manufacturer provides a recommendation of
the size that is suited to the vehicle. You should know this before going shopping.
</li><br>
<li><b>Usage: </b>Tyres used on passenger cars vary in technology and construction
from those designed for SUVs or transport vans. So you should be sure of the type of
vehicle you need the tyres for, its variant or specific model. </li><br>
<li><b>Application: </b>The next step is to choose a tyre by its intended application.
Those to be used mostly on highways or city roads are built to provide a softer ride
than those that are better suited to off-roading or rough terrain usage, people
transportation, goods carriage and so on. </li><br>
<li><b>Pattern: </b>The tread pattern of a tyre decides its ability to channel water
away from the contact patch between the tyre and the road. The tread pattern also
plays a part in how much road noise is generated by the tyre due to air getting trapped
and expelled from those channels during running. </li><br>
<li><b>Technology:</b> Tubeless tyres are now the norm as they allow for greater
running distance in case of a puncture and allow for better control of the vehicle, by
minimising sudden loss of air pressure. </li><br>
</ul>
<BR><BR><BR>
<TABLE WIDTH="99%">
<TR>
href="maintenance.html">Maintenance</a></CENTER></FONT></TD>
href="Making of a Tyre.html">Making of a Tyre</a></CENTER></FONT></TD>
</font>
</body>
</html>
BIBLIOGRAPHY
Books consulted:1.
Kevin A. Siegel, Essentials of Dreamweaver 4: Skills & Drills

Training
2.
David R. Brooks, An Introduction to HTML and Java Script
3.
Shelly Woods, HTML - Introductory Concepts and Techniques
Websites and URLs: http://www.w3schools.com/html/html_intro.asp

http://www.w3.org/TR/REC-html40/intro/intro.html
Persons consulted:
Dr Bipasha Chaudhary (H.O.D S.G.T.B.I.M & I.T)
Mr. AMANDEEP SINGH (LECTURER, S.G.T.B.I.M & I.T)

Apollo Tyre

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Apollo Tyre

Загружено:

Авторское право:

Доступные форматы

PROJECT REPORT

SRI GURU TEGH BAHADUR INSTITUTE OF

I hereby declare that the project work entitled APOLLO TYRE

Need for system

SYSTEM REQUIREMENT ANALYSIS

Methodology adopted for project

Software System Attributes

Features of the system

SYSTEM ANALYSYS & METHODOLOGY ADOPTED

Use Case Diagrams

Data Flow Diagram

Entity Relationship Diagram

ROLES & RESPONSIBILITIES

CONCLUSION & ACHIEVEMENTS

Water Fall Model

Use Case Diagram

Corporate social responsbilities.html

1.2. Advantages of html

Syntax is loose (Flexibility help complying with standards).

If not all, it is supported on almost all browsers.

Flexibility is high in HTML.

If not on all websites, it has been established on most websites and

It can also be used increasingly for data storage as it is like XML

1.3. Disadvantages of html

It can created only static and plain pages

Need to write lot of code

Security features are not good

If we need to write long code for making a webpages than it

Need for system

2. Understand the principles of creating an effective web page,

Assumptions and Dependencies:

2.2. Methodology adopted for project

"The analysis of the principles of methods, rules, and postulates

"The study or description of methods".

A methodology can be considered to include multiple methods, each as

We adopted methodology of water fall model:

Fig. 1: Water Fall Model

The waterfall model is a sequential design process, often used in

2.3. Design Constraints

2.4 Software System Attributes

2.5 Features of the system

To be used effectively, all computer software needs certain hardware components or

128 MB of RAM or higher recommended (64 MB minimum supported).

Keyboard and Microsoft mouse or compatible pointing device.

OS: Windows XP minimum or higher.

Hyper Text Mark up Language(HTML)

specific languages such as those for embeddedsystems. Scripting is usually a

Typically, a scripting language is characterized by the following

OS facilities - especially file system and related, built in with easy

probably already accustomed to storing data in tabular form. Its not

Associations. Associations between actors and use cases are

Use case Diagram :

Fig- 2 Use case diagram

3.2. Data Flow Diagram

This context-level DFD is next "exploded", to produce a Level 1 DFD

Data flow diagrams were proposed by Larry Constantine, the original

3.3. Entity Relationship Diagram

an instance of a given entity-type. There are usually many instances of an

a proved relationship between a mathematician and a theorem.

the declarative database query language ERROL, which mimics natural

database is a relationship set. In other words, a relationship set

Normalization usually involves dividing a database into two or more

and algorithm design and high-level, architecture design.