SRS_v1x

beigecakeUrban and Civil

Nov 16, 2013 (3 years and 10 months ago)

109 views



Middle East Technical University






Medi
-
Track

Software
Requirements Specification

Version 1.0




Supplier

Group Med

Semra
GÜLEÇ



40117

Kadriye
GÜÇLÜ

-

144341

Mesrure Işıl
ÖZTÜRK
-

108398

Mustafa Çağrı
TOROSLU
-

183629



Acquirer

Assoc. Prof. Halit OĞUZTÜZÜN


March
30
th
, 2012

Medi
-
Track

SRS

V1.0




2

Table of Contents


1.

Introduction

................................
................................
................................
..........

5

1.1

Purpose

................................
................................
................................
.........

5

1.2

Scope

................................
................................
................................
............

5

1.3

Definitions, acr
onyms, and abbreviations

................................
......................

5

1.4

References

................................
................................
................................
....

6

1.5

Evolution of SRS

................................
................................
...........................

6

1.6

Over
view

................................
................................
................................
.......

6

2.

Overall description

................................
................................
...............................

7

2.1

Product perspective

................................
................................
.......................

7

2.1.1

System Interfaces

................................
................................
...................

7

2.1.2

User Interfaces

................................
................................
........................

8

2.1.3

Ha
rdware Interfaces

................................
................................
................

8

2.1.4

Software Interfaces

................................
................................
.................

8

2.1.5

Communications Interfaces

................................
................................
.....

9

2.2

Product functions

................................
................................
...........................

9

2.3

User characteristics

................................
................................
.....................

11

2.4

Constraints

................................
................................
................................
..

11

2.5

Assumpti
ons and dependencies

................................
................................
..

11

2.6

Apportioning of requirements

................................
................................
......

11

3.

Specific requirements

................................
................................
.........................

11

3.1

Interface Requirements

................................
................................
...............

11

3.1.1

General Requirements

................................
................................
.............

11

3.1.2

Login Screen

................................
................................
............................

12

3.1.3

User Administration Screen

................................
................................
......

13

3.1.4

Equipment Administration Screen

................................
............................

15

3.1.5

Equipment History Query Screen

................................
.............................

16

3.1.6

Equipment History Replay Screen

................................
...........................

17

3.1.7

Equipment Tracking and Query Screen

................................
...................

18

3.2

Functional Requirements

................................
................................
.............

19

3.2.1

Login

................................
................................
................................
........

19

Medi
-
Track

SRS

V1.0




3

3.2.2

Create Use
r

................................
................................
..............................

20

3.2.3

Search User

................................
................................
.............................

20

3.2.4

Update User

................................
................................
.............................

21

3.2.5

Delete User

................................
................................
..............................

22

3.2.6

Create Equipment

................................
................................
....................

22

3.2.7

Search Equipment

................................
................................
....................

23

3.2.8

Update Equipment
................................
................................
....................

24

3.2.9

Delete Equipment

................................
................................
.....................

25

3.2.10

List Equipment History

................................
................................
..........

25

3.2.11

Track Equipment

................................
................................
...................

26

3.2.12

Find Single Equipment

................................
................................
..........

27

3.2.13

Find Equipment in a Category

................................
...............................

28

3.3

Non
-
Functional Requirements

................................
................................
.....

33

3.3.1

Security

................................
................................
................................
....

33

3.3.2

Performance

................................
................................
.............................

33

3.3.3

Usab
ility

................................
................................
................................
....

34

3.4

Logical Database Requirements
................................
................................
..

34





Medi
-
Track

SRS

V1.0




4

Table of Tables

Table 1 Abbreviations

................................
................................
................................
.

6

Table 2 References

................................
................................
................................
....

6

Table 3 Use cases

................................
................................
................................
....

10



Table of Figures

Figure 1 System Context Diagram

................................
................................
..............

7

Figure 2 Medi
-
Track Software Interfaces

................................
................................
....

9

Figure 3 Use Case Diagram

................................
................................
.....................

10

Figure 4 Login Screen

................................
................................
..............................

12

Figure 5 User Administration Screen

................................
................................
........

13

Figure 6 Deletion confirmation pop
-
up

................................
................................
......

13

Figure 7 Equipment Administration Screen

................................
.............................

15

Figure 8 Equipment History Query Screen

................................
...............................

16

Figure 9 Equipment History Replay Screen

................................
..............................

17

Figure 10 Equipment Tracking & Query Screen

................................
.......................

18

Figure 11 Sequence Diagram Part 1

................................
................................
........

