Web Portal for Vehicle Servicing at Home

Software Requirements Specification

Version 1.0

Group Id: F2202E320D

Supervisor Name: Mehboob Ali

 Revision History
Date Version Description Author
(dd/mm/yyyy)
17/01/2023 1.0 This SRS document describes BC190400166
how that system will work. This
document contains:
 Use case diagram
 Usage scenarios
 Functional and non-
functional requirements
 Adopted methodology
Gantt chart
 Table of Contents

1. Scope (of the project)

2. Functional Requirements Non Functional requirements

3. Use Case Diagram

4. Usage Scenarios

5. Adopted Methodology

6. Work Plan (Use MS Project to create Schedule/Work Plan)

 SRS Document

Scope of Project:

In this project, we will build a web-based application named as “Web portal for vehicle
servicing at home”. This project acts as a significant role in saving the time of
people by providing services at doorstep. All the services at their cost are
displayed on the website, customer only register and login on the website
and confirm the services by selecting the time slot and payment method.
This project is build within a year and by using this project there is no need
to physically visit the workshop.

Functional and non-Functional Requirements:

Functional Requirements:
Following are the functional requirements for the project:
1. User registration module, which can gather user basic, contact and address
information for the project;
2. User management section on admin side(add/update/delete);
3. Workshop management feature (add/update delete workshop information);
4. Category management for services;
5. Service management (add/update/delete or change category of service for
workshop);
6. Browse and search for services on user end for required service;
7. Place order for particular service by selecting the time slot and payment method
(Cash on delivery, bank transfer, easy paisa, jazz cash).

Non-Functional Requirements:

“Non-functional requirements are those which are not directly associated with the
functionality of the purposed system but related to the environment and constraints in
which system is going to operate on. A non-functional requirement will describe how a
system should behave and what limits there are on its functionality. Non-functional
requirements are those on which system’s functional requirements can perform.

i. User-friendly interface:

The interface of the web application will be user-friendly and easy to use.
The web application will have attractive Graphical User Interface.
The names of the buttons, menus & tabs will be self-explanatory.
ii. Usability:

Use of this web application will be absolutely free. It will be very simple and easy to use
the app. Data templates will be available for reusability.
It will have user friendly interface. Buttons, options and menus name will be self-
descriptive / self-explanatory so that stack-holder gets the correct meaning while
performing task.
iii. Reusability

Application should be designed and developed in such a way that its modules can be
ported and integrated to other applications with small changes. Reusability minimizes the
duplication of components and also the implementation time.
iv. Reliability:

The ability of a system to perform and maintain its functions in routine circumstances, as
well as hostile or unexpected circumstances be taken on daily basis. The application will
be available 24 hours a day after installation and configuration.
v. Maintainability:

Web application will be built up in such a way that classification of errors and
maintenance of mechanism become easy. Modular approach will be adopted to gain loose
coupling and high cohesion for inter and intra modules.
vi. Flexibility:

Web application will be flexible so that so that it can easily accept all changes at low
cost, time and experience. Existing modules can be enhanced and new modules can be
added without affecting other modules. Any changes and future enhancements will easily
be incorporated into android application.
vii. Availability:
Availability defines the proportion of time that the system is functional and working. It
can be measured as a percentage of the total system downtime over a predefined period.
Availability will be affected by system errors, infrastructure problems, malicious attacks,
and system load.

viii. Performance:

Performance is the essential quality measure for any system as many users can access the
system at any time from any location. So, our application will be implemented to gain
high performance.
ix. Supportability:

The application will be developed as a web based and any browser can be used to
perform all intended functionalities of it. The application supports all modern browsers
and operating systems, e.g., Windows, Linux, and Unix etc., Including desktop and
mobiles.
x. Security/data integrity:

Web application will be designed in such a way that it can handle all the security and data
integrity threats. The system will provide a web base interface so, in order to make
system secure all the user need to get authenticated. This would be helpful for the system
to be free from the spamming and other kind of things that can sacrifice its security and
data integrity.

Use Case Diagram(s):

Usage Scenarios:
 REGISTRATION
