Top Banner
MEGHNAD SAHA INSTITUTE OF TECHNOLOGY E-Cops Software Requirements Specification Team Sparkz Sparkz Team Members Arunima De Neethi Sen Gatha Bhowal Project Guide: Mom Banerjee
44
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Final srs

MEGHNAD SAHA INSTITUTE OF TECHNOLOGY

E-Cops Software Requirements Specification

Team

SparkzSparkz

Team Members

Arunima DeNeethi Sen

Gatha Bhowal

Project Guide:

Mom Banerjee

Page 2: Final srs

Contents1)Introduction:....................................................................................................................11.1) Purpose: ........................................................................................................................11.2) Scope: ...........................................................................................................................11.3) Abbreviations:...............................................................................................................21.4)References: ....................................................................................................................31.5)Technologies: ................................................................................................................31.6)Overview........................................................................................................................42)OverallDescription:.........................................................................................................................42.1) Product Perspective: .....................................................................................................42.2) Software Interface:........................................................................................................52.3) Hardware Interface: ......................................................................................................52.4) Communication Interface:.............................................................................................62.5) User Characteristics:......................................................................................................62.6) Constraints: ...................................................................................................................63) Use-Case Model Survey:.................................................................................................73.1) Administrator.........:.......................................................................................................83.2) Police Officer: ...............................................................................................................83.3)Citizen: ...........................................................................................................................93.4)Magistrate:......................................................................................................................104) SpecificRequirements:....................................................................................................................104.1) Use-Case Reports:........................................................................................................105)Entity Relationship Diagram:.......................................................................................376)Tables And Attributes:..................................................................................................387)Context Level Diagram:................................................................................................398)Database Description:...................................................................................................409)Conclusion:....................................................................................................................43

Page 3: Final srs

1)Introduction:1.1)Purpose:To deliver next generation police and law enforcement reporting tools,and setting up intelligence platformsthat agencies use to take incoming incident reports,lessen live employee resources and allow these enforcement agencies to reallocate resources to much needed community areas

1.2)Scope:

*Administrator should be able to create/edit a virtual

police station which represents a real police station as a first time setup.

*Appointing of police officers to a particular police station which is present in a specific zone or to a specific district as a first time setup,he should be transferable at later time.

*Police station should have areas of control which can be

modified at later times.

*Police station has several departments like Law and

Order,Women Protection,Cyber crime,Traffic and control,CBI,etc.

*When a complaint is made it undergoes various processes like FIR,Charge Sheet,Property Seizure,court disposal etc all these activities are performed by a Police station.

*Traffic and Control has important part where the Traffic

inspector would be filing a charge sheet from a mobile or PDA.

*Maintaining the criminal information state wise/area

wise/age wise is mandatory. 1

Page 4: Final srs

*Sharing of case details with Police station in other states

is needed.

*Communication between officers is mandatory through forum,chat,polls.

*The magistrate should be able to apply for various

licenses like Arms,loud speaker,Hotel/Lodge,browsing center, mass meeting etc, and the officer should be able to approve/reject which will be notified to the applicant via SMS and Mail.

*Secured registration of citizens is needed where they

need to provide proof of citizenship,which will be cross checked by the police officer of that area.

1.3)Abbreviations:*HTML: Hypertext Markup Language is a markup language used

to design static web pages.

*EJB: Enterprise Java Beans.

*J2EE: Java 2 Enterprise Edition is a programming platform— part of the Java Platform-for developing and running distributed multitier architecture Java applications,based largely on modular software components running on an application server.

*DB2: DB2 Database is the database management system that delivers a flexible and cost effective database platform to build robust on demand business applications.

*WAS: Web sphere application server is an application server that runs business applications and supports the J2EE and web services standards.

2

Page 5: Final srs

*WSAD: Web sphere studio application developer is a toolkit which is designed for the creation of more complex projects, providing fully dynamic web application utilizing EJB’s . This consist of EJB tools,CMP ,data mapping tools & a universal test client that is designed to aid testing of EJB’s.

*HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server.

*HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).

*TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP.

1.4) References:* IEEE SRS Format

* Problem Definition (Provided by IBM)

* CT Arrington. Enterprise Java with UML. OMG Press.

