Online Complaint & Threats Awareness Platform

SUBMITTED BY
Sardar Bilal Hussain 2015-GCUF-76831
Habibullah 2015-GCUF-76197

BACHELOR OF SCIENCE
IN
COMPUTER SCIENCE
(BSCS)

Department of Computer Science

GCUF, Sahiwal Campus
OCTA

DECLARATION

The work reported in this thesis carried out by me under the supervision of Hafza Mehreen
Department of Computer Sciences GC University, Faisalabad, Sahiwal Campus, Pakistan.

I here to declare that the title of Project Online Complain and Threat Awareness
Platform and the contents of thesis are the product of my own research and no part has been
copied from any published source (except the references, standard mathematical or genetic
models /equations /formulas /protocols etc.). I further declare that this work will not been
submitted for award of any other degree /diploma. The University may take action if the
information provided found inaccurate at any stage.

Students Name & Signature

Sardar Bilal Hussain Habibullah

2015-GCUF-76831 2015-GCUF-76197

_______________ ______________

ii
OCTA

CERTIFICATE BY SUPERVISORY COMMITTEE

This is to certify that Sardar Bilal Hussain Roll No. 2015-GCUF-76831, Habibullah Roll
No. 2015-GCUF-76197, has successfully completed the final project named as: Online
Complain & Threats Awareness Platform, at the Department of Computer Science,
Government College University, Faisalabad, to fulfill the partial requirement of the degree of
BS(CS).

Signature of Supervisor ………………….

Name: ……………………………………..
Designation with Stamp……………………….

Co-Supervisor (if any)

Signature ………………………………….
Name: ……………………………………..
Designation with Stamp……………………….

Member of Supervisory Committee

Signature ………………………………….
Name: ……………………………………..
Designation with Stamp……………………….

Member of Supervisory Committee

Signature ………………………………….
Name: ……………………………………..
Designation with Stamp……………………….

Chairperson
Signature with Stamp……………………………

Dean / Academic Coordinator

Signature with Stamp……………………………

iii
OCTA

ACKNOWLEDGEMENT

We thank the management of GCUF, our faculty and the staff of the Computer
Sciences Department, for motivating us to think beyond books and imbibing in us
the attitude and aptitude to implement what we have studied so far to make us
aware with some of the real-world challenges. We would like to convey our
heartfelt gratitude to our project guide “Ma’am Hafza Mehreen” inspiring us to
take up this project. His valuable guidance and timely support, without which, we
would have never been able to complete the project, cannot be forgot.
Finally, we would like to express our gratitude for the faculty members of
Computer Sciences Department of GCUF and thank them for their cooperation
and timely assistance. Finally, we would like to thank our parents for their
moral support.

iv
OCTA

ABSTRACT

The purpose of this creation for helping the user to communicate with our police via Portal. So that
the user can do their home. That complaint will automatically show at the portal of the respective
police station so the complaint can be submit and resolved on time. In police portal we will give
option of the do complaints, see news feed and prisoners ran away from the police custody. In
police custody console we will use face recognizer so that it will easy for the officer to detect the
prisoner face.

In this Production, there is an option of login for Investigation Officer that he can see daily
notifications by Admin and Applications whether he is in home or anywhere and he can see daily
base threats that is occur in station area.

v
OCTA

TABLE OF CONTENTS

1 INTRODUCTION
1.1 Introduction & History ............................................................................. 2
1.2 Clear Statement of the problem ................................................................ 3
1.3 Introduction to the Software tools ............................................................ 4
1.4 Objectives ................................................................................................. 4
1.5 Proposed Solution..................................................................................... 5
1.6 Motivation ................................................................................................ 5
1.7 Scope of Proposed Solution ..................................................................... 6
1.8 Relevance to Courses ............................................................................... 6
1.8.1 Introduction to Computer Programming (CSC103) ............................................ 6
1.8.2 Object Oriented Programming (CSC241) ............................................................ 6
1.8.3 Web Engineering (CSC336) ................................................................................ 6
1.8.4 Software Engineering (CSC291 & CSC392) ....................................................... 6
1.8.5 Database Systems (CSC271) ............................................................................... 6
1.8.6 Computer Communication and Networking (CSC339) ....................................... 6
1.9 Tools & Techniques ................................................................................. 7
1.9.1 Hardware Details ................................................................................................. 7
1.9.2 Software Details ................................................................................................... 7
1.10 Document Details ..................................................................................... 7
2 STATE OF THE ART
2.1 Cognitive Services .................................................................................... 9
2.2 Face API ................................................................................................... 9
2.3 Online Complain & Threats Awareness Platform .................................. 9
2.3.1 Implementations of the Online Complain & Threats Awareness
Platform in the world ......................................................................................... 9
2.4 Existing Applications ............................................................................. 10
2.5 Drawbacks of Existing Applications ...................................................... 10
2.6 The Necessity ......................................................................................... 10
2.6.1 Appoint Confidentiality ..................................................................................... 10

vi
OCTA

2.6.2 Accurate Records ............................................................................................... 11

