Software Requirements

Specification

For

Smart Door

Prepared by

Group Members Name:

Name Id Email

Asad Ullah 12627 asadafridi256@gmail.com

Asad Khan 13313 uasad70343@gmail.com

Qudratullah 12915 qudratullahwazir2@gmail.com

Instructor:
Madam Zartasha Saeed

Date: 26th November 2022.

0|Page
TABE OF CONTENTS
Table of contents

1. INTRODUCTION...............................................................................................................4
1.1 PURPOSE OF THE DOCUMENT:..................................................................................4
1.2 INTENDED AUDIENCE:................................................................................................4
1.3 OBJECTIVE OF THE SYSTEM:.....................................................................................4
1.4 SCOPE OF THE SYSTEM...............................................................................................5

2. OVERALL DESCRIPTION...............................................................................................5
2.1 PRODUCT PERSPECTIVE:............................................................................................5
2.2 PROJECT PLAN:..............................................................................................................5
2.3 PRODUCT FEATURES...................................................................................................5
2.4 OPERATING ENVIRONMENT:.....................................................................................6
3. SYSTEM FEATURES........................................................................................................6
3.1 FUNCTIONAL REQUIREMENTS:................................................................................6

4. INTERFACE REQUIREMENTS.......................................................................................7
4.1 HARDWARE INTERFACE:............................................................................................7
4.2 SOFTWARE INTERFACE:.............................................................................................7

5. OTHER NON-FUNCTIONAL REQUIREMENTS...........................................................8

5.1 RESPONSE TIME:...........................................................................................................8
5.2 SAFETY AND SECURITY REQUIREMENTS..............................................................8

1|Page
 5.3 SOFTWARE QUALITY ATTRIBUTES.........................................................................8

6. OTHER REQUIREMENTS................................................................................................9
6.1 Appendix A: Requirement Elicitation...............................................................................9
6.1.1 Questionnaire for smart door........................................................................................10
6.1.3 Requirements Specification/Documentation:...............................................................11
6.2 Appendix B: Analysis model...........................................................................................12
6.2.1 Use case diagram..........................................................................................................12
6.2.2 End user flow diagram..................................................................................................13
6.2.3 Data flow diagram........................................................................................................14
Appendix 3: Risk factors.......................................................................................................15

2|Page
 1. INTRODUCTION

1.1 PURPOSE OF THE DOCUMENT:

The purpose of this document is to collect, analyze and describe requirements of the system in
such a way that team members working on this system do not feel any difficulty in understanding
the system. This document is focused to describe the project, intended users, hardware and
software requirements and functionalities of the system. It also sums up the scope of the project
and define boundaries for it.

1.2 INTENDED AUDIENCE:

There would be a single audience of the system:

User: The application user would be the single audience of the system as per the description
given by the client.

1.3 OBJECTIVE OF THE SYSTEM:

Objective of the system is to provide a relax environment to the client so he does not have to
leave the bed to open the door for someone.

1.4 SCOPE OF THE SYSTEM

Scope of the system is to develop such a system that the client uses it when someone knocks the
door. The system is developed to provide convenience to the client so at any time he wants to
lock or unlock the door and the system does it perfectly.

 Provide security to the system

 Convenience in opening and closing the door
 Easy to use at any time

3|Page
 2. OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE:

The client manually opens the door for someone when he knock’s the door for which he has to
leave his bed. It is a daily routine, so the client wants to develop such a system that he doesn’t
have to leave his bed and open or close the door from his bed. The smart door system will help
the client in opening the door from a mobile application without leaving the bed.

Definitions:

Client: Client is the single user of this application that will lock or unlock the door at any desired
time.

2.2 PROJECT PLAN:

After requirements elicitation and gathering, a plan will be developed to follow for the
development of this project. As we will be using agile method, the system will be developed and
provided to the client in the first iteration. A feedback will be taken if the system worked
properly or not when someone knocks. Enhancements will be made against the feedback given
by the client.

2.3 PRODUCT FEATURES

 The first step when someone knocks, the client will have to open the application and login
it.
 As logged in, the client will verify if the door is locked or not, if not, will click on the
button Unlock the door.
 The system will unlock the door and the door will open.
 Client will log out and will close the application

2.4 OPERATING ENVIRONMENT:

The project will have two operating environments:

Hardware installation: Install hardware of the system at client’s door. The hardware would be
fixed in such a way that do not affect the door opening or closing flow.