29

Figure 12 Sequence Diagram Part 2

................................
................................
........

30

Figure 13 Sequence Diagram Part 3

................................
................................
........

31

Figure 14 Sequence Diagram Part 4

................................
................................
........

32

Figure 15 Class Diagram

................................
................................
..........................

33

Figure 16 ER Diagram

................................
................................
..............................

34




Medi
-
Track

SRS

V1.0




5

1.

Introduction

1.1

Purpose

The purpose of
this Software

Re
quirements Specification (SRS) d
ocument is to
d
efine, specify and examine the
software r
equirements of Medi
-
Track.


It
is

prepared:




As a reference for customer(s), visual and textual presentation of their needs
and expectations
from

the system.



As a refere
nce and

guide for the designer(s), by mapping the already identified
customer needs to technical needs.


1.2

Scope


Medi
-
Track application will be used to track critical portable medical
equipment

within the hospital by using a RFID tag embedded on them.

Medical
equipment

such as ventilators, defibrillators, ultrasounds, portable x
-
ray
machines in a hospital are quite mobile. They can be used wherever they are
needed at that time; emergency rooms, operating rooms, patient rooms. Because
of the mobility of such dev
ices, it is hard to track whereabouts of these devices
within the hospital.

Medi
-
track will keep information on all critical portable devices and provide ne
ar
real
-
time monitoring of these devices within hospital premises.

Application will be used by medi
cal staff through displays located in various
places of the hospital.

1.3

Definitions, acronyms, and abbreviations

Radio
-
frequency identification

(RFID):

W
ireless non
-
contact system that uses
radio
-
frequency

electromagnetic fields

to transfer data from a tag attached to an
object, for the purposes of automatic identification and tracking.

Real
-
time locating systems (RTLS):


Type of

local positioning system

that allow
to track and identify the location of objects in real time.

Database:

Organized collection of data stored in digital format which models the
real life information of an enterprise.



Entity
-
relationship (ER) Diagram:


An abstract and conceptual representation
used to model relational databases.


Unified Modeling
Language


(UML):

a standardized general
-
purpose

modeling
language

used
in
object
-
oriented

software engineering
.


Medi
-
Track

SRS

V1.0




6

Graphical User interface

(GUI):

type of
user
interface

that allows
users

to
interact

with electronic devices with

images rather than text commands.


Local Area Network (LAN):

C
omputer network

that interconnects computers in a
limited area such as a home, school, computer laboratory, o
r office building.


Desktop Application:

An application that runs stand alone in a computer; in
contrast with "Web
-
based application," which requires the Web browser to run.


MySQL:

A free relational database management system.



Abbreviation

Definition

SPMP

Software Project Management Plan

SRS

Software Requirements Specification

Table
1

Abbreviations

1.4

References


Index

Related Document

[SPMP]

Medi
-
Track
Software Project Management Plan

V1.0


Table
2

References

1.5

Evolution of SRS

This document is the first version of SRS. All versions of this document will be taken
under configuration control af
ter submission to the acquirer.
Any changes to this
document will be explained in this section.


1.6

Overview


This document has two more sections. Second section, “Overall Description”
section, gives an overview of the functionality of the product. Providing a full
description of the project, it lists all the functions performed by the system, describes
the info
rmal requirements and is used to establish a context for the technical
requirements specification for the next chapter.

The final chapter, “Specific Requirements” section is written primarily for the
designers and developers, and describes in technical

terms the details of the
Medi
-
Track

SRS

V1.0




7

functionality of the product. In this section both functional and non
-
functional
requirements are listed.



2.

Overall description


This section of the SRS describes all general factors of the product and its
requirements.

2.1


Product

perspective

Looking from general perspective
,

Medi
-
Track is going to interact with RTLS software
to get
current
location information of the equipment. There

are

two types of actors
who use the system: administrator and user. They will use the system throu
gh GUI.



Context
d
iagram is depicted below:


Figure
1

System Context Diagram


2.1.1

System Interfaces

Medi
-
Track is going to interact with RTLS software to get location information of the
equipment. RTLS system will provide equipment id, floor id and x,y coordinates of the
RTLS

Medi
-
Track

Current
e
quipment
location Info

GUI

Administrator

User

Medi
-
Track

SRS

V1.0




8

equipment to Medi
-
Track. Medi
-
Track will query this information from RTLS in every
5

seconds.

2.1.2

User Interfaces



Medi
-
Track should interact with its users by using GUI and all
screens

of the
system should follow a consistent theme and clear structure.



