Download Visualizza/apri

52
CHAPTER 6. THE CASE STUDY
behave in particular situations (Sommerville, 2010).
In this case study the RTLS would have to meet the following requirements:
Client side
View location of sensors, on a grid matrix where the map of the barn
is reproduced.
Identify the sensors.
Activate the UWB tags.
Calibrate the system.
View graphics and statistics of location information.
Server side
A computer with optimum operating system and hardware.
A permanent Internet connection to communicate with the client.
Maintain a database of all known APIs.
Maintain location informations of all clients and update this whenever
possible.
Display this information graphically.
Send this informations to the clients.
A fully functional Graphical User Interface (GUI).
6.2.1.2
Non-functional requirements
Non-functional requirements, as the name suggests, are requirements that are
not directly concerned with the specific services delivered by the system to its
users. They may relate to system properties such as reliability, response time,
store occupancy and the constraints on the system implementation such as
the capabilities of I/O devices or the data representations used in interfaces
with other systems (Sommerville, 2010).
In this case study the non-functional requirements are: