Black Book Project 12

FLY WHEEL CAR CARE
INDEX
Chapte Contents Page No.
r No.
PRELIMINARY INVESTIGATION AND INTRODUCTION 8
01
1.1 Organizational Overview
1.2 Description of System
1.3 Limitation of present system
1.4 Proposed system and advantages.
1.5 Gantt chart
02 SURVEY OF TECHNOLOGY 14
2.1 Feasibility Study
2.2 Software and Hardware requirements
2.3Development Tools and Technology
2.3.1Front End
2.3.2Back End
2.3.3 Development Environment
03 REQUIREMENTS AND ANALYSIS 37
3.1 E-R Diagram
3.2 Use case Diagram & use case Description
3.3 Sequence Diagram/Collaboration Diagram
3.4Data Flow Diagram
3.5 Class Diagram
3.6 Activity Diagram
04 SYSTEM DESIGN 52
4.1 Data Dictionary (Table List)
4.2 Basic Modules
4.3 Test Cases Design
05 IMPLEMENTATION AND TESTING 60

5.1 Form Design
5.2 Coding
5.3 Test Reports
06 CONCLUSION AND FUTURE ENHANCEMENT 88
[1]
FLY WHEEL CAR CARE
07 BIBLOGRAPHY AND REFERENCES 92

7.1 Websites
7.2 Books
[2]
FLY WHEEL CAR CARE
01.
PRELIMINARY
INVESTIGATION
AND
INTRODUCTION
[3]
FLY WHEEL CAR CARE
1.1 Organizational Overview

FLY WHEEL CAR CARE car service provider deals with
complete cars solution for maintenance and repairs with the help of our
expertise technicians.
We are taking care of all kinds of car service varying from the
car wash to all kinds of repairs and servicing. We specialize in servicing cars
for reputed and trusted brands like Hyundai, Tata, Ford, Maruti, Mahindra,
Honda and many other brands.
It provides quality and quick service with easy and free

pick-up and drop facility for cars requested for service. Our well-trained staff
helps our customer to get a fine service at the earliest.
The repairs and maintenance are done by our skilled

technician in the minimum duration. The work initialization immediately
starts after a proper examination of the servicing car. We also provide oil
service least possible time.
[4]
FLY WHEEL CAR CARE
1.2 Description of System
The objective of the Vehicle Services is to provide better

information for the users of this system for better results for their maintainence
in the product details that is sales, purchases and stock.
• Automation of the entire system improves the efficiency

• It provides a friendly graphical user interface which proves to be
better when compared to the existing system.
• It gives appropriate access to the authorized users depending on
their permissions.
• It effectively overcomes the delay in communications.
• Updating of information becomes so easier.
• System security, data security and reliability are the striking
features.
• The System has adequate scope for modification in future if it is
necessary.
[5]
FLY WHEEL CAR CARE
1.3 Limitation of present system
Existing system is a manual one in which users are maintaining

books to store the information like product details, Distributors details,
purchases, sales details and accounts for every month. It is very difficult to
maintain historical data.
The following are the disadvantages of the existing system
• It is difficult to maintain important information in books.
• More manual hours need to generate required reports.
• It is tedious to manage historical data which needs much space to keep

all the previous years’ ledgers, books etc.
• Daily sales and purchases details must be entered into books are very
difficult to maintain.
[6]
FLY WHEEL CAR CARE
1.4 Proposed System and Advantages
The FLY WHEEL CAR CARE ONLINE CAR SERVICING

MANAGEMENT SYSTEM is a web based website which avoids more manual
hours that need to spend in record keeping and generating reports.
The following are the advantages of the existing system:
• This website keeps the data in a centralized way which is available to

all the users simultaneously.
• It is very easy to manage historical data in database. No specific
training is required for the distributors to use this website.
• They can easily use the tool that decreases manual hours spending for
normal things and hence increases the performance.
• It is very easy to record the information of online sales and purchases
in the databases.
[7]
FLY WHEEL CAR CARE
1.5 Gantt chart
PLANNED COMPLETED
NOV DEC JAN FEB MAR APR

2016 2016 2017 2017 2017 2017
ANALYSIS
• Feasibility study
• Data gathering
• Documentation
[8]
FLY WHEEL CAR CARE
DESIGNING
• Table designing
• Form designing
CODING
• Form coding
• Report coding
TESTING
• Implementation
of single form
• Testing of entire
system as whole
[9]
FLY WHEEL CAR CARE
02.
SURVEY OF
TECHNOLOGY
2.1 Feasibility Study
A feasibility study is not warranted for this system in which

economic justification is obvious, technical risk is low, few legal problems are
expected and no reasonable alternative exits. However, if any of the preceding
condition fails, a study of that should be conducted.
All projects are feasible- given unlimited time! Unfortunately, the development of
computer- based system of courses more like plagued by a scarcity of resources.
[10]
FLY WHEEL CAR CARE
It is necessary and prudent to evaluate the feasibility of project at the earliest

possible time.
Feasibility and risk analysis are related in many ways. If project risk is great, the
feasibility of providing quality software is reduced.
The feasibility study may be documented as an appendix to the system

specification.
2.1.1 Operational feasibility

Proposed projects are beneficial only if they
c a n b e t u r n e d o u t i n t o i n f o r m a t i o n system. That will meet the
organization’s operating requirements. Operational feasibility aspects of the
project are to be taken as an important part of the project implementation. Some
of the important issues raised are to test the operational feasibility of a project
includes the following: -
• Is there sufficient support for the management from the users?
• Will the system be used and work properly it is being developed and
implemented?
• Will there be any resistance from the user that will undermine the possible
application benefits?
This system is targeted to be in accordance with the above
–mentioned issues. Beforehand, the management issues and user
r e q u i r e m e n t s h a v e b e e n t a k e n i n t o consideration. So there is no
question of resistance from the users that can undermine the possible
application benefits. The well-planned design would ensure the optimal
utilization of the computer resources and would help in the improvement of
performance status.
2.1.2 Technical feasibility
[11]
FLY WHEEL CAR CARE
The technical issue usually raised during the feasibility stage of the
investigation includes the following:
•Does the necessary technology exist to do what is suggested?
•Do the proposed equipments have the technical capacity to hold the data
required to use the new system?
•A r e t h e r e t e c h n i c a l g u a r a n t e e s o f a c c u r a c y , r e l i a b i l i t y , e a s e o f
a c c e s s a n d d a t a security? Earlier no system existed to cater to the needs of
‘Secure Infrastructure Implementation System’. The current system
developed is technically feasible. It is a web based user interface for audit
workflow at NIC-CSD. Thus it provides an easy access t o t h e u s e r s . T h e
database’s purpose is to create, establish and maintain a
w o r k f l o w among various entities in order to facilitate all concerned users in
their various capacities o r r o l e s . P e r m i s s i o n t o t h e u s e r s w o u l d
b e g r a n t e d b a s e d o n t h e r o l e s s p e c i f i e d . Therefore, it provides
the technical guarantee of accuracy, reliability and security. The
software and hard requirements for the development of this project are
not many and are already available in-house at NIC or are available as
free as open source. The work f o r t h e p r o j e c t i s d o n e w i t h t h e
current equipment and existing software technology.
Necessary bandwidth exists for providing a fast feedback to the users irrespective
of the number of users using the system
2.1.3. Economic Feasibility
A system can be developed technically and that will be used if installed

must still be a good investment for the organization. In the economical
feasibility, the development cost in creating the system is evaluated against
the ultimate benefit derived from the new systems. Financial benefits must
equal or exceed the costs.
The system is economically feasible. It does not require any addition
hardware or software
[12]
FLY WHEEL CAR CARE
2.2 Software and Hardware requirements
Hardware Requirements:-
• Pentium-IV(Processor).
• 256 MB Ram
• 512 KB Cache Memory
• Hard disk 10 GB
• Microsoft Compatible 101 or more Key Board
Software Requirements: -
• Operating System : Windows
• Programming language: MS.NET
• Web-Technology: ASP.NET
• Front-End: C#.NET
[13]
FLY WHEEL CAR CARE
• Back-End: SQLSERVER 2000
• Web Server: IIS5.1

2.3Development Tools and Technology
2.3.1Front End
Microsoft .NET Framework

The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet. The .NET
Framework is designed to fulfill the following objectives:
• To provide a consistent object-oriented programming environment
whether object code is stored and executed locally, executed locally but
Internet-distributed, or executed remotely.
• To provide a code-execution environment that minimizes software
deployment and versioning conflicts.
• To provide a code-execution environment that guarantees safe
execution of code, including code created by an unknown or
semi-trusted third party.
• To provide a code-execution environment that eliminates the
performance problems of scripted or interpreted environments.
• To make the developer experience consistent across widely varying
types of applications, such as Windows-based applications and
Web-based applications.
• To build all communication on industry standards to ensure that code
based on the .NET Framework can integrate with any other code.
The .NET Framework has two main components: the
common language runtime and the .NET Framework class library. The
common language runtime is the foundation of the .NET Framework. You can
think of the runtime as an agent that manages code at execution time,
[14]
FLY WHEEL CAR CARE
providing core services such as memory management, thread management,

