0% found this document useful (0 votes)
37 views

Project

The document provides specifications for a major project report, including formatting requirements such as font, margins, chapter structure, and more. It states that the report should be typed, hard bound, and printed on A4 paper with specified information on the cover. It lists 11 numbered points covering details of the report contents, structure, references, diagrams, graphs, and conclusions. It also states there should be 3 copies of the final report.

Uploaded by

aditya7398460102
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
37 views

Project

The document provides specifications for a major project report, including formatting requirements such as font, margins, chapter structure, and more. It states that the report should be typed, hard bound, and printed on A4 paper with specified information on the cover. It lists 11 numbered points covering details of the report contents, structure, references, diagrams, graphs, and conclusions. It also states there should be 3 copies of the final report.

Uploaded by

aditya7398460102
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 61

SPECIFICATIONS FOR MAJOR PROJECT REPORT

1. Report shall be computer typed (English- British, Font -Times Roman, Size-12
point) and printed on A4 size paper.

2. The Report shall be hard bound with cover page in white colour. The name of the
candidate, degree (specifying the branch) ,roll no, session , year of submission,
name of the University including college name shall be printed in black on the
cover [Refer sample sheet (outer cover)]

3. The report shall be typed on one side only with double space with a margin 3.5
cm on the left, 2.5 cm on the top, and 1.25 cm on the right and at bottom.

4. In the report, the title page [Refer sample sheet (inner cover)] should be given
first then the Certificate by the candidate and the supervisor(s) in sequence,
followed by an abstract of the report (not exceeding 1500 words). This should be
followed by the acknowledgment, list of figures/list of tables,
notations/nomenclature, and then contents with page no.s

5. References and Bibliography should be included in report.

7. The diagrams should be printed on a light/white background, Tabular matter


should be clearly arranged. Decimal point may be indicated by full stop(.)The
caption for Figure must be given at the BOTTOM of the Fig. and Caption for the
Table must be given at the TOP of the Table.

8. The graphs should be combined for the same parameters for proper comparison.
Single graph should be avoided as far as possible.

9. Conclusions must not exceed more than two pages.

10. The report must consist of following chapters


Chapter 1- Introduction
Chapter 2- Requirement Analysis and System Specification
Chapter 3- System Design
Chapter 4- Implementation, Testing and Maintenance
Chapter 5-Results and Discussions
Chapter 6-Conclusion and Future Scope
References
Appendix (if any)
Annexures-I,II,III

11. There should be 3 copies of Final Report.


MAJOR PROJECT REPORT
‘‘Car Washing Management System”
A Project Submitted in partial fulfillment of their
requirements for the award of the Diploma

INFORMATION TECHNOLOGY

Under the Supervision of


Mr.DEVKI NANDAN SHUKLA
SubmittedBy

Aditya Rawat (E21222335600069)


Kajal Maurya (E21222335600060)

Submitted To

HEWETT POLYTECHNIC LUCKNOW


DECLARATION

This is to certify that the project report entitled “Car Washing

Management System” is done by us is an authentic work carried out

for the partial fulfillment of the requirements for the award of the

Diploma in “Information Technology” under the guidance of DN

Shukla. The matter embodied in this project work has not been

submitted earlier for award of any degreeorB.Techto the best of my

knowledge and belief.

Aditya Rawat

Kajal Maurya
ACKNOWLEDGEMENT

I/We would like to express my deep and sincere gratitude to Hewett

polytechnic College, who gave me his full support and encouraged me

to work in an innovative and challenging project for Educational field.

His wide knowledge and logical thinking gave me right direction all the

time.

I/We am deeply grateful my project coordinator for his/her help and

support provided at every step of the project.

Last but not the least, I thank to all employees of I.T. Branch for their

support

and co-operation.

Aditya Rawat

Kajal Maurya
Hewett Polytechnic Lucknow

COMPLETION CERTIFICATE

This is to certify that Aditya Rawat , Kajal Maurya of Diploma (I.T.) from.
Hewett polytechnic Lucknow was working on the project entitled “Car
Washing Management System ”They were engaged.

They have done an excellent job during his engagement with the Software
Development &Testing Division of the company. He has completed his/her
project during the training tenure. His performance has been good and
satisfactory.

I would like to take this opportunity to express my appreciation to Mr.

Aditya Rawat, Kajal Maurya For his and wish him all the very best for his

future end beavours.

Regards,

DN Shukla
Hewett Polytechnic Lucknow
CAR WASHING MANAGEMENT SYSTEM

The car wash management system is easy to use since they only require initial setup and
configuration. The car wash management system also enables the customer to present a
valid tag in front of the antenna, and his details are recorded. Such simplicity in use is driving
the growth of the car wash management system market. The car wash management system
allows users to manage multiple sites by creating a centralized database and installing
master management software. Thus, car wash management system increases the efficiency of
the service provider Such factors are further driving the growth of car wash management
system in the market.

The car wash management system requires a certain infrastructure to be set up. The car wash
management system also requires specific software packages to be purchased. Thus, a lot of
initial investment is required to set up the car wash management system. Such factors are
hampering the growth of car wash management system

The Car Wash Management System market is segmented across North America, Latin
America, Western Europe, Eastern Europe, China, SEA and others of APAC, Japan, and Middle
East & Africa. North America is expected to be a large market for Car Wash Management
System as a majority of the Car Wash Management System vendors such as GAO RFID Inc,
National Carwash Solutions and Innovative Control Systems, Inc. are based in the region. The
increasing requirement of generating customizable reports and just in time access and
availability of data is driving the adoption of Car Wash Management System solutions in
European countries.

The growing popularity of Car Wash Management System in developing regions, such as
APEL, Latin America and parts of Africa, are characterized by the increased spending
connected devices. Rising disposable income among people in the countries mentioned
above is likely to increase the scope of penetration of Car Wash Management System in
these regions in the near future.

The research report presents a comprehensive assessment of the Car Wash Management
System market and contains thoughtful insights, facts, historical data and statistically
supported and industry-validated market data. It also contains projections using a suitable
set of assumptions and methodologies. The research report provides analysis and
information according to market segments such as geographies, application and industry
Members of Project

Aditya Rawat Kajal Maurya