Use Case Title Registration
Use Case Id UC-01
Actors User
Description: In this case Users go to the Registration page and provide required details
then he will be registered
Pre-Conditions: User initiates the command to starts the application. Has an active
internet connection.
Task Sequence Exceptions
 Admin will open the application, provide required  Database exception.
information.  Network exception.
 Click on “Register” button.  Already registered
Post Conditions: Admin has registered successfully.
Alternative Path: If the provided information is wrong then Registration page will
reopen and ask again valid information.
Author F2202E320D

LOGIN
Use Case Title Login
Use Case Id UC-02
Actors Admin, User
Description: In this case User/Admin go to the login page and provide his username
and password then he will access their accounts.
Pre-Conditions: User/Admin initiates the command to starts the application. Has an
active internet connection.
Task Sequence Exceptions
 User/Admin will open the application, provide login  Database exception.
credentials.
 Click on “login” button.  Network exception.
Post Conditions: Logged in successfully.
Alternative Path: If the username and password will be wrong then login page will
reopen and ask again valid username and password.
Author F2202E320D

MANAGE USERS
Use Case Title Manage users
Use Case Id UC-03
Actors Admin
Description: In this case Admin will access his accounts by login and manage users.

Pre-Conditions: Admin initiates the command to starts the application. Has an active
internet connection.
Task Sequence Exceptions
 Admin will open the application, provide login  Database exception.
credentials. Click on “login” button.
 Click on “Users”. Here Admin will see the “Add”  Network exception.
button to add new users.
 Here Admin will also find the “Update” and “Delete”
icons to perform action on previous users.
Post Conditions: Admin has managed (Add/Update/delete) the users successfully.
Alternative Path: N/A
Author F2202E320D

MANAGE WORKSHOP INFORMATION

Use Case Title Workshop information
Use Case Id UC-04
Actors Admin
Description: In this case Admin will access his accounts by login and manage
workshop information i.e., workshop Name, Address, Opening/Closing timings etc.
Pre-Conditions: Admin initiates the command to starts the application. Has an active
internet connection.
Task Sequence Exceptions
 Admin will open the application, provide login  Database exception.
credentials. Click on “login” button.
 Click on “Workshop”, here Admin will manage (add,  Network exception.
delete and update) the workshop information.
Post Conditions: Admin has managed (Add/Update/delete) the workshop information
successfully.
Alternative Path: N/A
Author F2202E320D

MANAGE SERVICES CATEGORY

Use Case Title Services category
Use Case Id UC-05
Actors Admin
Description: In this case Admin will access his accounts by login and manage Services
categories.
Pre-Conditions: Admin initiates the command to starts the application. Has an active
internet connection.
Task Sequence Exceptions
 Admin will open the application, provide login  Database exception.
credentials. Click on “login” button.
 Click on “Services” here he will manage the services  Network exception.
categories.
Post Conditions: Admin has managed the services categories successfully.
Alternative Path: N/A
Author F2202E320D

MANAGE SERVICES
Use Case Title Services category
Use Case Id UC-06
Actors Admin
Description: In this case Admin will access his accounts by login and manage Services.

Pre-Conditions: Admin initiates the command to starts the application. Has an active
internet connection.
Task Sequence Exceptions
 Admin will open the application, provide login  Database exception.
credentials. Click on “login” button.
 Click on “Services” here he will manage the services  Network exception.
information in detail.
Post Conditions: Admin has managed the services information successfully.
Alternative Path: N/A
Author F2202E320D

SEARCH SERVICES
Use Case Title Search services
Use Case Id UC-07
Actors User
Description: In this case User goes to the login page and provides his username and
password then he will access their accounts.
Pre-Conditions: User/Admin initiates the command to starts the application. Has an
active internet connection.
Task Sequence Exceptions
 User will open the application, provide login  Database exception.
 credentials. Click on “login” button.
 Go to search bar and type the desire services, then  Network exception.
related results will be shown.
Post Conditions: Search results will be shown.
Alternative Path: N/A
Author F2202E320D

