qwertyuiopasdfghjklzxcvbnmqwerty
uiopasdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfghjklzx
Software Requirement Specification
DAILY ROUTINE MANAGEMENT OF FSL
cvbnmqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopasdfg
hjklzxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopasdfg
hjklzxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopasdfg
hjklzxcvbnmrtyuiopasdfghjklzxcvbn
mqwertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyuiopas
for
Prepared By
Deepanshu
01016404814
M.tech(CSE) 1st sem
USICT,GGSIPU
Table of Contents
1.
2.
Introduction ................................................................................................................................................. 4
1.1
Purpose ................................................................................................................................................ 4
1.2
Scope .................................................................................................................................................... 4
1.3
Definitions, Acronyms and abbreviation ............................................................................................. 4
1.4
References ........................................................................................................................................... 5
1.5
Overview .............................................................................................................................................. 5
The Overall Description................................................................................................................................ 5
2.1
3.
Product Perspective ............................................................................................................................. 5
2.1.1
System Interfaces ......................................................................................................................... 5
2.1.2
Interfaces ..................................................................................................................................... 5
2.1.3
Hardware Interfaces .................................................................................................................... 6
2.1.4
Software Interfaces ...................................................................................................................... 6
2.1.5
Communication Interfaces ........................................................................................................... 6
2.1.6
Memory Constraints ................................................................................................................... 6
2.1.7
Operations.................................................................................................................................... 6
2.1.8
Site Adaptation Requirement ...................................................................................................... 6
2.2
Product Functions ................................................................................................................................ 6
2.3
User Characteristics ............................................................................................................................. 7
2.4
Constraints ........................................................................................................................................... 7
2.5
Assumption and dependencies ............................................................................................................ 7
2.6
Apportioning of Requirements ............................................................................................................ 8
Specific Requirements ................................................................................................................................. 8
3.1
External Interfaces ............................................................................................................................... 8
3.1.1
User Interface............................................................................................................................... 8
3.1.2
Hardware Interface ................................................................................................................... 15
3.1.3
Software Interface..................................................................................................................... 15
3.1.4
Communication Interface ......................................................................................................... 15
3.2
Functions ............................................................................................................................................ 15
3.2.1
Administrative Functions ........................................................................................................... 15
3.2.2
Receipt Clerk Functions.............................................................................................................. 16
3.2.3
DD,SA,SSA,SO Functions............................................................................................................ 16
3.2.4
SA,JLA Functions......................................................................................................................... 16
3.3
Performance requirements................................................................................................................ 16
3.3.1
Response Time ........................................................................................................................... 16
[Daily Routine management of FSL]
Page 2
4.
3.3.2
Administrator Response............................................................................................................. 16
3.3.3
Throughput ................................................................................................................................ 16
3.4
Logical database requirements .......................................................................................................... 16
3.5
Design Constraints ............................................................................................................................. 17
3.6
Software System attributes............................................................................................................... 17
3.6.1
Usability...................................................................................................................................... 17
3.6.2
Reliability ................................................................................................................................... 17
3.6.3
Availability .................................................................................................................................. 17
3.6.4
Security ...................................................................................................................................... 17
3.6.5
Maintainability ........................................................................................................................... 17
3.6.6
Portability ................................................................................................................................... 17
3.7
Organization of specific requirements............................................................................................... 17
3.8
Additional comments ......................................................................................................................... 17
Annexures .................................................................................................................................................. 18
4.1 List Of Common Messages ....................................................................................................................... 18
[Daily Routine management of FSL]
Page 3
1. Introduction
This document aims at defining the overall software requirements for “Daily Routine
Management of FSL”. Efforts have been made to define the requirements exhaustively and
accurately. The final product will be having only features/functionalities mentioned in this
document and assumptions for any additional functionality/feature should not be made by any
of the parties involved in developing/testing/implementing using this product. In case it is
required to have some additional features, a formal change request will need to be raised and
subsequently a new release of this document and /or product will be produced.
1.1
Purpose
The specification document describes the capabilities that will be produced by the software
application ‘“Daily Routine Management of FSL”. It also states the various required constraints
by which the system will abide. The intended audiences for this document are the development
team, testing team and end users of the product.
1.2
Scope
This system will capture the registration process of exhibits comes for examination in the FSL.
Apart from maintaining the details first user will have to do day begin to register the cases for
that day. Day End functionality is provided to close the registration for a day, after day end user
will not be able to make registration for that day. Here user can also set the
reminders/summons received against a case in FSL. If a case is rejected by the section expert
than the user can mark that case a RIO (Return In Original).
1.3
Definitions, Acronyms and abbreviation
S No.
Abbreviation
Description
1
DD
Deputy Director
2
DC
Dispatch Clerk
3
FSL
Forensic Science Laboratory
4
IO
Investigating Officer
5
JD
Joint Director
6
JLA
Junior Laboratory Assistant
7
RC
Receipt Clerk
8
SA
Scientific Assistant
9
SO
Scientific Officer
10
SSA
Senior Scientific Assistant
11
SHO
Station House Officer
[Daily Routine management of FSL]
Page 4
12
CJM
Chief Judicial Magistrate
13
DJ
District Judge
14
CMO
Chief Medical Officer
15
SP
Superintendent of Police
1.4
i.
ii.
1.5
References
IEEE Recommended Practice for Software Requirement Specification- IEEE Std. 830-1993
Software Engineering(3rd ed.) by K.K. Aggarwal and Yogesh Singh
Overview
The SRS will provide a detailed description of the Daily Routine Management of FSL. This
document will provide the outline of the requirements, overview of the characteristics and
constraints of the system.
The SRS will provide the general factors that affect the product and its requirements. It provides
the background for those requirements. The items such as product perspective, product
function, user characteristics, constraints, assumptions and dependencies and requirements
subsets are described in this section.
The SRS contains all the software requirements mentioned in detail sufficient enough to enable
designers to design the system to satisfy the requirements and testers to test if the system
satisfies those requirements.
2. The Overall Description
2.1
Product Perspective
The application is web based and connected with database.
Front end Client
Web Application
(with data
entry/update/dele
te, view and
reporting facility
2.1.1
Backend
Database
System Interfaces
None
2.1.2
Interfaces
The application will have a user friendly and menu based interfaces. Following Screens will be
provided:
[Daily Routine management of FSL]
Page 5
i.
ii.
iii.
iv.
v.
vi.
2.1.3
Screen to begin the day for making receipts of case materials.
Screen to register a new case material received at FSL for examination.
Screen to search & view functionality for ‘Registered Case Materials’.
Screen to modify details of registered cases.
Screen to set reminder/summon comes against registered case.
Screen to make day end of already begin day
Hardware Interfaces
i.
Since the application must run over the internet, all the hardware shall require to
connect internet will be hardware interface for the system. As for e.g. Modem, WAN –
LAN, Ethernet Cross-Cable.
ii.
Best viewed at : 1024x768, IE 7, Firefox 3.6.3
iii.
Support for printer to print reports
2.1.4
i.
ii.
iii.
iv.
2.1.5
Software Interfaces
Sql Server 2008
Dot net Framework 4
Visual Studio 2010 to develop these application
SQL server business intelligence Studio for SSRS reports
Communication Interfaces
None
2.1.6
Memory Constraints
At least 1 GB RAM and 500 GB of hard disk will be required to run this application
2.1.7
Operations
This product release will not cover any automated housekeeping aspects of the
database. The DBA at the client site will be responsible for manually deleting old / nonrequired data. Database backup and recovery will also have to be handled by DBA.
2.1.8
Site Adaptation Requirement
The terminals at client site will have to support the hardware and software interfaces
specified in above sections.
2.2
Product Functions
This system will allow only to authorized users with specific roles like RC,SA,SSA,JLA admin
etc. Depending on the user’s role. He/she will be able to access only specific modules of the
system.
A summary of the major functions that the system will perform:
i.
A login facility for enabling only authorized access to the system.
ii.
Authorized user can start the day by going to Receipt->Day Begin.
If user wants o start the day for another date, he/she may do so by first doing day end of
previous day.
[Daily Routine management of FSL]
Page 6
iii.
User with privilege of registration can Register a new case for the date whose day has
already begun. If there is no day open, then it will redirect to home page with a prompt
message of “Do day begin first”.
User can search the registered case of only his/her lab. If user is from specific division,
then he/she may search case for their respective divisions only.
User can View and modify the case which have already registered , if and only if he has a
permission to do so.
User can set reminder/summon against registered case.
User can at last perform day end operation.
iv.
v.
vi.
vii.
2.3
User Characteristics
User of the system should be equipped with complete domain knowledge as well as flow
knowledge of FSL. The system has well designed user interfaces. In house training will be
provided to the staff for using the system. Yet the staff should at least be able to use general
purpose applications of the computers and should have basic knowledge about computer
2.4
Constraints
The information of all the users must be stored in a database that is accessible by the Online
Daily Routine Management of FSL.
 The Lab information security system must be compatible with the Internet applications.
 The users access the System from any computer that has Internet browsing capabilities and
an Internet connection.
 The users must have their correct usernames and passwords and roles to enter into the
Online System.
 Pages specific to their roles are only visible to the users.
 Hierarchy is also implemented in the system. i.e. The user having role above the another
may see the records of their lower level role users. Vice versa is not possible.
 User of lab i.e. Director of lab can manage the records of his/her lab and their respective
divisions only.
2.5




Assumption and dependencies
The users have sufficient knowledge of computers.
The Lab computer should have Internet connection and Internet server capabilities.
The users know the English/Hindi language, as the user interface will be provided in both
languages.
The product can access the database of LAB
[Daily Routine management of FSL]
Page 7
2.6
Apportioning of Requirements
Not Required
3. Specific Requirements
3.1
External Interfaces
3.1.1
User Interface


The Following screens will be provided
Login Screen
This will be the first screen that will be displayed. It will allow user to access different
screens based upon user’s role. Various fields on this screen will be

User ID: Alphanumeric of length upto 10 characters

Password: Alpha numeric of length upto 10 characters.

Role: Dropdown is given having different roles
Day Begin Screen
This screen provides the functionality to begin the day for making receipts of case materials.
Data field:
S. No.
Data Field Type
Mandatory
(Entry/Display/Selection) (Yes/No/NA)
Field
Length
Permissible
Data
1
Day Begin
Date
NA
DD/MM/YYYY

Selection
Yes
Registration of New Case
This screen provides the functionality to register a new case material received at FSL for
examination.
Data field:
S.
No.
Data Field
Type
Mandatory
Field
(Entry/Display/Selection) (Yes/No/NA) Length
Permissible
Data
1
Lab Receipt
Number
Display
Yes
NA
System
generated
Number
2
Lab Code
Display
Yes
NA
From Lab Master
3
Division
Name
Selection
Yes
NA
From Division
Master
[Daily Routine management of FSL]
Page 8
4
Division Case
Number
Display
Yes
NA
System
generated
alphanumeric,
special character
5
Forwarding
Authority
Selection
Yes
NA
From Forwarding
Authority Master
6
Forwarding
District
Selection
Yes
NA
From District
Master
7
Forwarding
Area
Entry
No
50
alphanumeric,
special character
8
Forwarding
Letter
Number
Entry
Yes
20
alphanumeric,
special character
9
Forwarding
Date
Selection
Yes
NA
DD/MM/YYYY
10
District
Selection
Yes
NA
From District
Master
11
Police
Station
Selection
Yes
NA
FromPolice
Station Master
12
Crime
Number
Entry
Yes
10
numeric, special
character (/)
13
FIR Date
Selection
No
NA
DD/MM/YYYY
14
Accused
Name
Entry
No
50
Character
15
Messenger
Name
Selection
No
50
From
Appointment
Lookup
16
Receipt Date
Display
Yes
NA
DD/MM/YYYY
Case Material Details
17
Container
Type
Selection
Yes
NA
From Container
Type Master
18
Exhibit Type
Selection
Yes
NA
From Exhibit
Type Master
19
Quantity
Entry
Yes
15
Alphanumeric
[Daily Routine management of FSL]
Page 9
Act & Section Details
20
Act
Selection
Yes
NA
From Act Master
21
Section
Selection
Yes
NA
From Section
Master
Medical Information
22
Medical
Officer
Name
Entry
No
50
Characters
23
Letter
Number
Entry
No
20
alphanumeric,
special character
24
Letter Date
Selection
No
NA
DD/MM/YYYY
25
Dead Person
Name
Entry
No
50
Characters
26
Hospital
Name
Entry
No
50
alphanumeric,
special character
27
Remarks
Entry
No
500
alphanumeric,
special character
Entry
No
30
alphanumeric,
special character
Linking Info
28
Link To

Search and view Registered Cases
This screen provides for search & view functionality for ‘Registered Case Materials’.
Data field:
S.
No.
Data Field
Type
(Entry/Display/Selection)
Mandatory
Field
(Yes/No/NA) Length
Permissible
Data
Searching Criteria
1
District
Name
Selection
No
NA
From District
Master
2
Police
Station
Selection
No
NA
From Police
Station Master
3
Crime
Number
Entry
No
5
Numeric
[Daily Routine management of FSL]
Page 10
From
4
Crime
Number To
Entry
No
5
Numeric
5
Crime Year
Entry
No
4
Numeric
6
Accused
Name
Entry
No
50
Characters
7
Lab Code
Selection
No
NA
From Lab Master
8
Lab Receipt
Number
Entry
No
20
Numeric
9
Division
Name
Selection
No
NA
From Division
Master
10
Division
Case
Number
Entry
No
20
Alphanumeric
11
Receipt
Date From
Selection
No
NA
DD/MM/YYYY
12
Receipt
Date To
Selection
No
NA
DD/MM/YYYY
Special
Characters
Registered Cases (Search Result)
13
S. No.
Display
NA
NA
NA
14
Division
Case
Number
Display
NA
NA
NA
15
District
Display
NA
NA
NA
16
Police
Station
Display
NA
NA
NA
17
Accused
Name
Display
NA
NA
NA
18
Nature of
Exhibits
Display
NA
NA
NA
19
Receipt
Date
Display
NA
NA
NA
20
Lab Receipt
Display
NA
NA
NA
[Daily Routine management of FSL]
Page 11
Number
21
Lab Code

Display
NA
NA
NA
Modify Registered Cases
This screen provides the functionality to modify registered cases.
Data field:
S.
No.
Data Field
Type
Mandatory
(Entry/Display/Selection) (Yes/No/NA)
Field
Length
Permissible
Data
1
Lab Receipt Display
Number
Yes
NA
System
generated
Number
2
Lab Code
Display
Yes
NA
From Lab Master
3
Division
Name
Display
Yes
NA
From Division
Master
4
Division
Case
Number
Display
Yes
NA
System
generated
alphanumeric,
special character
5
Forwarding
Authority
Selection
Yes
NA
From Forwarding
Authority Master
6
Forwarding
District
Selection
Yes
NA
From District
Master
7
Forwarding
Area
Entry
No
50
alphanumeric,
special character
8
Forwarding
Letter
Number
Entry
Yes
20
alphanumeric,
special character
9
Forwarding
Date
Selection
Yes
NA
DD/MM/YYYY
10
District
Selection
Yes
NA
From District
Master
11
Police
Station
Selection
Yes
NA
From Police
Station Master
12
Crime
Entry
Yes
10
alphanumeric,
[Daily Routine management of FSL]
Page 12
Number
special character
13
FIR Date
Selection
No
NA
DD/MM/YYYY
14
Accused
Name
Entry
No
50
Character
15
Messenger
Name
Selection
No
50
From
Appointment
Lookup
16
Date of
Receipt
Display
Yes
NA
DD/MM/YYYY
Case Material Details
17
Container
Type
Selection
Yes
NA
From Container
Type Master
18
Exhibit
Type
Selection
Yes
NA
From Exhibit
Type Master
19
Quantity
Entry
Yes
15
Numeric
Act & Section Details
20
Act
Selection
Yes
NA
From Act Master
21
Section
Selection
Yes
NA
From Section
Master
Medical Information
22
Medical
Officer
Name
Entry
No
50
Character
23
Letter
Number
Entry
No
20
alphanumeric,
special character
24
Letter Date
Selection
No
NA
DD/MM/YYYY
25
Dead
Person
Name
Entry
No
50
Characters
26
Hospital
Name
Entry
No
50
alphanumeric,
special character
27
Remarks
Entry
No
500
alphanumeric,
special character
[Daily Routine management of FSL]
Page 13
Linking Info
28
Link To

Entry
No
30
alphanumeric,
special character
Set Reminder/Summon against Registered Cases
This screen provides the functionality to set reminder/summon comes against registered case.
Data field:
S. No.
Data Field
Type
Mandatory
Field
(Entry/Display/Selection) (Yes/No/NA) Length
Permissible
Data
Case Details
1
Crime
Number
Display
NA
NA
NA
2
Division
Case
Number
Display
NA
NA
NA
3
Lab Receipt
Number
Display
NA
NA
NA
4
Division
Name
Display
NA
NA
NA
5
Accused
Name
Display
NA
NA
NA
6
State
Display
NA
NA
NA
7
District
Display
NA
NA
NA
8
Police
Station
Display
NA
NA
NA
9
Date of
Receiving
of Case
Display
NA
NA
NA
10
Date of
Dispatch
Display
NA
NA
NA
Reminder/Summon Details
[Daily Routine management of FSL]
Page 14
11
Type
Selection
Yes
NA
Reminder
Summon
12
Serial
Number
Display
Yes
3
Auto generated
Alphanumeric,
special character
13
Forwarding
Authority
Selection
Yes
NA
From Forwarding
Master
14
Letter
Number
Entry
Yes
20
Alphanumeric,
special character
15
Letter Date
Selection
Yes
NA
DD/MM/YYYY
16
Messenger
Name
Entry
No
50
Characters
17
Receipt
Date
Selection
Yes
NA
DD/MM/YYYY

Day End
This screen provides the functionality to make day end of already begin day.
Data field:
S. No. Data Field
Type
Mandatory
(Entry/Display/Selection) (Yes/No/NA)
Field
Length
Permissible
Data
1
Display
NA
DD/MM/YYYY
Day End For
3.1.2
Yes
Hardware Interface
As stated in section 2.1.3
3.1.3
Software Interface
As stated in section 2.1.4
3.1.4
Communication Interface
None
3.2
Functions
3.2.1
Administrative Functions
Administrator can perform various functions.
[Daily Routine management of FSL]
Page 15

He can add data in master tables like Container Type, Divisions, Labs, Exhibit Type,
Forwarding Authority

He can add new users to the system

He can perform all the duties as shown in Use Case diagram.
3.2.2
Receipt Clerk Functions

3.2.3
3.2.4
He can perform all the activities related to data entry by his/her login as shown in
Use Case Diagram.
DD,SA,SSA,SO Functions

He can Search the records i.e. registered cases in the lab.

Search is possible based on the hierarchy of their role i.e. Upper level can see
records of lower level role. Vice versa is not possible.

He can only view the records. He doesn’t have right of modification.
SA,JLA Functions
Users of this role can only set reminder/Summon against registered case.
3.3
3.3.1
Performance requirements
Response Time
The System page should be able to be display within a minute. The information is
refreshed every two minutes.
3.3.2
Administrator Response
The system shall take as less time as possible to provide service to the administrator or
the FSL LAB.
3.3.3
Throughput
The number of transactions is directly dependent on the number of users, the users may be the
administrator, Receipt Clerk of the lab ,Director of the lab etc. who use the system.
3.4
Logical database requirements
The following information will be places in a database

User Info

Day Log Details: Labcode, DayBeginDate, DayCloseDate, IsDayClosed, Date

Case Registration Details: LabReceiptNo,LabCode,DivisionName.DivisionCaseNo etc.

Case Material Details: ContainerTypeCode,Exhibit Type Code,Quantity

Case Act Section: Act, Section

Case Reminder Summon: Type,SrNo,Forwarding Authority,LetterNo,ReceiptDate,Letter Date
: User name, User id, User password, User role
[Daily Routine management of FSL]
Page 16
3.5
Design Constraints
None
3.6
Software System attributes
3.6.1
Usability


3.6.2
The system shall allow the users to access the system from the computers that are
installed with application in lab using a user common interface.
The system is user friendly and self-explanatory.
Reliability
The system has to be very reliable due to the importance of data and the damages
incorrect or incomplete data can do. The system will be developed and tested in such a way
that chances of failure are negligible. Even if the system fails, the system will be recovered
back up within an hour or less .The system shall provide 100% access reliability.
3.6.3
Availability
The system is available 100% for the user and is used 24 hrs a day and 365 days a year. The
system shall be operational 24 hours a day and 7 days a week.
3.6.4
Security
The application will be password protected. Users will have to enter correct username,
password and role in order to access the application.
3.6.5
Maintainability
The application will be designed in a maintainable manner. It will be easy to incorporate
requirements in the individual modules .
3.6.6
Portability
The application will be easily portable on any server with a dot net capability.
3.7
Organization of specific requirements
None
3.8
Additional comments
None
[Daily Routine management of FSL]
Page 17
4. Annexures
4.1 List Of Common Messages
List of Common Messages
Message
ID
Message Description
Select
MSG01
Incorrect username or password, please try again
MSG02
Incorrect service request / complaint / FIR number. Please try again
MSG03
The following fields xx,xx,xx are mandatory
MSG04
Service Request Number XX has been registered
MSG05
Temporary Service Request Number XX has been registered. If you do not
submit within 48 hrs., the service request will not be taken up for approval
MSG06
All data will be lost, do you wish to continue?
MSG07
Service Request Number XX has been approved
MSG08
Service Request Number XX has been rejected
MSG09
Assigned to <Name of Officer In charge>
MSG10
Please select from the dropdown menu
MSG11
Application forwarded to <Officer Name> for decision
MSG12
Service Request Number XX has been saved
MSG13
Please fill all mandatory fields
MSG14
Please enter e mail id in the following format user name @ Domain name
MSG15
Please enter a numeric value. Country code should start with ‘+’
MSG16
Content cannot exceed 300 characters
MSG17
Date cannot be a future date
MSG18
Please enter data in a proper format. Only alphabets a-z, numbers 0-9 and
special characters( ‘ )are allowed
MSG19
Please enter data in a proper format. Only alphabets a-z, numbers 0-9 and
[Daily Routine management of FSL]
Page 18
special characters ‘/’, ‘-‘ and ’,’ are allowed
MSG20
Please enter a numeric value
MSG21
Content can’t exceed 500 words
MSG22
Content can’t exceed 1000 words
MSG23
Please enter data in proper format. Only alphabets a-z, numbers 0-9 are
allowed
MSG24
Please enter data in the proper format. Only alphabets a-z, numbers 0-9, and
special characters ‘-‘, ‘/’ are allowed
MSG25
Please enter data in the proper format. Only alphabets a-z are allowed
MSG26
Contents cannot exceed 150 words
MSG27
Data entered in <Name of the Field> is incorrect. Please enter the correct data
MSG28
All data fields would be reset to Blank
MSG29
You have made three failed login attempts. Please try again after one hour or
contact your administrator for the correct username and/or password
MSG30
You are already logged in. Please use the existing session or wait for twenty
minutes to login again
MSG31
Please change your password
MSG32
The new password should be different from the previous five passwords
entered
MSG33
Password should be as per password policy
MSG34
Security question answered incorrectly, please try again
MSG35
You have exceeded the maximum number of tries. Your account has been
locked. Please contact the administrator
MSG36
Please select / enter data for at least one field, other than the mandatory field
Crime & Criminal Tracking Network & Systems System Requirement
Specifications
MSG37
Enquiry Report has been successfully saved
MSG38
Please enter a valid complaint number
MSG39
Complaints have been successfully delinked
MSG40
Complaints have been successfully linked
[Daily Routine management of FSL]
Page 19
MSG41
Age should be greater than or equal to 18 years
MSG42
Reassigned enquiry officer cannot be the current enquiry officer
MSG43
Date of assigning cannot be a back date
MSG44
Enquiry report has been submitted successfully for Service request ID XXXX
MSG45
Enquiry report by ‘with Name of corresponding Police station has been
submitted successfully for Service request ID XXXX
MSG46
Date of birth should not be greater than current date
MSG47
Enquiry officer has been assigned/reassigned successfully for the ‘Service
request ID XXXX
MSG48
Enquiry report by ACP/DSB has been submitted successfully for Service request
ID XXXX
MSG49
Registration certificate issued
MSG50
Registration certificate rejected
MSG51
Details Doesn’t exist
MSG52
Passport date cannot be the future date
MSG53
Date of arrival cannot be the future date
MSG54
Service Requests number XXXX doesn’t exist!
MSG55
The FIR number doesn’t exist
MSG56
Please install the necessary software <name of software>
MSG57
Password should be 8 characters or more
MSG58
Password should be combination of a-z, 0-9 & Special characters or more
MSG59
Password and Confirm Password should be same for user creation
MSG60
User created successfully, Please login using your username and password
MSG61
ID is already in use. Please select another user id
MSG62
User details are modified successfully
MSG63
Your Password has been reset successfully
MSG64
Information successfully submitted
MSG65
Please upload the correct document
MSG66
Complaint successfully assigned
[Daily Routine management of FSL]
Page 20
MSG67
Date of leaving cannot be a future date
MSG68
Age cannot be a future date
MSG69
Reassigned enquiry officer cannot be the current enquiry officer
MSG70
Recommendation has been successfully submitted for service request ID XXXX
MSG71
Your Passport verification is received for police verification. You can track the
request though <service request Id>
MSG72
‘Service requests linked’(for approved) and ‘Linking of service requests
rejected’ (for rejected)
MSG73
Do you want to link another complaint?
MSG74
The case crime number doesn’t exist
MSG75
Please enter a valid case crime number
MSG76
Document uploaded successfully.
MSG77
Document modified successfully.
MSG78
No Result Found.
MSG79
Replacing document will result to deletion of existing document. Are You sure
you want to continue?
MSG80
Are you sure you want to delete it?
MSG81
Are you sure you want to modify it?
MSG82
Document for <file Name> is already uploaded. To modify document, Kindly
access Admin -> Modify Document.
MSG83
Select Duty Type First.
MSG84
Select Sub Duty Type First.
MSG85
Record saved successfully.
MSG86
Record modified successfully.
[Daily Routine management of FSL]
Page 21