Safe Child-Parental Control Requirements Specifications Document

Requirements Specification Document

Safe Child-Parental Control

Project Code:
CS-456

Advisor:
Mr. Anzar Saleem

Project Team:

Usman Tahir (15140047)

Suman Amjad (15140050)
Shehroze Raza (15140048) Project Leader
Tayyab Farooq (15140049)

1|Page
Safe Child-Parental Control Requirements Specifications Document

Document Information

Category Information
Customer
Project Child Monitoring App
Document Requirement Specifications
Document Version 1.0
Identifier
Status Draft
Usman Tahir
Shehroze Raza (Project Leader)
Author(s)
Muhammad Tayyab Farooq
Suman Amjad
Approver(s)
Issue Date
Document Location GIFT University, Gujranwala
Distribution

Definition of Terms, Acronyms and Abbreviations

This section should provide the definitions of all terms, acronyms, and abbreviations required to interpret the terms used in the document
properly.

Term Description

API Application Programming Interface

SRS Software Requirement Specification

SMS Short Messaging Service

Safe Child-Parental Control The name of our application which is to be developed

RPC Remote Procedural Calls

2|Page
Safe Child-Parental Control Requirements Specifications Document

Table of Contents
1. Introduction 4
1.1 Problem Statement 4
1.2 Solution 4
1.3 Purpose 4
1.4 Scope 4
1.5 Overview 5

2. Overall Description 5
2.1 Product Perspective 5
2.2 Product Functions 6
2.3 System Contraints 6
2.4 Assumptions and Dependencies

3. Specific Requirements 6
3.1 Business Requirements 6
3.2 User Requirements 7
3.3 Functional Requirements 7

3.4 Non-Functional Requirements 9

3.4.1 Usibility 9

5
3.4.2 Performance 9
3.4.3 Access Security 9
3.3 Design Constraints 9

4. Learning Outcomes 10

5. Practical Applications 10

3|Page
Safe Child-Parental Control Requirements Specifications Document

1. Introduction
1.1 Problem Statement
In this era of technology, teens and preteens are fond of using mobile phone
devices. They spend most of their time in using mobile phones like playing games,
chatting and calling all the time etc. This results in loss of their studies and health as well
as they indulge in false activities like keeping bad company.
Parents are worried about their children’s educational, emotional and social development
because mobile phones are spreading like a virus in children’s routine life. They try to
control the mobile usage of their children but all in vain.

1.2 Our Solution

We are coming up with a solution to all the problems mentioned above by
offering a mobile application. By using this application, parents can monitor and control
their children’s activities which they carry out on their smart phones.

1.3 Purpose
The purpose of this SRS document is to give a detailed description of
requirements for our application. It will illustrate the purpose and complete declaration of
development of the application. It will also explain non-functional requirements, design
constrains and some quality factors.

1.4 Scope
The software system will be an android based application for any person who want to
monitor his/her children’s android phone.
This application will perform the following functionalities.
Calls:
This application monitors the call logs made using built-in calling application of
android OS.
Messages:
This application monitors the messages sent and received using built-in
application of android OS.
Applications:
Parents can control the usage of applications installed on child’s mobile by
locking and unlocking the applications.
Location:
This application is concerned to track only the current location of child’s mobile
phone.
Notifications:
Parent can get notifications of received messages, applications and battery.

4|Page
Safe Child-Parental Control Requirements Specifications Document

1.5 Overview
The section 2, Overall Description of the document gives an overview and
background for the requirements in the section 3 of this documents. The section 3 of the
document gives the description of system’s specific requirements in full detail that
include functional requirements including features and non-functional requirements.
Section 4 describes the Learning outcomes from this application. Section 5 describes the
practical applications that what will be the target market of our application.

2. Overall Description
2.1 Product Perspective:
We will propose the system that will help the parents to control child’s phone
remotely. There will be two android applications. One for parent’s mobile and other for
children’s mobile.
Some advantages of this application that parents can get are:
i. Parents can track the child’s location instead of calling him/her to know about
his/her location.
ii. Parents can lock the child’s mobile applications for the sleep time of children.
iii. Parents can lock some applications for study hours of children.
iv. Parents can lock some applications that are not useful or suitable for children.
v. Parent can save their children from keeping them a bad company.
vi. Safe Child-Parental Control can assure the safety of children.

5|Page
Safe Child-Parental Control Requirements Specifications Document

2.2 Product Functions:

The main features of the system under consideration are
F-1) View Contacts’ list
F-2) View recent call logs
F-3) View call logs using filters (Frequency of contact, time)
F-4) View Missed Calls
F-5) View Incoming Calls
F-6) View Outgoing Calls
F-7) View Conversations
F-8) View Received Messages
F-9) View conversation of a selected person
F-10) View content of messages
F-11) Track Location
F-12) Lock applications instantly
F-13) Set time to lock applications automatically

2.3 Constraints
This section describes the major constraints on the system.
 Users of this application must have android phone having android version
above 5.0.
 Parent and child must be registered.

2.4 Assumptions and Dependencies:

 Users must have sufficient knowledge of using mobile phones.
 Users must have internet connection on mobile phones.
 This app requires different permissions of android to operate.
 Server must be available.

3. Specific Requirements
Following are the functionalities of the system under consideration.

3.1 Business Requirements:

Business requirements are described by the product owner and modified by Business
Analysts. Following are the Business Requirements for Safe Child-Parental Control:

6|Page
Safe Child-Parental Control Requirements Specifications Document

BR_01 We need a system, by using which parents can monitor children’s communication.
BR_02 We need a system, through which parents would be able to know to children’s
location.
BR_03 We need a system, by using which parents would limit excessive mobile usage of
children
BR_04 To develop a system that can help to parents to prevent their children from wasting
time in mobile phone.

3.2 User Requirements:

Following are the user requirements of Safe Child-Parental Control

Parent:

UR_01 User should be able to view contacts of child’s mobile phone.

UR_02 User should be able to view call logs of child’s mobile phone.
UR_03 User should be able to view messages of child’s phone.
UR_04 User should be able to lock applications of child’s mobile phone
UR_05 User should be able to unlock applications of child’s mobile phone.
UR_06 User should be able to set time to lock applications of child’s mobile phone.
UR_07 User should be able to set time to unlock the applications of child’s mobile
UR_08 User should be able to add child for monitoring.
UR_09 User should be able to remove child from monitoring list.
UR_10 User should be able to view the applications list of child’s mobile phone
UR_11 User should be able to view the current location of child’s phone.
UR_12 User should be able to get notifications from child’s mobile.

3.3 Functional Requirements:

The functional requirements describe the core functionalities of the application.
This section includes functional requirements that defines what the application is
supposed to do.
This application will perform the following functionalities.
1. Contacts
FR_01 System shall allow the user to view contacts of child’s mobile phone on his
phone.

2. Calls
FR_02 System shall allow the users to view recent call logs of child’s mobile phone
on his phone.
FR_03 System shall allow the users to filter call logs of child’s mobile phone based
on frequency of contact.

7|Page
Safe Child-Parental Control Requirements Specifications Document

FR_04 System shall allow the users to filter call logs of child’s mobile phone based
on time of contact.
FR_05 System shall allow the user to view Missed calls of child’s phone.
FR_06 System shall allow the user to view Incoming calls of child’s phone.
FR_07 System shall allow the user to view Outgoing calls of child’s phone.

3. Messages
FR_08 System shall allow the users to view conversations of child’s mobile phone
on his phone.
FR_09 System shall allow the user to view Received messages of child’s phone.
FR_10 System shall allow the user to view conversation of selected contact.

4. Applications
FR_11 System shall allow users to lock any app on child’s mobile phone.
FR_12 System shall allow users to unlock any app on child’s mobile phone.
FR_13 System shall allow users to set time to automatically lock any app on child’s
mobile phone.
FR_14 System shall allow users to set time to automatically unlock any app on
child’s mobile phone.
FR_15 System shall allow the user to view the applications list of child’s mobile
phone.
5. Location
FR_16 System shall allow users to view current location of child’s phone.

6. Connection
FR_17 System shall allow users to connect his/her phone to child’s mobile phone.

FR_18 System shall allow users to add more than one phones as child phones for
monitoring.
FR_19 System shall allow users to remove any child mobile phone from
monitoring list.

7. Notifications
FR_20 System shall allow the user to get notifications of received messages from
child’s mobile phone.
FR_21 System shall allow the user to get notifications of applications from

8|Page
Safe Child-Parental Control Requirements Specifications Document

child’s mobile phone.

FR_22 System shall allow the user to send a notification to mobile’s phone.
FR_23 System shall allow the user to get battery notifications from child’s mobile
phone.

3.4 Traceability Matrix

User Requirements Functional Requirements
UR_01 FR_01
FR_02
UR_02 FR_03
FR_04
FR_05
FR_06
FR_07
FR_08
FR_09
UR_03 FR_10
FR_11
FR_12
FR_13
FR_14
UR_04 FR_16
UR_05 FR_17
UR_06 FR_18
UR_07 FR_19
UR_08 FR_23
UR_09 FR_24
UR_10 FR_20
UR_11 FR_21

3.5 Non Functional Requirements

Usability
Parental control is an android application with a simple user friendly interface.
Users can use it efficiently with satisfaction in a specified context of use.

NFR_01 A new user should be able to register the application in 7 to 8 steps

NFR_02 8 out of 10 users must be able to register and connect both apps in first
attempt.
NFR_03 Content on screen must be relevant to the features.
NFR_04 The product should be self-explanatory and intuitive such that a normal

9|Page
Safe Child-Parental Control Requirements Specifications Document

user should be able to understand it in 7 to 8 minute.

Performance
NFR_05 The response time to access data of child’s phone from server must be less
than 80 seconds
NFR_06 The response time for tracking the child’s location must be less than 30
seconds.
NFR_07 The visibility time of application interface must be less than 10 seconds.

Access Security:
NFR_08 The application will be installed in both phones, children’s and parent’s
When children try to uninstall the application, a notification will be sent
on parents’ phone.

3.6 Design Constraints

Software Languages
 Java
 Xml
 Php
Tools
 Android Studio
 VS Code

Database
 Firebase
 SQLite

4. Learning Outcomes
 Advanced android programming and development
 Writing a server software
 Use of API’s in android
 Working of Distributed System

5. Practical Applications
The end product would be beneficial for our society where growing technology
urge our pre-teen and youngsters to use mobile phone with modern technology. To avoid
them from using that technology in unmannered way, this application will allow the
parents to view and control their phones. It may allow the parents/users to lock the

10 | P a g e
Safe Child-Parental Control Requirements Specifications Document

children’s phone for stopping them form using phone every time.

11 | P a g e