FUNCTIONAL REQUIREMENTS

The DMT system has four types of user i.e. staff, disaster management
administrator, system administrator, and organization user. Staff is trusted
staff or volunteer of disaster management team, can report incident, provide
updates over incidents from disaster site as well as status of resources and
request for resources. EQSIM provides the seismic update to the main
dynamic server.
Adding to these functionalities disaster management admin can allocate
resources, deallocate assigned resources and request for external resources.
System admin is responsible for adding organizations (Govt. or private) and
other users to the system. Organization users are those representatives of
organization who will allocate, deallocate resources requested for their
organization. Apart from these four user guest user can also report incidents
to the system.

TESTING
1. User login
There are two type of user in our system, volunteer are the disaster
management staff and trusted volunteers, help in reporting incident and
updates. When user login on the system, it will check for user id and
password for that user type, it is correct it will open the home page of user.
Test Plan
Requirement Addressed: To verify the staff or volunteer details.
Test Case 1: User Login
Test case 1: Login

Priority (H, L):

High

Test Objective: Ensure that the login details entered by staff or volunteer on
the registration form are valid or invalid.
Test Description: The existing user of the DMT will try to login in to server system
with proper user ID and password.
Requirements Verified: Yes
Test Setup/Pre-Conditions: Receiver (Disaster response admin ) should be in
connection accept state
Actions

Expected Results

The user will click on the login button.

Pass: Yes

Conditions pass: No

valid/invalid
Fail: No

Problems / Issues: NIL

Notes: Successfully Executed
Test Cases
Value
Entered

Interface ID

Data Field

1) DMT_1

Username

pjohn

2) DMT_1

Password

Pjohn@5

3) DMT_1

Username

@pj-hn

4) DMT_1

Password

!7856@

5) DMT_1

Username

#6790

6) DMT_1

Password

Ag+&

7) DMT_1

Username

QP56-

8) DMT_1

Password

%7*()

9) DMT_1

Username

10) DMT_1

Password

Expected Results:
Test 1 to 2 is valid and remaining all is rejected.
Actual Results:
Test 1 to 2 is accepted. Test 3,4,5,6,7,8,9 and 10 were rejected with error message.

2. Registered user home

Registered user can report an incident, and then a form will take that
information about the incident. If the incident form is new within 100 m
radius, then system will take these information as update, and compare and
ask for the information to be updated or not(Dynamic server does this).
When a new incident is reported or an update on previous information has
been made, then it will take us to the incident homepage. If the user is
system administrator who will manage the system then he can add
organizations and users to the system using admin interface.
Test Plan

Requirement Addressed: To verify that the report provided by registered

user is new or existing.
Test Case 2: Incident Report

Test case 2: Incident report

Priority (H, L):

High

Test Objective: To ensure that the incident report is new and updated.
Test Description: The registered user will fill the incident details in the form and that
report will be updated if new.
Requirements Verified: Yes
Test Setup/Pre-Conditions: Receiver (Dynamic Server ) should be in connection
Actions

Expected Results

The user will click on the submit button.

Pass: Yes

updated/existing

Conditions pass: No

Fail: No

Problems / Issues: NIL

Notes: Successfully Executed

Test Cases
Interface ID

Data Field

Value Entered

1) DMT_2

Id

5012

2) DMT_2

location

Ghandi nagar

3) DMT_2

Affected people

1052

4) DMT_2

severity

High/low/medium

5) DMT_2

injured

102

6) DMT_2

dead

51

7) DMT_2

timestamp

20/06/2016
12:02:02

8) DMT_2

city

jaipur

9) DMT_2

state

10) DMT_2

Incident type

11) DMT_2

Id

50_12

12) DMT_2

location

Ghandi,;nagar

13) DMT_2

Affected people

1052+_-

14) DMT_2

severity

15) DMT_2

injured

658][*9

16) DMT_2

dead

12$#/.,

17) DMT_2

timestamp

20-06-2016/
(12:02:02)

18) DMT_2

city

jaip@#$%!ur

19) DMT_2

state

%^&arath

20) DMT_2

Incident type

Earthquak123e

Gujarath
Earthquake

Guj

Expected Results:
Test 1 to 10 is valid and remaining all is rejected.
Actual Results:
Test 1 to 10 is accepted. Test 11, 12, 13,14,15,16,17,18,19 and 20 were rejected
with error message.

3. Incident homepage

Incident homepage will show the guidelines for which shows the task need to
perform, authorities to inform and resource required for type of incident
reported. If a new type of incident is reported then a new template could be
created by or generic template could be used for that incident type and then
entry can be made in our database for that new type of disaster. Request
resource will show the resource list and the amount of resource estimated
from the information and severity of the incident. If a new type of resource is
not in the system or not suggested for that incident then we can add new
resource for the request.
Test Plan
Requirement Addressed: To verify that the incident template exists if not
create new and request for resource is made if new then it is added in the
list.
Test Case 3: Incident homepage

Test case 3: Incident report

Priority (H, L):

High

