CAR RENTAL SYSTEM

SYSTEM DESCRIPTION:
Our system has a record of the details like the model of the cars to be rent, date, time, car number, number of days. It could also add a car, car model, edit and view the details who rented the car.

TEAM NAME:
F.O.D.
MEMBERS:

INGRID A. FERNANDEZ - DOCUMENTATION IVY DAYOC - DESIGNER
ANDREW LOUI S. ORANTES - PROGRAMMER

Project Description:

In terms of application, our system has the ability to input the necessary details from the user and our system also comply the needed output.
In addition, our system can view a record of details like the type of the cars to be rented it can also keep and track details like date of rented, time of rented, car number, numbers of days to be rented, it could also add a car, choose a car model, edit and view the details by the client who rented the car. It can also monitor the date of over dues and damages of the car.

Requirements Summary:

In part 1 we come up in planning and introducing our system through a brief description, overview of potential users, functionality of the system to be provided to the users, what would be the potential problems and in the same way the statement interface, and to analyzed of the existing system including its strong points and deficiencies and in part 2 we undergo our system design in which we conclude 3 designs and compare its design alternative, ideas in other aspects and choose our final design for the system and it is also concern the necessary requirement for our system. Type of Requirement | Key requirements | FunctionalRequirements | * Automatic calculation.The system shall automatic to calculate when you want to know the total amount of your payments and it will generate a report to the system. * Rent Car. The customers want to rent a car they should be register first. And then to rent car the customer must pay before they want to get car. * Reservation of cars. The customers should be able to use the system to make booking or the reservation. * Customers Registration.The system shall allow adding new customers in the Customer form. So that they can proceed to transaction such as reservation and to rent a car. If the customers haven’t yet register they cannot allow rent a car and reserve. * Add Car. The system must have a car list so that the customer they will know what kind of car they want to rent. * Summary Reports of Damages and Overdue. The user can easily view the damages and overdue of the customer. * | Target UserRequirements | * Car rental staff should perform the task of what does the system required. * She or he must have the basic knowledge on how to operate the system. * The staff also knows how to resolve in terms of error and malfunction concern in the system design. * Must have also skills in encoding. | Usability Requirements | * System design must be at ease to use so that users or staff can easily adopt and more knowledgeable to the functional requirements. | EnvironmentalRequirements | * It must be transferable in other unit and easily to acquire the functional requirements. | TechnicalRequirements | * The system has a database that can manage the customer information and other important information’s. * It has also a large range to store those information’s and those information’s can be access easily as the user wants. |

Prototype Description:

o An overview of the prototype that you developed.
This System is a manual process, they have two processes which is booking and renting a car. In the car rental system they have a total of six (6) types of cars the Pick-up 4x4, Van, SUV (Sport Utility Vehicle), Compact, Mini Van and Truck. o Each piece of the prototype in more detail, using screen shots or photographs to help illustrate the design.

Log-in Form
The login page allows the user to enter the system. The page has two fields, which must be filled: Username – the user name of the user.
Password – the password of the user.
Tab key or the mouse can be used to move between the fields. After the fields are filled, the user click the login button to proceed in the main or to click the cancel button is to clear the field.

Main Form
In this main form, all the transactions are there. You can add costumer, add cars, reserve a car, rent a car and return a car, there is also payments of overdue and damages. At the above left side statistics reports, reports/payments, and overdue/damages can be showed.

Add Customer
In adding a costumer there are field that you can fill-up driver’s licenses, name, middle name, last name, address, phone, gender and birth date then the age will automatically appear. The costumer I.D. will automatically appear, then after click the confirm button, it will be saved and it will also be edit and showed if the costumer want.

Adding Car Form
This form is for adding another car, fill-up all the empty fields the car registration number is the plate number of the car, the make field is the one who made the car, model, condition of the car, category of the car, rate and days fields. You can also add another category just click the category button at the upper right side of form and then after signing all the fields click confirm and it will saved to the grid view. Then this data grid view will check if the cars are available or on-repair.