1.5) Technologies:* J2EE: Application Architecture

* DB2: Database

* WSAD: Development Tool

* WAS: Web Server

* Rational: Design Tool

* IBM Lotus Symphony

3

Page 6: Final srs

1.6) Overview: SRS will include two sections:

* Overall Description will describe major components of the system 2 interconnection and external interfaces.

*Specific Requirements will describe the functions of actors, their role in the system an constraints.

2) Overall Description:Describe the general factors that affect the product and itsrequirements.2.1)Product Perspective:

4

First Tier:Web Clients

Third Tier(DBMS):Database Cluster(s)

Client Browsers

SQL Server

DB2 Database

Internet

Database Cluster

Second Tier: Server Side Web Applications

Other Database

Database Connectivity

Application ServerWeb Server

Page 7: Final srs

* The web pages (XHTML/JSP) are present to provide the userinterface on client side. Communication between client and server isprovided through HTTP/HTTPS protocols.

* The Client Software is to provide the user interface on system userclient side and for this TCP/IP protocols are used.

* On the server side web server is for EJB and database server is forstoring the information.

2.2) Software Interface:Client on Internet: Web Browser, Operating System (any)Client on Intranet: Client Software, Web Browser, Operating System

(any)Web Server: WAS, Operating System (any)Data Base Server: DB2, Operating System (any)Development End: WSAD (J2EE, Java, Java Bean, Servlets, XML),

DB2, OS (Windows), Web Server.Software Requirement Specification:IBM Lotus Symphony

2.3)Hardware Interface:

Client SideProcessor RAM Disk Space

InternetExplorer

6.0

Intel Core Duo 4GB 500GB

Server SideWeb sphereapplication

serverV5.0

Intel Core Duo 4GB 500GB

5

Page 8: Final srs

2.4) Communication Interface:* Client on Internet will be using HTTP/HTTPS protocol.

* Client on Intranet will be using TCP/IP protocol.

2.5)User Characteristics:Every user should be comfortable of working with computer and net browsing. He must have basic knowledge of English too.

2.6) Constraints:* GUI is only in English.

* Login and password is used for identification of citizen and there isno facility for non-members.

* This system is working for single server.

* There is no maintainability of back up so availability will get effected.

* Limited to HTTP/HTTPS.

6

Page 9: Final srs

3.USE CASE MODEL SURVEY3.USE CASE MODEL SURVEY

Communicate with Magistrate

Takes Complaints

Appoint Detective

Appoint Police Officer

Maintains Criminal Information

Manage SystemCommunicate Police Officer Administratorwith P.S

View LogsGrant/Denylicenses View all details

Checks citizenship proof

Register

Lodge complains Citizen

Apply for post of Police/Detective

View own details

Apply for license

7

Page 10: Final srs

Magistrate View case details

Grant/Deny arrest warrant

USE CASE DIAGRAM

3.1)Administrator: Responsible for managing system, appointingpolice officer and view logs.

*Manage System: The Administrator will create different roles. System users will be created and will be assigned to different roles. More than one task can be granted or revoked from the system users.

*Appoint Police Officer: Citizens can apply for postions of police officer or detective. The Administrator will check the eligibility of the citizen and will either grant or deny.

*View Logs:Responsible for checking the logs of different system users for auditing and maintaining integrity of the system.

*View all details:View all records of the system users and case details.

3.2)Police Officer:Responsible for communicating with magistrate, taking complaints,appointing detective,maintaining criminal information,communicating with other police stations,granting license,checking for proof of citizenship.

8

Page 11: Final srs

*Communicating with Magistrate:Police Officer will submit charge sheet to the Magistrate.

*Takes Complaints:Police Officer will accept complaints from registered citizen.

*Appoints Detectives:If required police officer will contact detective for certain cases.

*Maintains Criminal Information:Maintains criminal information in a log.

*Grant or Deny License:Police Officer checks for eligibility of the citizen and grants or denies him license.

*Checks for proof of citizenship:Checks whether the identification of the citizen is authentic or not.

*Communication with other Police Stations:Share the case details with Police Officers of other zones.

*View all details:Police Officers will view details of all cases under him.

3.3)Citizen:Citizen will register,view own details,lodge complaints,apply for license and positions of police or detective.