and remoting, while also enforcing strict type safety and other forms of code
accuracy that ensure security and robustness. In fact, the concept of code
management is a fundamental principle of the runtime.
Code that targets the runtime is known as managed
code, while code that does not target the runtime is known as unmanaged
code. The class library, the other main component of the .NET Framework, is a
comprehensive, object-oriented collection of reusable types that you can use to
develop applications ranging from traditional command-line or graphical user
interface (GUI) applications to applications based on the latest innovations
provided by ASP.NET, such as Web Forms and XML Web services.
The .NET Framework can be hosted by unmanaged components that
load the common language runtime into their processes and initiate the
execution of managed code, thereby creating a software environment that can
exploit both managed and unmanaged features. The .NET Framework not only
provides several runtime hosts, but also supports the development of
third-party runtime hosts.
For example, ASP.NET hosts the runtime to provide a scalable,
server-side environment for managed code. ASP.NET works directly with the
runtime to enable Web Forms applications and XML Web services, both of
which are discussed later in this topic.
Internet Explorer is an example of an unmanaged application that hosts
the runtime (in the form of a MIME type extension). Using Internet Explorer to
host the runtime enables you to embed managed components or Windows
Forms controls in HTML documents. Hosting the runtime in this way makes
managed mobile code (similar to Microsoft® ActiveX® controls) possible, but
with significant improvements that only managed code can offer, such as
semi-trusted execution and secure isolated file storage.
The following illustration shows the relationship of the common
language runtime and the class library to your applications and to the overall
system. The illustration also shows how managed code operates within a
larger architecture.
Features of the Common Language Runtime

The common language runtime manages memory, thread execution,
code execution, code safety verification, compilation, and other system
[15]
FLY WHEEL CAR CARE
services. These features are intrinsic to the managed code that runs on the
common language runtime.
With regards to security, managed components are awarded varying
degrees of trust, depending on a number of factors that include their origin
(such as the Internet, enterprise network, or local computer). This means that
a managed component might or might not be able to perform file-access
operations, registry-access operations, or other sensitive functions, even if it is
being used in the same active application.
The runtime enforces code access security. For example, users can trust
that an executable embedded in a Web page can play an animation on screen
or sing a song, but cannot access their personal data, file system, or network.
The security features of the runtime thus enable legitimate Internet-deployed
software to be exceptionally featuring rich.
The runtime also enforces code robustness by implementing a strict
type- and code-verification infrastructure called the common type system
(CTS). The CTS ensures that all managed code is self-describing. The various
Microsoft and third-party language compilers generate managed code that
conforms to the CTS. This means that managed code can consume other
managed types and instances, while strictly enforcing type fidelity and type
safety.
In addition, the managed environment of the runtime eliminates many
common software issues. For example, the runtime automatically handles
object layout and manages references to objects, releasing them when they are
no longer being used. This automatic memory management resolves the two
most common application errors, memory leaks and invalid memory
references.
The runtime also accelerates developer productivity. For example,
programmers can write applications in their development language of choice,
yet take full advantage of the runtime, the class library, and components
written in other languages by other developers. Any compiler vendor who
chooses to target the runtime can do so. Language compilers that target the
.NET Framework make the features of the .NET Framework available to
existing code written in that language, greatly easing the migration process for
existing applications.
While the runtime is designed for the software of the future, it also
supports software of today and yesterday. Interoperability between managed
[16]
FLY WHEEL CAR CARE
and unmanaged code enables developers to continue to use necessary COM

components and DLLs.
The runtime is designed to enhance performance. Although the common
language runtime provides many standard runtime services, managed code is
never interpreted. A feature called just-in-time (JIT) compiling enables all
managed code to run in the native machine language of the system on which it
is executing. Meanwhile, the memory manager removes the possibilities of
fragmented memory and increases memory locality-of-reference to further
increase performance.
Finally, the runtime can be hosted by high-performance, server-side
applications, such as Microsoft® SQL Server™ and Internet Information
Services (IIS). This infrastructure enables you to use managed code to write
your business logic, while still enjoying the superior performance of the
industry's best enterprise servers that support runtime hosting.
.NET Framework Class Library

The .NET Framework class library is a collection of reusable types that
tightly integrate with the common language runtime. The class library is
object oriented, providing types from which your own managed code can
derive functionality. This not only makes the .NET Framework types easy to
use, but also reduces the time associated with learning new features of the
.NET Framework. In addition, third-party components can integrate
seamlessly with classes in the .NET Framework.
For example, the .NET Framework collection classes implement a set of
interfaces that you can use to develop your own collection classes. Your
collection classes will blend seamlessly with the classes in the .NET
Framework.
As you would expect from an object-oriented class library, the .NET
Framework types enable you to accomplish a range of common programming
tasks, including tasks such as string management, data collection, database
connectivity, and file access. In addition to these common tasks, the class
library includes types that support a variety of specialized development
scenarios. For example, you can use the .NET Framework to develop the
following types of applications and services:
• Console applications.
• Scripted or hosted applications.
[17]
FLY WHEEL CAR CARE
• Windows GUI applications (Windows Forms).

• ASP.NET applications.
• XML Web services.
• Windows services.
For example, the Windows Forms classes are a comprehensive set of reusable
types that vastly simplify Windows GUI development. If you write an ASP.NET
Web Form application, you can use the Web Forms classes.
Client Application Development

Client applications are the closest to a traditional style of application in
Windows-based programming. These are the types of applications that display
windows or forms on the desktop, enabling a user to perform a task. Client
applications include applications such as
word processors and spreadsheets, as well as custom business applications

such as data-entry tools, reporting tools, and so on. Client applications usually
employ windows, menus, buttons, and other GUI elements, and they likely
access local resources such as the file system and peripherals such as printers.
Another kind of client application is the traditional ActiveX control
(now replaced by the managed Windows Forms control) deployed over the
Internet as a Web page. This application is much like other client applications:
it is executed natively, has access to local resources, and includes graphical
elements.
In the past, developers created such applications using C/C++ in
conjunction with the Microsoft Foundation Classes (MFC) or with a rapid
application development (RAD) environment such as Microsoft® Visual
Basic®. The .NET Framework incorporates aspects of these existing products
into a single, consistent development environment that drastically simplifies
the development of client applications. The Windows Forms classes contained
in the .NET Framework are designed to be used for GUI development. You can
easily create command windows, buttons, menus, toolbars, and other screen
elements with the flexibility necessary to accommodate shifting business
needs.
For example, the .NET Framework provides simple properties to adjust visual
attributes associated with forms. In some cases the underlying operating
[18]
FLY WHEEL CAR CARE
system does not support changing these attributes directly, and in these cases
the .NET Framework automatically recreates the forms. This is one of many
ways in which the .NET Framework integrates the developer interface, making
coding simpler and more consistent.
Unlike ActiveX controls, Windows Forms controls have semi-trusted
access to a user's computer. This means that binary or natively executing code
can access some of the resources on the user's system (such as GUI elements
and limited file access) without being able to access or compromise other
resources. Because of code access security, many applications that once
needed to be installed on a user's system can now be safely deployed through
the Web. Your applications can implement the features of a local application
while being deployed like a Web page.
Server Application Development

Server-side applications in the managed world are implemented
through runtime hosts. Unmanaged applications host the common language
runtime, which allows your custom managed code to control the behavior of
the server. This model provides you with all the features of the common
language runtime and class library while gaining the performance and
scalability of the host server.
The following illustration shows a basic network schema with managed
code running in different server environments. Servers such as IIS and SQL
Server can perform standard operations while your application logic executes
through the managed code.
Server-side managed code

ASP.NET is the hosting environment that enables developers to use the
.NET Framework to target Web-based applications. However, ASP.NET is more
than just a runtime host; it is a complete architecture for developing Web sites
and Internet-distributed objects using managed code. Both Web Forms and
XML Web services use IIS and ASP.NET as the publishing mechanism for
applications, and both have a collection of supporting classes in the .NET
Framework.
XML Web services, an important evolution in Web-based technology,
[19]
FLY WHEEL CAR CARE
are distributed, server-side application components similar to common Web

sites. However, unlike Web-based applications, XML Web services components
have no UI and are not targeted for browsers such as Internet Explorer and
Netscape Navigator. Instead, XML Web services consist of reusable software
components designed to be consumed by other applications, such as
traditional client applications, Web-based applications, or even other XML
Web services. As a result, XML Web services technology is rapidly moving
application development and deployment into the highly distributed
environment of the Internet.
If you have used earlier versions of ASP technology, you will
immediately notice the improvements that ASP.NET and Web Forms offers.
For example, you can develop Web Forms pages in any language that supports
the .NET Framework. In addition, your code no longer needs to share the same
file with your HTTP text (although it can continue to do so if you prefer). Web
Forms pages execute in native machine language because, like any other
managed application, they take full advantage of the runtime. In contrast,
unmanaged ASP pages are always scripted and interpreted. ASP.NET pages are
faster, more functional, and easier to develop than unmanaged ASP pages
because they interact with the runtime like any managed application.
The .NET Framework also provides a collection of classes and tools to
aid in development and consumption of XML Web services applications. XML
Web services are built on standards such as SOAP (a remote procedure-call
protocol), XML (an extensible data format), and WSDL ( the Web Services
Description Language). The .NET Framework is built on these standards to
promote interoperability with non-Microsoft solutions.
For example, the Web Services Description Language tool included with
the .NET Framework SDK can query an XML Web service published on the
Web, parse its WSDL description, and produce C# or Visual Basic source code
that your application can use to become a client of the XML Web service. The
source code can create classes derived from classes in the class library that
handle all the underlying communication using SOAP and XML parsing.
Although you can use the class library to consume XML Web services directly,
the Web Services Description Language tool and the other tools contained in
the SDK facilitate your development efforts with the .NET Framework.
If you develop and publish your own XML Web service, the .NET
Framework provides a set of classes that conform to all the underlying
communication standards, such as SOAP, WSDL, and XML. Using those classes
[20]
FLY WHEEL CAR CARE
enables you to focus on the logic of your service, without concerning yourself
with the communications infrastructure required by distributed software
development.
Finally, like Web Forms pages in the managed environment, your XML Web
service will run with the speed of native machine language using the scalable
communication of IIS.
Active Server Pages.NET