Errors should be minimized through the use of checkboxes, ra
dio
-
buttons, drop
-
down menus

by

reduc
ing

the amount of text input from user.



Error message should be located
next to

error input which clearly highlight
s

and
tell
s

user how to solve it.



Screen should have tool tips whenever necessary.

Requirements for user interfaces will be desc
ribed in section 3.1 of this
document.

2.1.3

Hardware Interfaces

M
edical equipment
will have
active
RFID tags attached to them.
RTLS system will
have readers which receive wireless signals from these tags to determine their
locations. RTLS will
calculate the coordinates of the medical equipment using
triangulation and send
current
location information to Medi
-
Track [SPMP]

.

Medi
-
Track
will
be a desktop application which
run
s

on a Windows server. Database
will be hosted on the same server.

Clients will access the application using Windows clients.
Client computer should
have TCP
/
IP LAN connection to the server.

2.1.4

Software Interfaces

Medi
-
Track application will run on a Microsoft Windows Server
2003 (or higher)
operating system. MySQL database

will be used as the database.


Application will use .NET Framework 3.5
.


Medi
-
Track

SRS

V1.0




9


Figure
2

Medi
-
Track Software Interfaces


2.1.5


Communications Interfaces

TCP
/
IP LAN network is necessary between server and clients.

2.2

Product functions


Produc
t functions are depicted as use case diagram

below:









Medi
-
Track

MySQL

Infrastructure (Microsoft .NET)

Operating System (Windows 2003
/XP)

Medi
-
Track

SRS

V1.0




10

Figure
3

Use Case Diagram


#

Actor

Use Case

1

Administrator / User

Login

2

Administrator

Create User

3

Administrator

Search User

4

Administrator

Update User

5

Administrator

Delete User

6

Administrator

Create Equipment

7

Administrator

Search Equipment

8

Administrator

Update Equipment

9

Administrator

Delete Equipment

10

Administrator

List equipment history

11

Administrator / User

Track

equipment

12

Administrator / User

Find single
equipment

13

Administrator / User

Find
equipment
in a category

Table
3

Use cases

Medi
-
Track

SRS

V1.0




11

2.3

User characteristics

Users of the system are chief of operations and medical staff of the hospital. Users
should be familiar with standard computer usage.

2.4

Constraints



User interface
shall

be in Turkish.



Error messages, tooltips
and help

shall be in Turkish.

2.5

Assumptions and dependencies



RFID system’s signals are not interfered by other equipment in the hospital
.



Hospital floor plans will be supplied in electronic format.



Every

equipment has a unique identification.



Correct functioning of

Medi
-
Track highly

depends on

accuracy of equipment
location information retrieved from RTLS system.

A properly setup
RTLS
system operates with
1
-
2 meters accuracy
.

2.6

Apportioning of requirements

There are no requirements that may be delayed until future
versions of the system.

3.

Specific requirements

3.1

Interface Requirements

3.1.1

General Requirements

3.1.1.1

Every screen shall have
X

on
its
upper right corner
. It
will

be
used to exit
from each screen.



3.1.1.2

Lists shall have scroll bars (up
-
down, left
-
right) when content of the list
does not fit
in

the list area.

3.1.1.3

Every screen shall have current date

and time

information.


Medi
-
Track

SRS

V1.0




12

3.1.2


Login Screen



Figure
4

Logi
n Screen

3.1.2.1

There
shall

be userid and password fields on the screen.
Both fields
shall
be

required and
shall be editable.


3.1.2.2

If userid and/or password
is

invalid, system
shall

display error message
and does not allow the user to log in.


3.1.2.3

If userid and password are both valid,
system

shall display

the
appropriate menu
depending on the u
ser

type
.


3.1.2.4

There
shall

be 4 tabs in
administrator
menu:



User administration screen




Equipment administration screen




Equipment history query screen



Equipment tracking and query screen


3.1.2.5

For administrators, “
User administration screen


shall

be active at login.


3.1.2.6

For u
ser
s,
only
the
“Equipment tracking and query screen”

shall

be
display
ed
.






Kullanıcı Kodu
:

Şifre:

X

GİRİŞ

Medi
-
Track

SRS

V1.0




13

3.1.3

User Administration Screen



Kullanıcı Kodu

Adı

Soyadı


1111

Ahmet

Yılmaz

1122

Mehmet

Türk


1133

Canan

Yıldırım


1234

Zeynep

Kılıç

Kullanıcı Kodu

1

Adı


Soyadı


Şifre


Kullanıcı Tipi


Figure
5

