AUTOMOBILE AFFAIRS MANAGEMENT SYSTEM

Software Requirements Specification

Version:1.0

Date:25/01/2016

Prepared By:

KARTIK JADHAV

36

PRANAV GANORKAR

25

Prepared for

Software Project Management

Date: 25-01-2015

Table of Contents
1. INTRODUCTION 1

1.1 PURPOSE 1

1.2 SCOPE 1

2. OVERALL DESCRIPTION 2

2.1 USERS OF THE SYSTEM 2

2.2 FUNCTIONAL REQUIREMENTS 2

2.3.1 Performance 4

2.3.2 Reliability 4

2.3.3 Availability 4
2.3.4 Security 4

2.3.5 Maintainability 4

2.3.6 PORTABILITY 42

2.4 OPTIONAL FEATURES 2

2.5 REPORTS 2

3. USE CASE DIAGRAM 2

Software Requirements Specification Template

1.0. Introduction
These days there is a lot of craze for automobiles not only in higher class people, but
also in the general public. So, seeing the need of a company like affair which caters to these
activities like buying, selling, repair, insure and provide automobiles on rent basis, we
decided to make a project to solve this problem.
1.1 Purpose
The Software is for the automation of Automobile Affairs. The main purpose of our system is
to make the buying and selling of the automobiles easier and efficient. It maintains two levels
of users:
Administrator Level
User Level
The Software includes:
Maintaining Customer/Clients details.
Providing necessary services for automobiles.
Providing and maintaining all kinds of guidelines for client-administrator relationship.
Billing and Report generation.
1.2 Scope of Project
This project deals with processing of each and every department in the automobile affairs and
sincerely aims to serve the people with automobiles in altogether a new way. As discussed in
the problem definition, the project is a solution to the needs of anyone and everyone and
hence happens to have a lot of scope.
Our project will be used by four types of clients:
1) Automobile shops who trade cars
2) Automobile shops who rent cars
3) Garages who repair automobiles
4) Car Insurance or Finance Companies
The end user's will be the customers of the above shops (general public) to whom these
services are catered.
1.3 Users of the System
Following are the users of System:

Customer
Clients
Labor
Companies
Employees
There is also an Enf-user, a final user of commercial product or service.

2. Overall Description
2.1 Product Perspective
The AA is designed to help the Automobile transactions easier and convenient.
2.2 Product Functions
The AA will allow the user to manage information about vehicles. It will also support the
automatic backup and protection of data. The data represented in the application will perform
the following major function:
Customer Details
Automobile Details
Billing Details
This software will help to calculate the bill much quicker and simpler way. This enables the
organization to keep the information in efficient and systematic way.
2.3 User Characteristics
Administrator:
The Automobile Affairs Administrator, who will be most familiar with the problem domain,
is the only person who will have the authority to change information stored in the database.
Administrative Clerks:
The administrative clerks will be the one who shall handle the data entry for the Automobile
Affairs. They may have a data entry training from college. Administrative Clerks are those
familiar with basic computer operations.
End Users:
The end users of our clients will use the front end interface of our system to communicate
with the client and provide them the required information.
2.4 Constraints
There are various standards on security, privacy, transaction and code sets, and identifiers to
which this system must adhere.
Both the administrator and user database will need large storage capabilities and a process
to archive outdated data.
The system must be implemented within the approved budget and within the specified time.
2.5 Assumptions and Dependencies
The system works on the maintaining the customers appointment and transaction history
record, to keep check and keep the data up to date for the easy working of administration.
The Use- case implemented insures data integrity and functionality.
2.1 Functional Requirements
USER SPESIFICATION

Admin : Admin can add a car, manage booking car and rent and also view feedback and enquiry.

User : User can view information of available car, booking car, easily get the car on rent and also
give feedback and can enquiry.

MODULE SPECIFICATION

View Availabale Cars : It is a system design specially for large, premium and small car rental
business. The user can view Available cars and user can book for that car.

Booking Car : The user can view Available cars and user can book for that car.

Easily Get the Car on rent : The Customer can easily get the car whenever they need to on the rent
with use of this system.

Give Feedback : The customer will give the feedback to the admin.

Enquiry: The inquiry can easily done by user.

Add Car : The Admin can add the car so that The user can see the available cars and book the car.

Manage Rent : The Admin can manage the rent so that The user can see the rent and book the
car.

View Feedback : The admin easily view the feedbacks and solve the query. 6 HARDWARE REQUI

Buying, Selling, Repair & Renting:(These are the four main modules)
Add Customers:
o The Automobile Affairs shall allow front-desk staff to add new customers to the system.
Assign IDs:
o The Automobile Affairs system shall allow front-desk staff to give each customer an ID
and add it to the customers record. This ID shall be used by the customer throughout his/her
relationship with the company.
 Customer Information:
o The Automobile Affairs system shall generate reports on customers about the following
information: customers name, vehicle type, customer number, and the name of the
transaction details till date.
Vehicle availability(Only for Selling & Renting):
o The Automobile Affairs system shall generate reports on vehicle availability about the
following
information: type
no. of wheels: 2 or 4
brand: company name
name: model name\
Deposits and Tenure Maintenance (Renting):
The Automobile Affairs System should take the deposit from the customer and maintain the
records of the time period.

Bill generation:
o Selling-The Automobile Affairs system shall generate bills/receipts of the transaction for
future references if needed by the customer/client.
o Renting-The Automobile Affairs system shall calculate the rent depending on the number
of days and the rate per day decided.
Database:
Customer/Client Mandatory Information:
o Each customer/client shall have the following mandatory information: first and last name,
phone number:(personal,office), address, postal code, city, country, customer/client
identification number.
Update Customer/Client Information:
o The Automobile Affairs system shall allow the user to update any of the customers/clients
(end users) information.
2.2 Non-Functional Requirements
Security: The security requirements are concerned with security and privacy issues. All the
customer data is to be kept private. The transaction will be carried out under a very encrypted
security level.The SQL injection attacks will not be possible.The AA shall protect user's
browsing history information.
The AA shall support different user access privileges:
o The administrative clerks have a security privilege level 1. They can only read the
customer's information. They cant access users history information.
 o System administrators shall have a security privilege level 3. They can read and write the
customer's information. They can also read user's history information.

The AA shall protect customers history information.

Reliability
The system will be developed in such a way that it may fail once in a year. Even if the
system fails, the system will be recovered back up within an hour or less. The system
shall provide 100% access reliability.
Maintainability: The maintainability requirements are concerned with the maintenance
issues of the system.
o System downtime for maintenance should be less than 6 hours per quarter of a
year.
Availability
The system is available 100% for the user and is used 24 hrs a day and 365 days a year. The
system shall be operational 24 hours a day and 7 days a week.

Scalability: The scalability requirements are concerned with the scalable issues of the
system.
Portability:
The system is developed for secured purpose, so it cant be portable.
2.3 Optional Features

Accounting Management
Financial Management
Inventory Management
CRM
Spare Part Management
Service Management
Mobile Device Compatible
Service Packages
Service Scheduling (planning)
Service History
Service Work Warranty
Insurance Financial Management
External Service Management
Spare Part Catalogue Integration

2.4 Reports
The owner of the application can generate monthly reports on the number of users and their
activities.
3.3 Use Cases

Admin:
Maintenance Manager:

Drier
Details

Vendor
Details

Vehicle
Details
Maintenance
Manager
spare part
Details

spare part
billing