ASP.NET is a programming framework built on the common language runtime
that can be used on a server to build powerful Web applications. ASP.NET
offers several important advantages over previous Web development models:
• Enhanced Performance. ASP.NET is compiled common language
runtime code running on the server. Unlike its interpreted predecessors,
ASP.NET can take advantage of early binding, just-in-time compilation,
native optimization, and caching services right out of the box. This
amounts to dramatically better performance before you ever write a
line of code.
• World-Class Tool Support. The ASP.NET framework is

complemented by a rich toolbox and designer in the Visual Studio
integrated development environment. WYSIWYG editing, drag-and-drop
server controls, and automatic deployment are just a few of the features
this powerful tool provides.
• Power and Flexibility. Because ASP.NET is based on the common

language runtime, the power and flexibility of that entire platform is
available to Web application developers. The .NET Framework class
library, Messaging, and Data Access solutions are all seamlessly
accessible from the Web. ASP.NET is also language-independent, so you
can choose the language that best applies to your application or
partition your application across many languages. Further, common
language runtime interoperability guarantees that your existing
investment in COM-based development is preserved when migrating to
ASP.NET.
• Simplicity. ASP.NET makes it easy to perform common tasks, from

simple form submission and client authentication to deployment and
[21]
FLY WHEEL CAR CARE
site configuration. For example, the ASP.NET page framework allows

you to build user interfaces that cleanly separate application logic from
presentation code and to handle events in a simple, Visual Basic - like
forms processing model. Additionally, the common language runtime
simplifies development, with managed code services such as automatic
reference counting and garbage collection.
• Manageability. ASP.NET employs a text-based, hierarchical

configuration system, which simplifies applying settings to your server
environment and Web applications. Because configuration information
is stored as plain text, new settings may be applied without the aid of
local administration tools. This "zero local administration" philosophy
extends to deploying ASP.NET Framework applications as well. An
ASP.NET Framework application is deployed to a server simply by
copying the necessary files to the server. No server restart is required,
even to deploy or replace running compiled code.
• Scalability and Availability. ASP.NET has been designed with

scalability in mind, with features specifically tailored to improve
performance in clustered and multiprocessor environments. Further,
processes are closely monitored and managed
by the ASP.NET runtime, so that if one misbehaves (leaks, deadlocks), a

new process can be created in its place, which helps keep your
application constantly available to handle requests.
• Customizability and Extensibility. ASP.NET delivers a well-factored

architecture that allows developers to "plug-in" their code at the
appropriate level. In fact, it is possible to extend or replace any
subcomponent of the ASP.NET runtime with your own custom-written
component. Implementing custom authentication or state services has
never been easier.
• Security. With built in Windows authentication and per-application

configuration, you can be assured that your applications are secure.
Language Support
[22]
FLY WHEEL CAR CARE
The Microsoft .NET Platform currently offers built-in support for three
languages: C#, Visual Basic, and JScript.
What is ASP.NET Web Forms?

The ASP.NET Web Forms page framework is a scalable common
language runtime programming model that can be used on the server to
dynamically generate Web pages.
Intended as a logical evolution of ASP (ASP.NET provides syntax
compatibility with existing pages), the ASP.NET Web Forms framework has
been specifically designed to address a number of key deficiencies in the
previous model. In particular, it provides:
• The ability to create and use reusable UI controls that can encapsulate
common functionality and thus reduce the amount of code that a page
developer has to write.
• The ability for developers to cleanly structure their page logic in an
orderly fashion (not "spaghetti code").
• The ability for development tools to provide strong WYSIWYG design
support for pages (existing ASP code is opaque to tools).
ÀSP.NET Web Forms pages are text files with an .aspx file name
extension. They can be deployed throughout an IIS virtual root directory tree.
When a browser client requests .aspx resources, the ASP.NET runtime parses
and compiles the target file into a .NET Framework class. This class can then
be used to dynamically process incoming requests. (Note that the .aspx file is
compiled only the first time it is accessed; the compiled type instance is then
reused across multiple requests).
An ASP.NET page can be created simply by taking an existing HTML file
and changing its file name extension to .aspx (no modification of code is
required). For example, the following sample demonstrates a simple HTML
page that collects a user's name and category preference and then performs a
form post back to the originating page when a button is clicked:
[23]
FLY WHEEL CAR CARE
ASP.NET provides syntax compatibility with existing ASP pages. This

includes support for <% %> code render blocks that can be intermixed with
HTML content within an .aspx file. These code blocks execute in a top-down
manner at page render time.
Code-Behind Web Forms

ASP.NET supports two methods of authoring dynamic pages. The first is
the method shown in the preceding samples, where the page code is physically
declared within the originating .aspx file. An alternative approach--known as
the code-behind method--enables the page code to be more cleanly separated
from the HTML content into an entirely separate file.
Introduction to ASP.NET Server Controls

In addition to (or instead of) using <% %> code blocks to program
dynamic content, ASP.NET page developers can use ASP.NET server controls to
program Web pages. Server controls are declared within an .aspx file using
custom tags or intrinsic HTML tags that contain a runat="server" attributes
value. Intrinsic HTML tags are handled by one of the controls in the
System.Web.UI.HtmlControls namespace. Any tag that doesn't explicitly map
to one of the controls is assigned the type of
System.Web.UI.HtmlControls.HtmlGenericControl.
Server controls automatically maintain any client-entered values between
round trips to the server. This control state is not stored on the server (it is
instead stored within an <input type="hidden"> form field that is
round-tripped between requests). Note also that no client-side script is
required.
In addition to supporting standard HTML input controls, ASP.NET enables
developers to utilize richer custom controls on their pages. For example, the
following sample demonstrates how the <asp:adrotator> control can be used
to dynamically display rotating ads on a page.
• ASP.NET Web Forms provide an easy and powerful way to build dynamic Web
UI.
• ASP.NET Web Forms pages can target any browser client (there are no script
library or cookie requirements).
• ASP.NET Web Forms pages provide syntax compatibility with existing ASP
pages.
[24]
FLY WHEEL CAR CARE
• ASP.NET server controls provide an easy way to encapsulate common

functionality.
• ASP.NET ships with 45 built-in server controls. Developers can also use
controls built by third parties.
• ASP.NET server controls can automatically project both up level and down
level HTML.
• ASP.NET templates provide an easy way to customize the look and feel of list
server controls.
• ASP.NET validation controls provide an easy way to do declarative client or
server data validation.
2.3.2 Back End
About Microsoft SQL Server 2000

Microsoft SQL Server is a Structured Query Language (SQL) based,
client/server relational database. Each of these terms describes a fundamental
part of the architecture of SQL Server.
Database
A database is similar to a data file in that it is a storage place for data. Like a
data file, a database does not present information directly to a user; the user
runs an application that accesses data from the database and presents it to the
user in an understandable format.
A database typically has two components: the files holding the physical
database and the database management system (DBMS) software that
applications use to access data. The DBMS is responsible for enforcing the
database structure, including:
• Maintaining the relationships between data in the database.
• Ensuring that data is stored correctly and that the rules defining data
[25]
FLY WHEEL CAR CARE
relationships are not violated.

• Recovering all data to a point of known consistency in case of system
failures.
Relational Database
There are different ways to organize data in a database but relational

databases are one of the most effective. Relational database systems are an
application of mathematical set theory to the problem of effectively organizing
data. In a relational database, data is collected into tables (called relations in
relational theory).
When organizing data into tables, you can usually find many different
ways to define tables. Relational database theory defines a process,
normalization, which ensures that the set of tables you define will organize
your data effectively.
Client/Server
In a client/server system, the server is a relatively large computer in a
central location that manages a resource used by many people. When
individuals need to use the resource, they connect over the network from their
computers, or clients, to the server.
Examples of servers are: In a client/server database architecture, the

database files and DBMS software reside on a server. A communications
component is provided so applications can run on separate clients and
communicate to the database server over a network. The SQL Server
communication component also allows communication between an
application running on the server and SQL Server.
Server applications are usually capable of working with several clients
[26]
FLY WHEEL CAR CARE
at the same time. SQL Server can work with thousands of client applications
simultaneously. The server has features to prevent the logical problems that
occur if a user tries to read or modify data currently being used by others.
While SQL Server is designed to work as a server in a client/server
network, it is also capable of working as a stand-alone database directly on the
client. The scalability and ease-of-use features of SQL Server allow it to work
efficiently on a client without consuming too many resources.
Structured Query Language (SQL)
To work with data in a database, you must use a set of commands and
statements (language) defined by the DBMS software. There are several
different languages that can be used with relational databases; the most
common is SQL. Both the American National Standards Institute (ANSI) and
the International Standards Organization (ISO) have defined standards for
SQL. Most modern DBMS products support the Entry Level of SQL-92, the latest
SQL standard (published in 1992).
SQL Server Features

Microsoft SQL Server supports a set of features that result in the following
benefits:
• Ease of installation, deployment, and use

SQL Server includes a set of administrative and development tools that
improve your ability to install, deploy, manage, and use SQL Server
across several sites.
• Scalability
The same database engine can be used across platforms ranging from
laptop computers running Microsoft Windows® 95/98 to large,
multiprocessor servers running Microsoft Windows NT®, Enterprise
Edition.
• Data warehousing
SQL Server includes tools for extracting and analyzing summary data
for online analytical processing (OLAP). SQL Server also includes tools
for visually designing databases and analyzing data using English-based
questions.
[27]
FLY WHEEL CAR CARE
• System integration with other server software