User
Administration

Screen




Kayıdı silmek istediğinizden emin misiniz?

Figure
6

Deletion confirmation pop
-
up

3.1.3.1

Screen consists of two areas: Data entry area and list

area
.
Fields
in
data
entry
area
shall be

editable
.

List area
shall be

read
-
only.


3.1.3.2

When administrator enters
userid

and
press
es “BUL” button, system
shall display matching use
r information in the list area.

BUL

EKLE

SİL

䟜乃E䱌i

u

SİL

İPTAL

u

Medi
-
Track

SRS

V1.0




14


3.1.3.3

If userid is left blank,

system shall
display all

users in

the list area

in
ascending userid order.


3.1.3.4

If
part of userid is given,
system shall
display all

users whose

userid
begin
s
with those characters

in the list area
in ascending userid order.


3.1.3.5

If there are no matching userid found, system shall inform the us
er with a

warning

message.


3.1.3.6

When administrator
select
s

one user fr
om the list and double
-
clicks it,
system shall highlight the s
elected line.
All information of the
selected
user shall be displayed in the relative fields

at data entry area
.


3.1.3.7

When
administrator

change
s

some information
of the user
and hit
s


GÜNCELLE” button, system shall update the information in the
database.


3.1.3.8

Userid
shall not

be
updated
.


3.1.3.9

When administrator
select
s

one user from the list and hit “SİL
” button,
s
ystem shall ask for
confirmation

(
Figure
6
)
. If
administrator

accepts
delet
ion,
u
ser information shall be deleted from the database.



3.1.3.10

In order to add a new user,
administrator

enter
s

all fields

in data entry
area

and

press
es

“EKLE” button.

Userid type can be either A (for
administrator) or U (user).
New user

shall be created in the database.

If
userid is already exists, system shall inform the
administrator
with an
error message.







Medi
-
Track

SRS

V1.0




15


3.1.4

Equipment Administration Screen












Cihaz Kodu

V1

Cihaz Grubu


Aktif/Pasif Kodu


Açıklama



Cihaz
Kodu

Cihaz G
rubu


V101

Solunum Cihazı

V102

Solunum Cihazı


V110

Solunum Cihazı


Figure
7

Equipment Administration Screen


3.1.4.1

Screen consists of two areas: Data entry area and list area.
Fields in data
entry area
shall be

editable. List area
shall be

read
-
only.


3.1.4.2

Administrator

may

enter
equipment id or equipment group

in related

field
and press “BUL” button. Minimum 1 character of
the field

should

be
given. All matching
equipment

information shall be displayed in the list
area in ascending
equipment
id

order. If there are no matching
equipment

found, system shall inform the user
with an

error message.


3.1.4.3

When administrator selects one equipment from the list and double
-
clicks
it, system shall highlight the selected line. All information of the selected
equipment shall be displayed in the relative fields at data entry area.


3.1.4.4

When ad
ministrator changes some information of the equipment and hits
“GÜNCELLE” button, system shall update the information in the
database.


BUL

EKLE

SİL

u

䟜乃E䱌i

Medi
-
Track

SRS

V1.0




16


3.1.4.5

Equipment
id
shall not

be updated.


3.1.4.6

When administrator selects one equipment from the list and hit “SİL”
button, system
shall ask for confirmation

(
Figure
6
)
. If administrator
accepts deletion, equipment information shall be deleted from the
database.


3.1.4.7

In order to add
a
new

equipment
,
administrator
will

enter all fields in data
entry area and press “EKLE” button. New
equipment

shall be created in
the database. If
equipmentid

already exists, system shall inform the
administrator
with an error message.



3.1.5

Equipment
History Query Screen






Cihaz Kodu




Başlangıç Tarih/ Zaman




Bitiş

Tarih/ Zaman




Zaman

Konum


19.03.2012 08:00:00

Kat 1, 1, 1.5

19.03.2012 08:00:05

Kat 1, 1, 5.0


19.03.2012 08:00:10

Kat 1, 1, 15.0


19.03.2012 08:00:20

Kat 2, 1, 13.0


19.03.2012 08:00:25

Kat 2, 1, 10.0


Figure
8

Equipment History Query Screen

3.1.5.1

Screen consists of two areas: Data entry area and list are
a. In data entry
area equipment
id, beginning and end date fields
shall be

required

for
searching the equipment history
, other fields
shall be

optional. List area
shall be

read
-
only.


3.1.5.2

The whole equipment
id shall be given.


BUL

X

OYNAT

Medi
-
Track

SRS

