Scribd
Upload
9 views3 pages

Se 4

This document outlines the requirements for a simple vehicle rental system, detailing functional requirements such as user management, vehicle listing, booking system, and admin features. It also includes non-functional requirements focusing on security, performance, and data storage, along with a proposed technology stack for implementation. The project will follow the Waterfall Model for structured development, aiming to create an efficient and user-friendly rental process.

Uploaded by

jadejaparikshitsinh84
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
9 views3 pages

Se 4

This document outlines the requirements for a simple vehicle rental system, detailing functional requirements such as user management, vehicle listing, booking system, and admin features. It also includes non-functional requirements focusing on security, performance, and data storage, along with a proposed technology stack for implementation. The project will follow the Waterfall Model for structured development, aiming to create an efficient and user-friendly rental process.

Uploaded by

jadejaparikshitsinh84
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/ 3

PRACTICAL-4

AIM : Gather application specific requirements- Requirement gathering.


Requirement Gathering for a Simple Vehicle Rental System

Since you want an easy-to-implement version of the project, this document will outline the
basic features and structure while keeping development simple.

1. Functional Requirements (What the System Should Do)


1.1 User Management

 Users can register by providing their name, email, and password.


 Users can log in securely using their email and password.
 A basic profile page allows users to see their rental history.
 Users can log out from their account.

1.2 Vehicle Listing

 The system displays available vehicles with details like:


o Vehicle name (e.g., Honda City, Suzuki Swift)
o Type (Car, Bike, SUV)
o Rental price per day
o Availability status (Available or Booked)
o Simple vehicle images (optional)
 A search bar allows users to find vehicles easily.
 A filter option to view only available vehicles.
1.3 Booking System
 Users can select a vehicle and choose:
o Rental start date
o Rental end date
 The system calculates the total cost based on price per day and rental duration.
 Users can confirm the booking, and the system marks the vehicle as Booked.
1.4 Payment Processing (Simplified Approach)

Software Engineering (4340702) Enrollment No : 239830331091


 Instead of integrating a real payment gateway (which is complex), the system will:
o Show a message like “Please pay at pickup” or
o Allow users to mark the payment as Paid manually (admin verifies it).
1.5 Admin Features (Rental Management)
 Admins can log in to a separate admin panel.
 Admins can add new vehicles (name, type, price, image).
 Admins can update or remove vehicles from the list.
 Admins can view all bookings and update the rental status.

1.6 Rental History


 Users can view their past bookings with details like:
o Vehicle name
o Rental duration
o Payment status (Paid / Unpaid)
 Admins can also see all rentals in a simple report.

2. Non-Functional Requirements (System Quality & Performance)


2.1 Security & Authentication
 Users must log in to book a vehicle.
 Admin access is restricted to authorized users only.
 Passwords should be hashed (for basic security).
2.2 Performance & Usability
 The system should load quickly and work smoothly.
 The user interface should be simple and easy to navigate.
 Mobile-friendly design for easy use on phones.
2.3 Data Storage
 A basic database to store:
o Users (ID, Name, Email, Password)
o Vehicles (ID, Name, Type, Price, Availability)
o Bookings (User ID, Vehicle ID, Start Date, End Date, Status)
3. Technology & Implementation Approach
Since you want an easy-to-develop project, we can use:
 Frontend (User Interface):
o HTML, CSS, JavaScript (Simple UI without complex frameworks)
o Bootstrap for styling (optional but makes it look better)
 Backend (Logic & Data Handling):
o Python (Flask or Django) – Simple and beginner-friendly
o OR PHP if you are familiar with it

Software Engineering (4340702) Enrollment No : 239830331091


o OR Node.js (Express.js) if you prefer JavaScript
 Database:
o SQLite (Lightweight and easy to set up)
o OR MySQL (If you need a full database)

4. How the Waterfall Model Fits This Project


We follow the Waterfall Model step by step to make sure the project is structured and manageable:
1. Requirement Gathering (Current Step):
o Identifying what features are needed.
2. System Design:
o Creating simple UI wireframes.
o Planning the database structure.
3. Implementation (Development):
o Building login, vehicle listing, booking, and admin panel.
4. Testing:
o Checking if bookings, logins, and data storage work correctly.
5. Deployment:
o Hosting the system on a local or cloud server.
6. Maintenance (Optional):
o Fixing bugs or adding small improvements if needed.

5. Project Scope (What This System Will Achieve)


 Provide a simple and fast vehicle rental process.
 Allow users to browse, book, and pay easily.
 Help admins manage vehicles and bookings efficiently.
 Keep the system easy to use and develop with basic programming knowledge.

Software Engineering (4340702) Enrollment No : 239830331091

You might also like