KOGI STATE POLYTECHNIC LOKOJA, KOGI

STATE,

SCHOOL OF APPLIED SCIENCES,

DEPARTMENT OF COMPUTER SCIENCE.

INTRODUCTION TO SOFTWARE ENGINEERING

(COM324)

FEASIBILITY REPORT
ON
AUTOMATION OF AN AUTOMOBILE FAULT
DETECTION SYSTEM FOR TOYOTA COMPANY

GROUP (004 – 006)

SNo. NAME MATRIC NO.

1. INTRODUCTION

Nowadays, the car technology is very crucial and significant to any car manufacturing
companies as car specifications are changing rapidly stimulated by environmental and
economic factors. This issue presents a challenge to both car mechanics and drivers in
handling car failures and malfunctions. With the advent of new technologies like the
hybrid engine, there are many changes that need to be learned. In fact, in a normal
situation, car fault identification is still a challenging task, especially for the
inexperienced mechanics and drivers. Consequently, the success of finding the fault is
extremely dependent on the expertise of the individual. However, the dependence on the
experts can be minimized if the expertise is captured, documented, and retained in some
computer applications.

Software for car faults diagnosis is a system that detects information about car faults and
provides possible solutions to fixing the problem. It works by entering the type of fault
your car is giving you, and then it will retrieve the information of the possible fault and
also display the result of how you can solve the problem without the presence of an
expert.

WHY DO WE NEED AN AUTOMATED FAULT DETECTING SYSTEM?

Faults occur in vehicles or automobiles very often than not. This can be due to several
reasons. The ability to detect and isolate these faults in complex technical systems such
automobile is important in order to fulfill dependability requirements.
In dealing with problems of a car and troubleshooting, automobile repairers are those
who can help to solve them. The use of a computer expert system is beneficial in
different ways. It gives a temporary and instant guide to car owners in different situations
like:
 Assistance in the absence of automobile repairers.
 Being an alternative considering the distance of automobile repairers.
 Situations where automobile repairers diagnosis wrongly

WHAT ARE THE SIGNIFANCE OF THIS SYSTEM TO THE COMPANY?

1. To help automobile repairers diagnose serious faults and repair vehicles at a faster
rate through the pre-diagnosis and advice web-based software.
2. To provide recommendation in case of automobile break-down and maintainers
advice to users in order to avoid future fault from occurring.

HOW DOES IT WORK?

It works by entering the type of fault your car is giving you, and then it will retrieve the
information of the possible fault and also display the result of how you can solve the
problem without the presence of an expert.

2. CRITERIA OR CONSTRAINT
WHAT IS THE EXPECTED SOFTWARE?
The proposed software to be designed is an automobile car fault detection program. The
program will be designed using Microsoft Visual Basic programming language, and
Microsoft Access as its Database management tool.

What are the Expected outcomes from the implementation of the system?
a. Increase reliability
b. reduce expenses associated with human efforts
 c. Reduced work load on attending to minor issues
d. A standalone program to carry troubleshooting.

SYSTEM REQUIREMENTS
The system requirements are the software and hardware requirements. The software
requires act of instructions that controls a computer’s, action.
It is a computer program that accomplishes some specific applications or tasks, this
software can be purchased or a user can develop the software from the software
developers.
The hardware requirement unlike the software refer to the physical components of the
computer i.e the peripherals in this design the hardware and software requirement for this
system are listed bellow

SOFTWARE REQUIREMENTS
The software used in development of this program is VB.NET because of the peripherals
and this system interface.

HARDWARE REQUIREMENTS
1. Pentium processor (4 or above)
2. RAM (256 MB – 2GB)
3. Standard Keyboard
4. Hard disk (40 above)
5. A 1500v uninterruptible power supply (UPS)

3. METHOD
System changeover is concerned with the smooth shift from one way of doing things to
another and the mitigation of disruption to business activities during the changeover.
There are five main methods used:
1. Direct Changeover
 2. Parallel Conversion.
3. Modular Conversion
4. Distributed Conversion

4. EVALUATING ALTERNATIVE OPTIONS

1. DIRECT CHANGEOVER
Conversion by direct changeover means that, on a specified date, users stop using
the old system and the new system is put into use. Direct changeover can only be
successful if extensive testing is done beforehand, and it works best when some
delays in processing can be tolerated. Direct changeover is considered a risky
approach to conversion. Disruption to the work environment may occur if users
resent being forced into using an unfamiliar system without recourse. Finally,
there is no adequate way to compare new results with old.

2. PARALLEL CONVERSION
Parallel conversion refers to running the old system and the new system at the
same time, in parallel. When the same results can be gained over time, the new
system is put into use and the old one is stopped. One advantage of running both
systems in parallel is the possibility of checking new data against old data to catch
any errors in processing in the new system. The main disadvantages include the
cost of running two systems at the same time and the burden on employees of
virtually doubling their workload during conversion.

3. MODULAR CONVERSION
Modular conversion uses the building of self-contained, operational subsystems to
change from old systems to new in a gradual manner. As each module is modified
and accepted, it is put into use. One advantage is that each module is thoroughly
 tested before being used. Another advantage is that users are familiar with each
module as it becomes operational. Their feedback has helped determine the final
attributes of the system. Object-oriented methodologies often use this approach.

4. DISTRIBUTED CONVERSION
Distributed conversion refers to a situation in which many installations of the
same system are contemplated, as is the case in banking or in franchises such as
restaurants or clothing stores. One entire conversion is done (with any of the four
approaches considered previously) at one site. When that conversion is
successfully completed, other conversions are done for other sites. An advantage
of distributed conversion is that problems can be detected and contained rather
than inflicted simultaneously on all sites. A disadvantage is that even when one
conversion is successful, each site will have its own people and culture, along
with regional and local peculiarities to work through, and they must be handled
accordingly.
5. GRADUAL CONVERSION
Gradual, or phased, conversion attempts to combine the best features of the two
previously mentioned plans, without incurring all the risks. In this plan, the
volume of transactions handled by the new system is gradually increased as the
system is phased in.

5. CONCLUSION
Before choosing any conversion method or technique some factors needs to be put into
consideration. These are:

1. Ordering equipment (up to three months ahead of planned conversion).

2. Ordering the necessary materials that are externally supplied to the information
system.
 3. Appointing a manager to supervise, or personally supervising, the preparation of
the installation site.
4. Planning, scheduling, and supervising programmers and data entry personnel who
must convert all relevant files and databases.

After all evaluations, the changeover method to be adopted for the implementation of this
system is the parallel changeover method.

In parallel hand over, it involves the old and new systems running concurrently, thereby
using the same input. This occurs after the outputs are compared and reasons for
differences resolve. In this regard, if the output from the new system is proven
satisfactory, the old system at this point is discarded and the new system becomes
operational. This system or procedure is expensive but however, it serve as s the standby,
should the new system fails to meet its sets objectives. In the case of this work, Users are
advised to make use of the parallel hand over procedure.

6. RECOMMENDATION
This proposed system (web application) will help Toyota, Nissan and Mercedes Benz
vehicle users have a better understanding of their cars. It will contain all the common
faults experienced daily by users of mentioned brand of vehicles, as well as provides
solution to those problems. Although, this software will provides solution to some
categories of problem. It may not have all the problems and solutions but good news is
that it is subject to improvement and enhancement-meaning that the web application
administrators will continue working round the clock to keep it up-to-date in order to
satisfy the needs of users.
I recommend that the system should be integrated in other to help technicians, or users to
detect a problem in a car and provide available solution to that.