Chapter 2

System Requirement
Specification
2.1 Introduction
2.1.1 Purpose
This document provides requirement specification for Speech Emotion Recognition System
mobile application. This system goal to provide recognition of emotions from speech. The aim of
our project is to measure student satisfaction by identifying feelings in any E-Learning
environment. It also provides some specific analysis results and leads to ideas that can move the
E-Learning environment.

2.1.2 Scope
Modern day security systems rely heavily on bio-informatics, like as speech, fingerprint, and
facial images and so on. Besides, determination of a user’s emotional state with voice analysis
plays a fundamental part in man-machine interaction (MMI) systems, since it employs verbal
cues to estimate the user’s emotional state. Therefore, recognizing human emotion has been an
attractive task for data scientists. On the other hand, there are many challenges in emotional data
evaluation such as collection of proper datasets, definition of number of emotions to recognize,
selection of the labelled data, etc. Due to the many challenging tasks under evaluation, MMI
systems that utilize multimodal information about their users' current emotional state are interest
of the computer vision and artificial intelligence communities.
In this study a software algorithm will be implemented for extracting emotion related features
from speech signals. Then we will infer an emotional state by designing a decision algorithm.
Open source software algorithms will be utilized to implement the recommended system. The
project will be directed as an interdisciplinary study and will be carried out as a joint work with a
group.
A software program will be designed and developed for a Speech Emotional Recognition
System. The system will be able to receive and process only a human voice in the form of
recorded signals and will present information about the emotional state as an output.

2.1.3 Definitions, acronyms, and abbreviations

Term Definition
SER Speech Emotion Recognition
Admin Person who manage the system
User Person who wants to know the situation of
emotion
2.1.4 Reference
2.1.5 Overview
The SRS is divided into three major components:
The first part contains the introduction about the project to be prepared; it also describes the
basic purpose and the scope of the document.
The second part describes the overall description about the project. Then in the last part specific
requirements are listed
2.2 Overall Description
2.2.1 Product Perspective
An emotion recognition system can detect the emotion condition of a person from his speech
information. In this scope, speech emotion recognition system requires to evaluate the emotion
of a person from his speech information.
The software described in this SRS will be used to detect people's emotions. This project can be
used in several areas that like to measure customer satisfaction in a marketing platform, help
advertisers to sell products more effectively.

2.2.1.1 System interfaces

This should list each system interface and identify the functionality of the software to accomplish
the system requirement and the interface description to match the system.

2.2.1.2 User interfaces

As it is mentioned above this product would contain numerous user interfaces ranging of that
from app. The list below shows the user interfaces that are comprised in Application
respectively. There are numerous features that we are trying to embed in this particular software
so quite a few screens are used to show clarity amongst different interfaces.
Screens for application
• Login
• Sign Up
• Exit
• Upload Voice
• Record Voice
• Detect Emotion
• Detect Age
• Detect gender
• Detect All Parameters
• View voice metrics

2.2.1.3 Hardware interfaces

To access Application following hardware tools must be used:

Processor core i3/i5 | dual core
Hard Disk 250 GB
RAM: 2 GB
LAN CARD

Keyboard 108 keys

Monitor VGA
2.2.1.3.1 Computer
A personal mobile to install and to view this application is required.

2.2.1.3.2 Internet Access Device

Internet access is recommended to download this application.

2.2.1.4 Software interfaces

Operating System Any
Programming Language Python
Database: MS SQL database

2.2.1.5 Communications interfaces

As this is only mobile application so there is no other way to communicate or third party is not
involved in this software. There is an internet connection is required to run this software.
2.2.1.6. Memory
There are no constraints on either primary or secondary memory.

2.2.1.7. Operations
The basic operations are as follow:
• Login
• Exit

2.2.1.8. Site adaptation requirements

There are no special requirements for this app adaption a user just must have any smart phone.

2.2.2 Product functions

There will be two types of users for “Speech Emotion Recognition”. The first one is
administrator the second is salesman. They can identify when log into the website.

2.2.2.1 Administrator
Administrator has access to many different features of this App. He can make changes in the
database. He has access to maintain the application.

2.2.2.2 User
User can manage their account. User can add profile. They can change their information.

2.2.3 Users Characteristics

There are two types of people that are interacting with the system: user and administration. Each
of them has different use of system so each of them has their own requirements.
2.2.3.1 General Users
This user will be a normal user who will be able to use the system according to their own
requirements. This user shall be able to perform register, login and other functions according to
things.

2.2.3.2 Software Engineers

This user will be able to deal with the technical end like bug fixes, system and development
related issues.

2.2.3.3 Administrator
This will be an advanced user who shall have proper training to use the system and provide the
support to the general users.

2.2.4 Constraints
The internet connection is the main constraint for the application. Since the application can
perform functions only when user login, so internet connection is crucial.