Index
1. Declaration
2. Certificate
3. Acknowledgement
4. Introduction
5.
Overview of Organization
6. Objectives
7. Existing System Description
8. Proposed System
9. Tools Used
10. System
11. Analysis
12. Objective
13.
SDLC Phases

13.1
Feasibility Study
13.2
Report Approval
13.3
System Analysis
13.4
System Design
13.5
Coding
13.6
Testing
13.7
Implementation
13.8
Maintenance

14. Process Description


15. Project Model Used
16. ER-Diagram
17. Data Flow Diagram
18. Software Requirement

19. Specification……….

19.1 Hardware Requirement


19.2 Software Requirement
19.3 Support Maintenance

20. System Design……………


21 . Lo w Level Design
22. 22.1 Description of Classes and Methods
23. Data Modeling
24. List of Tables
25. Structure of Tables
26. Testing
27. Input-Output
28. Forms………

28.1 Modularization Details


28.2 User Screenshots
28.3 Admin Screenshots

29. Future Scope………….


30. Conclusion……………..
INTRODUCTION

Car Washing Management System Project is a web application.


In-Car Washing Management System Project in PHP performed all the operations needed
to clean the car successfully by using highly expert and experienced workers, also
developed mimic of the whole system, works and checked the overall process step by step
by visualization.
In this project, we use PHP and My SQL database. It has two modules i.e. Admin and user

the standard of living of individuals has increased. This has driven the growth of a number

of people owning a MARKET RESEARCH SURVEY private car since it is time-saving and

convenient. This, in tum, has increased the need for car wash service providers. The

growing number of cars has created complexities for car wash service providers to manage

each can which has led to the adoption of car wash management system in the market. The

car wash management system allows car wash service providers to manage profiles of

customers and keep track of the cars that are washed and also records each customer

7
Overview Of Organization

Hewett Polytechnic was originally started at Gorakhpur in 1904.Some-Time in 1908 the


institution wasshifted from Gorakhpur to Lucknow in a rented building at Jagat
NarainRoad ,the main reason being that Lucknow was the capital of Avadh enjoying a central
position in Uttar Pradesh.
Onwards the institution by virtue of well-trained staff and their spirit of great enterprises
progressed by leaps and bounds. It enjoyed not only country wide popularity but a good number
of student, from Middle East, Iran, Tibbet, Bhutan, Ceylon etc. had their training in it. In 1934 the
institution was formally recognized by the. And at a later stage by the Govt. of India also.

Prior to 1957 the institution did not receive any assistance or aid from any quarter -public or
private. In 1957 the institution received a token grant-in-aid by the state Govt. and subsequently
received substantial grants by the state Govt. and Union Govt. for equipment and building and the
net deficit was met by Govt funds. At its inception the institute ran with a single branch of civil
Engineering
In 1957, the institution shifted from hired building to its own premises in Mahanagar, Lucknow.
Ten kilometers distant from Charbagh northern Railway Station and Bus-Station, this polytechnic
now possesses 45 Bigha’s of land.
In 1958-59 the institution was permitted by the state Govt. to start two additional courses i.e.
Diploma in Electrical and Mechanical Engineering in addition to the Civil Engineering branch,
each of three years duration. Shortly afterward a change in nomenclature of the institution from
Hewett Engineering School to Hewett Polytechnic was affected at the instance of the
Government.

The institute is running four courses in Civil, Electrical, Mechanical Engineering and Information
Technology with intake of 60 Students in each branch.As regards norms and standards of
training the polytechnic earnestly intends to follow the guide lines as laid down by the A.I.C.T.E.
statutory apex body on technical education.

8
OBJECTIVES
 You can create your personal account here.
 You can login easily
you can learn Program easily on any language.
There you can increase your programming.
You can meet best programmers.
You can up load your program.
There you can write your programming easy way.
You can buy the premium of programmer sadda for download program.
If you have any error then you can upload on programmer sadda.
 There we provide a Certificate on your choosed programming language
1) Easy for patient stouse and customize.
2) Event Clinic Notification to Patients.
3) To provide best medicine and Diagnostic centerin lowest cost.
8).Organize check all activities/Information of the registered students.
9) Easily accessible from any corner of the world if you have internet connection.
10) Toprovideonlinediscussionboard,betweenallregisteredpatientsandadmin.
To provide medicine and Diagnostic center for patients

9
PROBLEM DEFINITION
In this section we shall discuss the limitation and drawback of the existing system

that forced us to take up this project. Really that work was very typical to manage the daily

errors free records and adding or removing any node from server. This problem produces a

need to change the existing system. Some of these short coming share being discussed

below:-

 Low Functionality

With the existing system, the biggest problem was the low functionality. The

problem faced hampered the work. For small task like adding any new node

to server or deleting anode or keeping daily record we have to appoint

minimum two or three employee.

 Erroneous Input and Output

In the existing system, human sperformed all the tasks. As in the human

tendency , errorisalsoa possibility .Therefore ,the input sentered by the

person who is working in the Company, in the registers may not be

absolutely foolproof and may be erroneous. As a result of wrong input, the

output reports etc. will also be wrong which would in turn affect the

performance.

10
 Portability Problem

System that existed previously was manual. As a result, the system was less

portable. One has to carry the loads of many registers to take the data from

one place to another. A big problem was that the system was less flexible

and if we wanted to calculate yearly or monthly maintenance report or

efficiency report, then it was a big head ache.

 Security-

Security concerns were also one of the motives of the Company for the need

of software. In the registers, the data is not secure as anybody can tamper

with the data written in the registers. While in this software, just a password

makes it absolutely secure from there each of unauthorized persons.

 Data Redundancy

In the case of manual system, the registers are maintained in which, a lot of

detail written.

 Processing Speed

In manual system maintaining a register and performing the necessary

calculation has proved to beat rouble some job, which takes a lot of time and

may affect the performance of the Company. But with this software we can

11
have all the tasks performed in a fraction

Of second by a single click thus making the trouble some job much easier.

 Manual Errors

When a number of tough tasks are prepared by the humans like preparation of
reports, performing long calculation then some human error are obvious due to a
number of factors like mental strain, tiredness etc. But as we all know that computer
never get tire dir respective of the amount of work it has to do. So this software
cannullify the probability of manual error that improve the performance

 Complexity in Work

