The problem with some of the current system is that:

·       Based on observations, some small companies already have a car rental system which is not a web based application. This is a limitation that gives them capability to store customer’s details, but at the same time they cannot make their services more available to the public through the internet, they rather make use of posters to advertise their services to the public. These types of companies can overcome these problems by switching to the web base application of their type of system.

·       They also make use of phone call reservations which is also limited to many features as compare to a web base system. For example a customer may make a phone call reservation for a particular car, but when he/she comes to pick the car, he/she might turn not to like the car; this could be because the customer could not see a sample picture of the car he/she wants to rent

1.4            Methodology

The Iterative Waterfall Model is the development methodology that will be used in this project to develop the CRS. This [1] [2] [18] Model is derived from the evolution of the Traditional Waterfall Model. It consist of five phases, which include; the Requirement and Definition, System and Software Design, Implementation and testing, System testing, Operation and maintenance. Each of these phase is repeated if an error is discover, this enables the correction of errors before moving to the next phase. The Figure 1.1 below represents the Iterative Waterfall Model for this project, and each of the phases is explain accordingly.

(http://www.dimacleod.co.uk/msc/thesis267.htm, 2014)

Figure 1.1: Iterative Water Fall Model

1.4.1   Requirement analysis and definition

The system’s services, constraints and goals are established by consultation with system users. Once these have been agreed, they must be defined in a manner which is understandable by users and development team. For example project scope, objectives.

1.4.2   System and software design

Using the requirement definition as a foundation, the requirements are divided into software and hardware. This is called system design. Software design is the process of representing the functions of each software system in a manner which may readily be transformed to one or more computer programs. Use case diagrams, class diagrams, sequence diagrams, entity relationship diagrams (ERD) and data dictionary are use at this level to represent the system design.

1.4.3   Implementation and unit testing

During this stage, the software design is released as a set of programs. Unit testing involves verifying that each unit is working according to the specification of the customer.

1.4.4   System testing

The individual programs or units are integrated and tested as a complete system to ensure that the software requirements have been met as specified by the end users. After testing has been completed, the software system is delivered to the customer.

1.4.5   Operation and maintenance

This is the longest life cycle phase. The system is installed and put into practical use. Maintenance involves correcting errors which were not discovered in the earlier stages of the life cycle. The software must be adapted to accommodate changes in its external environment. For example, a change required because of a new operating system or peripheral device, or because the customer requires functional or performance enhancement.

1.4.6   Feedback

During use, errors and omissions in the original software requirements are discovered, program and design errors come to light and the need for new functionality is identified.

1.5            Software development tools