Some of the constraints are as follows:

2.2.4.1 Cost
Owner of this project defined cost, that project should be done in 1 lacks instead of 2 lacks.

2.2.4.2 Schedule/time
Appointment time fixed by the owner and owner gives the deadline to project team to done this
project in 5 months.

2.2.4.3 System Software constraints

The system will run under window 7, 8 or higher platform of operating system

2.2.5 Assumptions and Dependencies

Dependency of our product is that always be used if you have internet connection. Some of the
others are as follows:

(a) Budget
Project developer team estimates that all cost on this project would be around 3 lacks.

(b) Schedule of reporting

Project team will have some appointments with the owner regarding project and they assume that
project can be done in 7 months.

(c) Resource Availability

As we are developing a software project, system manager should provide suitable resources for
the project team considering the complexity of project.

(d) Environment/Circumstances
Project team should developed software which has to suitable for the environment. On which
circumstances project will be used, they have to consider all these situations and have to fulfill
them.

(e) Technical (Technology)

Hardware and web app both system would have that flexibility to indulge themselves in terms of
evolutions.

(f) Dependencies
Project dependencies should be followed, like project finish-start dependency. All the activities
of our project from analyzing to deploying should be followed step by step.

(g) Security
System requirement are particular significant in defense system and database system they place
restrictions on the use of certain commands and maintain a log of activities in the system.

2.2.6. Apportioning of requirements

If there are any updates in the software, we may need a few additional requirements to cope with
the problem.

2.3 Specific Requirements

2.3.1 Functional Requirements

Functional requirement is used to define a function of a system and its components. Functional
requirements of SER mobile application may be its technical details, data manipulation and
processing and other specific functionality that define “what is system going to do”.
There are two main modules in our project:
• Admin
• User

2.3.1.1 Admin Panel

1. Login:
The sub-modules and the functional requirement of module Login Access are as following:
Login Module:
• Login
• Forget ID or Password
ID: FR_01
Name: Login

Description Input Output Basic work flow

It will let the user to login in the Users must have User logged in to the Authenticated user will fill the
system and shows the screens their ID or system. login form.
according to their roles. Password. Submit the login form.
System verifies the id and
password.
Dashboard of the user
appears on the screen where
user can perform desired
tasks.

Table 1 Functional Requirement Login

ID: FR_02
Name: Forget Password or ID

Description Input Output Basic work flow

User forgets his password or id Users must have The admin reset the User list will be appeared on
then he will recover it. their ID. user password or Id the screen.
and send him mail. Select the user for reset
password.
Reset the Password or Id.

Table 2 Functional Requirement Forget ID or Password

2. Exit
ID: FR_03
Description Input Output Basic work flow

System will show exit button Press the App will be close by Admin go to the exit button.
to exit the app. exit button the admin by clicking Click the exit button to exit
to close the just one button. from the app.
app.

Table 3 Functional Requirement Exit

3. View registered user’s profile

ID: FR_04
Description Input Output Basic work flow

System will show all the Clicking the System will show all Admin will go to the register
register users profile user profile the register user module.
button to profile in one screen. Select the user to view that
view the user profile.
registered .
user.

Table 4 Functional Requirement View registered user’s profile

4. View User’s Voice Recording

ID: FR_05
Description Input Output Basic work flow

System will show all the user Clicking the System will show all Admin will go to the User
voice recording User Voice the User voice Voice Recording module.
Recording recording in one User Voice Recording list will
button to screen. be appeared on the screen.
view the Select the user to listen to the
User voice. User voice recording.

Table 5 Functional Requirement View User’s Voice Recording

5. View detected parameters (emotion, age, gender) of Users
ID: FR_06
Description Input Output Basic work flow

System will show the detected Clicking the System will show the Admin will go to the detected
parameters by clicking the detected detected parameters parameters Tab.
options that are emotion, age parameters of the Users in one Select the detected parameter
and gender of the Users. to view the screen. to view.
detected List of that parameter will
parameters display on the screen that is
of the Users. selected by the admin.

Table 6 Functional Requirement View detected parameters (emotion, age, gender) of Users

6. View voice metrics

ID: FR_07
Description Input Output Basic work flow

System will show all the voice Select the System will show the Admin will go to the view voice
metrics. voice metrics voice metrics. metrics Tab.
to view all Select the view voice metrics.
the user List of that user voice metrics
voice. will display on the screen that
is selected by the admin.

Table 7 Functional Requirement View voice metrics

2.3.1.2 User Panel

7. Login:
The sub-modules and the functional requirement of module Login Access are as following:
Login Module:
• Login
• Forget ID or Password
ID: FR_8
Name: Login
Description Input Output Basic work flow

It will let the user to login in the Users must have User logged in to the Authenticated user will fill the
system and shows the screens their ID or system. login form.
according to their roles. Password. Submit the login form.
System verifies the id and
password.
Dashboard of the user
appears on the screen where
user can perform desired
tasks.