2.6.3 Better Streaming ................................................................................................ 11
2.7 Proposed Application Architecture ........................................................ 11
3 METHODOLOGY & WORKPLAN
3.1 Existing Methodology ............................................................................ 13
3.1.1 Waterfall Model ................................................................................................. 13
3.1.2 Incremental Model ............................................................................................. 14
3.1.3 Spiral Model....................................................................................................... 15
3.1.4 Agile Model ....................................................................................................... 16
3.2 Adopted Methodology ............................................................................ 17
3.3 Project Time Allocation ......................................................................... 18
3.4 Roles & Responsibilities ........................................................................ 19
4 SYSTEM ANALYSIS & DESIGN
4.1 Requirements Gathering Techniques ..................................................... 21
4.2 Requirement Analysis ............................................................................ 21
4.2.1 Functional Requirements ................................................................................... 21
4.2.2 Non-Functional Requirements ........................................................................... 22
4.2.3 Website Quality Attribute .................................................................................. 22
4.2.3.1 Availability ................................................................................................. 22
4.2.3.2 Maintainability............................................................................................ 22
4.2.3.3 Consistency................................................................................................. 23
4.2.3.4 Portability ................................................................................................... 23
4.2.4 Database Requirements ...................................................................................... 23
4.3 Planning & Scheduling........................................................................... 23
4.3.1 Gantt Chart ......................................................................................................... 23
4.4 Use Cases................................................................................................ 24
4.4.1 UC1: Login ........................................................................................................ 24
4.4.2 UC2: Maintain Database .................................................................................... 25
4.4.3 UC3: Take Photo................................................................................................ 26
4.4.4 UC4: Analyze face Attributes ............................................................................ 27
4.4.5 UC5: Face Verification ...................................................................................... 28
4.4.6 UC6: Logout ...................................................................................................... 30
4.4.7 UC7: Admin Functionalities .............................................................................. 31
4.4.8 UC8: User Functionalities.................................................................................. 32
vii
OCTA

4.5 Sequence Diagrams ................................................................................ 32

4.5.1 SQ1: Administrator ............................................................................................ 33
4.5.2 SQ3: User ........................................................................................................... 34
4.6 Activity Diagram .................................................................................... 34
4.6.1 AD: Administrator ............................................................................................. 35
4.6.2 AD: User ............................................................................................................ 36
4.7 Entity Relationship Diagram .................................................................. 36
5 SYSTEM IMPLEMENTATIONS
5.1 Introduction ............................................................................................ 39
5.2 Screenshots ............................................................................................. 39
6 SYSTEM TESTING
6.1 Introduction ............................................................................................ 46
6.2 Testing Plan ............................................................................................ 46
6.2.1 Unit Testing ....................................................................................................... 46
6.2.2 System Testing ................................................................................................... 47
6.2.3 Integration Testing ............................................................................................. 47
6.2.4 User Acceptance Testing ................................................................................... 47
6.3 Test Cases ............................................................................................... 48
6.4 Test Results ............................................................................................ 49
7 CONCLUSION & FUTURE WORK
7.1 Conclusion .............................................................................................. 51
7.2 Future Work............................................................................................ 51

REFERENCES .................................................................................................. 52

viii
OCTA

LIST OF FIGURES
Figure 1: Waterfall Model .................................................................................................................... 14
Figure 2: Incremental Model................................................................................................................. 15
Figure 3: Spiral Model .......................................................................................................................... 16
Figure 4: Agile Iterative Model ............................................................................................................ 17
Figure 5: Adopted Methodology ........................................................................................................... 18
Figure 6: Work Plan (using Gantt chart) ............................................................................................... 23
Figure 7: Login (Use Case) ................................................................................................................... 24
Figure 8: Maintain database (Use Case) ............................................................................................... 25
Figure 9: Take photo (Use Case) .......................................................................................................... 26
Figure 10: Select photo from gallery (Use Case) .................................................................................. 27
Figure 11: Face verification (Use Case) ............................................................................................... 29
Figure 12: Logout (Use Case) ............................................................................................................... 30
Figure 13: Administrator functionalities (Use Case) ............................................................................ 31
Figure 14: User functionalities (Use Case) ........................................................................................... 32
Figure 15: Administrator (Sequence Diagram) ..................................................................................... 33
Figure 16: User (Sequence Diagram).................................................................................................... 34
Figure 17: Administrator (Activity Diagram) ....................................................................................... 35
Figure 18: User (Activity Diagram) ...................................................................................................... 36
Figure 19: Entity Relationship Diagram ............................................................................................... 37
Figure 20: Front Page (Screenshot) ...................................................................................................... 39
Figure 21: Admin Portal (Screenshot) .................................................................................................. 40
Figure 22: Add Employee (Screenshot) ................................................................................................ 41
Figure 23: Add News Feed (Screenshot) .............................................................................................. 42
Figure 24: Assign Complaints (Screenshot) ......................................................................................... 43
Figure 25: Complaints from User (Screenshot) .................................................................................... 44

ix
OCTA

List of Tables

Table 1: Project Plan & Key Milestones ............................................................................................... 18

Table 2: Test Cases ............................................................................................................................... 48

Table 3: Test Results............................................................................................................................. 49

x
 CHAPTER 1

INTRODUCTION
OCTA

1 INTRODUCTION
In this chapter, we will introduce this application, software tools, problem statement,
objectives, scope of this application, proposed application, motivation of this proposed
solution, relevance to courses and tools & techniques those are uses to implement this
application.