Software Installation: A mobile application will be installed on the mobile of the client that will
not require any internet or Wi-Fi services

4|Page
 3. SYSTEM FEATURES

3.1 FUNCTIONAL REQUIREMENTS:

Following are the functional requirements of the system:

3.1.1 LOGIN TO THE APPLICATION:

Function: Login to the application
Priority: Top (Required on first release)
Requirement: The user will be able to provide specific credentials for logins to the system. As
there is only a single user for the application, the credentials will be defined statically

3.1.2 UNLOCK THE DOOR

Function: Unlock the door if locked
Priority: Top (Required on first release)
Requirement: The user will be able to click on a button in the application “Unlock the door”
that will immediately unlock the door and the door will open.

3.1.3 LOCK THE DOOR

Function: Lock the door if unlocked
Priority: Top (Required on first release)
Requirement: The user will be able to click on a button in the application “Lock the door” that
will immediately lock the door.

3.1.4 LOG OUT

Function: Log out of the system
Priority: Top (Required on first release)
Requirement: The user will be able to click on a button in the application “Logout” that will
immediately log the user out of the system.

5|Page
 4. INTERFACE REQUIREMENTS

In this system, we can have hardware requirements and software requirements:

4.1 HARDWARE INTERFACE:

The system will have the following hardware requirements:

 Bluetooth Module
 Relay
 Arduino UNO
 Door Lock

The mobile Bluetooth will send data that will be received by the Bluetooth module and sent to
Arduino program, the Arduino program will decide what to do next, and will send instructions to
relay, that will either lock or unlock the door

4.2 SOFTWARE INTERFACE:

The software interface requires:

 Smart phone with Bluetooth

 Mobile application
 Login page with login credential fields
 Main page of the application
 Unlock the door button
 Lock the door button
 Logout button

6|Page
 5. OTHER NON-FUNCTIONAL REQUIREMENTS

5.1 RESPONSE TIME:

Application response time should be fast so that the door opens immediately.

5.2 SAFETY AND SECURITY REQUIREMENTS

 This system has no hazards on human health and is safe to use.
 This system does not affect environment.
 This system is secure.

5.3 SOFTWARE QUALITY ATTRIBUTES

Portability:

This application is for all android phones that have Bluetooth.

Maintainability:

If user finds errors and report then it is easy to maintain.

Availability:

The application is available locally without internet connection establishment.

Usability:

This application will be built on latest GUI and design patterns.

7|Page
Appendix A: Requirement Elicitation

Because there is not a professional client for this assignment, the elicitation phase will
consist of the team. And Ethnography will be carried out because it is the possible
functionality from the” clients” point of view. The elicited requirements will be based
primarily on the observations conducted in existing house.

Questionnaires will be generated on the basis of the observed and gathered information
about the specific work environment, as well as the actor and their connections. And
because (Ethnography can be used in conjunction with a variety of elicitation methods like
questionnaires and interviews to obtain comprehensive responses from stakeholders)

6.1.1 Questionnaire for smart door

8|Page
6.1.2 Requirements Analysis:
During the analysis phase, team members will take the derived requirements and transform
them into a constant, thorough and complete set of requirements. This will include
formulating a use cases, UML analysis.

6.1.3 Requirements Specification/Documentation:

The outcome of this final phase will be the production of the final report, including the full
Software
Requirements Specification and an appendix concerning process reflection. Details of the
specification will be finalised and all requirements and diagrams will be collated and
organised into a single coherent Software Requirements Specification document.

9|Page
6.2 Appendix B: Analysis model

6.2.1 Use case diagram

10 | P a g e
6.2.2 End user flow diagram

11 | P a g e
6.2.3 Data flow diagram

12 | P a g e
Appendix 3: Risk factors
After deployment of the system, different risk factors can occur:
 As the door lock will be handled by the client in his bed, if someone else wants to come
inside the door will have to ask the client to unlock the door
 Incase if the door is locked and no charge is given to the Arduino, the door will remain
locked
 In case the client is outside the room, locked the door, and leaves home for something, no
one else will be able to go to the room, as Bluetooth won’t work in long distance,
GSM/Wi-Fi and server can be used to solve it.
 If there is any technical issue in the mobile or mobile is out of charge, system will not
work
 If any physical object comes in front of the door, the client will have to leave the bed to
open the door
 Maintenance of house can also affect it in case of painting or cleaning the house

13 | P a g e