V1.0




17

3.1.5.3

Date shall be in DD.MM.YYYY format or selected from the calendar next
to field.


3.1.5.4

Time shall be given in HH:MM:SS format. If time values are not given,
system shall take 00:00:01 for the beginning time and 23:59:59 for the
end time.


3.1.5.5

When b
eginning date/time
is

greater

than end date/time
, s
ystem shall
inform the administrator with an e
rror message.


3.1.5.6

System shall list all equipment history information in the list in ascending
date and time order.
When user

press
es “OYNAT” button,

system shall
replay the equipment history for only selected equipment in
the
“Equipment History Replay
Screen”





3.1.6


Equipment History Replay Screen


Figure
9

Equipment History Replay Screen


3.1.6.1

Selected e
quipment
id shall be displayed on the screen.


3.1.6.2

History date and time shall be displayed on the screen and refreshed on
every
record
read from history
.

Medi
-
Track

SRS

V1.0




18


3.1.6.3

System shall display new location of the equipment
refreshed on every
record read from history.


3.1.6.4

System shall inform the user when end of history is reached.



3.1.7

Equipment Tracking and Query Screen

Figure
10

Equipm
ent Tracking &
Query

Screen

3.1.7.1

All hospital floor plan
shall

be displayed in different tabs.



3.1.7.2

System shall enable the u
ser
s to
switch between
floor plans

by pressing
on the
related tab.


3.1.7.3

All equipment

on that floor
shall

be displayed with predefined
icon

and
unique
equipment
id

next to it.


3.1.7.4

Only acti
ve equipment

shall

be displayed on the screen.


3.1.7.5

New positions of equipments
shall

be read from RTLS system in every 5
seconds and new positions
shall

be refreshed on the screen.



3.1.7.6

To locate a single equipment, user
will select

the equipment

from the
drop
-
down

menu and press


BUL
” button

next to device list
.

System
shall

switch to the floor
tab
the equipment is at and
shall

blink the icon of the
equi
p
ment to ease recognition.


Medi
-
Track

SRS

V1.0




19

3.1.7.7

To

locate a category of equipments
, user
will

select

the equipment

category from

the drop
-
down menu an
d press


BUL
” button

category list
.

System
shall

list all

equipment

on that category
.


3.1.7.8

User
will

select
a single

equipment from the list and double
-
click it.
System
shall switch

to the floor tab the equipment is at and shall blink the
icon of the equi
p
ment to ease recognition
.


3.1.7.9

System shall display a warning pop
-
up when
equipment

goes out of the
hospital.


3.2

Functional Requirements

3.2.1

Login


Use case

Login

Actors:

Administrator
, User

Description:

Actors of the system
login to the
system

Related User
Interface

Login

Pre
-
conditions:

None

Post
-
conditions:

None

Priority:

High

Frequency of Use:

Frequently

Basic Flow:

1.

User enter
s

userid
and password

2.

System displays main menu

depending on user type


Alternative Flows:

None

Error Flows

1.

User enters wrong userid

a.

Systems sends an error message that wrong
userid is entered

b.

S
ystem does not allow the users to
access the
system

2.

User enters wrong
pasword

a.

Systems sends an error message that password
id invalid

Medi
-
Track

SRS

V1.0




20

b.

S
ystem does not allow the users to access the
system



3.2.2

Create User

Use case

Create User

Actors:

Administrator


Description:

Create a new user

Related
User
Interface

User administration

Pre
-
conditions:

Administrator

should be logged in

Post
-
conditions:

New user should be created

Priority:

Medium

Frequency of Use:

Medium

Basic Flow:

1.

Administrator
enters userid, firstname, lastname,
password and

user

type

information

2.

Administrator
presses “
EKLE
” button

3.

New user information is stored in database

Alternative Flows:

None

Error Flows

1.

User
already exists


a.

Systems sends an error message that
userid
exists

b.

System does not allow
creation of new user



3.2.3

Search User

Use case

Search

User

Actors:

Administrator

Description:

Search for u
ser
s

Related User
Interface

User administration

Pre
-
conditions:

Administrator
should be logged in

Medi
-
Track

SRS

V1.0




21

Post
-
conditions:

None

Priority:

High

Frequency of Use:

Frequently

Basic Flow:

1.

Administrator
enters userid


2.

Administrator
presses “BUL” button



A汬 u獥牳r 獡瑩tfy楮i 獥a牣栠捯nd楴içn a牥r 汩獴ed 楮i 汩獴s
a牥r⁩ a獣snd楮i⁵獥r楤iç牤rr