*Register:Citizen will have to fill up a form to become a registered citizen.

*Apply for Post of Police or Detective:Will have to fill up a application form for a particular post.

*View Own Details:Citizen will enter his own username and password and view details.

*Lodge Complaints:Authentic user can only complain.

*Apply for License:Will fill up a form and wait for reply.9

Page 12: Final srs

3.4)Magistrate:Magistrate will view case details and grant or deny warrant.

*View Case Details:Can view all the case details under him.

*Grant or Deny arrest warrant:Review the case details and give appropriate judgement.

4.SPECIFIC REQUIREMENT:4.SPECIFIC REQUIREMENT:

USE CASE REPORTS:->Administrator: Responsible for managing system, appointingpolice officer and view logs.

*Manage System: The Administrator will create different roles. System users will be created and will be assigned to different roles. More than one task can be granted or revoked from the system users.

*Appoint Police Officer: Citizens can apply for postions of police officer or detective. The Administrator will check the eligibility of the citizen and will either grant or deny.

*View Logs:Responsible for checking the logs of different system users for auditing and maintaining integrity of the system.

*View all details:View all records of the system users and case details.

10

Page 13: Final srs

MANAGE SYSTEM USERS

<<include>>View System Users

<<include>> Create System Users

Manage System Users <<include>>

Update Details of Users

View SystemUsers

->Name of use case: View System UsersDescription: View the list of system users in a role and view thedetails of roles, tasks and permissions assigned to a system user.Preconditions:

* Administrator is already logged in.

* System users have already been created and assigned some roles, tasks and permissions.

11

Select type of System User

Details of roles,tasks and permissions of users

List of system users which are assigned

selected roles

Page 14: Final srs

Normal flow of events:* The system user or a role will be selected.

* Query will be submitted.

* Relevant output will be displayed (If system user is selected then roles, tasks and permissions assigned to one will be displayed and if role is selected then list of system users assigned to that role will be displayed).

Alternate flow of events: None.

Post Condition: None.

Create System User

DuplicateU ID

->Name of use case: Create System Users.

Description: To create system users (Giving them a login name,password and assign roles, tasks and permissions to them).

12

Enter User ID & password

User Created

Page 15: Final srs

Preconditions: Administrator is already logged in. Normal flow of events:

* New Login name, password, details, roles, tasks and permissions will be entered.

* Save the details.

Alternate flow of events:* A message appears for duplicate login name.

* The administrator has to fill the details again.

Post condition: A login id is generated with its details.

Update Details

->Name of use case: Update details of Users

Description: To update the details of system users (assigning orrevoking roles, tasks and permissions).

Preconditions:* Administrator is already logged in.

13

Ask for selecting system user

Updation in role,task and permission

Page 16: Final srs

* System Users have already been created.

Normal flow of events:* Select the user name.

* Assign or Revoke the roles, tasks and permissions.

Post Condition: None

Appoint Police Officer

<<extends>>

<<extends>> <<include>>

Appoint Police Officer <<include>>

14

Check Eligibility

Issue Tranfer

Assign Zone/Post

Grant Promotion

Page 17: Final srs

Check Eligibility

Illegal

Failed

->Name of Use Case:Check Eligibility.

->Description:To check the eligibility of the citizen who have appliedfor the post of police officer or detective.

->Precondition:User have already filled up the form.

->Normal Flow of Events:*The application form is viewed.

*Identification proof is checked.

*Qualification is checked.

15

View Form

I D Proof Check

Qualification Check

Successfull Appoint

Page 18: Final srs

*Appoint successfully.

->Alternate Flow of Events:*If identification proof is illegal,then view next form.

*If qualification is not satisfactory,then view next form.

->Post Condition:None.

Issue Transfer

->Name of Use Case:Issue transfer.

->Description:Issuing tranfer of Police Officer to required zones afterchecking the eligibility.

->Precondition:Candidate is already a Police Officer.

16

View Present Location

Zone where P.S recquired

Issue Transfer

Page 19: Final srs

->Normal Flow of Events:*Present location of the Police Officer is previewed.

*The zone where Police Officer is required is checked.

*Transfer is issued.

->Alternate Flow of Events:None.