Test Objective: To ensure that the incident report is new and updated.
Test Description: The report will send the incident to request template and request
resource
Requirements Verified: Yes
Test Setup/Pre-Conditions: Receiver (Dynamic Server ) should be in connection
Actions

Expected Results

Once the incident is updated

Pass: Yes

request template & request

resource/ add template & add
new resource
Conditions pass: No

Fail: No

Problems / Issues: NIL

Notes: Successfully Executed

Test Cases
Interface ID

Data Field

Value Entered

1) DMT_3

Incident Id

5012

2) DMT_3

Template id

EQ1

3) DMT_3

Incident id

5012

4) DMT_3

Resource id

EQ_1

5) DMT_3

Incident Id

10*/2

6) DMT_3

Template id

5!@#$1

7) DMT_3

Incident id

&-*/HG_:

8) DMT_3

Resource id

3213uytwd

Expected Results:
Test 1 to 4 is valid and remaining all is rejected.
Actual Results:
Test 1 to 4 is accepted. Test 5, 6, 7 and 8 were rejected with error message.

4. Request and allocate resource

Request for resources is made from this page. Now, from here we can do
allocation request, deallocation request if the resources are constrained or
very far. We can also ask for the external resource through web service of
that resource provider.
If user type is disaster management admin then, allocation of resources has
been done by allocate resource button. It will show all the allocation
requests, and deallocation requests. Disaster management admin can accept
the allocation request either fully or partially by changing the amount of
resource allocated.
Test Plan
Requirement Addressed: To request and allocate resources nearer, if far
request for other resources.
Test Case 4: Suggested resource request

Test case 4: resource allocation

Priority (H, L):

High

Test Objective: To ensure that the requested resource is allocated if not ask for

external.

Test Description: The system will send request to nearer server systems.
Requirements Verified: Yes
Test Setup/Pre-Conditions: Receiver (Dynamic Server ) should be in connection or
admin
Actions

Expected Results

Resources request is sent

Pass: Yes

allocate resource/ request

external resource
Conditions pass: No

Fail: No

Problems / Issues: NIL

Notes: Successfully Executed

Test Cases
Interface ID

Data Field

Value Entered

1) DMT_4

Resource name

Ambulance

2) DMT_4

Incident id

5012

3) DMT_4

timestamp

02-06-2016
02:06:05

4) DMT_4

Requested from

Ghandi nagar

5) DMT_4

location

jaipur

6) DMT_4

Resource type

EQ

7) DMT_4

Request id

8588

8) DMT_4

Resource id

EQ_1

9) DMT_4

Resource name

Qwe2323

10) DMT_4

Incident id

987-*/

11)DMT_4

timestamp

02_06/2016)
02:06:05

12) DMT_4

Requested from

Ghandi-+nagar

13) DMT_4

location

Jaipur!@#

14) DMT_4

Resource type

EQ*/

15) DMT_4

Request id

858&*(8

16) DMT_4

Resource id

EQ<>?:_1

Expected Results:
Test 1 to 8 is valid and remaining all is rejected.
Actual Results:
Test 1 to 8 is accepted. Test 9, 10, 11, 12, 13, 14, 15, 16, 17 and 18 were rejected
with error message.

5. Organization login
Organization user will login using the organization user name and password.
If it is valid then it will take to the registered organization homepage. Now,
resource requests could be allocated, and already allocated resource could
be released form here using web service call to the actual system of that
organization. We can also manage and update inventories through web
service call.
Test Plan
Requirement Addressed: To verify login details of external organizations
and allocate resources
Test Case 5: Login
Test case 5: external organization/govt. login

Priority (H, L):

High

Test Objective: To ensure that the login details are valid

Test Description: The details are entered and resources are allocated
Requirements Verified: Yes
Test Setup/Pre-Conditions: Receiver (Dynamic Server ) should be in connection

Actions

Expected Results

User clicks on login button and allocates

resources

Pass: Yes

valid/ invalid
allocate resources/release
resource

Conditions pass: No

Fail: No

Problems / Issues: NIL

Notes: Successfully Executed

Test Cases
Interface ID

Data Field

1) DMT_5

Organization name

NGO

2) DMT_5

Resource type

Fire engine

3) DMT_5

location

Hareram street

4) DMT_5

description

non-government
organization

5) DMT_5

Contact

978945647

6) DMT_5

email id

emailed@gmail.c
om

7) DMT_5

resource cost

8000

8) DMT_5

Organization name

N21@GO

9) DMT_5

Resource type

Fire,, engine

10) DMT_5

location

Hareram-*street

11) DMT_5

description

non-government
organizatio9879n

12) DMT_5

Contact

978^&*()945647

13) DMT_5

email id

Emai>}led@gma
il.com

14) DMT_5

resource cost

80hf00

Expected Results:
Test 1 to 7 is valid and remaining all is rejected.

Value Entered

Actual Results:
Test 1 to 7 is accepted. Test 8, 9, 10 , 11, 12, 13 and 14 were rejected with error
message.