1.1 Introduction & History

It was difficult for people to going Police station for complaint. They bring our CNIC and
thumb expressions and many more requirements for complaints. They cannot satisfied
because there is a long period of investigation. They are not comfortable with going to Police
Station and wastage of time. Because it takes more time and not satisfied. They want an
easier way to submit the complaint according to their own words and advise. They want to
get status about their complaint.

For this reason, we created unique application working for the help of these peoples who
cannot waste their time on going to Police station and just want one click to submit the
complaints.

For the reason we design a mobile application which is based on "ONLINE COMPLAIN &
THREATS AWARENESS PLATFORM ".

Our project based on ANDROID, UWP and WEB API (ASP.NET MVC5). We have created
this Application for Criminal & Terrorists face detection.

Our application will use cognitive service for detecting face it will work online.

For face detection, we will create API controller in web application and we will get prisoners
& criminal record in our application but using JSON conversions.

This application is bases on latest Microsoft technology JSON and cognitive services built
already separately. We are make it with combination.

The complaints will be recommend upon the area category.

2
OCTA

User can easily do complaint from application using this app user can see news feed and they
can get access by swipe the page to choose action.

Admin have login module for see relevant complaint and assign these complaints to
employees after that the data that we enter in admin panel will be assign to the employee in
database according to area categories.

Headquarter has following features:

• Assign Complaints to officers

USER has following features:

• Do Complaint

• Select City

• Select Station.

• See News Feed

1.2 Clear Statement of the problem

ONLINE COMPLAIN & THREATS AWARENESS PLATFORM are not use yet but we are
trying to implement this through an organization on Google play store. During the last decade
availability of the internet connections at the reasonable cost to make it affordable to a much
wider group of users.

Now a day’s people want to secure themselves in easier way by this type of complaint cells
but this production is first time in Mobile Application that is access by handheld devices.

1.3 Introduction to the Software tools

The " VISUAL STUDIO 2017" and POSTMAN ", "ADOBE PHOTOSHOP “are the software
that are used in the backend for overall developing this project. Reason behind using latest
versions is that; they support latest technologies and libraries for developing this project.

For front end we are using XAML, HTML and for backend implementation, C#, ASP.NET
framework have been used. Rather than writing numerous lines of code, we are using built in

3
OCTA

controllers for making API and DATABASE. You can add scaffolding to your project when
you want quickly add code that interacts with data models. In this, you may also use ready-
made objects. Each object has its own properties, determining its positions, nature of its text
and much more.

Model: Model contains the application logic, represents the things in the application.

View: Views present the data to the user.

Controllers: The controller decide what to do with the various user actions.

Various Nugget Packages are uses in this project such as:

• Work is done with Media Manager, Newton Soft in this project

• For add and removes we use modules for this purpose and, we use Nugget Packages
for support minimum latency.

• Database Management System

• We use Visual Studio for the ASP.NET, XAMARIN code

We are using API controller for creating JSON and calling it into mobile application.

1.4 Objectives

The objectives are important to achieve the goal. The main objectives of this project are:

• Make a reliable, inexpensive and easy solution for people who want to access
complaint cell at any place.
• Do complaint easily from user’s relevant area.
• Admin can store new employee through their respective login portal.
• Admin can Detect face Verification.
• Assign complaints according to area.
• Our application is compatible with cross platforms.
• ONLINE COMPLAIN & THREATS AWARENESS PLATFORM can see all stuff of
movies.
• Today, the platform like this has become a need of our society.
• Online systems are always welcome in this new world of I.T.

4
OCTA

• It can be uses in any location like a robbery site.

1.5 Proposed Solution

Online Complain & Threats Awareness Platform is a cross Platform based, all type of
complaints that have user to do with face detection that was launch earlier this year with the
objective of providing users with a single platform on web forms do not in mobile App.

After using the app for a good long while, we have come to realize that we no longer need
web base platform for do complaints like PM Complaint Cell. This app does it all and more!

This application has friendly user interface. It is very useful for us for do complaint. In this
app we verified prisoners with detect emotions.

The aim is to provide one platform for users and Police Officers.

1.6 Motivation

Online Complain & Threats Awareness Platform saves significant amount of time in terms of
going to Police Station to meet with relevant officer to resolve their problems. Despite the
inexistence of these types of projects application, the following features are the motivational
source of our project:

• It is mobile base application with 8 MB of storage.

• We are using face detection for taking decision to detect prisoners.

• User can do complaint through required data enter in entries.

1.7 Scope of Proposed Solution

Primarily, the scope pertains to the Cross product features for making Online Complain &
Threats Awareness Platform live. It focuses on the company, the stakeholders and
applications, which allow for online complaint, identity capturing and complaint according to
user. According to our survey those we have done to check the feasibility of this project, the
modules that selected to implement in this cross platform based project (Online Complain &
Threats Awareness Platform) are he modules are need of society.

5
OCTA

1.8 Relevance to Courses

1.8.1 Introduction to Computer Programming (CSC103)

We have studied the basics of programming in this course. Using the concepts of C#.

1.8.2 Object Oriented Programming (CSC241)