In manual system whenever a record is to be updated or to be deleted a lot of cutting


And overwriting needs to be done on the registers that are concerned that are deleted
Or updated record, which makes the work very complex

12
SYSTEM ANALYSIS

OBJECTIVE:

After gathering requirements we have decided the following aims and objectives of
Canteen Automation System:

1). To provide online booking from any corner of local area of campus.

2). To provide best services of food material, the student who want to enjoy with
his friend son getting good marks in exams or birthday etc.

3). WealsoprovidestheofferlikeasotherotherRestaurant.thenadminnotifytotheregist
eredstudents.
4).To maintain causer records.

Phases:

System Development Life Cycle (SDLC) mainly consists of the following7


phases which can be detailed:-

Preliminary Investigation:-

This is the first phase of the system development life cycle. In this phase
we tend to find out the needs of the client ―what exactly does the client
want? Before the development of any system the important point is to
know the needs, objectives and scope of the system.

12
Feasibility Study:-

Feasibility study is these conducted step of the system development life cycle.
Things are always easy at the beginning in any software process. In fact nothing is
infeasible with unlimited time and resources. But it is not the fact. So, practically
we have to do in limited resources in a restricted time margin. So for the system to
be feasible, following points we have to consider.
The feasibility study is conducted to check whether the candidate system is
feasible. The system which is selected to be the best against the criteria is thereafter
designed and developed. The feasibility study takes in to consideration, the risks
involved in the project development be forehand. Therefore in this phase we have,
impact on the organization, ability to meet user need and effective use of resources.
We do the feasibility study for website to analyze the risks, costs and benefits
relating to economics, technology and user organization. There are several types of
feasibility depending on the aspect they cover. Import of these includes:

 Technical Feasibility:

Thisisanimportantoutcomeofpreliminaryinvestigation.Itcompriseoffoll
owingquestions:-
 Can the work of project bed one with the current equipment,
existing software and available man power resource?
 If Technology is required what are the possibilities that it can be developed?

 Economic Feasibility:

It deals with question related to the economy. It comprise of the following questions:-
 Are there sufficient benefits in creating the system to make the cost acceptable?
 Are the cost soft not creating the system so great that the
project must be undertaken?
12
 Legal Feasibility:

It deals with the question related to the legal issues. It comprise of the following
questions:-
 Contract Signing
 Software License agreement
 Issue related to cyber laws.
 Legal issues relating to the man power contract.

 Operational Feasibility:

The operational feasibility consists of the following activity:-

 Will the system be use fully developed & implemented?


 Will there be resistance from employee?

 Social & Behavioral Feasibility:

It deals with the various issues related to the human behavior like:-
 Whether the user be able to adapta new change or not?
 Whether the ambiance we are providing suits the user or not?

Request Approval:-

Request approval is the third phase of system development lifecycle. Request


approval is the phase in which all the requirements which would be provide in the
system are stated. The request approval is a sort of agreement between the client
and the company which is building this software. Both the parties should be
mutually agreed on the stated requirements.

13
System Analysis:-

System analysis is the phase following the phase of the request approval. In
this phase we tend to analyze the overall system which we have to build.
System analysis is the crucial part in SDLC.

System Design:-

System design means the designing of the system. The System can be done in
either of the following two ways:-

 Logical System Design


 Physical System Design

Coding:-

Coding is the phase in which a developer codes using any programming


languages. Coding constitutes only20 %of the whole project and which is
easier to write. The coding work is also done in the teams; development of the
system is usually done under the modular programming style, which can be
either top-down approach or bottom-up approach.

Testing:-

Testing is the phase in which the system that has been developed is tested.
Testing comprises of the 60%ofthe overall development of the system. Testing
of the system is important because testing aims toun cover the different errors
in the system. There are various different testing techniques that can be used
for the testing of the system.
14
Implementation:-

Implementation process involved the installation of software on user’s side.


Implementation process actually depends on type of a system &various. Opting
for suitable conversion approach is as implementation. The conversion
processes are as follows:-

 Parallel Conversion
 Direct Conversion Approach
 Pilot Conversion Approach
 Phase In Conversion Approach

Maintenance:-

Merely developing the system is not important but also maintenance is important.
The company that has built the system provides for some time free of cost
maintenance to the client and after that period it is usually a paid service.

15

15
Process Description

Gantt charts mainly used to allocate resources to activities. The resources allocated
to activities include staff, hardware, and software. Gantt charts (named after its
developer Henry Gantt) are useful for resource planning. A Gantt chart is special
type of bar chart where each bar represents an activity. The bars are drawn along a
timeline. The length of each bar is proportional to the duration of the time planned
for the corresponding activity.
Gantt chart is a project scheduling technique. Progress can be represented easily in
a Gantt chart, by coloring each milestone when completed. The project will start in
the month of January andendafter4monthsatthebeginningof April.

16
PROJECT MODELUSED

Iterative Enhancement Model

 This model has the same phases as the water fall model, but with
fewer restrictions.
Generally the phases occur in the same order as in the water fall model, but they
may be
Conducted in several cycles.
 Useable product is released at the end of the each cycle, with each
release providing additional functionality. Customers and developers specify
as many requirements as possible and prepare a SRS document. Developers
and customers then prioritize these requirements. Developers implement the
specified requirements in one or more cycles of design, implementation and
test based on the defined priorities.

The procedure itself consists of the initialization step, the iteration step, and
the Project Control List. The initialization step creates a base version of the system.
The goal for this initial implementation is to create a product to which the user can
react. It should offer a sampling of the key aspects of the problem and provide a
solution that is simple enough to understand and implement easily. To guide the
iteration process, a project control list is created that contains are cord of all tasks
that need to be performed. It includes such items as new features to be
implemented and areas of redesign of the existing solution. The control list is
constantly being revised as a result of the analysis phase.

The iteration involves there design and implementation of iteration is to be


simple, straight forward, and modular, supporting redesign at that stage or as a task
added to the project control list. The level of design detail is not dictated by the
17
iterative approach. In a light-weight iterative project the code may represent the
major source of documentation of the system; however, in a critical iterative
project a formal Software Design Document may be used. The analysis of an
iteration is based upon user feedback, and the program analysis facilities available.
It involves analysis of the structure, modularity, usability, reliability, efficiency, &
achievement of goals. The project control list is modified in light of the analysis
results.

