18-05-2013, 12:21 PM
Project Report on Greyhound Fleet Manager
Greyhound.pdf (Size: 1.55 MB / Downloads: 35)
ABSTRACT
To develop a feature rich web solution for a typical transportation
department of a particular manufacturing company in a typical software
development environment.
The ‘Greyhound Fleet Manager’ keeps track the information about the
Vehicles, Maintenance, Repair, Parts, Employees, Location and Vendors. It also
keeps track the maintenance performed for different vehicles which are used
for transportation.
The super users of the system are the ‘ADMIN’ and the ‘MANAGERS’ of the
different departments allocated by the admin. The admin may be the owner of
the transportation organization or the manager of transportation department
of a particular manufacturing company.
If any other vehicle is added to the fleet which already exists for the
organization/department the details of the vehicle is added. The details
includes whether it is a new one or taken any loan/lease. Any employee is
newly appointed or the existing employee is taken off both the details are
maintained including their personal details and profession details.
INTRODUCTION & OBJECTIVE
The ‘Greyhound Fleet Manager’ keeps track the information about the
Vehicles, Maintenance, Repair, Parts, Employees, Location and Vendors. It also
keeps track the maintenance performed for different vehicles which are used
for transportation.
The super users of the system are the ‘ADMIN’ and the ‘MANAGERS’ of the
different departments allocated by the admin. The admin may be the owner of
the transportation organization or the manager of transportation department
of a particular manufacturing company.
If any other vehicle is added to the fleet which already exists for the
organization/department the details of the vehicle is added. The details
includes whether it is a new one or taken any loan/lease. Any employee is
newly appointed or the existing employee is taken off both the details are
maintained including their personal details and profession details.
The details of the maintenance that are being performed such as
repairs/services and to be performed are also maintained. The maintenance to
be performed can also be scheduled for each type of vehicles. The details of
the parts/inventory used for the vehicles are maintained. The reorder level
and the reorder quantity are predefined for each particular type of part.
The Vendors or suppliers of the vehicles, parts and performs maintenance
required for the vehicles. The particulars of the various vendors are
maintained in this system.
PURPOSE OF THE PROJECT
Purpose of developing this application is to streamline the vehicle
management process in the company and avoid any human errors. Tracking
of vehicle information manually, especially when hundreds vehicles are there
for the organization, is a tedious process. One of the major tasks is sending
the vehicles for servicing. In manual process there won’t be any provision to
know that the vehicle should be sent for servicing, unless the vehicle record
is verified manually.
Vehicle Module:
• Adding vehicles and/or equipment is a simple process and doesn’t require a
wealth of information.
• As long as we have the year, make, model, current Mi/Km/Hr and the base
information, that is all you need.
• We can add a vehicle with the most basic information.
Employee Information:
• The application will keep track of many details include Employee number,
Name, personal information, License Information.
• It also allows you to edit your Employee Information. Under this module
there will be facility to add, delete, Modify the information regarding
Employee.
1) System/Information Engineering and Modeling
As software development is large process so work begins by establishing
requirements for all system elements and then allocating some subset of these
requirements to software. The view of this system is necessary when software
must interface with other elements such as hardware, people and other resources.
System is the very essential requirement for the existence of software in any
entity. In some cases for maximum output, the system should be re-engineered
and spruced up. Once the ideal system is designed according to requirement, the
development team studies the software requirement for the system.
2) Software Requirement Analysis
Software Requirement Analysis is also known as feasibility study. In this
requirement analysis phase, the development team visits the customer and
studies their system requirement. They examine the need for possible software
automation in the given software system. After feasibility study, the development
team provides a document that holds the different specific recommendations for
the candidate system. It also consists of personnel assignments, costs of the
system, project schedule and target dates.
The requirements analysis and information gathering process is intensified
and focused specially on software. To understand what type of the programs to be
built, the system analyst must study the information domain for the software as
well as understand required function, behavior, performance and interfacing. The
main purpose of requirement analysis phase is to find the need and to define the
problem that needs to be solved.
3) System Analysis and Design
In System Analysis and Design phase, the whole software development
process, the overall software structure and its outlay are defined. In case of the
client/server processing technology, the number of tiers required for the package
architecture, the database design, the data structure design etc are all defined in
this phase. After designing part a software development model is created. Analysis
and Design are very important in the whole development cycle process. Any fault
in the design phase could be very expensive to solve in the software development
process. In this phase, the logical system of the product is developed.
4) Code Generation
In Code Generation phase, the design must be decoded into a machinereadable
form. If the design of software product is done in a detailed manner, code
generation can be achieved without much complication. For generation of code,
Programming tools like Compilers, Interpreters, and Debuggers are used. For
coding purpose different high level programming languages like C, C++, Pascal
and Java are used. The right programming language is chosen according to the
type of application.
5)Testing
After code generation phase the software program testing begins. Different
testing methods are available to detect the bugs that were committed during the
previous phases. A number of testing tools and methods are already available for
testing purpose.
6) Maintenance
Software will definitely go through change once when it is delivered to the
customer. There are large numbers of reasons for the change. Change could
happen due to some unpredicted input values into the system. In addition to this
the changes in the system directly have an effect on the software operations. The
software should be implemented to accommodate changes that could be happen
during the post development period.