Using the concepts of OOP approach in programming pattern and coding design we
implemented our project.

1.8.3 Web Engineering (CSC336)

Using the concepts of Web Engineering, application will developed using C#.net framework,
ASP.NET.

1.8.4 Software Engineering (CSC291 & CSC392)

This course helped us to evaluate our development methodologies those are uses in our
project.

1.8.5 Database Systems (CSC271)

In this project, we develop relational database system for efficient working of the project by
using the concepts of database systems.

1.8.6 Computer Communication and Networking (CSC339)

Communication to different ends will done using the knowledge learned from this course.

1.9 Tools & Techniques

Online Complain & Threats Awareness Platform! Cross platform based Project consists of
software and hardware tools and technologies. Hardware details are given in section 1.9.1,
Software details are given in section 1.9.2 and document details are given in section 1.10.3.

1.9.1 Hardware Details

• No Hardware Require except laptop/tablet/phones.

6
OCTA

• Normal Internet Connection

1.9.2 Software Details

• Visual Studio 2017

• Postman

• Adobe Photoshop

1.10 Document Details

Presently, our app for a user to do complaint first user can click from Get Started button and
then after enter the data about himself like as CNIC, Area and Station that will be shown on
the do complaints page.
After that write complaint and submit by the user.
If you do not complaint then see news feed about Police Headquarter by swiping the
complaints page.
In Admin portal the only way to get face verification about prisoners are through directly
capture picture, select picture from police database, and then detect accuracy of pictures.
It is a problem for those people who don’t want to search .in this app just use button clicks no
more searching required .it is best application for complaints and threats awareness.

7
 CHAPTER 2
STATE OF THE ART
OCTA

2. STATE OF THE ART

In this chapter, we will discuss. What is cognitive services? What is Face API? What is Online
Complain & Threats Awareness Platform? How we’ll implement this application in real
world? Why we need it? What is the pros and cons of existing applications and proposed
application?

2.1 Cognitive Services

Cognitive Services are a set of machine learning algorithms that Microsoft has developed to
solve problems in the field of Artificial Intelligence (AI). ... Web and Universal Windows
Platform developers can consume these algorithms through standard REST calls over the
Internet to the Cognitive Services.

2.2 Face API

The Face API detect faces at a range of different angles. Face detection is the process of
automatically locating human faces in visual media (digital images). A Face that is detected
and reported at a position with an associated size and orientation and detect prisoner’s face.

2.3 Online Complain & Threats Awareness Platform

OCTA is a mobile application in which user can do his/her complaint and submit according to
their area. Admin detect prisoner image is detected by using Microsoft cognitive services.

2.3.1 Implementation of Online Complain & Threats Awareness Platform to

World:
We can implement this Project in Google play store. Firstly, we must give an access to any
administrator for administrator’s role. He/she can add employee of an application. Any
member can access this application with Normal internet connection. Speed and accuracy are
the main advantages of proposed system.
There are no redundancies of data. The employee details are easily stored, retrieved and
add and delete news feed at any time. The proposed system will easily handle all the data and
the work done by the existing systems. The proposed systems eliminate the drawbacks of the
existing system to a great extent and it provides tight security to data It provides easiest way

9
OCTA

for all the users and admin to get all the information needed as quick as possible that too from
anywhere in the world. The persons and updating in time.
Admin can assign complaint at any time at any place and user can resolve their complaint at
any time at any place.

2.4 Existing Applications

Currently, there are no more familiar websites we have in the pocket now a day but we will
try our best to implement this projects in the market for the first time because it will make ease
in the world of Criminal courts.
Presently, our system for detect face of prisoner and complaint cell. The only way to get all
these features to complaint cell and helping for officers to face recognition of prisoner. Hence,
it’s a very big problem for those who don’t have any idea of how to do complaint in Police
station. This application is beneficial for those users who want to know direct do complaint in
relevant station about his/her criminal or fraud cases.

2.5 Drawbacks of Existing Applications

Currently, there is no other Mobile application exists so we have no drawbacks but if it exists
then we have several drawbacks:
• There is no application of this type is in the market so it’s very difficult to implement
this into market
• People cannot easily attract to the application we have to take them here.
• We should have to work deeply and work in the way so that people show their interest
in this project.

2.6 The Necessity

There are some necessities for this android and website conduct meetings are as follows:

2.6.1 Appoint Confidentiality

Appoint Confidentiality must maintained by Online Complain & Threats Awareness Platform
By this administrator have full control over all Portals.

2.6.2 Accurate Records

Online Complain & Threats Awareness Platform must show accurate records of prisoners.

2.6.3 Better streaming

10
OCTA

Online Complain & Threats Awareness Platform must provide the facility of better streaming
using internet connection.

2.7 Proposed Application Architecture

Those problems have been occurring in the existing applications, overcome in proposed
project. In this, we are implemented all of the functionality by using any device with internet
access for application to handling the circulate entries and built better streaming for the user.

The objective of the project is a system that used for providing easiest approach according to
user needs. It captures the information of prisoner and provide the prisoner list. It provides a
facility for all user according to their area and stations.

11
 CHAPTER # 3

METHODOLOGY & WORKPLAN

OCTA

3 METHODOLOGY & WORKPLAN