18
PHASES:

Incremental development slices the system functionality into increments


(portions). In each increment, a slice of functionality is delivered through cross-
discipline work, from the requirements to the deployment. The unified process
groups increments/iterations into phases: inception, elaboration, construction, and
transition.
 Inception identifies project scope, requirements (functional and non-functional)
and risks at a high level but in enough detail that work can be estimated.
 Elaboration delivers a working architecture that mitigates the top risks and
fulfills the non-functional requirements.
 Construction incrementally fills-in the architecture with production-ready
code produced from analysis, design, implementation, and testing of the
functional requirements.
 Transitiondeliversthesystemintotheproductionoperatingenvironment.

19
ER-Diagram

Introduction:-

In software engineering, an entity - relationship model(ERM) is an abstract and


conceptual representation of data. Entity-relationship modeling is a database
modeling method, used to produce a type of conceptual schema or semantic data
model of a system, often a relational database, and its requirements in a top-down
fashion. Diagrams created by this process are called entity- relationship diagrams,
ER diagrams, or ERDs. ER Diagrams depicts relationship between data objects.
The attribute of each data objects noted in the entity-relationship diagram can be

20
described using a data object description. Entity relationship diagram is very basic,
conceptual model of data and it is fundamental to the physical database design.
This analysis is then used to organize data as relations, normalizing relations, and
obtaining a Relational database.

The entity- relationship model for data uses three features to describe data. These are:
1. Entities which specify distinct real-world items in an application.

2. Relationship, which connect entities and represent meaningful


dependencies between them.

3. Attributes which specify properties of entities &relationships

21
Data Flow Diagram

Introduction:-

DFD is an acronym for the word Data Flow Diagram. DFD is pictorial
representation of the system. DFD is a graphical representation of the ―flow of
data through the information system.DFD are also used forth visualization of data
processing (structured design). ADFD provides no information about the timings of
the process, or about whether process will operate in parallel or sequence. DFD is
an important technique for modeling a system’s high-level detail by showing how
input data is transformed too input results through as sequence of functional
transformations. DFD reveal relationships among between the various components
in a program or system. of DFD lies in the fact that using few symbols we are able
to express program design in an easier manner .ADFD can be used to represent the
following:-
 External Entity sending and receiving data.
 Process that change the data.
 Flow of data within the system.
 Data Storage locations.

Uses of DFD:-

The main uses of data flow diagrams are as follows:-


DFDisamethodofchoiceforrepresentationofshowingofinformationthroughasystemb
ecause of the following reasons:-

 DFD s are easier to understand by technical and non-technical audiences.


 DFD scan provide a high level system over view , complete
with bound and connections too their system.
22
0 LevelDFD:-

1 LevelDFD:-

2. LevelDFD:-

23
SOFTWAREREQUIREMENTSPECIFICATION
A requirements specification for a software system is a complete description of the
behavior of a system to be developed and it includes a set of use cases that describe
all the interactions the users will have with the software. In addition to use cases,
the SRS also contains non-functional requirements.

Non-
functionalrequirementsarerequirementswhichimposeconstraintsonthedesignorimple
mentation (such as performance engineering requirements, quality standards, or
design constraints).Requirements are a sub-field of software engineering that deals
with the elicitation,analysis,specification,andvalidationofrequirementsforsoftware.

The software requirement specification document enlists all necessary


requirements for project development. To derive the requirements we need to have
clear and thorough understanding of the products to be developed. This is prepared
after detailed communications with project team and the customer.

Hardware Requirements

(A) For Client Side–


 Internetexplorer8,Chrome orany supported browser
 Pentium4
 256MBRAM
 1GBHDD

(B) For Server Side–


 Xeon based or higher end Server
 4 GBRAM
200GBdiskspace

Software Requirements

 Client on Internet : Web Browser, Operating System(any).


 Client on Intranet: Client Software, Web Browser, Operating System(any).
 Web Server: IIS7 or higher, Operating System(windows server).
 Application frame work: Microsoft. NET Framework 4.0.
 Data Base Server: MS SQLSERVER2008R2, Operating System(windows Server).
 DevelopmentEnd:VisualStudio2012(ASP.NET,HTML,JavaScri
pt),MSSQLSERVER2008,OS(WindowsServer),WebServer(IIS
6orhigher).
SUPPORT AND MAINTENANCE

One year free support for rectifying system bugs including front end and beck end
will be provided. During war ran typeriod Software Engineers will be responsible
fore moving bugs and improving it. After one year support can be extended @
20% of the total product deployment cost.

SYSTEM DESIGN APPROACH

Top–Down designing:

The top - down designing approach started with major components of the system.
It is a step wise refinement which starts from an abstract design, in each steps the
design is refined two or more concrete levels until were acha level where no–more
refinement is possible not needed.

Bottom–Up designing:

In bottom – up designing the most basic and primitive components are designed
first, and we proceed to higher level components. We work with layers of
abstractions and abstraction are implemented until the stage is reached where the
operations supported by the layer is complete.
Approach we are following:

In this project we are following Mixed Approach i.e. A combination of top–


down and bottom
– up. We are developing some of the components using top – down designing
approach (e.g. the Web Pages) and the some components in bottom – up designing
approach (e.g. the middle tier classes).

DATA MODELING

LISTOFTABLES:

1. Tbl_Create Account
2. Tbl_Enquaiy
3.Tbl_Review
4.Tbl_Notification
5.Tbl_Login
1. Tbl_CreateAccount
Field Name Data Type Status
Name Var char(100) Not null
Father’s Name Var char(7) Not null
Gender Var char(100) Not null(Primary key)
DOB Var char(20) Not null
College Var char(Max) Not null
Course Var char(Max) Not null
Year Var char(20) Not null
Address Var char(30) Not null
Contact Var char(70) Not null
Email Var char(120) Not null
Password Var char(30) Not null
Profile Var char(200) Not null
Reg Date Date Time Null

2. Tbl_Enquiry
FieldName DataType Status
Id Int Not null(primary key)
Name Var char(50) Not null
Mobile Var char(30) Not null
Email Id Var char(90) Not null
Massage Var char(100) Not null
End_Date Date time Null