->Post Condition:None.

No vacancy

No Vacancy

Higher

Not Eligible

->Name of Use Case:Grant Promotion.

->Description:If suitably qualified then promotion is granted .

->Precondition:Candidate is already a Police Officer.

17

Grant PromotionVacency Check

Count the no of vacency

View Status of vac

View Status of police

Eligibility Check

Vacancy Check Grant

Page 20: Final srs

->Normal Flow of Events:*Vacancy is checked.

*Count the no. of vacancy and status.

*Current status of Police Officer is viewed.

*Eligibility of Police Officer is checked.

*Vacancy is checked again.

*Promotion is granted.

->Alternate Flow of Events:*If no vacancy in particular department,then another department is checked.

*If eligibility of the Police Officer is higher than the required eligibility,then another Police Officer's status is viewed.

*If position is already filled up,then another post is checked.

->Post Condition:None.

18

Page 21: Final srs

->Name of Use Case:View Logs.

->Description:To view the activities of the system users.

->Precondition:*Administrator is already logged in.

*System users have already been created.

->Normal Flow of Events:*Select user name.

*Select date.

*Logs of system users to be selected.

->Alternate Flow of Events:None.

->Post Condition:None.

19

View Logs

Select User Name

Select Date

Logs of System Users of Selected Dates

Page 22: Final srs

Police Officer:Responsible for communicating with magistrate, taking complaints,appointing detective,maintaining criminal information,communicating with other police stations,granting license,checking for proof of citizenship.

*Communicating with Magistrate:Police Officer will submit charge sheet to the Magistrate.

*Takes Complaints:Police Officer will accept complaints from registered citizen.

*Appoints Detectives:If required police officer will contact detective for certain cases.

*Maintains Criminal Information:Maintains criminal information in a log

*Grant or Deny License:Police Officer checks for eligibility of the citizen and grants or denies him license.

*Checks for proof of citizenship:Checks whether the identification of the citizen is authentic or not.

*Communication with other Police Stations:Share the case details with Police Officers of other zones.

*View all details:Police Officers will view details of all cases under him.

20

Page 23: Final srs

TakesComplaints

Not Authentic

->Name of Use Case:Takes Complaint.

->Description:Police Officer can only takes complaint from aregistered citizen.

->Precondition:User must be registered.

->Normal Flow of Events:*Authentication of the citizen is checked.

*Takes general dairy from the user.

*Registers FIR.

*Charge Sheet is prepared for court disposal.21

Check for authentication

Logdes G.D

Register FIR

Prepares Charge Sheet

Page 24: Final srs

->Alternate Flow of Events:If user is not authorized,then anothercomplaint is viewed.

->Post Condition:None. Criminal Information

Maintains Nominal Role

<<extends>>

Maintains Case Register<<extends>>

Maintain Criminal Information

<<extends>><<extends>>

Maintains Release Diary

Interview Request

22

Page 25: Final srs

Grant or Deny License

Check Citizenship Proof

Grant/Deny License Check Case Register

Check Eligibility

Check CitizenshipProof

Not

Eligible

23

View ID Proof

Apply for license

Page 26: Final srs

->Name of Use Case:Checks citizenship proof.

->Description:Citizenship identification is checked.

->Precondition:User has applied for license.

->Normal Flow of Events:*View identification of the user.

*Apply for license.

->Alternate Flow of Events:If identification proof is illegal,then viewnext application.

->Post Condition:None.

Check Case Register

Case

Issues

->Name of Use Case:Check case register.

->Description:Case register of the citizen is checked.24

View Case Register

Apply for license

Page 27: Final srs

->Precondition:User has applied for license.

->Normal Flow of Events:*View case register.

*Apply for license.

->Alternate Flow of Events:If there is an existing case,then view other application.

->Post Condition:None.

Check Eligibility

Not

Eligible

25

Fulfil Criteria

Grant license

Page 28: Final srs

->Name of Use Case:Check Eligibility.

->Description:Eligibility of Citizen is checked.

->Precondition:User has applied for license.

->Normal Flow of Events:*View criteria.

*Grant license.

->Alternate Flow of Events:If criteria is not fullfiled,then view another application.

->Post Condition:None.

Contact Detective