SQL Server integrates with e-mail, the Internet, and Windows.
• Databases
A database in Microsoft SQL Server consists of a collection of tables that
contain data, and other objects, such as views, indexes, stored
procedures, and triggers, defined to support activities performed with
the data. The data stored in a database is usually related to a particular
subject or process, such as inventory information for a manufacturing
warehouse.
SQL Server can support many databases, and each database can store either
interrelated data or data unrelated to that in the other databases. For example,
a server can have one database that stores personnel data and another that
stores product-related data. Alternatively, one database can store current
customer order data, and another; related database can store historical
customer orders that are used for yearly reporting. Before you create a
database, it is important to understand the parts of a database and how to
design these parts to ensure that the database performs well after it is
implemented.
Normalization theory
Relations are to be normalized to avoid anomalies. In insert, update and delete
operations. Normalization theory is built around the concept of normal forms.
A relation is said to be in a particular form if it satisfies a certain specified set
if constraints. To decide a suitable logical structure for given database design
the concept of normalization, which are briefly described below.
1. 1 st Normal Form (1 N.F): A relation is said to be in 1 NF is and only if

all unaligned domains contain values only. That is the fields of an n-set
should have no group items and no repeating groups.
2. 2 nd Normal Form (2 N.F) : A relation is said to be in 2 NF is and only if
it is in 1 NF and every non key attribute is fully dependent on primary
key. This normal takes care of functional dependencies on non-key
attributes.
3. 3 rd Normal Form (3 N.F) : A relation is said to be in 3 NF is and only if
it is in 2 NF and every non key attribute is non transitively dependent
on the primary key. This normal form avoids the transitive
[28]
FLY WHEEL CAR CARE
dependencies on the primary key.

4. Boyce code Normal Form (BCNF) : This is a stronger definition than that
of NF. A relation is said to be in BCNF if and only if every determinant is
a Candidate key.
5. 4 th Normal Form (4 NF) : A relation is said to be in 4 NF if and only if
whenever there exists a multi valued dependency in a relation say
A->->B then all of the relation are also functionally dependent on A(i.e.
A->X for all attributes x of the relation.).
6. 5 th Normal Form (5 NF) OR Projection Join Normal Form (PJNF): A

relation R is in 5 NF .if and only if every join dependency in R is implied
by the candidate key on R . A relation can’t be non-loss split into two
tables but can be split into three tables. This is called Join Dependency.
[29]
FLY WHEEL CAR CARE
2.3.3 Development Environment
Microsoft Visual Studio 2010
Microsoft Visual Studio is an integrated development