In this chapter, we will discuss that what are the existing methodologies and which one we
have chosen for implementation of this project in an effective way and we will discuss
advantages of adopted methodology.

What is the methodology and why need it?

Whenever a small or large project have started to develop, first thing all of programmers
required is methodology. Methodology is a way of developing a project, in which all the
programmers gather the user’s requirements, design the project, implement it, and after all this
testing and maintenance of the project, in a satisfaction of user and according to the project
requirements.

3.1 Existing Methodology

There are several existing methodologies can be used to develop this application using software
development processes.

3.1.1 Waterfall Model

In the software development process, the very first model that published from other
engineering processes that is cascaded from one phase to another form that known as Waterfall
model. This model is also known as linear sequential model. In the waterfall model, firstly all
the requirements gathered. After gathering all the requirements and analysis of all the
requirements further move to next phase that is making the design of a project and then Simple
mentation, testing and maintenance phases.

As all the next phases of this model is dependent on previous phase. All the phases worked as
a waterfall after one another. It is a documentation driven model. In this model, feedback of
the client received at the end of the project and when the product will delivered to the user.
Hence, mistake in the product requirement specification will discovered after delivered to the

13
OCTA

user. This is Time and cost consuming methodology, that is why we have not used this
methodology in developing this project.

The waterfall model further described in the following diagram:

Figure 1: Waterfall Model

3.1.2 Incremental Model

To overcome the drawbacks of the waterfall model, incremental model is used. In incremental
model, the product developed in increments and partitioned into smaller pieces. These smaller
pieces then built and delivered to client in increments. Quick response from clients. Each
module is smaller than compare to whole module.

14
OCTA

Figure 2: Incremental Model

3.1.3 Spiral Model

Spiral Model developed by Barry Boehm. The main idea of this model is to avert risk, as there
is always an element of risk in development of software. For example, key personnel may
resign at a critical juncture, the manufacturer of the software development may go bankrupt,
etc. In its simplified form, the Spiral Model is Waterfall model plus risk analysis. In this case
each stage is preceded by identification of alternatives and risk analysis and is then followed
by evaluation and planning for the next phase.

If risks cannot be resolved, project immediately terminated. This depicted in the following
diagram.

15
OCTA

Figure 3: Spiral Model

3.1.4 Agile Model

Agile model is useful when there is no hope for changings in product after deployment. It is a
approach to project management that is utilized in software development. This method assists
teams in responding to the unpredictability of constructing software. It uses incremental,
iterative work sequences that commonly known as sprints. The ability to create and respond to
change to succeed in an uncertain and turbulent environment.

16
OCTA

Figure 4: Agile Iterative Model

3.2 Adopted Methodology

Incremental model used to develop this project, in which we divided our work in multiple
modules. All these modules further divided into more easily managed modules that made up
the actual implementation of the requirements.

Reason behind using this model is:

 It is easy to test and debug the product during iterations.

 Software released in increments over time is more likely to satisfy changing user
requirements than if it was plan as a single overall release at the end of the same period.

17
OCTA

Figure 5: Adopted Methodology

3.3 Project Time Allocation

Table 1: Project Plan and key milestone

Key Milestones of the Project with dates

S. No Elapsed time since start of the Milestone Deliverable

project

1. Month (September 11,2018 – Analysis & Complete Research

October 09,2018) Requirements Proposal

2. Month (October 10,2018 – Planning, scheduling Report

and purchase of
November 13,2018)
hardware
3. Month (November 14,2018 – Modeling & design Report
December 18,2018)

4. Month (December 19,2018 – Coding & testing Software System

January14,2019)

5. Month (January 19,2019 – Deployment Hardware & Software

System
May 14,2019)

18
OCTA

3.4 Roles & Responsibilities

Project development team is consisting of two members. To accomplish a goal,

documentation and development will equally distributed among them and each member work
on parallel to avoid wastage of time.

19
 CHAPTER 4

SYSTEM ANALYSIS & DESIGN

OCTA

4 SYSTEM ANALYSIS & DESIGN

In this chapter requirements analysis, feasibility study, planning, forecasting, modeling,

scheduling and design of the project discussed. For developing any project, the major problem
is requirement gathering. Asking questions from clients is straightforward than collecting
requirements. We will also focus on functional and non-functional requirements.

The procedure for gathering requirements has its own defined procedure according to the
complexity of the application. To define project schedule and processing, different models and
techniques also focused on this chapter.

4.1 Requirements Gathering Techniques

A requirement can defined as a condition or capability that must processed by a product or an

application. Techniques that can used for collecting requirements are as follows:

 By questionnaire and survey

 By interview
 By observations

The techniques we have used to collect requirements are observations and interviews.

4.2 Requirement Analysis

Requirements analysis is the process of planning, forecasting and studying the overall
former needs of the application requirements. Requirements analysis further divided into two
parts:

1. Functional Requirements
2. Non-Functional Requirements

4.2.1 Functional Requirements

Functional requirements are the requirements that should provide by an application. It defined
as a service statement. Functional requirements tell how an application should behave in
different situations and how it will react to an input.

Functional requirements of the ONLINE COMPLAIN & THREATS AWARENESS

PLATFORM are as follows:

REQ-F1: The project will generate administrator service for login.