3. Tbl_Review
FieldName DataType Status
ID Int Not null(primary key)
Name Var char(100) Not null
Percentage Var char(20) Not null
Review_date Date time Null
4. Tbl_ Login
Field Name Data Type Status
ID Int Not null(primary key)
Email Id Var char(100) Not null
Password Var char(60) Not null

5. Tbl_Notification
Field Name Data Type Status
ID Int Not null(primary key)
Notification Var char(100) Not null
Notification Type Var char(60) Not null
Low Level Design

Description: Low Level Design creation is one of the most important


activities in the development of any software product. The low level design
document gives the design of the actual software application. Low level
design document is based on High Level Design document . It defines
internal logic of every sub module. A good low level design document will
make the application very easy to develop by the developer. An effective
design do comment result sin very lower fort sin developing a Software
product.

Each project's low level design document should provide a complete


anddetailedspecificationofthedesignforthesoftwarethatwillbedeveloped in
the project,
Including the classes, member and non-member functions, and associations
between classes that are involved.

The low level design document should contain a listing of the declarations
of all the classes, non-member-functions, and class member functions that will be
defined during the sub sequentimp lamentation stage, along with the associations
between those classes and any other details of those classes (such as member
variables) that are firmly determined by the low level design stage. The low level
design document should also describe the classes, function signatures, associations,
and any other appropriate details, which will be involved in testing and evaluating
the project according to the evaluation plan defined in the project's requirements
document.

29
TESTING

Testing is the integral part of any System Development Life Cycle insufficient and
interested application tends to crash and result in loss of economic and manpower
investment be sides user’s dissatisfaction and down fall of reputation.

“Software Testing can be looked upon as one among much process, an


organization performs, and that provides the last opportunity to correct any flaws in
the developed system. Software Testing includes selecting test data that have more
probability of giving errors.” The first step in System testing is to develop the plan
that all aspect of system .Complements, Correctness, Reliability and
Maintainability.

Software is to be tested for the best quality assurance, an assurance that


system meets the specification and requirement for its in ten de use and
performance.
System Testing is the most use ful practical process of executing the
program with the implicitintention of finding errors that makes the program fail.

Types of Testing

Black Box (Functional) Testing:

30
Testing against specification of system or component. Study it by examining its
inputs and related outputs. Key is to devise inputs that have a higher likelihood of
causing outputs that reveal the presence of defects. Use experience and knowledge
of domain to identify such test cases. Failing this a systematic approach may be
necessary. Equivalence partitioning is where the input to a program falls into a
number of classes, e.g. positive numbers vs. negative numbers. Programs normally
behave the same way for each member of a class. Partitions exist for both input and
output. Partitions may be discrete or overlap. Invalid data (i.e. outside the normal
partitions) is one or more partitions that should be tested.

Internal System design is not considered in this type of testing. Tests are based on
requirements and functionality.
This type of test case design method focuses on the functional requirements of
thesoftware,ignoringthecontrolstructureoftheprogram.Blackboxtestingattemptstofin
derrorsinthe
 Following categories:
Incorrect o r missing functions.

Interface errors.

Errors in data structures or external database access.

Performance errors.

Initialization and termination errors.

White Box(Structural) Testing

Testing based on knowledge of structure of component(e.g .by looking at source


code).Advantage is that structure of code can be used to find out how many test
case need to be performed. Knowledge of the algorithm (examination of the code)

31
can be used to identify the equivalence partitions. Path testing is where the tester
aims to exercise every independent execution path through the component. All
conditional statements tested for both true and false cases. If a unit has n control
statements, there will be up to 2n possible paths through it. This demonstrates that
it is much easier to test small program units than large ones. Flow graphs are a
pictorial representation of the paths of control through a program(ignoring
assignments, procedure calls and I/O statements). Use flow graph to design test
cases that execute each path. Static tools may be used to make this easier in
programs the complex branching structure. Tools support. Dynamic program
analysers instrument a program with additional code. Typically this will count
how many times each statement is executed. At end print out report showing which
statements have and have not been executed. Problems with flow graph derived
testing:
 Data complexity could not taken to account.
 We cannot test all paths in combination.

In really only possible at unit and module testing stages because beyond
that complexity is too high.
Thistestingisbasedonknowledgeoftheinternallogicofanapplication’scode.Alsoknow
nasa Glass Box Testing .Internal software and code working should be known for
this type of testing. Tests are base don coverage of code statements,
branches ,paths ,conditions.

Unit Testing:

Unit testing concentrates on each unit of the software as implemented in the code.
This is done to check syntax and logical errors in programs. At this stage, the test
focuses on each module individually, assuring that it functions properly as a unit.
In our case, we used extensive white-box testing at the unit testing stage.
32
A developer and his team typically do the unit testing do the unit testing is done in
parallel with coding; it includes testing each function and procedure.

Increment al Integration Testing:

Bottom up approach for testing i.e. continuous testing of an application as new


functionality is added; Application functionality and modules should be
independent enough to test separately done by programmers or by testers.

Integration Testing:

Testing of integration modules to verify combined functionality after


integration .Modules are typically code modules, individual applications, client
and server and distributed systems.

Functional Testing:

This type of testing ignores the internal parts and focus on the output is as per
requirement
ornot.Blackboxtypetestinggearedtofunctionalityrequirementsofanapplication.

System Testing:

Entire system is tested as per the requirements. Black box type test that is based on
overall requirement specifications cover sall combined part so for system.

End-to-End Testing:

Similar to system testing ,involves testing of a complete application environment


33
in a situation that mimics real-world use, such as interacting with a database ,using
network communications, or interacting with hardware, applications ,or system if
appropriate.

Regression Testing:
Testing the application as a whole for the modification in any module or
functionality. Difficult to cover all the system in regression testing so typically
automation tools are used for these testing types.

Acceptance Testing:

Normally this type of testing is done to verify if system meets the customer
specified requirements. User or customers do this testing to determine whether to
accept application.

Performance Testing:

Term often used interchangeably with “stress” and “load” testing, To check
whether system meets performance requirements ,Used different performance and
load tools to do this.

Alpha Testing:

In house virtual user environment can be created for this type of testing. Testing
is done at the end of development. Still minor design changes may be madeasa
result of such testing.

Beta Testing:

Testing typically done by end-user so others. This is final testing be for releasing
application for commercial purpose.

34
Description Of Classes and Methods:

Data manager.cs:

usingSystem;
usingSystem.Collection
s.Generic;usingSystem.
Linq;
using
System.Web;usi
ngSystem.Data;
usingSystem.Data.Sq
lClient;usingSystem
.IO;

namespaceCarwashingmanagemetsystem.Models
{
publicclassDatabaseManager
{
SqlConnectioncon = new SqlConnection(@"Data
Source=DESKTOP-129QF40\
SQLEXPRESS;InitialCatalog=student_tbl;Integrated
Security=True");
publicboolInsertUpdateAndDelete(stringcommand)
{
SqlCommandcmd = new
SqlCommand(command,con);if(Con
nectionState.Closed==con.State
)
{
con.Open();
}
int
n=cmd.ExecuteNonQue
ry();if(n>0)
return
true;else
returnfalse;
}
publicDataTableGetAllRecord(stringcommand)
{
35
SqlDataAdaptersa = new
SqlDataAdapter(command,con);DataTab
ledt=new DataTable();
sa.Fill(
dt);retu
rndt;

}
}

Captch a Generator.cs:-
usingSystem;
usingSystem.Collection
s.Generic;usingSystem.
Linq;
usingSystem.Web;

namespaceCarwashingmanagementsystem.Models
{
publicclassCaptchaGenerator
{
publicstring captcha()
{
char ch1, ch2, ch3,
ch4, ch5;stringcph;
Randomrm =newRandom();
ch1=(char)(rm.Next(65,90));
ch2=(char)(rm.Next(48,55));
ch3=(char)(rm.Next(97,122));
ch4=(char)(rm.Next(65,90));
ch5=(char)(rm.Next(50,55));
cph=(ch1+""+ ch2+""+ ch3+""+ ch4 +""+
ch4+""+ ch5).ToString();returncph;
}

}
}

36
Encryption Manager.Cs
usingSystem;
usingSystem.Collection
s.Generic;usingSystem.
Linq;
using
System.Web;usi
ngSystem.Text;

namespaceCarwashingmanagementayatem.Models
{
publicclassEncryptionManager
{
publicstringEncrrypt(stringencrpt)
{
byte[]
b;strin
genc;
b =
ASCIIEncoding.ASCII.GetByte
s(encrpt);enc=Convert.ToBas
e64String(b);
returnenc;
}
//codefordecryptdata
publicstring Decrypt(stringdecrpt)
{
byte[]
b;string
dec;
b =
Convert.FromBase64String(d
ecrpt);dec =
ASCIIEncoding.ASCII.GetStr
ing(b);returndec;
}
}

37
User Screen Short

HOME PAGE-:

38
Contact Us:-

39
WASHING PLAN:

CARWASHING AND DETAILING-:


40
41
Index. Cs html:-
@{
ViewBag.Title = "Index";
Layout = "~/Views/Shared/HomeMaster.cshtml";
}
<head>
<style>

.p1 {
min-height:100px;
background:rgba(84,85,99,0.27);
margin:18px;
border-radius:0px20px0px20px;
padding-top:32px;
text-decoration:none;
font-size:20px;
text-align:center;
font-weight:bold;
color:green;

}
.p1:hover {

background:white;

}
.p2 {
min-height:100px;
background:rgba(240,163,163,0.77);
margin:18px;
border-radius:20px0px20px0px;
padding-top:32px;
text-decoration:none;
font-size:20px;
text-align:center;
font-weight:bold; 42
color:green;

}
.p2:hover {

background:white;

}
.t {
min-height:120px;
width:100%;
}
.t1 {
min-height:120px;
width:100%;
}
</style>
</head>

<!--Start Preloader-

<divclass="preloader">
<divclass="sk-spinner sk-spinner-wave">
<divclass="sk-rect1"></div>
<divclass="sk-rect2"></div>
<divclass="sk-rect3"></div>
<divclass="sk-rect4"></div>
<divclass="sk-rect5"></div>
</div>
</div>
<!--End Preloader-->

<!-- start home -->


<sectionid="home"style="min-height:600px">
<divclass="row slider">

<divclass="col-md-offset-2 col-md-8 inner">


43
<h1class="wow fadeIn"data-wow-offset="50"data-wow-
delay="0.9s"style="font-size:40px;color:white;font-weight:300">We make
website that are<span>awesome</span></h1>
<divclass="element">
<divclass="sub-element">Hello, This is a HTML Website.</div>
<divclass="sub-element">Awesome Website is Designed and provided by

ADITYA RAWAT , KAJAL MAURYA.</div>


<divclass="sub-element">If you need these kind of website, Please
contact us.</div>
</div>
<adata-scrollhref="#about"class="btnbtn-default wow

fadeInUp"data-wow-offset="50"data-wow-delay="0.6s">GET STARTED</a>
</div>

</div>
</section>
<!-- end home -->

<divclass="container-fluid"style="background:gray;">

<h2class="wow bounceIn"data-wow-offset="50"data-wow-

delay="0.3s"style="color:white;font-size:50px;text-align:center;font-

weight:bold">INTRO<spanstyle="font-size:50px;font-weight:bold;
color:rgb(20,60,121)">DUCTION</span></h2>
<divclass="container">
<divclass="row"style="background:gray;">
<divclass="container"style="background:rgba(68,119,147,0.74);border-

radius:30px30px0px0px">
<pstyle="font-size:18px;text-align:justify;padding:50px;color:white">The

Car Washing Management System is a leading and award winning it solution

Company providing full cycle services id areas of software development


web based enterprises
solution, web 44
Application portal development, and iphone application

development.<br><br>
The Car Washing Management System was set up by a group of well-

educated, highly

qualified, hugely
experienced technically sound, and extremely talented College Student,

each one of whom is


an expert in his own field. At TCA, we carry out projects dealing with

Web Development,
applications in Financial Domain, and Smart Phone applications

delivering quality “ every


time on time ”.<br><br>
Car Washing Management System brings innovative Ideas and cutting-edge
technology

into the business of


customer relationship. We take full advantage of the web and make it be

work for you.<br><br>


Our credibility and accountability ensure professional and rapid project

accomplishment of
any size – from small websites to complex software systems with

quality.<br><br>
Our highly skilled programmers accomplish various site development

projects starting from

scratch working in various web development

</p>

45
</div>

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

<divclass="container-fluid"style="background:gray;padding-top:50px">
<divclass="row"style="min-height:700px">
<divclass="container"style="min-

height:550px;background:lightgray;border-radius:0px0px30px30px">
<divclass="row">
<divstyle="min-height:80px;">
<h2class="wow bounceIn"data-wow-offset="50"data-wow-

delay="0.3s"style="color:darkblue;font-size:50px;text-align:center;font-

weight:bold">STUDY <spanstyle="font-size:50px;font-

weight:bold;color:rgb(255,0,220)"> MATERIAL</span></h2>
</div>
</div>
<divstyle="min-height:400px;background:rgba(47,45,45,0.92);border-

radius:20px">
<divclass="pp1">
<divclass="container t1">
<divclass="row">
<ahref="https://www.w3schools.com/c/index.php"><divclass="col-sm-2

p2">C</div></a>
<ahref="https://www.w3schools.com/cs/index.php"><divclass="col-sm-2

p1">C#</div></a>
<ahref="https://www.w3schools.com/html/default.asp"><divclass="col-sm-2

p2">HTML</div></a>
<ahref="https://www.w3schools.com/html/default.asp"><divclass="col-sm-2

p1">CSS</div></a>
46
<ahref="https://www.w3schools.com/bootstrap/bootstrap_ver.asp"><divclass="

col-sm-2 p2">BOOTSTRAP</div></a>
</div>
</div>

<divclass="container t1">
<divclass="row">
<ahref="https://www.w3schools.com/js/default.asp"><divclass="col-sm-2

p1">JavaScript</div></a>
<ahref="https://www.w3schools.com/jquery/default.asp"><divclass="col-sm-

p2">JQuery</div></a>
<ahref="https://www.w3schools.com/java/default.asp"><divclass="col-sm-2

p1">JAVA</div></a>
<ahref="https://www.w3schools.com/python/default.asp"><divclass="col-sm-

2 p2">PYTHON</div></a>
<ahref="https://www.w3schools.com/angular/default.asp"><divclass="col-

sm-2 p1">AngularJS</div></a>
</div>
</div>

<divclass="container t">
<divclass="row">
<ahref="https://www.w3schools.com/php/default.asp"><divclass="col-sm-2

p2">PHP</div></a>
<ahref="https://www.w3schools.com/cpp/default.asp"><divclass="col-sm-2

p1">C++</div></a>
<ahref="https://www.w3schools.com/sql/default.asp"><divclass="col-sm-

47
2p2">MySQL</div></a>

<ahref="https://www.tutorialspoint.com/laravel/index.htm"><divclass="col-
sm-2 p1">LARAVEL</div></a>

<ahref="https://www.w3schools.com/django/index.php">
<divclass="col-sm-2 p2">DJango</div></a>
</div>
</div>

</div>

</div>
</div>

</div>

Contact Us. Cs html:-

@{
ViewBag.Title="ContactUs";
Layout="~/Views/Shared/HomeMaster.cshtml";
}

<!--startcontact-->
<sectionstyle="background:#202020">

<divclass="container-fluid">
<div class="row" style="min-
height:400px;background-image:url('../Content/ima
ges/1.jpg');background-size:cover">
<divclass="col-md-12"style="padding-top:150px">
<h2class="wowbounceIn"data-wow-
offset="50"data-wow-delay="0.3s"style="color:white;font-
size:45px;text-align:center;font-weight:bold">CONTACT <span
style="font-size:50px;font-weight:bold;color:darkcyan">US</span></
48
h2>
</div>
</div>
</div>

<divclass="container"id="contact">
<divclass="row">
<divclass="col-md-6col-sm-6col-xs-
12wowfadeInLeft"data-wow-offset="50"data-wow-
delay="0.9s"style="padding-top:20px">
<formaction="/Home/ContactUs"method="post">
<label>NAME</label>
<inputname="Name"type="text"class="form-
control">

<label>EMAIL</label>
<inputname="Email"type="email"class="form-
control">
<label>MOBILE No.</label>
<inputname="Mobile"type="number"class="form-
control">

<label>MESSAGE</label>
<textareaname="msg"rows="4"class="form-
control"i></textarea>

<inputtype="submit"class="form-control">
</form>
</div>
<divclass="col-md-6col-sm-6col-xs-
data-wow- 12wowfadeInRight"data-wow-offset="50"
delay="0.6s">
<address>
<pclass="address-
title"style="color:white">OUR ADDRESS</p>

49
<spanstyle="color:white">If You Make Awesome Website Please Contact :-

<br>Turbo Technology, Lko.</span>


<p><iclass="fa fa-phone"style="padding-

top:8px"></i>&nbsp;&nbsp;&nbsp;&nbsp;+91 7398XXXXXX</p>
<p><iclass="fa fa-envelope-o"style="padding-

top:8px"></i>&nbsp;&nbsp;&nbsp;&nbsp;[email protected]</p>
<p><iclass="fa fa-map-marker"style="padding-

top:8px"></i>&nbsp;&nbsp;&nbsp;&nbsp;Turbo Technology Lko.</p>


</address>
<ulclass="social-icon">
<li><h3style="color:white">WE ARE

SOCIAL</h3></li>

<li><ahref="#"class="fa fa-facebook"></a></li>
<li><ahref="#"class="fa fa-twitter"></a></li>

<li><ahref="https://www.youtube.com/channel/UC4yzoGuKkCL_8FzI-B-0

x83A"class="fa fa-youtube"></a></li>

</ul>
</div>
</div>
</div>
</section>
<!-- end contact -->

Programmerlist.cshtml:-

@{
ViewBag.Title="ProgrammerList";
Layout="~/Views/Shared/HomeMaster.cshtml";
}

<!--startteam-->
<sectionid="team">
<divclass="container">
<divclass="rowteam-body">
50
<divclass="col-md-12"style="height:100px;">
<h2class="wowbounceIn"data-wow-
offset="50"data-wow-delay="0.3s"style="font-
size:45px;color:white;text-align:center"><span style="font-
size:45px;color:cyan;font-weight:bold">OUR</span>TEAM</h2>
</div>
<divclass="col-md-3col-sm-6col-xs-12wowfadeIn"data-wow-
offset="50"data-
wow-
delay="1.3s <divclass="team-wrapper"style="height:360px;">
"> <ahref="../Home/member1">
<imgsrc="~/Content/team/246.jpg"class="img-
responsive"alt="team img 1">
<divclass="team-des">
img1"> <h4>Er. ADITYA RAWAT</h4>
<span>Designer and developer</span>

</div>
</a>
</
div>
</div>
<divclass="col-md-3col-sm-6col-xs-12wowfadeIn"data-wow-
wow- offset="50"data-
delay="1.6s
"> <divclass="team-wrapper"style="height:360px;">
<ahref="../Home/member2">

51
<imgsrc="~/Content/team/840.jpg"class="img-
img2 responsive"alt="team img 2">
"> <divclass="team-des">
<h4>Er. ADITYA RAWAT</h4>

<span>Director and Tester</span>


</div>
</a>
</
div>
</div>
<divclass="col-md-3col-sm-6col-xs-12wowfadeIn"data-wow-
offset="50"data-
wow-
delay="1.3s <divclass="team-wrapper"style="height:360px;">
"> <ahref="../Home/member3">
<imgsrc="~/Content/team/126.jpg"class="img-
responsive"alt="team img 3">
<divclass="team-des">
alt="teamim <h4>KAJAL MAURYA</h4>
g3"> <span>Developer AND Costomer service
Representative</span></a>
</div>
</
</div> div>
<divclass="col-md-3col-sm-6col-xs-12wowfadeIn"data-wow-
offset="50"data-
wow-
delay="1.6s <divclass="team-wrapper"style="height:360px;">
"> <ahref="../Home/member4">
<imgsrc="~/Content/team/149.jpg"class="img-
responsive"alt="team img 4">
<divclass="team-des">
alt="teamim <h4>ADITYA RAWAT</h4>
g4"> <span>Projet Manager and SEO specialist</span>

</div>
</a>
</
div>
</div>
52
</ </div>
section> </
div>
<!--endteam-->
<!--startservice-->
<sectionid="service">
<divclass="container">
<divclass="row">
<divclass="col-md-12">
<h2class="wowbounceIn"data-wow-
offset="50"data-wow-delay="0.3s"style="color:white;font-
size:30px;font-weight:bold;text-align:center;word-spacing:10px">OUR
<spanstyle="font-size:35px;color:cyan;font-weight:300">AWESOME</span
>THINGS</h2>
</div>
<divclass="col-md-4activewowfadeIn"data-wow-
offset="50"data-wow-
delay="0.
6s"> <iclass="fafa-laptop"></i>
<h4>Web Design</h4>
<p>It is a longest abolished fact that a reader
will be distracted by the
Read able content of a page when looking at its layout. The point of
using Lorem Ipsum is that it has a more-or-less normal distribution of
letters, as opposed tousing' Content here, content here',making it look
like readable English. Many desktop publishing packages and web page
editors now use Lorem Ipsum as their default model text, and a search
for' loremip sum' will un cover many websites still in their infancy.</p>

delay="0.9s">

53
</div>
<divclass="col-md-4activewowfadeIn"data-wow-offset="50"data-wow-

<iclass="fafa-cloud"></i>
<h4>Cloud Computing</h4>
</div>
<divclass="col-md-4activewowfadeIn"data-wow-
offset="50"data-wow-
delay="0.
6s"> <iclass="fafa-cog"></i>
<h4>UX Design</h4>
<p>Contrary to popular belief, Lorem Ip sum is not
simply random text. It
has roots in a piece of classical Latin literature from 45 BC, making it
over 2000 years old. Richard Mc Clintock, a Latin professor at Hampden-
Sydney College in Virginia, looked up one of the more obscure Latin
words, consectetur, from a Lorem Ipsum passage, and going through the
cites of the word in classical literature, discovered the un doubtable
source.</p>
</div>
</div>
</div>
</section>
<!--endservie-->

54
FUTURE SCOPE-:

Alerts for geofence transitions may be late or not received at all. Depending on the size
of the radius and when the device receives location updates, a transition event may not occur. If
the application is open, the accuracy will be higher because it will be regularly requesting
updates, but when the application closes the location request stops and geofence transitions are
managed only by the Android geofence service. Clashes will occur if the same names are used
for the tags. This happens when a geofence transition is triggered, as the application searches
through a complete list
ofGeoTagobjectstomatchthetriggeringIDagainstthetagname.Thiscouldbefixedbyimplementingau
nique ID for each tag

CONCLUSION:

It was an exciting project to work on and there is a lot I learnt from it, above and beyond its original
scope. I was able to study and train myself on development in an environment that was almost
completely foreign to me, which I believe I have been reason ably successful with. Although I was
not able to complete some of the proposed functionality, the functionality related to the core
purpose of the application is working as desired. I believe there is still a lot of potential for this
application, and will continued evelopment in the future.

References:
[1] ASP.NET MVC and Web
Development
Overview,http://msdn.microsoft.com/en-
us/library/4w3ex9c2.aspx

[2] MicrosoftVisualStudioOverview,http://
en.wikipedia.org/wiki/
Microsoft_Visual_Studio#Visual_Studio_2012
[3] Microsoft SQL Server
2008,http://en.wikipedia.org/wiki/Micr
osoft_SQL_Server
[4] 3-Tier System
Architecture,http://en.wikipedia.org/w
iki/Multitier_architecture
[5] Introduction to
ADO.NET,http://en.wikipedi
a.org/wiki/ADO.NET
55
[6] Load Testing using Apache
JMeter Testing Tool,
http://jakarta.apache.org/jmeter/
[7] Introduction to .NET
Architecture,http://www.devt
opics.com/what-is-net/
[8] CommonLanguage Infrastructure
Definition,http://en.wikipedia.org/wiki/Common
_Language_Infrastructure
[9] AJAX – Bridging the Thin-Client Performance
Gap,http://www.ironspeed.com/articles/ajax-bridging
%20the%20thinclient

56

You might also like