environment (IDE) from Microsoft. It is used to develop computer
programs for Microsoft Windows, as well as web sites, web apps, web
services and mobile apps. Visual Studio uses Microsoft software development
platforms such as Windows API, Windows Forms, Windows Presentation
Foundation, Windows Store and Microsoft Silverlight. It can produce both native
code and managed code.
Visual Studio includes a code
editor supporting IntelliSense (the code completion component) as well as code
refactoring. The integrated debugger works both as a source-level debugger and a
machine-level debugger. Other built-in tools include a code profiler, forms
designer for building GUI applications, web designer, class designer,
and database schema designer. It accepts plug-ins that enhance the functionality
at almost every level—including adding support for source control systems
(like Subversion) and adding new toolsets like editors and visual designers
for domain-specific languages or toolsets for other aspects of the software
development lifecycle (like the Team Foundation Server client: Team Explorer).
Visual Studio supports different programming languages and
allows the code editor and debugger to support (to varying degrees) nearly any
programming language, provided a language-specific service exists. Built-in
languages include C,[6] C++ and C++/CLI (via Visual C++), VB.NET (via Visual Basic
.NET), C# (via Visual C#), and F# (as of Visual Studio 2010[7]). Support for other
languages such as Python,[8] Ruby, Node.js, and M among others is available via
language services installed separately. It also
supports XML/XSLT, HTML/XHTML, JavaScript and CSS. Java (and J#) were
supported in the past.
[30]
FLY WHEEL CAR CARE
Features of Microsoft Visual Studio

Visual Studio 2010 comes with .NET Framework 4 and supports
developing applications targeting Windows 7. It supports IBM
DB2 and Oracle databases, in addition to Microsoft SQL Server. It has integrated
support for developing Microsoft Silverlight applications, including an interactive
designer.
Visual Studio 2010 offers several tools to make parallel programming simpler: in
addition to the Parallel Extensions for the .NET Framework and the Parallel
Patterns Library for native code,
Visual Studio 2010 includes tools for debugging parallel
applications. The new tools allow the visualization of parallel Tasks and their
runtime stacks. Tools for profiling parallel applications can be used for
visualization of thread wait-times and thread migrations across processor
cores. Intel and Microsoft have jointly pledged support for a new Concurrency
Runtime in Visual Studio 2010 and Intel has launched parallelism support
in Parallel Studio as an add-on for Visual Studio.
The Visual Studio 2010 code editor now highlights references;
whenever a symbol is selected, all other usages of the symbol are highlighted. It
also offers a Quick Search feature to incrementally search across all symbols in
C++, C# and VB.NET projects. Quick Search supports substring matches
and camelCase searches.
The Call Hierarchy feature allows the developer to see all the
methods that are called from a current method as well as the methods that call
the current one. IntelliSense in Visual Studio supports a consume-first mode
which developers can opt into. In this mode, IntelliSense does not auto-complete
identifiers; this allows the developer to use undefined identifiers (like variable or
method names) and define those later.
Visual Studio 2010 can also help in this by automatically
defining them, if it can infer their types from usage. Current versions of Visual
Studio have a known bug which makes IntelliSense unusable for projects using
pure C (not C++).
Visual Studio 2010 features a new Help System replacing
the MSDN Library viewer. The Help System is no longer based on Microsoft Help
2 and does not use Microsoft Document Explorer.
Dynamic help containing links to related help topics based
[31]
FLY WHEEL CAR CARE
on where the developer was in the IDE has been removed in the shipping
product, but can be added back using a download from Microsoft.
C# Language
C# (pronounced C Sharp) is a multi-paradigm programming language that
encompasses functional, imperative, generic, object-oriented (class-based), and
component-oriented programming disciplines. It was developed by Microsoft as
part of the .NET initiative and later approved as a standard by ECMA (ECMA-334)
and ISO (ISO/IEC 23270). C# is one of the 44 programming languages supported
by the .NET Framework's Common Language Runtime.
C# is intended to be a simple, modern, general-purpose, object-oriented
programming language. Anders Hejlsberg, the designer of Delphi, leads the team
which is developing C#. It has an object-oriented syntax based on C++ and is
heavily influenced by other programming languages such as Delphi and Java. It
was initially named Cool, which stood for "C like Object Oriented Language".
However, in July 2000, when Microsoft made the project public, the name of the
programming language was given as C#. The most recent version of the language
is C# 3.0 which was released in conjunction with the .NET Framework 3.5 in 2007.
The next proposed version, C# 4.0, is in development.
History
In 1996, Sun Microsystems released the Java programming
language with Microsoft soon purchasing a license to implement it in their
operating system. Java was originally meant to be a platform independent
[32]
FLY WHEEL CAR CARE
language, but Microsoft, in their implementation, broke their license agreement

and made a few changes that would essentially inhibit Java's
platform-independent capabilities. Sun filed a lawsuit and Microsoft settled,
deciding to create their own version of a partially compiled, partially interpreted
object-oriented programming language with syntax closely related to that of C++.
During the development of .NET, the class libraries were
originally written in a language/compiler called Simple Managed C (SMC). In
January 1999, Anders Hejlsberg formed a team to build a new language at the
time called Cool, which stood for "C like Object Oriented Language".Microsoft had
considered keeping the name "Cool" as the final name of the language, but chose
not to do so for trademark reasons. By the time the .NET project was publicly
announced at the July 2000 Professional Developers Conference, the language had
been renamed C#, and the class libraries and ASP.NET runtime had been ported
to C#.
C#'s principal designer and lead architect at Microsoft is Anders
Hejlsberg, who was previously involved with the design of Visual J++, Borland
Delphi, and Turbo Pascal. In interviews and technical papers he has stated that
flaws in most major programming languages (e.g. C++, Java, Delphi, and
Smalltalk) drove the fundamentals of the Common Language Runtime (CLR),
which, in turn, drove the design of the C# programming language itself. Some
argue that C# shares roots in other languages.
Features of C#
By design, C# is the programming language that most directly reflects the
underlying Common Language Infrastructure (CLI). Most of C#'s intrinsic types
correspond to value-types implemented by the CLI framework. However, the C#
language specification does not state the code generation requirements of the
compiler: that is, it does not state that a C# compiler must target a Common
Language Runtime (CLR), or generate Common Intermediate Language (CIL), or
generate any other specific format. Theoretically, a C# compiler could generate
machine code like traditional compilers of C++ or FORTRAN; in practice, all
existing C# implementations target CIL.
Some notable C# distinguishing features are:
• There are no global variables or functions. All methods and members must
be declared within classes. It is possible, however, to use static
methods/variables within public classes instead of global
variables/functions.
[33]
FLY WHEEL CAR CARE
• Local variables cannot shadow variables of the enclosing block, unlike C

and C++. Variable shadowing is often considered confusing by C++ texts.
• C# supports a strict Boolean data type, bool. Statements that take
conditions, such as while and if, require an expression of a boolean type.
While C++ also has a boolean type, it can be freely converted to and from
integers, and expressions such as if(a) require only that a is convertible to
bool, allowing a to be an int, or a pointer. C# disallows this "integer
meaning true or false" approach on the grounds that forcing programmers
to use expressions that return exactly bool can prevent certain types of
programming mistakes such as if (a = b) (use of = instead of ==).
• In C#, memory address pointers can only be used within blocks specifically
marked as unsafe, and programs with unsafe code need appropriate
permissions to run. Most object access is done through safe object
references, which are always either pointing to a valid, existing object, or
have the well-defined null value; a reference to a garbage-collected object,
or to random block of memory, is impossible to obtain. An unsafe pointer
can point to an instance of a value-type, array, string, or a block of memory
allocated on a stack. Code that is not marked as unsafe can still store and
manipulate pointers through the System.IntPtr type, but cannot
dereference them.
• Managed memory cannot be explicitly freed, but is automatically garbage
collected. Garbage collection addresses memory leaks. C# also provides
direct support for deterministic finalization with the using statement
(supporting the Resource Acquisition Is Initialization idiom).
• Multiple inheritance is not supported, although a class can implement any
number of interfaces. This was a design decision by the language's lead
architect to avoid complication, avoid dependency hell and simplify
architectural requirements throughout CLI.
• C# is more type safe than C++. The only implicit conversions by default are
those which are considered safe, such as widening of integers and
conversion from a derived type to a base type. This is enforced at
compile-time, during JIT, and, in some cases, at runtime. There are no
implicit conversions between booleans and integers, nor between
enumeration members and integers (except for literal 0, which can be
implicitly converted to any enumerated type). Any user-defined conversion
must be explicitly marked as explicit or implicit, unlike C++ copy
constructors (which are implicit by default) and conversion operators
[34]
FLY WHEEL CAR CARE
(which are always implicit).

• Enumeration members are placed in their own scope.
• C# provides syntactic sugar for a common pattern of a pair of methods,
accessor (getter) and mutator (setter) encapsulating operations on a single
attribute of a class, in form of properties.
• Full type reflection and discovery is available.
• C# currently (as of 3 June 2008) has 77 reserved words.
[35]
FLY WHEEL CAR CARE
03.
REQUIREMENTS AND
ANALYSIS
3.1 E-R Diagram

1. An entity relationship diagram is a means of visualizing how the
information a system produces is related. There are five main components
of an ERD:
2. Entities, which are represented by rectangles. An entity is an object or
[36]
FLY WHEEL CAR CARE
concept about which you want to store information..
3. Actions, which are represented by diamond shapes, show how two entities
share information in the database. In some cases, entities can be
self-linked. For example, employees can supervise other employees.
4. Attributes, which are represented by ovals. A key attribute is the unique,

distinguishing characteristic of the entity. For example, an employee's
social security number might be the employee's key attribute.
5. Connecting lines, solid lines that connect attributes to show the

relationships of entities in the diagram.
6. Cardinality specifies how many instances of an entity relate to one instance

of another entity. Ordinality is also closely linked to cardinality. While
cardinality specifies the occurrences of a relationship, ordinality describes
the relationship as either mandatory or optional. In other words,
cardinality specifies the maximum number of relationships and ordinality
specifies the absolute minimum number of relationships.
[37]
FLY WHEEL CAR CARE
3.2 Use case Diagram
[38]
FLY WHEEL CAR CARE
Use case diagrams model behavior within a system and helps the developers understand
of what the user require. The stick man represents what’s called an actor.
Use case diagram can be useful for getting an overall view of the system and clarifying
who can do and more importantly what they can’t do.
Use case diagram consists of use cases and actors and shows the interaction between the
use case and actors.
1. The purpose is to show the interactions between the use case and actor.
2. To represent the system requirements from user’s perspective.
3. An actor could be the end-user of the system or an external system.
4. A Use case is a description of set of sequence of actions. Graphically it is

rendered as an ellipse with solid line including only its name.
5. Use case diagram is a behavioral diagram that shows a set of use cases and
actors and their relationship. It is an association between the use cases and
actors. An actor represents a real-world object. Primary Actor – Sender,
Secondary Actor Receiver.
[39]
FLY WHEEL CAR CARE
[40]
FLY WHEEL CAR CARE
3.3 Sequence Diagram/Collaboration Diagram
Sequence diagram and collaboration diagram are called

INTERACTION DIAGRAMS. An interaction diagram shows an interaction,
consisting of set of objects and their relationship including the messages that
may be dispatched among them.
A sequence diagram is an introduction that empathizes the time ordering

of messages. Graphically a sequence diagram is a table that shows objects
arranged along the X-axis and messages ordered in increasing time along the
Y-axis
1. Object - this box shape represents a class, or object, in UML. They

demonstrate how an object will behave in the context of the system. Class
attributes should not be listed in this shape.
2. Activation boxes - symbolized by a rectangle shape, an activation box

represents the time needed for an object to complete a task. The longer the
task will take, the longer the activation box becomes.
3. Actors - represented by a stick figure, actors are entities that are both
interactive with and external to the system.
4. Lifeline - a dashed vertical line that represents the passage of time as it

extends downward. Along with time, they represent the sequential events
that occur to an object during the charted process. Lifelines may begin with
a labeled rectangle shape or an actor symbol.
5. Alternatives - used to symbolize a choice (that is usually mutually

exclusive) between two or more message sequences. To represent
alternatives, use the labeled rectangle shape with a dashed line inside.
6. Messages - packets of information that are transmitted between objects.

They may reflect the start and execution of an operation, or the sending
[41]
FLY WHEEL CAR CARE
and reception of a signal.
[42]
FLY WHEEL CAR CARE
Collaboration Diagram
A collaboration diagram is an introduction diagram that
emphasizes the structural organization of the objects that send and receive
messages. Graphically a collaboration diagram is a collection of vertices and arcs.
[43]
FLY WHEEL CAR CARE
System database
Authentication
User Reg
Checking
Servicing car
Not Valid user
Valid user
Registration
Servicing Car
Main Page
3.4 Data Flow Diagram
The DFD takes an input-process-output view of a system i.e. data

objects flow into the software, are transformed by processing elements, and
resultant data objects flow out of the software.
Data objects represented by labeled arrows and transformation are
[44]
FLY WHEEL CAR CARE
represented by circles also called as bubbles. DFD is presented in a hierarchical

fashion i.e. the first data flow model represents the system as a whole.
Subsequent DFD refine the context diagram (level 0 DFD), providing increasing
details with each subsequent level.
The DFD enables the software engineer to develop models of the

information domain & functional domain at the same time. As the DFD is refined
into greater levels of details, the analyst perform an implicit functional
decomposition of the system. At the same time, the DFD refinement results in a
corresponding refinement of the data as it moves through the process that
embody the applications.
A context-level DFD for the system the primary external entities

produce information for use by the system and consume information generated
by the system.
RULES FOR DFD:
1. Fix the scope of the system by means of context diagrams.
2. Organize the DFD so that the main sequence of the actions
3. Reads left to right and top to bottom.
4. Identify all inputs and outputs.
5. Identify and label each process internal to the system with Rounded circles.
6. A process is required for all the data transformation and Transfers. Therefore,
never connect a data store to a data Source or the destinations or another data
store with just a Data flow arrow.
7. Do not indicate hardware and ignore control information.
8. Make sure the names of the processes accurately convey everything the
[45]
FLY WHEEL CAR CARE
process is done.
9. There must not be unnamed process.
10. Indicate external sources and destinations of the data, with Squares.
11. Number each occurrence of repeated external entities.
12. Identify all data flows for each process step, except simple Record retrievals.
13. Label data flow on each arrow.
14. Use details flow on each arrow.
15. Use the details flow arrow to indicate data movements.
[46]
FLY WHEEL CAR CARE
Vehicle
registration
Servicing
car
Vehicle
service
Database
[47]
FLY WHEEL CAR CARE
3.5 Class Diagram
The class diagram is a static diagram. It represents the

static view of an application. Class diagram is not only used for visualizing,
describing and documenting different aspects of a system but also for
constructing executable code of the software application.
The class diagram describes the attributes and

operations of a class and also the constraints imposed on the system. The class
diagrams are widely used in the modelling of object oriented systems because
they are the only UML diagrams which can be mapped directly with object
oriented languages.
Class diagrams are the most popular UML diagrams

used for construction of software applications. So it is very important to learn
the drawing procedure of class diagram.
Class diagrams have lot of properties to consider while

drawing but here the diagram will be considered from a top level view.
Class diagram is basically a graphical representation of

the static view of the system and represents different aspects of the application.
So a collection of class diagrams represent the whole system.
So the purpose of the class diagram can be summarized as:
1. Analysis and design of the static view of an application.
2. Describe responsibilities of a system.
3. Base for component and deployment diagrams.
4. Forward and reverse engineering.
[48]
FLY WHEEL CAR CARE
[49]
FLY WHEEL CAR CARE
3.6 Activity Diagram

Activity diagram is another important diagram in UML to
describe dynamic aspects of the system.
Activity diagram is basically a flow chart to represent the

flow from one activity to another activity. The activity can be described as an
operation of the system.
So the control flow is drawn from one operation to another.

This flow can be sequential, branched or concurrent. Activity diagrams deals
with all type of flow control by using different elements like fork, join etc.
The basic purposes of activity diagrams are similar to other

four diagrams. It captures the dynamic behaviour of the system. Other four
diagrams are used to show the message flow from one object to another but
activity diagram is used to show message flow from one activity to another.
Activity is a particular operation of the system. Activity

diagrams are not only used for visualizing dynamic nature of a system but they
are also used to construct the executable system by using forward and reverse
engineering techniques. The only missing thing in activity diagram is the
message part.
The purposes can be described as:
1. Draw the activity flow of a system.
2. Describe the sequence from one activity to another.
[50]
FLY WHEEL CAR CARE
3. Describe the parallel, branched and concurrent flow of the system.
[51]
FLY WHEEL CAR CARE
[52]
FLY WHEEL CAR CARE
04.
SYSTEM DESIGN
[53]
FLY WHEEL CAR CARE
4.1 DATA DICTIONARY

DataBase Tables
1.Registration
id int Unchecked
name varchar(50) Checked
password varchar(50) Checked
confirmpassword varchar(50) Checked
address varchar(MAX) Checked
phonenumber varchar(50) Checked
emailid varchar(50) Checked
vehiclemodel varchar(50) Checked
vehiclenumber varchar(50) Checked
2.Booking Request
id int Unchecked
userid varchar(50) Checked
vehiclenumber varchar(50) Checked
servicingtype varchar(50) Checked
others nchar(10) Checked
[54]
FLY WHEEL CAR CARE
3.Feedback
COLUMN NAME DATA TYPE ALLOW NULL

id int Unchecked
feedback varchar(MAX) Checked
4.Problem Form
id int Unchecked
customername varchar(50) Checked
vehicleno varchar(50) Checked
problemreported varchar(MAX) Checked
status varchar(50) Checked
Unchecked
5.Service Charge Form
id int Unchecked
equipmentused varchar(50) Checked
[55]
FLY WHEEL CAR CARE

servicingcharges varchar(50) Checked
totalamount varchar(50) Checked
6.Submition Form
id int Unchecked
phoneno varchar(50) Checked
handoverto varchar(50) Checked
Unchecked
7.Admin Login
id int Unchecked
username varchar(50) Checked
password varchar(50) Checked
Email varchar(50) Checked
8.Admin ForgetPasword
id int Unchecked
currentpassword varchar(50) Checked
newpassword varchar(50) Checked
[56]
FLY WHEEL CAR CARE
retypenewpassword varchar(50) Checked

username varchar(50) Checked
9.Contact Us
COLUMN NAME DATA TYPE ALLOW NULL

id int Unchecked
mobilenumber varchar(50) Checked
message varchar(MAX) Checked
address varchar(MAX) Checked
[57]
FLY WHEEL CAR CARE
4.2 BASIC MODULES
The basic idea is that the users can take book the requent for car
servcing from anywhere during any time by using their id and password
provided to them. The database will maintain the car servicing details
information. user can view their profile . This Online Car Servicing Management
system involves with two types of users.
➢ USER
➢ ADMINISTRATOR
USER ROLE
The user can login/logout the System. He or She can book the request for servicing
the car and servicing details and booked it. The customer can just view the
information whereas he/she could not make changes in the database.
ADMINISTRATOR ROLE
The administrator plays a vital role in the Online Car Servicing Management
system. The administrator controls the entire database. The report of the services
is generated by the administrator itself. The main role of the administrator is to
safeguard the database and can add/delete the batches and data of the cars
serviced or not from the database.
[58]
FLY WHEEL CAR CARE
4.3 TEST CASES DESIGN

Software testing is an investigation conducted to provide stakeholders with
information about the quality of the product or service under test.
The essence of testing is to:
• Catch as much error as possible.

• Correct the errors.
• Track the errors to understand their causes and any patterns that may
exist.
• Revalidate the stability of the solutions, including ensuring that the
correction of one error does not lead to introduction of another error
somewhere else.
A primary purpose for this testing is to detect software failures so that defects
may be uncovered and corrected. The scope of this software testing often includes
examination of code as well as execution of that code in various environments
and conditions as well as examining the aspects of code: does it do what it is
supposed to do and do what it needs to do.
Testing is done on the following levels:
Regression Testing:
Regression testing focuses on finding defects after a major code change has
occurred. Specifically, it seeks to uncover software regression, or old bugs that
have come back. Such regressions occur whenever software functionality that
was previously working correctly stops working as intended.
Stability Testing:
Stability testing checks to see if the software can continuously function well
in or above an acceptable period. This activity of non-functional software
Usability Testing:
Usability testing is needed to check if the user interface is easy to use and
[59]
FLY WHEEL CAR CARE
understand. It approaches towards the use of the application.
Unit Testing
The minimal software components (module) are tested.
Each unit(basic component) of the software is tested to verify that the detailed
design for the unit has been correctly implemented.
1. Testing is done at class level, and the minimal unit tests include the
constructors and destructors.
2. In Black Box Testing specification based testing is done to find that each
module gives specific output for particular input integration testing.
3. The interfaces and interaction between integrated components are tested.
4. Progressively larger group of tested software components corresponding to
elements of the architectural design are integrated and tested until the
software works as a system.
SR Form Test Step or Input Test Expected Actual Pass/Fail

No Name Conditi Procedur Data Result Output
on e
1 Login Check Username
User name: Display Display Pass
login with
Revaskarp Message: Message
with Wrong
rachi22@g “Invalid “Invalid User
valid password
mail.com User or or Password”
input Password: Password”
123
2 Login Check Wrong Username: Display Display Pass
login Username Revaskarp Message: Message:
with with rachi22@g “Welcome” “Welcome”
valid correct mail.com
input password Password:
1234
3 Check If Phone 959474892 Display Display Pass
Registration Phone Number Is 11 Message: Message:
Number More “enter valid “enter valid
Than 10 contact no” contact no”
Digit
4 Registration Check If S!@#gmail. Display Display Pass
[60]
FLY WHEEL CAR CARE
emailid incorrect com Message: Message:

emailid “enter valid “enter valid
emailid” emailid”
05.
IMPLEMENTATION AND
[61]
FLY WHEEL CAR CARE
TESTING
[62]
FLY WHEEL CAR CARE
5.1 FORM DESIGN

1.User Login
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Configuration;
using System.Data;
using System.Data.SqlClient;
public partial class _Default : System.Web.UI.Page
SqlConnection con=new
SqlConnection(ConfigurationManager.ConnectionStrings["myconnectionstring
"].ConnectionString);
// string strconnString =
ConfigurationManager.ConnectionStrings["myconnectionstring"].ConnectionSt
ring;
string str = null;
SqlCommand com;
protected void Button1_Click(object sender, EventArgs e)
object obj = null;
// SqlConnection con = new SqlConnection(strConnString);
con.Open();
[63]
FLY WHEEL CAR CARE
Session["Username"] = TextBox1.Text;
str = "select count(*) from registration where name=@Username and

password=@Password";
com = new SqlCommand(str,con);
com.CommandType = CommandType.Text;
com.Parameters.AddWithValue("@Username", Session["Username"]);
com.Parameters.AddWithValue("@Password", TextBox2.Text);
obj = com.ExecuteScalar();
if ((int)(obj) != 0)
Response.Redirect("welcome.aspx");
else
Label1.Text = "invalid username and password";
con.Close();
}
}
[64]
FLY WHEEL CAR CARE
USER LOGIN
[65]
FLY WHEEL CAR CARE
2.Change Password
using System;
using System.Linq;
using System.Web;
using System.Data;

{
string user;
string pass;
string strConnString =
ConfigurationManager.ConnectionStrings["myconnectionString"].ConnectionStri
ng;
string str = null;
SqlCommand com;
byte up;
{
SqlConnection con = new SqlConnection(strConnString);
con
.Open();
str = "select name,password from registration where name='"+txtuser.Text +"'
and password='"+txtcpass.Text+"'";
com = new SqlCommand(str, con);
SqlDataReader reader = com.ExecuteReader();
[66]
FLY WHEEL CAR CARE
if (reader.Read())
{
user = reader["name"].ToString();
pass = reader["password"].ToString();
}
reader.Close();
if(user.Equals(txtuser.Text) && pass.Equals(txtcpass.Text))
{
str = "update registration set password='"+txtnewpass.Text+"' where
name='" + txtuser.Text + " '";
com.ExecuteNonQuery();
con.Close();
Label1.Text = "Password changed Successfully";
}
else
{
Label1.Text = "Please enter correct Current password";
}
}
}
CHANGE PASSWORD
[67]
FLY WHEEL CAR CARE
[68]
FLY WHEEL CAR CARE
3.Forget Password
using System;
using System.Linq;
using System.Web;
using System.Data;
using System.Net.Mail;

{
SqlConnection con = new
SqlConnection(ConfigurationManager.ConnectionStrings["myconnectionstring"].
ConnectionString);
{
//Create Connection String And SQL Statement
string strConnection =
ConfigurationManager.ConnectionStrings["myconnectionstring"].ConnectionStrin
g;
string strSelect = "SELECT name,password,emailid FROM registration
where emailid = @Email";
SqlConnection connection = new SqlConnection(strConnection);
SqlCommand command = new SqlCommand();
command.Connection = connection;
command.CommandType = CommandType.Text;
command.CommandText = strSelect;
SqlParameter email = new SqlParameter("@Email", SqlDbType.VarChar,
50);
email.Value = txtEmail.Text.Trim().ToString();
command.Parameters.Add(email);
//Create Dataset to store results and DataAdapter to fill Dataset
DataSet dsPwd = new DataSet();
SqlDataAdapter dAdapter = new SqlDataAdapter(command);
connection.Open();
dAdapter.Fill(dsPwd);
connection.Close();
if (dsPwd.Tables[0].Rows.Count > 0)
{
[69]
FLY WHEEL CAR CARE
MailMessage loginInfo = new MailMessage();

loginInfo.To.Add(txtEmail.Text.ToString());
loginInfo.From = new MailAddress("revaskarprachi22@gmail.com");
loginInfo.Subject = "Forgot Password Information";
loginInfo.Body = "Username: " + dsPwd.Tables[0].Rows[0]["emailid"] +
" Password: " + dsPwd.Tables[0].Rows[0]["password"] + " ";
loginInfo.IsBodyHtml = true;
SmtpClient smtp = new SmtpClient();
smtp.Host = "smtp.gmail.com";
smtp.Port = 587;
smtp.EnableSsl = true;
smtp.Credentials = new
System.Net.NetworkCredential("revaskarprachi22@gmail.com", "prachi2215");
smtp.Send(loginInfo);
Label1.Text = "Password is sent to you email id,you can now <A
href='login.aspx'>Login</A>";
}
else
{
Label1.Text = "Email Address Not Registered";
}
}
FORGET PASSWORD
[70]
FLY WHEEL CAR CARE
[71]
FLY WHEEL CAR CARE
4.User Registration
using System;
using System.Linq;
using System.Web;

{
ConnectionString);
protected void Page_Load(object sender, EventArgs e)
{
}
{
SqlCommand cmd = new SqlCommand("INSERT INTO
registration(name,password,confirmpassword,address,phonenumber,emailid,ve
hiclemodel,vehiclenumber)VALUES('" + TextBox1.Text + "','" + TextBox2.Text + "','"
+ TextBox3.Text + "','" + TextBox4.Text + "','" + TextBox5.Text + "','" + TextBox6.Text
+ "','" + TextBox7.Text + "','" + TextBox8.Text + "')", con);
con.Open();
cmd.ExecuteNonQuery();
con.Close();
Label1.Text = "Registered Successfully";
}
5.Booking Request
using System;
using System.Linq;
using System.Web;
[72]
FLY WHEEL CAR CARE

{
ConnectionString);
{
}
{
bookingrequest(name,emailid,vehiclemodel,vehiclenumber,servicingtype,others)
VALUES('" + TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text + "','" +
TextBox4.Text + "','" + DropDownList1.Text + "','" + TextBox5.Text+ "')",con);
con.Open();
con.Close();
Label1.Text = "Booked appointment Successfully";
}
USER REGISTRATION
[73]
FLY WHEEL CAR CARE
5.Booking Request
using System;
using System.Linq;
using System.Web;
{
ConnectionString);
{
}
{
[74]
FLY WHEEL CAR CARE

bookingrequest(name,emailid,vehiclemodel,vehiclenumber,servicingtype,others)
VALUES('" + TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text + "','" +
TextBox4.Text + "','" + DropDownList1.Text + "','" + TextBox5.Text+ "')",con);
con.Open();
con.Close();
Label1.Text = "Booked appointment Successfully";
}
}
VEHICLE BOOKING REQUEST
[75]
FLY WHEEL CAR CARE
[76]
FLY WHEEL CAR CARE
6.Submition Form
using System;
using System.Linq;
using System.Web;
public partial class ADMIN_Default : System.Web.UI.Page

{
ConnectionString);
{
}
{
submitionform(customername,phoneno,emailid,vehicleno,handoverto)VALUES('"
+ "','" + TextBox5.Text + "')", con);
con.Open();
con.Close();
Label1.Text = "Submited Successfully";
}
}
[77]
FLY WHEEL CAR CARE
VEHICLE SUBMITION FORM
[78]
FLY WHEEL CAR CARE
7.Service Charge Form
using System;
using System.Linq;
using System.Web;
public partial class ADMIN_Default : System.Web.UI.Page

{
ConnectionString);
{
}
{
submitionform(customername,phoneno,emailid,vehicleno,handoverto)VALUES('"
+ "','" + TextBox5.Text + "')", con);
con.Open();
con.Close();
Label1.Text = "Submited Successfully";
}
}
[79]
FLY WHEEL CAR CARE
VEHICLE SERVICE CHARGE FORM
[80]
FLY WHEEL CAR CARE
8.Repaired Details
<%@ Page Title="" Language="C#" MasterPageFile="~/ADMIN/MasterPage.master"
AutoEventWireup="true" CodeFile="repairdetails.aspx.cs"
Inherits="ADMIN_Default" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
<style type="text/css">
.style1
{
text-decoration: underline;
}
.style2
{
font-size: x-large;
text-align: center;
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">

REPAIRED DETAILS


 
<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False"
DataSourceID="SqlDataSource1" BackColor="LightGoldenrodYellow"
BorderColor="Tan" BorderWidth="1px" CellPadding="2" ForeColor="Black"
GridLines="None" Height="165px" Width="1126px">
<AlternatingRowStyle BackColor="PaleGoldenrod" />
<Columns>
<asp:BoundField DataField="id" HeaderText="id"
[81]
FLY WHEEL CAR CARE
SortExpression="id" InsertVisible="False" ReadOnly="True" />

<asp:BoundField DataField="vehicleno" HeaderText="vehicleno"
SortExpression="vehicleno" />
<asp:BoundField DataField="vehiclemodel" HeaderText="vehiclemodel"
SortExpression="vehiclemodel" />
<asp:BoundField DataField="status" HeaderText="status"
SortExpression="status" />
</Columns>
<FooterStyle BackColor="Tan" />
<HeaderStyle BackColor="Tan" Font-Bold="True" />
<PagerStyle BackColor="PaleGoldenrod" ForeColor="DarkSlateBlue"
HorizontalAlign="Center" />
<SelectedRowStyle BackColor="DarkSlateBlue" ForeColor="GhostWhite" />
<SortedAscendingCellStyle BackColor="#FAFAE7" />
<SortedAscendingHeaderStyle BackColor="#DAC09E" />
<SortedDescendingCellStyle BackColor="#E1DB9C" />
<SortedDescendingHeaderStyle BackColor="#C2A47B" />
</asp:GridView>
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
ConnectionString="<%$ ConnectionStrings:car servicingConnectionString %>"
SelectCommand="SELECT id, vehicleno, vehiclemodel, status FROM
problemform WHERE (status = 'Repaired')">
</asp:SqlDataSource>
ConnectionString="<%$ ConnectionStrings:car servicingConnectionString %>"
SelectCommand="SELECT id, vehiclemodel, vehicleno, status FROM
problemform WHERE (status = @Repaired)">
<SelectParameters>
<asp:Parameter Name="Repaired" />
</SelectParameters>
<asp:AccessDataSource ID="AccessDataSource1" runat="server">
</asp:AccessDataSource>
</asp:Content>
REPAIRED VEHICLE DETAILS
[82]
FLY WHEEL CAR CARE
9.Un Repaired Details

AutoEventWireup="true" CodeFile="unrepairedetail.aspx.cs"

.style1
{
text-align: center;
}
.style2
{
text-align: center;
}
</style>
</asp:Content>
[83]
FLY WHEEL CAR CARE
Runat="Server">

UNREPAIRED DETAILS




<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False"
CellPadding="2" DataSourceID="SqlDataSource1" Height="140px"
align="center"
Width="985px" BackColor="LightGoldenrodYellow" BorderColor="Tan"
BorderWidth="1px" ForeColor="Black" GridLines="None">
<Columns>
<asp:BoundField DataField="id" HeaderText="id" InsertVisible="False"
ReadOnly="True" SortExpression="id" />
<asp:BoundField DataField="vehiclemodel" HeaderText="vehiclemodel"
SortExpression="vehiclemodel" />
<asp:BoundField DataField="status" HeaderText="status"
SortExpression="status" />
</Columns>
</asp:GridView>

ConnectionString="<%$ ConnectionStrings:car servicingConnectionString
%>"
SelectCommand="SELECT [id], [vehicleno], [vehiclemodel], [status] FROM
[problemform] WHERE [status]='UnRepaired'">
[84]
FLY WHEEL CAR CARE
UNREPAIRED VEHICLE DETAILS
10.Vehicle Service Job

AutoEventWireup="true" CodeFile="vehicleservicejob.aspx.cs"

.style1
{
[85]
FLY WHEEL CAR CARE
text-align: center;
}
.style2
{
font-size: x-large;
}
</style>
</asp:Content>
Runat="Server">

VEHICLE SERVICE JOB




<asp:GridView ID="GridView1" runat="server"
AutoGenerateColumns="False"
BackColor="LightGoldenrodYellow" BorderColor="Tan" BorderWidth="1px"
CellPadding="2" DataSourceID="SqlDataSource1" Height="144px"
Width="1134px" ForeColor="Black" GridLines="None">
<Columns>
<asp:BoundField DataField="id" HeaderText="id" InsertVisible="False"
ReadOnly="True" SortExpression="id" />
<asp:BoundField DataField="customername"
HeaderText="customername"
SortExpression="customername" />
<asp:BoundField DataField="handoverto" HeaderText="handoverto"
SortExpression="handoverto" />
</Columns>
[86]
FLY WHEEL CAR CARE

</asp:GridView>
<asp:SqlDataSource ID="SqlDataSource2" runat="server"></asp:SqlDataSource>
ConnectionString="<%$ ConnectionStrings:car servicingConnectionString
%>"
SelectCommand="SELECT [id], [customername], [vehicleno], [handoverto]
FROM [submitionform]">
VEHICLE SERVICE JOB DETAILS
[87]
FLY WHEEL CAR CARE
7.Admin Login
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class ADMIN_Default2 : System.Web.UI.Page

{
ConnectionString);
// string strconnString =
ConfigurationManager.ConnectionStrings["myconnectionstring"].ConnectionStrin
g;
string str = null;
SqlCommand com;
{
}
{
object obj = null;
// SqlConnection con = new SqlConnection(strConnString);
con.Open();
Session["Username"] = TextBox1.Text;
str = "select count(*) from adminlogin where username=@Username and
password=@Password";
com.CommandType = CommandType.Text;
com.Parameters.AddWithValue("@Username", Session["Username"]);
com.Parameters.AddWithValue("@Password", TextBox2.Text);
obj = com.ExecuteScalar();
if ((int)(obj) != 0)
{
Response.Redirect("adminwelcome.aspx");
}
[88]
FLY WHEEL CAR CARE
else
{
Label1.Text = "invalid username and password";
}
con.Close();
}
}
ADMIN LOGIN
[89]
FLY WHEEL CAR CARE
[90]
FLY WHEEL CAR CARE
5.3 TEST REPORTS