Table 8 Functional Requirement Login

ID: FR_9
Name: Forget Password or ID

Table 9 Functional Requirement Forget ID or Password

Description Input Output Basic work flow

User forgets his password or id Users must have The admin reset the User list will be appeared on
then he or she will recover it. their ID. user password or Id the screen.
and send him mail. Select the user for reset
password.
Reset the Password or Id.
Send Mail to User.

8. Sign Up
ID: FR_10
Name: Sign Up
Description Input Output Basic work flow

System will show sign up form Fill Sign up form for Creation of new user User will fill the sign up form.
creation of accounts. Admin to create account. Submit the sign up form with
user account. defined user role.
Register user System saves the accounts.
account. Dashboard of the user
appears on the screen where
user can perform desired
tasks.

Table 10 Functional Requirement Sign Up

9. Exit
ID: FR_11
Description Input Output Basic work flow

System will show exit button Press the App will be close by User go to the exit button.
to exit the app. exit button the admin by clicking Click the exit button to exit
to close the just one button. from the app.
app.

Table 11 Functional Requirement Exit

10. Upload Voice
ID: FR_12
Description Input Output Basic work flow

It will let the user to upload User must Voice is successfully User click on the upload voice
the voice from the mobile have voice uploaded in the app. button.
storage. recording User select the voice from the
already in the mobile storage.
mobile Selected voice is uploaded in
storage to the app
upload it.

Table 12 Functional Requirement Upload Voice

11. Detect Emotion

ID: FR_13
Description Input Output Basic work flow

It will let the user to detect Voice must be Emotion is detected Let the user to upload the
the emotion of the voice uploaded in for the voice which voice in the app.
which is uploaded by the user. the app to the user uploaded it. Voice is uploaded successfully.
detect the Emotion is detected for the
emotion. upload voice to the user.

Table 13 Functional Requirement Detect Emotion

12. Detect Age

ID: FR_14
Description Input Output Basic work flow

It will let the user to detect Voice must be Age is detected for Let the user to upload the
the age of the voice which is uploaded in the voice which the voice in the app.
uploaded by the user. the app to user uploaded it. Voice is uploaded successfully.
detect the Age is detected for the upload
age. voice to the user.

Table 14 Functional Requirement Detect Age

13. Detect Gender

ID: FR_15
Description Input Output Basic work flow

It will let the user to detect Voice must be Gender is detected Let the user to upload the
the gender of the voice which uploaded in for the voice which voice in the app.
is uploaded by the user. the app to the user uploaded it. Voice is uploaded successfully.
detect the Gender is detected for the
gender. upload voice to the user.

Table 15 Functional Requirement Detect Gender

14. Detect All Parameters

ID: FR_16
Description Input Output Basic work flow

It will let the user to detect all Voice must be All the parameters is Let the user to upload the
the parameters which is uploaded in detected for the voice in the app.
uploaded by the user. the app to voice which the user Voice is uploaded successfully.
detect all the uploaded it. All the parameters are
parameters. It will display on the detected for the upload voice
screen. to the user.
Display all the detected
parameters

Table 16 Functional Requirement Detect All Parameters

2.3.2 Non-functional Requirements

The non-functional requirement explains a performance characteristic of the system.

2.3.2.1 Availability
Server will available 24 hours. If in any case server will be down because of overload than it will
gives access to you in few hours.

2.3.2.2 Usability
Usability of the system is high because it is easy to use. Names of choices are very clear and
according to their functionality. Its interface is not difficult as user can view everything clearly
and use its functionality without any confusion.

2.3.2.3 Reliability
Regular checks would be applied to the data that would make sure that data is clean in terms of
its reliability. The App will ensure the privacy of user’s status and ensure full control over
execution, so that resource allocation is not possible without administrator authority.

2.3.2.4 Performance
Performance of system is also high as that will response to user request within seconds. If user
wants to perform 2 or more functions at same time, then it will not affect performance and speed
of system.

2.3.2.5 Design Constraints

A user of this system must have a mobile to easily detect the Parameters (emotion, age, gender)
in one go.

2.3.2.6 Portability
Any single member listed in the app could avail the services of this product.

2.3.2.7 Security
If a user is logged in and during its performance by mistake App closed than it will not save
cookies on the system and system will automatically perform logout action. Just to provide
security to our user.

2.3.2.8 Maintainability
All the data would be effectively maintained by the App that will be on a server with high speed
Internet capability. Module of system will be documented and easy to understand if a person
hired newly. The software developed here assumes the use of a tool such as Python for
connection between the Web pages and the database. The speed of the connection will depend on
the hardware used rather than characteristics of this system.

2.3.2.9 License Agreement

There is not any license needed in our project.