<<extend>> Contact Detective

<<extends>>Appoint Detective

Share Details

26

Page 29: Final srs

->Name of Use Case:Contact Detective.

->Description:Police Officer contacts detectives for certain cases.

->Precondition:Detective is already registered.

->Normal Flow of Events:*Department of the case is selected.

*Check whether the detective is available or not.

*Appointed successfully.

27

Contact Detective

Select Department

Check Availability

Not Available

Appoints Successfully

Page 30: Final srs

->Alternate Flow of Events:If the detective is not available then otherdetective is considered.

->Post Condition:None.

29

Communicate With Other Police Station

Set Up Forum/Polls<<extends>>

Communicate With Police Station <<extends>>

Share Criminal Information/Case Details

Check For Citizen Proof

View Citizen ID

Check For Authentication

Not Authentic

Grant Access

Page 31: Final srs

->Name of Use Case:Check for citizenship proof for being an user.

->Description:Citizenship identification is checked.

->Precondition:Citizen has submitted the Identification proof.

->Normal Flow of Events:*View citizen's id.

*Check for authentication.

*Grant access.

->Alternate Flow of Events:If authentication is invalid then viewanother id.

->Post Condition:None.

Citizen:Citizen will register,view own details,lodge complaints,applyfor license and positions of police or detective.

*Register:Citizen will have to fill up a form to become a registered citizen.

*Apply for Post of Police or Detective:Will have to fill up a application form for a particular post.

*View Own Details:Citizen will enter his own username and password and view details.

*Lodge Complaints:Authentic user can only complain.

*Apply for License:Will fill up a form and wait for reply.

30

Page 32: Final srs

->Name of Use Case: Registration for authentic user.

->Description:Citizen has to provide authentic citizenship proof to bean user.

->Precondition:Citizen has already filled up a form.

->Normal Flow of Events:*The citizen must fill up the form.

*Citizenship proof is provided.

*Registration successful.

->Alternate Flow of Events:If authentication is invalid then viewanother form.

->Post Condition:None.

31

Registration

Not Authentic

Registration Successful

Citizenship Proof

Fill Up Form

Page 33: Final srs

->Name of Use Case: View own details.

->Description:Citizen can view his own profile.

->Precondition:Citizen has already a system user.

->Normal Flow of Events:*The citizen must give correct u-id & password.

*Citizen can now view his profile

->Alternate Flow of Events:If authentication is invalid then re-enteru-id & password.

->Post Condition:None. 32

Invalid

View details

Give U-id,password

View Own Details

Page 34: Final srs

->Name of Use Case: Complaint Lodge.

->Description:Citizen can lodge complaints.

->Precondition:Citizen is already an authentic user.

->Normal Flow of Events:

*The citizen must give u-id & password.

*Select department.

*General diary & FIR is lodged.

->Alternate Flow of Events:If authentication is invalid then re-enter.

->Post Condition:None.33

Give u_id & password

Lodge Complaint

Select Department

Invalid

Lodge GD

Register FIR

Page 35: Final srs

->Name of Use Case: Apply for license.

->Description:Citizen can apply for license for various purposes.

->Precondition:Citizen is already an authentic user.

->Normal Flow of Events:*The citizen must give u-id & password.

*Apply for license.

*Give citizenship-proof.

*Checks case register.

*License approved. 34

Apply for license

Give U-ID & password

Invalid

Apply for license

Give citizenship proof

Invalid

License Approved

Page 36: Final srs

->Alternate Flow of Events:*If authentication is invalid then re-enter.

*If there is a current case against user then view another form.

->Post Condition:None.

->Name of Use Case: Apply for post.

->Description:Citizen can apply for a job as a police officer ordetective.

->Precondition:None.

->Normal Flow of Events:

*The citizen will apply for job.

*Select department.35

Apply for post

Apply for post

Select Department

Fill Form

Wait for reply

Page 37: Final srs

*Fill up form.

* Wait for reply.

->Alternate Flow of Events:None.

->Post Condition:None.

36

Page 38: Final srs

5)

37

E-R DIAGRAM

DetectiveAdministrator

1 M

appoints consults

1M

Magistrate Citizen1 M

NMPoliceorders Complains to