BROWSE SERVICES
Use Case Title Browser services
Use Case Id UC-08
Actors User
Description: In this case User goes to the login page and provides his username and
password then he will access their accounts.
Pre-Conditions: User/Admin initiates the command to starts the application. Has an
active internet connection.
Task Sequence Exceptions
 User will open the application, provide login  Database exception.
credentials. Click on “login” button.
 User may browse to look his/her needed services.  Network exception.
Post Conditions: Know about his desire service.
Alternative Path: N/A
Author F2202E320D

PLACE ORDER FOR SERVICE

Use Case Title Place order
Use Case Id UC-09
Actors User
Description: In this case User goes to the login page and provides his username and
password then he will access their accounts.
Pre-Conditions: User/Admin initiates the command to starts the application. Has an
active internet connection.
Task Sequence Exceptions
 User will open the application, provide login  Database exception.
credentials. Click on “login” button.
 Search or browse for his needed service and click on  Network exception.
“Place order” button.
 A form will show, user fill the form and select the 
 suitable and available time slot and payment method.
 After completing the procedure, click on “Place 
order” button.
Post Conditions: Order has placed successfully.
Alternative Path: N/A
Author F2202E320D

LOGOUT
Use Case Title Logout
Use Case Id UC-10
Actors Admin, User
Description: In this case User/Admin Logout from the application.

Pre-Conditions: User/Admin initiates the command to starts the application. Has an

active internet connection.
Task Sequence Exceptions
 Click on “Logout” button  Database exception.
 Success massage will be displayed on the screen.  Network exception.
Post Conditions: User/Admin has logged out successfully.
Alternative Path: N/A
Author F2202E320D

Adopted Methodology

Software Development Methodologies

A lifecycle model is a series of steps through which the product progresses. Software
Development Lifecycle Models depict the way you organize your activities.
There are a number of Software Development Lifecycle Models, each having its
strengths and weaknesses and suitable in different situations and project types. The list of
models includes the following:

• Build-and-fix model
• Waterfall model
• Rapid prototyping model
• Incremental model
• Extreme programming
• Synchronize-and-stabilize model
• Spiral model
• Object-oriented life-cycle models
Waterfall modal:
The Waterfall Model was the first Process Model to be introduced. Because of the
cascade from one phase to another, this model is known as the waterfall model. It is very
simple to understand and use. In a waterfall model, each phase must be completed before
the next phase can begin and there is no overlapping in the phases.
The waterfall Model illustrates the software development process in a linear sequential
flow. This means that any phase in the development process begins only if the previous
phase is complete. In this waterfall model, the phases do not overlap.

Spiral modal:
The spiral model is similar to the incremental development for a system, with more
emphasis placed on risk analysis. The spiral model has four phases:
 Planning,
 Design,
 Construct
 Evaluation.
A software project repeatedly passes through these phases in iterations because of the
spiral nature of development it is easy to judge how much to test and there is no
distinction between development and maintenance.
Each phase in the Spiral model starts with a design goal and ends with a client reviewing
the process.

Adopted Methodology:
We select the VU process model which is the combination of both waterfall and spiral
model.
Our project is divided already into different phases. In which we gathered and analyzed
the requirements phase that also called SRS Document, Design Document, Test Phase 1,
Final project report phase, and Final report / Presentation. We will complete each phase
in sequence and submit it to our supervisor. If any improvements are required in each
phase, then he will recommend the improvements in each phase before starting the next
phase. If Supervisor suggests improvement, then we will make improvements in that
phase. VU Process Model will be chosen due to the spiral nature of this model. When the
phase is well-improved and well worked out, and also accepted by our supervisor then we
will proceed to the next phase. This will be done due to the waterfall nature of the VU
Process model

Benefits of using this methodology.

 This is sequenced model.
 This model is easy to understand and use.
 Each phase has specific deliverable.
 In this model phases are completed and processed one at a time.
 Avoidance of risk is enhanced.
 Additional functionality can be added later.

Why we use this methodology?

 This model is used when cost and risk evaluation is important.
 This methodology is also used when users are unsure of their requirement.
 It is also used when significant changes are expected.

Work Plan (Use MS Project to create Schedule/Work Plan)