SYSTEM IMPLEMENTATION
1.1. Methodology Adapted:
The methodology adapted while developing this system is “Waterfall Model”.
Waterfall Model:
This model, shown in figure is also called as Waterfall model, since the
typical diagram looks like a series of cascades. First described by Royce
in1970, it was the first realization of standard sequence of task. There are
many versions of the waterfall model although the specific development tasks
will occur in almost every development; there are many ways to divide them
into phases. This version of the waterfall, the project planning.
[91]
FLY WHEEL CAR CARE
[92]
FLY WHEEL CAR CARE
2 Process Involved In Our System :
The Linear Sequential Model:
System engineering and analysis encompasses requirement

gathering at the system level with small amount of top-level design and analysis.
Information engineering encompasses requirements gathering at a strategic
business level and at the business area level.
Software Requirement Analysis:
The requirement gathering process is intensified and focused specifically on

software. To understand the nature of the program to build, the software
engineer must understand the information domain for the software as well as
required function, behavior, performance and interface. Requirement for both
me system and the software are documented and reviewed with the customer.
Design:
Software design is actually a multi-step process that focuses on four

distinct attributes of program data structure, software architecture, interface
representation and procedural (algorithmic) detail. The design process translates
requirement into representation of the software that can be accessed for quality
before coding begins. Like requirements, the design is documented and becomes
part of the software configuration.
Code Generation:
The design must be translated into a machine-readable form. The code