21
OCTA

REQ-F2: The administrator will be able to add new employees in database.

REQ-F3: The user will be able to do complaint.

REQ-F4: The user will be able to select area from list according to stations.

REQ-F5: The user will be able to see news feed.

4.2.2 Non-Functional Requirements

Non-functional requirements are the constraints or checks on the services and functions
provided by an application such as constraints on the development standards/process and
constraints of time etc.

Non-Functional requirements of ONLINE COMPLAIN & THREATS AWARENESS

PLATFORM are as follows:

REQ-NF1: Mobile application shall provide better response and performance. It shall take
initial load time depending on internet connection strength.

REQ-NF2: Mobile application shall provide good quality of working in normal internet
connection.

REQ-NF3: Mobile application must be efficient.

REQ-NF4: Mobile application must be user interactive.

REQ-NF5: Mobile application must be user Friendly.

4.2.3 Mobile application Quality Attribute

4.2.3.1 Availability

 Mobile application must be responsive and available at every time.

 Availability of speedy internet connection is the major requirement of the application.

4.2.3.2 Maintainability

Making changes or upgradeability in the app will not be that much difficult. By having some
knowledge of programming, some features of the application might converted to a new version.

22
 OCTA

4.2.3.3 Consistency

When an administrator is updating information, consistency must hold there.

4.2.4 Database Requirements

In this section, the database requirements for this application mentioned:

We use MYSQL for the Database Management system.

4.3 Planning & Scheduling

4.3.1 Gantt chart

A Gantt chart is a scheduling technique that used commonly in project management. It is one
of the useful and common way of representation of activities displayed in contrast to time. On
the vertical side of the chart activities list displayed and on the top a time scale which is
appropriate. A bar represents each activity’s length and shows the start date, end date and
duration of the activity. This shows following information.

 “What the different activities are?”

 “When an activity starts and ends?”
 “How much long each activity is scheduled to finish?”
 “The start and finish date of the whole project.”

Figure 6: Work Plan (using Gantt Chart)

Working Schedule
No. Activities Duration(weeks)
1 2 3 4 5 6 7 8 9 10 11 12 13 14
1 Selection of Supervisor

23
 OCTA

2 Search about Project

3 Model of the Project
4 Proposal and Submission
5 Project Implementation
6 Project Designing
7 Project Functionality
8 Project Development
9 Final Testing of the project

4.4 Use Cases

An important part of the analysis phase is to draw the diagrams of Use cases. They are used
through the phase of analysis of a project to find and divide functionality of the application.
Application is separated into actors and use cases.

Actors play the role that are played by the application users. Use cases define the application
behavior when one of the actors sends any motivation. This type of behavior can be described
by text. It describes the motivation nature that activates use case, the inputs and outputs to some
other actors and the behavior of conversion of inputs to the outputs.

Usually the use case describes everything that can go wrong during the detailed behavior and
what will be helpful action taken by the application.

Some of the use cases are as follows:

4.4.1 UC1: Login

Actor: Administrator

24
OCTA

Figure 7: Login (Use Case)

Pre-Condition:

1. For the Admin, he/she must have controlled of LOGIN panel.

2. Admin must enter correct Email address and Password for login.

Post-Condition:

Admin can access to application’s DATABASE of movies.

Basic Path:

1. Enter Email-Address and password for login.

2. The application verifies the correct format and valid email address and Password.
3. If provided inputs are correct, the application displays the database of movies to the
Admin.

Constraints:

1. If provided email address and password are incorrect or invalid, application redirect to
main page for login.

Non-Functional Requirements:

1. Short Response Time

2. Better performance
3. Availability

25
OCTA

4.4.2 UC2: Maintain Database

Actor: Administrator

Figure 8: Maintain Database (Use Case)

Pre-Condition:

1. UC1
2. The administrator must provide complete details of a employee.

Post-Condition:

1. New employee should be add successfully.

2. New employee show in officers list.

Basic Path:

1. The administrator should be log in to the application to perform this activity.

2. The administrator enters employee information.
3. The administrator clicks on Add button.
4. The application verifies the valid entered inputs.
5. After verifying provided information of officers added in the application’s database.

26
OCTA

Non-Functional Requirements:

1. Better response
2. Reliable

4.4.3 UC3: Take Photo.

Actor: Admin

Figure 9: Take Photo (Use Case)

Pre-Condition:

1. User must enter in application.

2. User must click the “TAKE PHOTO” button.
3. User must access the camera for take photo.
4. User must access stored photo from gallery

Post-Condition:

1. User take photo successfully.

2. System access photo successfully from gallery.

Basic Path:

1. User enters in the application.

2. User clicks on the “TAKE PHOTO” button.
3. User access the camera then clicks camera’s button.

27
OCTA

4. User take- photo successfully.

Non-Functional Requirements:

1. Better response
2. Easy to use
3. Availability
4. Short response time.

4.4.4 UC4: Analyze the face attributes.

Actor: User

Figure 10: Select photo from gallery (Use Case)

Pre-Condition:

1. UC3
2. Selected photos exists in database.

Post-Condition:

1. User successfully select the photo.

2. User recognize to face attributes (Gender, age and bald).

Basic Path:

1. Select Camera and user take the photo.

28
OCTA

2. Then selected photo ready to analyze face attributes.

3. Check Face Recognize.

CONSTRAINTS:

1. User must take the photo.

2. User must analyze the face detect by camera.

NON-FUNCTIONAL REQUIREMENTS:

1. Short response time.

2. Efficient
3. Availability

4.4.5 UC5: Face verification.

Actor: User

Figure 11: Face verification (Use Case)

29
OCTA

Pre-Condition:

1. User must enter in face verification phase.

2. User move on face analyze page.
3. User must select the required photos.
4. User must click on verified button.

Post-Condition:

1. User successfully select the photo.

2. User selected photo send to the analyzer.

Basic Path:

1. User enters in the application.

2. User move on face verification page.
3. User take the photo from application camera.
4. User show the face attributes for recognition.

CONSTRAINTS:

1. User not move on Face verification page then no verification occur.

NON-FUNCTIONAL REQUIREMENTS:

1. Better response
2. Reliable

4.4.6 UC6: Logout

Actor: Administrator

30
OCTA

Figure 12: Logout (Use Case)

Pre-Condition:

1. UC1

Post-Condition:

1. Login Panel displayed to the Admin.

Basic Path:

1. Administrator clicks on logout.

2. Administrator exits from application.

NON-FUNCTIONAL REQUIREMENTS:

1. Secure
2. Reliable
3. Better performance
4. Short Response Time

31
OCTA

4.4.7 UC7: Administrator Functionalities

Figure 13: Administrator Functionalities

32
OCTA

4.4.8 UC8: Admin Functionalities

Figure 14: Administrator Functionalities

4.5 Sequence Diagrams

Sequence diagram uses concept of a Message-Sequence-Chart. It shows interactions of objects
in a sequence of time. It shows the classes and objects involved in the scenario and the message
sequence between the objects which is desired to carry out the functionality of a given scenario.

Sequence diagrams are usually related with the understanding of use case in the logical View
of the system which is under development. “Sequence diagrams are sometimes called event
diagrams, timing diagrams, event scenarios”.

33
OCTA

A parallel vertical line on sequence diagram is called lifeline. Different objects or processes
that live simultaneously, and, on horizontal arrows, the messages exchanged, in the order in
which processes occur. This allows some specification of some simple runtime scenarios in a
graphical pattern.

4.5.1 SQ1: Administrator

Figure 15: Administrator (Sequence Diagram)

34
OCTA

4.5.2 SQ2: User

Figure 16: User (Sequence Diagram)

4.6 Activity Diagram

Activity diagram is describing the dynamic aspects of the system. Activity diagram is
basically a flowchart to represent the flow from one activity to another activity. The activity
can be described as an operation of the system. The control flow is drawn from one operation
to another. The basic purposes of activity diagrams are like other diagrams. It captures the
dynamic behavior of the system. Other diagrams are used to show the message flow from one
object to another but activity diagram is used to show message flow from one activity to
another.

Activity is an operation of the system. Activity diagrams are not only used for visualizing the
dynamic nature of a system, but they are also used to construct the executable system by using

35
OCTA

forward and reverse engineering techniques. The only missing thing in the activity diagram is
the message part.

4.6.1 AD: Administrator

Figure 17: Administrator (Activity Diagram)

36
OCTA

4.6.2 AD: User

Figure 18: User (Activity Diagram)

4.7 Entity Relationship Diagram

An entity relationship model, also called an entity-relationship (ER) diagram, is a graphical

representation of entities and their relationships to each other, typically used in computing
regarding the organization of data within databases or information systems. An entity is a piece
of data-an object or concept about which data is stored.

37
OCTA

Figure19: Entity Relationship Diagram

38
 CHAPTER # 5

SYSTEM IMPLEMENTATION
OCTA

5 SYSTEM IMPLEMENTATION
In this chapter, we will focus on an implementation of “Online Complain & Threats
Awareness Platform” application. Where administrator and user can perform many activities
on mobile app.

5.1 Introduction
The most important goal of this phase is to develop the application. The work in this phase
should be much more straightforward because of the work done in the planning and design
phases. This phase involves changing design specifications into executable programs. When
the design is there, developers can have an idea on looks of application. All that is needed by
developers is to put them at one place to understand about the intended project.

5.2 Screenshots

Figure 20: Front Page (Screenshot)

40
OCTA

Figure 21: Admin Portal (Screenshot)

41
OCTA

Figure 22: Login (Screenshot)

42
OCTA

Figure 23: Take Photo (Screenshot)

43
OCTA

Figure 24: Do Complaints (Screenshot)

44
OCTA

Figure 25: complaint verify (Screenshot)

45
OCTA

Figure 26: Assign complaints (Screenshot)

46
OCTA

Figure 27: Add Employee (Screenshot)

47
 CHAPTER 6

SYSTEM TESTING
OCTA

6 SYSTEM TESTING
In this chapter, we will discuss the testing phase of developed application “Online Complain
& Threats Awareness Platform” in different manner to know that how much efficient and
effective application is.?

6.1 Introduction

A process of performing as application or program with the intention of finding errors and
whether the app is fulfilling user needs. It can also be defined as the ability of a program in
meeting the required or desired results.

