Experiment 1: Aim: Prepare A SRS Document in Line With The IEEE Recommended Standards

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 6

EXPERIMENT 1

Aim: Prepare a SRS document in line with the IEEE recommended


standards.
Software Requirement Specification (SRS)
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definition, Acronyms and abbreviations
1.4 References
1.5 Overview
2. The Overall Description
2.1 Product Perspective
2.1.1 System Interfaces
2.1.2 Interfaces
2.1.3 Hardware Interfaces
2.1.4 Software Interfaces
2.1.5 Communication Interfaces
2.1.6 Memory Constraints
2.1.7 Operations
2.1.8 Site Adaptation Requirements
2.2 Product Functions
2.3 User Characteristics
2.4 Constraints
2.5 Assumptions for dependencies
2.6 Apportioning of requirements
3. Specific Requirements
3.1 External Interfaces
3.2 Functions
3.3 Performance requirements
3.4 Logical database requirements
3.5 Design Constraints
3.6 Software System attributes
3.7 Organization of specific requirements
3.8 Additional Comments.
1. Introduction

1.1 Purpose
The purpose of this document is to provide a detailed outline of the
requirements for the development of an E-Car Rental System. It aims to
define the functionalities, constraints, and dependencies of the system
to ensure a comprehensive understanding by all stakeholders involved
in its development and implementation.

1.2 Scope
The scope of the E-Car Rental System encompasses the development of
a web-based application that facilitates the rental of vehicles to
customers. The system will allow users to browse available cars, make
reservations, process payments, and manage rental bookings. It will also
provide administrative tools for rental companies to manage their fleet,
monitor reservations, and handle customer interactions.

1.3 Definition, Acronyms and Abbreviations

 SRS: Software Requirement Specification


 E-Car Rental System: Electronic Car Rental System

1.4 References

The development of this document is based on various sources


including academic papers, project reports, and online resources. The
references consulted are:

1. System, Online. 'Online Car Rental System'. Academia.edu. N.p., 2015.


Web. 9 June
2015.
2. Scribd.com, Online. '49930505 Car Rental System Project Report'.
N.p., 2015. Web. 9
June 2015.
3. Scribd.com, Online. 'Car Rental System Documentation'. N.p., 2015.
Web. 9 June 2015.
4. Freelancer, Online. 'Project Documentation Car Rental Company
Software
Development Freelancers and Jobs - Freelancer'. N.p., 2015. Web. 9 June
2015.
5. Slideshare.net, Online. 'Zook Car Rental System Project'. N.p., 2015.
Web. 9 June 2015.
6. Kaewman, Sasitorn. 'Online Decision Support System of Used Car
Selection using K.
Nearest Neighbor Technique'. IJFCC (2012): 164-166. Web.

7. Wikipedia, Online. 'Use Case Diagram'. N.p., 2015. Web. 9 June 2015.

1.5 Overview

This document provides a comprehensive overview of the E-Car Rental


System, covering its purpose, scope, functionalities, constraints, and
requirements. The Car Rental System is the online facility to book cars
online within few clicks only. Some people can not afford to have a car, for
those people this system becomes very helpful. This system includes
various cars, as per the customer order and comfort, it place the order and
deliver the car as per the location within the area. For travelling a long
distance, booking can be done via internet service only.

2. The Overall Description

2.1 Product Perspective

2.1.1 System Interfaces


The E-Car Rental System will feature a web-based interface accessible to
users via internet browsers. It will also include a database interface for
storing and retrieving rental information.

2.1.2 Interfaces

 User Interface: The system will provide user interfaces for customers,
administrators, employees, and maintenance managers, each with
specific functionalities tailored to their roles.
 Hardware Interfaces: The system will require server-side hardware with
specific specifications for processor, HDD, RAM, OS, Database, and
Application. Client-side systems must also meet minimum requirements
for processor, HDD, RAM, and OS.

 Software Interfaces: The system will interact with various software


components including operating systems (Windows, Linux) and web
browsers (Mozilla Firefox, Internet Explorer, Opera, Chrome).

2.1.3 Hardware Interfaces:

The hardware interfaces of the system include server-side and client-


side systems with specific requirements for processing power, storage
capacity, and memory.

2.1.4 Software Interfaces:

The software interfaces of the system include operating systems and


web browsers used by users to access the application.

2.1.5 Communication Interfaces:

The system will utilize HTTP and FTP protocols for communication
between the server and clients. It will also use TCP/IP network protocol
for data transmission.

2.1.6 Memory Constraints:

The system will have memory constraints based on the server and client-
side hardware specifications.

2.1.7 Operations:

The system will perform various operations including car rental


management, availability checking, payment processing, and
maintenance management.

2.1.8 Site Adaptation Requirements:

The system will be designed for 24/7 availability with minimal


downtime. It will require an internet connection for operation.

2.2 Product Functions:


The core functions of the E-Car Rental System include:

 Car reservation management


 Availability checking
 Payment processing
 Maintenance management

2.3 User Characteristics

The system will cater to four main user roles:

 Admin: Responsible for system administration, car management, and


order processing.
 Employee: Involved in updating the database, providing information to
customers, and managing bookings.
 Maintenance Manager: Responsible for overseeing vehicle maintenance,
updating the database, and communicating with the admin.
 Customer: Engages in browsing available cars, making reservations,
processing payments, and managing bookings.

2.4 Constraints

The development of the system will be constrained by the use of specific


technologies including PHP, Ajax, JavaScript, jQuery, and CSS. Additionally, the
system will require an internet connection for operation.

2.5 Assumptions for Dependencies

Assumptions include:

 Users have authenticated accounts.


 The server must be online for system access.

3. Specific Requirements

3.1 External Interfaces

The system will provide user interfaces for login, profile management, and
order processing. It will also require hardware and software interfaces for
server and client systems.
3.2 Functions

The system will perform functions such as reservation, availability checking,


payment processing, and maintenance management.

3.3 Performance Requirements

The system must be responsive with minimal downtime to ensure efficient


operation.

3.4 Logical Database Requirements

The database must efficiently store and retrieve rental information to


support system functionalities.

3.5 Design Constraints

The system design will be constrained by the use of specific technologies


including PHP, Ajax, JavaScript, jQuery, and CSS.

3.6 Software System Attributes

The system will prioritize security measures to prevent SQL injections and
ensure data integrity. It will also require an internet connection for
operation.

This Software Requirement Specification (SRS) document provides a


detailed overview of the requirements for the development of the E-Car
Rental System, outlining its functionalities, constraints, and
dependencies.

You might also like