AssistantCommisioner

StaffPolice

Commissioner DeputyCommissioner

Officer in Charge

Page 39: Final srs

6) Tables & Attributes

,

38

DetectiveAgency

D-idPasswordDept-id

P-idP.S. No

Citizen

C-idPasswordC-name

SexAddress

Contact noEmail id

ProfessionNationality

ReligionV-id no

Pan card noPassport no

Complaint-no

PoliceInformation

P-idPassword

DesignationP.S. NoDept-id

DOJ

Magistrate

M-idDistrictCourtC-noP-id

Complaint

Complaint-noC typeP-idD-id

Suspect name

License

L-idL typeC-id

CyberCafe

Cafe-idCafe nameLocation

Administrator

Ad-idPasswordAd name

User name

Hotel

H-idH nameLocation

Page 40: Final srs

7)

39

CONTEXT LEVEL DIAGRAM(LEVEL 0 DFD)

CITIZEN POLICE

Appoints detectives

Takes complaint

Zone/post assigned

Applies for recruitment

App

oint

s offi

cers

Che

cks e

ligib

ility

ADMINISTRATOR

Requests for Registration

Gives membershipE_COPS SYSTEMLodges complaint

Acknowledgement for complaint

Page 41: Final srs

8) DATABASE DESCRIPTION

Citizen

Attribute Name Type ConstraintC-id Varchar(30) Primary key(Not null)Password Varchar(30) Not nullC-name Varchar(30) Not nullSex Varchar(10) Not nullAddress Varchar(50) Not nullContact no Number(20) Not nullEmail-id Varchar(30) Not nullProfession Varchar(20) Not nullNationality Varchar(20) Not nullReligion Varchar(20) Not nullV-id no Varchar(20) Not nullPassport no Varchar(20) Not null Pan card no Varchar(40) Not nullComplaint-no Varchar(30) Foreign Key(Not Null)

40

Page 42: Final srs

PoliceInformation

Attribute Name Type ConstraintP-id Varchar(30) Primary key(Not null)Password Varchar(30) Not nullDesignation Varchar(30) Not nullP.S. no Varchar(30) Not nullDept-id Varchar(30) Not nullDOJ Date Not null

DetectiveAgency

Attribute Name Type ConstraintD-id Varchar(30) Primary key(Not null)Password Varchar(30) Not nullDept-id Varchar(30) Not nullP-id Varchar(30) Foreign Key(Not Null)P.S. no Varchar(30) Not null

Complaint

Attribute Name Type ConstraintComplaint-no Varchar(30) Primary key(Not null)C-type Varchar(30) Not nullP-id Varchar(30) Foreign Key(Not Null)D-id Varchar(30) Foreign Key(Not Nul)Suspect name Varchar(30) Not null

41

Page 43: Final srs

License

Attribute Name Type ConstraintL-id Varchar(30) Primary key(Not null)L type Varchar(30) Not nullC-id Varchar(30) Foreign Key(Not Null)

Magistrate Attribute Name Type Constraint

M-id Varchar(30) Primary key(Not null)District Varchar(30) Not nullCourt Varchar(30) Not nullC-no Varchar(30) Foreign Key(Not Null)P-id Varchar(30) Foreign Key(Not Null)

HotelAttribute Name Type Constraint

H-id Varchar(30) Primary key(Not null)H name Varchar(30) Not nullLocation Varchar(30) Not null

Administrator

Attribute Name Type ConstraintAd-id Varchar(30) Primary key(Not null)Password Varchar(30) Not nullAd name Varchar(30) Not nullUser name Varchar(30) Not null

42

Page 44: Final srs

CyberCafe

Attribute Name Type ConstraintCafe-id Varchar(30) Primary key(Not null)Cafe name Varchar(30) Not nullLocation Varchar(30) Not null

9)Conclusion: This Project can be improved later. There somescopes for improvement. Such as:

*Integration of E-cops with Prison Management and Court is an immediate requirement.

*Chat using XMPP provides added feature.

*Biometric Authentication(Face detection or Fingerprint).

*Administrator should have a java client end rather than web end.

*Use of JMS for communication between other state database.

*Predicting criminal faces in various conditions using digital image processing via face points would be additional features.

43