Car Category
In this form you can only edit the type, name and rate of the car. It will be seen at the add cars form.

Report View Form
View reports- it will automatically view all the reports of active overdue, car due today, reservation due today, unpaid damages and unpaid overdue. As you can see the arrow beside of the exit button the purpose of that is to view the active costumers, cars report, rentals, reservations and the total payments.

Payments View
In this form the costumer and owner can check if there is a car repair will in or car was repair/out, in viewing of payments you can clarify that if who are the employees assist the costumer.

Overdue View Form
This form is only for the view reports for those costumer who wasn’t paid or paid their over dues.

Damages View Form This form is only for the view reports for those customers who wasn’t paid or paid their damages.

Car Rental Form
Just fill-up all the empty fields, first is select costumer and select a car and fill-up the processed for, car rented, data information and direct rental. After, pay at the cashier.

From Reservation In this form is under in car rental, if you want to rent a car then you had already to reserve

Return Car Form
When you return a car, first type rental number and click search and it will automatically view the details of the costumer. If ever the car has a damage type the description of damages then type the penalty damages then click return.

Reservation Form
At the reservation form you fill-up all the information data, after you fill-up please select a car and costumer, then click save.

Customer Select Form
This form is the under the reservation and rent car form for selecting a customer. When the customer is clear then click it for he can rent a car.

Car Select Form
This form is under the form of reservation and rental form, select your desire car and click ok for the reservation and rental.

Overdue Payment Form
If the costumer has overdue of the car just click this form. First is type the rental number and click the search button and the empty fields will automatically appear the details of the costumer. Pay at the cashier for the over dues and click confirm.

Damages Payments Form
At this payment mode it is the same at pay overdue first is type rental number and the empty fields will automatically, damage description will appear. After compute the amount to pay and confirm.

o At least one scenario from a user's perspective.

User: I suggest that your system must be a user friendly, can include all the data’s needed for our business.

* Can retrieve and view data or record. * Must be simple, directly and can modify. * The design must not be

o [20 pts] Rationale:

Advantages | Disadvantages | * User friendly | * Offline transaction | * View and retrieve data | | * All their requirements are met | | * Functional design as well as the GUI design | |

o [20 pts] Changes to your requirements:

In terms of design there’s a changes happen we improve the design of our prototype in order to be more presentable to the users. We alternate those requirements which are not useful into highly basic requirements.

Prototype Description
The type of prototype that we used was evolutionary prototyping because the main goal of using it is to build a very robust prototype in a structured manner and constantly refine it and evolutionary prototyping is a functional system. Although they may not have all the features the users have planned, they may be used on an interim basis until the final system is delivered. For a system to be useful, it must evolve through use in its intended operational environment. A product is never "done;" it is always maturing as the usage environment change we often try to define a system using our most familiar frame of reference in which where we are now. We make assumptions about the way business will be conducted and the technology base on which the business will be implemented. A plan is enacted to develop the capability, and, sooner or later, something resembling the envisioned system is delivered. It is not unusual within a prototyping environment for the user to put an initial prototype to practical use while waiting for a more developed version…The user may decide that a 'flawed' system is better than no system at all. To minimize risk, the developer does not implement poorly understood features. The partial system is sent to customer sites. As users work with the system, they detect opportunities for new features and give requests for these features to developers. Developers then take these enhancement requests along with their own and use sound configuration-management practices to change the software-requirements specification, update the design, recode and retest. Criteria | Features | Feedback | Visibility of system status(Feedback) | The system should always keep users informed about what is going on, through appropriate feedback within reasonable time. | | Match between system and the real world(Metaphor) | The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order. | | User Control and Freedom(Navigation) | Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo. | | Consistency and standards | Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions. | | Error prevention(Prevention) | Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action. | | Recognition rather than recall (Memory) | Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate. | | Flexibility and efficiency of use(Efficiency) | Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions. | | Aesthetic and minimalist design (Design) | Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility. | | Help users recognize, diagnose, and recover from errors (Recovery) | Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution. | | Help and documentation(Help) | Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large. | |