generation step performs this task If design is performed in a detailed manner,
code generation can be accomplished mechanistically.
Testing:
Once code has been generated, program testing begins. The testing
process focuses on the logical internals of the software, ensuring that all
statements have been tested, and on the functional externals; that is conducting
tests to uncover errors and ensures that defined input will produce actual results
that agree with required results.
[93]
FLY WHEEL CAR CARE
2. System Implementation
Once the designing is complete, it is time for the developers to put them in
place together. Although it has been tested while the designs were created,
it is the final construction of designs as the project manager or the assigned
developers combine them. From this point, developers have to be stand
with what they work for. In the previous stages, developers can freely
make some changes in their software design plans simply because it is still
in the designing phase. In this stage however, there is no going back as
everybody’s effort will be tested.
During this stage different types of errors will be determined. It will
gauge how far the team has advanced in building software. Since they are
also responsible for building software, it is also proper that they have to fix
these problems. Even though it is not mentioned before, this stage will
mark importance of documentation of the software. As the system is being
developed, developers must document on what they have done in this
stage. Once they are brought together, it becomes even more important
since developer will know how their documentation will fair against other
developers.
This phase integrates all the completed developments and allows user and
system testing. This phase delivers the working system in accordance with
defined requirement specification and agreed approach.
Activities Include:
• Link Testing
• System Testing
• User Acceptance Testing
• System Installation
1. Operational Environment
a. Platform being used:
Front-end: ASP.Net version 2010
Back-end: SQL Server 2008
[94]
FLY WHEEL CAR CARE
b. Hardwire requirement:
Min CPU Clock speed: 600 MHz
Processor: Intel core i3
Recommended Clock speed: 800 MHz
RAM: 64MB
Hard drive Space: 300MB as source code
25MB as setup file
Internet connection: Required
Minimum: 64Kbps dial up connection
[95]
FLY WHEEL CAR CARE
06.
CONCLUSION AND
FUTURE
[96]
FLY WHEEL CAR CARE
ENHANCEMENT
6.1 CONCLUSION
The package was designed in such a way that future

