SOFTWARE REQUIREMENT SPECIFICATION

FOR
NLP BASED SAFE CITY LABELLING USING
INFORMATION EXTRACTION FROM E-
NEWSPAPERS
[28/06/2019]
CDAC, MUMBAI

Revision History:

Reason For
Version Date Authored By Reviewed By
Change

00 28/06/2019 Team 3 1st Release

1
 Table Of Contents

Page
Sr.No Contents
No.
1. Introduction

1.1 Purpose 4

1.2 Product Scope 4

1.3 References 4

2 Overall Description

2.1 Product Perspective 4

2.2 Product Function 5

2.3 User Classes and Characteristics 5

2.4 Operating Environment 5

2.5 Design and Implementation Constraints 5

2.6 User Documentation 5

2.7 Assumptions and Dependencies 5

3. External Interface Requirements

3.1 User Interface 6

3.2 Hardware Interface 6

3.3 Software Interface 6

3.4 Communication Interface 6

4. System Features

4.1 Description 7

4.2 Functional Requirements 7

5. Performance Requirements

5.1 Safety Requirements 7

5.2 Security Requirements 7

5.3 Software Quality Attributes 7

6. Other Requirements

2
6.1 Appendix A:Glossary 8

6.2 Appendix B:Analysis Model

6.2.1 UseCase Diagram 9

6.2.2 Class Diagram 10

6.2.3 Activity Diagram 11

6.2.4 Sequence Diagram 11

3
1. Introduction

1.1. Purpose

NLP based safe city labelling using information extraction from E-news
paper is a web application which provides an information about city and its safe areas
through which users can view the safe and unsafe areas. The main objective is to
identify the unsafe areas using various news articles and label them on map.

1.2. Product Scope

Our project is targeted to make people aware about areas safety. The Admin
can view crime performance in mapping format and also this application will help
people to know information about crime of that particular place. It is more helpful for
people who are new and going to shift their place so that they can easily know which
area is secure and which is in danger zone and user can easily get the crime place so
for new person it will be helpful to secure their life.

1.3. References
 https://www.tutorialspoint.com/artificial_intelligence/artificial_intelligence_natural_lang
uage_processing.htm
 https://spring.io/
 http://www.mysqltutorial.org/
 https://nlp.stanford.edu/

2. Overall Description

2.1. Product Perspective

Existing technologies in the market i.e. maps, shows only areas, food places,
ATMs, Banks, routes etc.
Keeping in mind these types of projects we developed “NLP BASED SAFE
CITY LABELLING USING INFORMATION EXTRACTION FROM E-
NEWSPAPERS” system for people, where they can find whether a particular area that
they are searching for is safe or not with respect to crime. This is done using various
NLP techniques for information extraction from news API’s.

2.2. Product Function

Users can view safe/unsafe areas.
Users can provide and view feedback.

4
2.3. User classes and characteristics
Admin:
This person will be able to see all the crime record which is registered.
This person can validate News as per level of crime and also can add, update
and delete crime records.

User:
User can view the area. He can give feedback; also can view safe and
unsafe areas.

2.4. Operating environment

Hardware platform:
o Processor: Above Pentium 4, with clock speed 2.0 GHz
o RAM: 1GB or more
o Hard Disk: Free disk space of above 1GB
Software platform:
o Front End: HTML, CSS, Bootstrap, Spring
o Back End: MySQL
Development Tools:
o Eclipse IDE and MySQL WorkBench

2.5. Designing and implementation constraints

Constraints:
o User interface is only in English. No other language option is available
o User can log-in only with his assigned user-name and password
Limited to HTTP/HTTPS

2.6. User Documentation

User documentation mainly comprises of Help menu of application. It
will give all the minute details about the project, if any user has any query
about any module or functionality, one can refer it and see how to operate the
application. This report is the complete documentation of our project. It gives
complete details about the project, its functionality, users, software used,
hardware requirement, environment and so on.

2.7. Assumptions and Dependencies

o Assumptions
o There is an active internet connection with the system
o The system has internet browser installed Users know the English language,
as the user interface will be provided in English.
o Dependencies
o There is a need of constant updating of database
o Active participation of users on feedback.

5
3. External Interface Requirements
3.1. User Interfaces
The main element is web-pages using HTML, Angular Material.like home
page of people, Admin will update crime record accordingly data will be persisted.
Based on these information and the feedback provided by people performance would
be evaluated in a mapping format.

3.2. Hardware Interfaces

In the hardware interface, the system interacts with hardware given the
processor is above P4 with clock speed of 2.0 GHz with 1 GB RAM and the Hard
Disk with 1 GB free space in the memory. In future enhancements, it can be made
responsive to be able to work with mobile devices as well.

3.3. Software Interfaces

In software interfaces, Spring is the back-end technology used along with

MySQL Database. The front-end technologies include HTML, CSS, Bootstrap,
Angular and Angular Material. Data will be communicated between these interfaces
accordingly.

3.4. Communication Interfaces

The main communication interface for interacting with the System will be the
web Browser.

4. System Features

4.1. Description

This system will help people to ask. This system will help user to see the area.
This software also aims at carrying out an analysis of the crime in area that help user
to check the area before moving to that place.

4.2. Functional Requirements

4.2.1. Map Including Crime Records

The system should maintain a log of crimes.
The system will help us to view the map with safe and unsafe
areas with colour labelling.
Thus, using this system, we will be able to label which are
unsafe with crime records.

4.2.2. Forum
The system will allow people to give feedback.
The system will allow people to view the reviews of others.

6
5. Performance Requirements
The system should store all the database records of each area, crime and user
feedback properly and the application should be available for use 24*7 through the
server. Also, the application should be user friendly with a proper user interface
which makes it easy for the user to understand.

5.1. Safety Requirements

Areas will be shown in different colour shades on the basis of crime level in
that area. In case any user access to this system he/she can easily view the area and
can add additional feedback.

5.2. Security Requirements

All data of the area should be protected for privacy using some constraints
required in the database or the application. Feedback regarding user should be carried
out properly. Only admin will have access rights to the area data according to the need
for E.g.: -level of crime and feedback from user etc. The database should be protected
from attacks and unauthorized access. The interface should be protected from attacks.

5.3. Software Quality Attributes

5.3.1. Availability
The system should run on a variety of operating systems that support
the JavaScript language. The system should run on a variety of hardware.

5.3.2. Accessibility
The software will be accessible to allusers who want to shift Mumbai.

5.3.3. Compatibility
The software will be compatible with multiple platforms.

5.3.4. Durability
The software will be tested for working with multiple users.

5.3.5. Effectiveness
The software will be made to handle operations effectively.

5.3.6. Maintainability
The system should be easy to maintain. There should be a clear separation
between the interface and the business logic code. There should be a clear separation
between the data access objects that map the database and the business logic code.

7
6. Other Requirements

6.1. Appendix A:Glossary

o SRS: Software Requirement Specification

o GUI: Graphical User Interface
o P4: Pentium 4
o SQL: Structured Query Language
o HTML: Hyper Text Markup Language
o CSS: Cascading Style Sheet

6.2. Appendix B:Analysis Models

6.2.1. Use Case Diagram

8
6.2.2. Activity Diagram(User)

9
6.2.3. Activity Diagram(Admin)

6.2.4. Sequence Diagram(Admin)

10
6.2.5. Sequence Diagram(User)

6.2.6. Class Diagram

11