A汴l牮r瑩te⁆汯w猺

乯ke

b牲ç爠䙬çws



qÜe牥⁡牥ç⁵獥牳⁳at楳iy楮i⁳ a牣栠捯nd楴楯n



py獴sms

獥nd猠an⁥牲ç爠re獳sge 瑨a琠nç⁳ cÜ
u獥物d⁥x楳瑳



3.2.4

Update User

Use case

Update User

Actors:

Administrator

Description:

Update user information

Related User
Interface

User administration

Pre
-
conditions:

1.

User should be logged in

2.

Userid should be
created

3.

Userid should be listed in list area

Post
-
conditions:

Updated user information shall be stored in database

Priority:

Medium

Frequency of Use:

Medium

Basic Flow:

1.

Administrator
selects a user from list area by double
-
clicking it

2.

User information
is transfered in data entry area

3.

Administrator
updates information in data entry area

4.

Administrator
presses “
GÜNCELLE
” button

5.

System saves updated information in database

Alternative Flows:

None

Error Flows

1.

Userid field is updated

Medi
-
Track

SRS

V1.0




22

a.

Systems sends an error

message userid cannot
be changed



3.2.5

Delete User

Use case

Delete

User

Actors:

Administrator

Description:

Delete

user information

Related User
Interface

User administration
,

Deletion confirmation pop
-
up

Pre
-
conditions:

1.

Administrator
should be logged in

2.

Userid should be created

3.

Userid should be listed in list area

Post
-
conditions:

User information shall be deleted from database

Priority:

Medium

Frequency of Use:

Low

Basic Flow:

1.

Administrator
selects a user from list area by
double
-
clicking it

2.

User information is transfered in data entry area

3.

Administrator
presses “SİL” button

4.

System displays confirmation pop
-
up

5.

Administrator
presses “SİL” button on confirmation
pop
-
up

6.

System deletes user information from database

Alternative Flows:

1.

Administrator
presses “İPTAL” button on confirmation
pop
-
up

2.

System closes confirmation pop
-
up.

Error Flows

None




3.2.6

Create Equipment

Use case

Create Equipment

Medi
-
Track

SRS

V1.0




23

Actors:

Administrator

Description:

Create a new equipment

Related User
Interface

Equipment administration

Pre
-
conditions:

Administrator
should be logged in

Post
-
conditions:

New equipment should be created

Priority:

High

Frequency of Use:

Medium

Basic Flow:

1.

Administrator
enters equipmentid, equipment
category,
active/passive status and description
information

2.

Administrator
presses “EKLE” button



乥k⁥qu楰ien琠楮景牭a瑩tn⁩猠 瑯牥r⁩ ⁤a瑡ba獥

A汴l牮r瑩te⁆汯w猺

乯ke

b牲ç爠䙬çws



bqu楰ien琠a汲eady⁥xi獴猠



py獴sm猠獥nd猠an⁥牲ç爠re獳sge 瑨a琠
equ楰ien瑩t ex楳瑳



py獴sm⁤çe猠nç琠a汬ç眠捲敡瑩tnf new
equ楰ien琠


3.2.7

Search
Equipment

Use case

Search
Equipment

Actors:

Administrator

Description:

Search for
equipment

Related User
Interface

Equipment administration

Pre
-
conditions:

Administrator
should be logged in

Post
-
conditions:

None

Priority:

High

Frequency of Use:

Frequently

Basic Flow:

1.

Administrator
enters equipmentid or category
information.

Medi
-
Track

SRS

V1.0




24

2.

Administrator
presses “BUL” button



A汬 equ楰ien琠獡瑩tfy楮i 獥a牣栠捯nd楴楯n a牥 汩獴sd 楮
汩獴sa牥r⁩ a獣snd楮i
equ楰ien琠ç牤er

A汴l牮r瑩te⁆汯w猺

乯ke

b牲ç爠䙬çws



qÜe牥⁡牥ç⁥qu楰men琠獡瑩tfy楮i⁳ a牣栠cçnd楴楯i



py獴sm猠獥nd猠an⁥牲ç爠re獳sge 瑨a琠nç⁳ cÜ
equ楰ien琠ex楳瑳



3.2.8

Update
Equipment

Use case

Update
equipment

Actors:

Administrator

Description:

Update
equipment
information

Related User
Interface

Equipment administration

Pre
-
conditions:

1.

Administrator
should be logged in

2.

Equipment should be created

3.

Equipment should be listed in list area

Post
-
conditions:

Updated equipment information shall be
stored in
database

Priority:

Medium

Frequency of Use:

Medium

Basic Flow:

1.

Administrator
selects an equipment from list area by
double
-
clicking it

2.

Equipment information is
transferred

in data entry
area

3.

Administrator
updates information in data entry
area

4.

User presses “
GÜNCELLE
” button

5.

System saves updated information in database

Alternative Flows:

None

Error Flows

1.

Equipment field is updated

a.

Systems sends an error message equipmentid
cannot be changed


Medi
-
Track

SRS

V1.0




25


3.2.9

Delete
Equipment

Use case

Delete
equipment

Actors:

Administrator

Description:

Delete
equipment
information

Related User
Interface

Equipment administration,

Deletion confirmation pop
-
up

Pre
-
conditions:

1.

Administrator
should be logged in

2.

Equipment should be created

3.

Equipment should be listed in
list area

Post
-
conditions:

Equipment information shall be deleted from database

Priority:

Medium

Frequency of Use:

Low

Basic Flow:

1.

Administrator
selects an equipment from list area by
double
-
clicking it

2.

Equipment information is
transferred

in data entry
area

3.

Administrator
presses “SİL” button

4.

System displays confirmation pop
-
up

5.

Administrator
presses “SİL” button on confirmation
pop
-
up

6.

System deletes user information from database

Alternative Flows:

1.

Administrator
presses “İPTAL” button on
confirmation
pop
-
up

2.

System closes confirmation pop
-
up.

Error Flows

None



3.2.10

List Equipment History

Use case

List

equipment

history

Actors:

Administrator

Description:

List previous

equipment information

Related User
Equipment
history query
,

Medi
-
Track

SRS

V1.0




26

Interface

Equipment history replay

Pre
-
conditions:

Administrator
should be logged in

Post
-
conditions:

None

Priority:

High

Frequency of Use:

Medium

Basic Flow:

1.

Administrator
enters



equipment

id, beginning
date/time

and end date/time information



2.

Administrator
presses “
B啌
” button



py獴sm
汩獴s

a汬⁨楳瑯特 çf⁳ 汥捴ed⁥qu楰men琠景爠riven
瑩te pe物çd



Admin楳瑲慴ç爠
presses “OYNAT” button



py獴sm⁲ p污l猠s楳瑯特⁦ç爠瑨e⁳ 汥l瑥d⁩ fçrma瑩tn



py獴sm⁩ 景牭猠endf Ü楳瑯特⁩猠牥a捨ed

A汴l牮r瑩te⁆汯w猺

乯ke

b牲ç爠䙬çws



Beg楮i楮i⁤ate⽴ime⁩猠
g牥r瑥r

瑨an⁣ 牲en琠瑩me



py獴sm猠獥nd猠an⁥牲ç爠re獳sge
W

beg楮i楮i
da瑥⽴業e⁳ çu汤lbee獳⁴Üan⁣ 牲en琠瑩te



bnd date⽴ime⁩猠 牥rte爠瑨an⁣ 牲en琠瑩me




py獴sm猠獥nd猠an⁩ fç牭a瑩çn me獳age
W

end
da瑥⽴業e⁩猠 aken a猠su牲en琠瑩me



qÜe牥⁡牥ç⁨楳瑯特⁦ç爠瑨a琠pe物çd



py獴sm猠s楳灬iy猠sn⁩ 景牭a瑩tn me獳age
W

nç⁳ cÜ⁥qu楰men琠Ü楳瑯特⁩猠 çund 景爠rÜa琠
pe物çd



3.2.11

Track

Equipment

Use case

Monitor

equipment


Actors:

Administrator
, user

Description:

Monitor

equipment

in real
-
time


Related User
Interface

Equipment
tracking and query



Pre
-
conditions:

User should be logged in

Post
-
conditions:

None

Medi
-
Track

SRS

V1.0




27

Priority:

High

Frequency of Use:

High

Basic Flow:

1.

Systems displays all equipment on
floor plans with
predefined icons and names next to it.

2.

Current location of equipment is read from RTLS in
every 5 seconds and refreshed on the screen

3.

User can switch between floor plans by pressing the
tabs

Alternative Flows:

None

Error Flows

None




3.2.12

Find Single Equipment

Use case

Find single

equipment

Actors:

Administrator, user

Description:

Locate current position of a single equipment


Related User
Interface

Equipment tracking and query

Pre
-
conditions:

User should be logged in

Post
-
conditions:

None

Priority:

High

Frequency of Use:

High

Basic Flow:

1.