modifications can be done easily. The following conclusions can be
deduced from the development of the project.
a. Automation of the entire system improves the efficiency
b. It provides a friendly graphical user interface which proves to be

better when compared to the existing system.
c. It gives appropriate access to the authorized users depending on

their permissions.
d. It effectively overcomes the delay in communications.
[97]
FLY WHEEL CAR CARE
e. Updating of information becomes so easier.
f. System security, data security and reliability are the striking

features.
g. The System has adequate scope for modification in future if it is

necessary.
6.2 FUTURE ENHANCEMENTS
This application avoids the manual work and the problems

concern with it. It is an easy way to obtain the information regarding the various
products information that are present in the Super markets.
Well I and my team members have worked hard in order to

present an improved website better than the existing one’s regarding the
information about the various activities. Still ,we found out that the project can
[98]
FLY WHEEL CAR CARE
be done in a better way.
Primarily, when we request information about a particular

product it just shows the company, product id, product name and no. of
quantities available. So, after getting the information we can get access to the
product company website just by a click on the product name
The next enhancement that we can add the searching

option. We can directly search to the particular product company from this site
.These are the two enhancements that we could think of at present.
SYSTEM MAINTENANCE
AS the number of computer based systems, grieve libraries of computer

software began to expand. In house developed projects produced tones of
thousand soft program source statements. Software products purchased from the
outside added hundreds of thousands of new statements. A dark cloud appeared
on the horizon. All of these programs, all of those source statements-had to be
[99]
FLY WHEEL CAR CARE
corrected when false were detected, modified as user requirements changed, or

adapted to new hardware that was purchased. These activities were collectively
called software Maintenance.
The maintenance phase focuses on change that is associated with error

correction, adaptations required as the software's environment evolves, and
changes due to enhancements brought about by changing customer
requirements. Four types of changes are encountered during the maintenance
phase.
✓ Correction:
Even with the best quality assurance activities is lightly that the
customer will uncover defects in the software. Corrective maintenance
changes the software to correct defects.
Maintenance is a set of software Engineering activities that occur after

software has been delivered to the customer and put into operation.
Software configuration management is a set of tracking and control
activities that began when a software project begins and terminates only
when the software is taken out of the operation.
We may define maintenance by describing four activities that are

undertaken after a program is released for use:
1. Corrective Maintenance
2. Adaptive Maintenance
3. Perfective Maintenance or Enhancement
4. Preventive Maintenance or reengineering
[100]
FLY WHEEL CAR CARE
07.
BIBLOGRAPHY AND
REFERENCES
7.1 WEBSITES:
[101]
FLY WHEEL CAR CARE
• www.google.com
• www.microsoft.com
7.2 BOOKS REFERRED
Sr.No. Type Description

1. Book name : Visual basic
Author : The waite Group’s
Publication : Tata Ma-Graw Hill Edition

2. Book name : Programming in visual basic
6.0
Author : Julia case Bradley,Anita C
Millspough
Publication : Tata Mc-Graw Hill Edition
3. Book name : Database programming with
Visual Basic in 21 days
Author : Curtis Smith &Michale
Amundsen
Publication : MacMillan Computer Publish
,USA
[102]

Black Book Project 12

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Black Book Project 12

Hochgeladen von

Copyright:

Verfügbare Formate

FLY WHEEL CAR CARE

05 IMPLEMENTATION AND TESTING 60

06 CONCLUSION AND FUTURE ENHANCEMENT 88

07 BIBLOGRAPHY AND REFERENCES 92

1.1 Organizational Overview

It provides quality and quick service with easy and free

The repairs and maintenance are done by our skilled

1.2 Description of System

The objective of the Vehicle Services is to provide better

• Automation of the entire system improves the eﬃciency

1.3 Limitation of present system

Existing system is a manual one in which users are maintaining

The following are the disadvantages of the existing system

• It is diﬃcult to maintain important information in books.

• More manual hours need to generate required reports.

• It is tedious to manage historical data which needs much space to keep

1.4 Proposed System and Advantages

The FLY WHEEL CAR CARE ONLINE CAR SERVICING

The following are the advantages of the existing system:

• This website keeps the data in a centralized way which is available to

1.5 Gantt chart

NOV DEC JAN FEB MAR APR

2.1 Feasibility Study

A feasibility study is not warranted for this system in which

It is necessary and prudent to evaluate the feasibility of project at the earliest

The feasibility study may be documented as an appendix to the system

2.1.1 Operational feasibility

• Is there suﬃcient support for the management from the users?

2.1.2 Technical feasibility

•Does the necessary technology exist to do what is suggested?

2.1.3. Economic Feasibility

A system can be developed technically and that will be used if installed

2.2 Software and Hardware requirements

• 512 KB Cache Memory

• Microsoft Compatible 101 or more Key Board

• Operating System : Windows

• Programming language: MS.NET

• Back-End: SQLSERVER 2000

• Web Server: IIS5.1

Microsoft .NET Framework

providing core services such as memory management, thread management,

Features of the Common Language Runtime

and unmanaged code enables developers to continue to use necessary COM

.NET Framework Class Library

• Windows GUI applications (Windows Forms).

Client Application Development

word processors and spreadsheets, as well as custom business applications

Server Application Development

Server-side managed code

are distributed, server-side application components similar to common Web

Active Server Pages.NET

• World-Class Tool Support. The ASP.NET framework is

• Power and Flexibility. Because ASP.NET is based on the common

• Simplicity. ASP.NET makes it easy to perform common tasks, from

site conﬁguration. For example, the ASP.NET page framework allows

• Manageability. ASP.NET employs a text-based, hierarchical

• Scalability and Availability. ASP.NET has been designed with

by the ASP.NET runtime, so that if one misbehaves (leaks, deadlocks), a

• Customizability and Extensibility. ASP.NET delivers a well-factored

• Security. With built in Windows authentication and per-application

What is ASP.NET Web Forms?

ASP.NET provides syntax compatibility with existing ASP pages. This

Code-Behind Web Forms

Introduction to ASP.NET Server Controls