In many methodologies of software engineering, a separate phase is called phase of testing

which is performed after the completion of the implementation. There is a benefit in using this
approach that it is hard to see one's own mistakes, and a fresh eye can find observable errors
much faster than the person who has read the material many times.

6.2 Testing Plan

A process of performing as application or program with the intention of finding errors and
whether the application is fulfilling user needs.

6.2.1 Unit Testing

The software units in an application are modules and routines that are assembled and integrated
to perform a specific function. Unit testing focuses first on modules, independently of one
another, to locate errors. This enables, to detect errors in coding and logic that are contained
within each module. This testing includes entering data and ascertaining if the value matches
to the type and size supported by C#. The various controls are tested to ensure that each
performs its action as required.

Commonly used method is White-Box Testing method. Every time a component of the
program is changed, it can be run for testing that is the biggest and famous benefit of this testing
phase. Issues that are arises during this phase, allowing to be resolved as quickly as possible.
Unit testing is familiar by software developers. It allows them to test their application units
before moving them to testers for formal testing.

49
OCTA

6.2.2 System Testing

To test the complete application, system testing has been used. It is beneficial to check whether
the application meets its requirements and fulfill Quality Standards.

6.2.3 Integration Testing

Integration testing allows the software developers to integrate all the components/ units of the
application within a program and then test them in a group. Basically, this testing level is used
to catch the defects in the user interface between the functions/ modules. It is useful to
determine how logically and efficiently all the units/ components are running together. Here
the streaming module and encoding module options are integrated and tested. This testing
provides the assurance that the application is well integrated functional unit with smooth
transition of data.

6.2.4 User Acceptance Testing

User acceptance of an application is the key factor for the success of any application. The
application under consideration is tested for user acceptance by constantly keeping in touch
with the application users at time of developing and making changes whenever required.

50
OCTA

6.3 Test Cases

Table 2: Test Cases

Test Cases Objectives

1 Make sure that user can easily get started

Make sure that administrator can easily

2
manage Database.

3 Make sure that user can easily access

Camera for take photo.

Make sure that user can easily select area.

4

Make sure that user select area according

5
to relevant station.

6 Make sure that portals are signed up

successfully.

51
OCTA

6.4 Testing Results

CRITERIA Test Status REMARKS

All the graphical user interface

options display successfully. Test successful None

Enter valid login user email

address and password and then Test successful None
press login

Add files using Azure

Test successful
database None

Run Mobile in different Test successful None

platforms

Table 3: Test Results

52
 CHAPTER 7

CONCLUSION & FUTURE WORK

OCTA

7 CONCLUSION & FUTURE WORK

In this chapter, we will discuss the results and discussions of this framework “Online
Complain & Threats Awareness Platform ” with conclude remarks and will also discuss
related future work of this application.

7.1 Conclusion

“Online Complain & Threats Awareness Platform” is developed for do complaints with simple
click. The main objective of this application is to provide the facility of easily do complaint
through CNIC and area according to station. In other side see news feed only one swipe on
next page. Make a reliable, inexpensive and easy solution for people who want to submit
complaint at any place. Admin can store new employee through their respective login portal.
Online Complain & Threats Awareness Platform can see all stuff of Criminal cases which are
relevant to the Police Station. Today, the platform like this has become a need of our society.
Online systems are always welcomed in this new world of I.T. It can be used in any location
for Detect the Face of old and new Prisoners by database.

7.2 Future work

We will implement this application in desktop and IOS in future. In this application update
with new features. In future we will provide Face detection offline and pass away front of the
camera and system tell us what is real for better performance.

54
OCTA

7.3 REFERENCES:

[1] https://msdn.microsoft.com/en-us/library/dd381412(v=vs.108).aspx

[2] David britch - https://docs.microsoft.com/en-us/xamarin/xamarin-forms/data

cloud/cognitive-services/emotion-recognition

[3] https://msdn.microsoft.com/en-us/library/dd381412(v=vs.108).aspx

[4] Munib Ch - https://www.c-sharpcorner.com/article/emotion-detection-in-xamarin-

forms-by-using-azure-cognitive-services/

[5] https://deanilvincent.github.io/2017/05/16/xamarin-forms-simple-login-with-rest-
api/

[6] Bill Wagner - https://docs.microsoft.com/en-us/dotnet/csharp/programming-

guide/concepts/serialization/

[7] Carter, David L., and Louis A. Radelet. The police and the community. Upper Saddle River,
NJ: prentice hall, 2002.

[8] Collao, Rodrigo. "Developing Affordable Smart Solutions for Police Reporting." (2018).
[9] Del Sole, A., 2018. Computer Vision on Mobile Apps with Xamarin. In Microsoft Computer
Vision APIs Distilled (pp. 43-67). Apress, Berkeley, CA.

[10] Puder, A., Tillmann, N. and Moskal, M., 2014, June. Exposing native device APIs to web
apps. In Proceedings of the 1st International Conference on Mobile Software Engineering and
Systems (pp. 18-26). ACM.

[11] Ding C, Tao D. Trunk-branch ensemble convolutional neural networks for video-based
face recognition. IEEE transactions on pattern analysis and machine intelligence. 2017 May
2;40(4):1002-14.

55