User selects an equipment from equipment dro
p
-
down
list

and press “BUL” button

2.

System switches to the floor plan the selected
equipment is currently at.

3.

System blinks the icon for
the selected equipment for
10 seconds.

Alternative Flows:

None

Error Flows

None



Medi
-
Track

SRS

V1.0




28


3.2.13

Find Equipment in a Category

Use case

Find equipment
in a category

Actors:

Administrator, user

Description:

Locate current position of

equipment

in a given
category

Related User
Interface

Equipment tracking and query

Pre
-
conditions:

User should be logged in

Post
-
conditions:

None

Priority:

High

Frequency of Use:

High

Basic Flow:

1.

User selects an equipment
category
from equipment

category


drop
-
down
list

and press “BUL” button

2.

System lists all
equipment

in that category in the list.

3.

User selects an equipment from the list by double
-
clicking it

4.

System switches to the floor plan the selected
equipment is currently at.

5.

System blinks the icon for the selected

equipment for
10 seconds.

Alternative Flows:

None

Error Flows

None





Medi
-
Track

SRS

V1.0




29


Sequence diagrams for the process are depicted below:


Figure
11

Sequence Diagram Part 1

Medi
-
Track

SRS

V1.0




30

Figure
12

Sequence Diagram Part 2

Medi
-
Track

SRS

V1.0




31

Figure
13

Sequence Diagram Part 3





Medi
-
Track

SRS

V1.0




32










Figure
14

Sequence Diagram Part 4

Medi
-
Track

SRS

V1.0




33


Class Diagram is depicted below:

Figure
15

Class Diagram


3.3

Non
-
Functional Requirements

3.3.1

Security

3.3.1.1

Medi
-
Track shall be used by only authorized personnel of the hospital.


3.3.1.2

Administrators shall do user and equipment administration and query
equipment history.


3.3.1.3

Users shall only
track

current location of equipment
.


3.3.2

Performance

3.3.2.1

System shall support at least
20 users.


3.3.2.2

System shall support at least 20 equipment.


3.3.2.3

All Medi
-
Track queries should be ended in less than 10 seconds.

Medi
-
Track

SRS

V1.0




34


3.3.2.4

E
quipment
location
information shall be refreshed in every 5 seconds.

3.3.3

Usability

3.3.3.1

All user interfaces
shall have same theme and color.


3.3.3.2

All buttons should be placed in
the
same order in
all

screens.


3.3.3.3

All buttons with same functionality should be named the same.


3.3.3.4

Deletion of information should be confirmed.


3.3.3.5

90 % of the administrators should learn how to

use the system in less
than 2 hours.


3.3.3.6

90 % of the users should learn how to use the system in less than 1 hour.


3.4

Logical Database Requirements

Logical database design is given

in
below ER diagram:


Figure
16

ER Diagram



Medi
-
Track

SRS

V1.0




35

Data
Dictionary

Name

:


User


Definition

:

P
erson who uses the Medi
-
track application

Attributes :

User id

: An attribute to identify each user uniquely

First name

: First name of the user, string

Last name
: Last name of the user, string

Password
: Password of the user, alphanumeric

User type
: Administrator or standart user
, A or U




Name

:

Equipment

Definition

:

Equipment

that Medi
-
track keeps information about

Attributes :

Equipment

id

: An attribute to identify each
device

uniquely

Equipment type

:
Type of the equipment
, string


Active
/Passive

Status:
Active/Passive status of the equipments. Only active devices
are displayed on screens.



Description: Description for

the equipment



Name

:

Real Time
Location


Definition

:

Current l
ocation of equipment

read
from

RTLS



Attributes :


Equipment id
: An attribute to identify each device uniquely


Floor

:
Identification

of the floor that device in currently at, alphanumeric


X coordinate: X coordinate of the
the device with respect to lower left corner of the
floor

plan
, given in meters, positive number

Y coordinate: Y coordinate of the the device with respect to lower left corner of the
floor

plan
, given in meters, positive number


Medi
-
Track

SRS

V1.0




36



Name :

Location History

Definition
: Location information history of equipments

Attributes :

Equipment id

: An attribute to identify each device uniquely


Floor


:
Identification of the floor that device in currently at, alphanumeric

X coordinate: X
coordinate of the the device with respect to lower left corner of the
floor

plan
, given in meters, positive number

Y coordinate: Y coordinate of the the device with respect to lower left corner of the
floor

plan
, given in meters, positive number

Date
:
History date,
DD.MM.YYYY


Time: History time, hh:mm:ss