2 SYSTEM REQUIREMENTS
Our objective is to devise a software architecture
for surveillance systems composed of a sensor net-
work of different sources. The architecture should al-
low adding new and improved surveillance techniques
while the network continues operating. The require-
ments are divided in non-functional, functional and
hardware categories. The first two categories of re-
quirements are based on (Detmold et al., 2006) and
(Valera and Velastin, 2008).
2.1 Non-Functional Requirements
The non-functional requirements for video surveil-
lance networks include scalability, availability, evolv-
ability, integration, security and manageability.
• Scalability: We should consider different scopes
for scalability. Processing the data generated in a
large-scale surveillance system in a centralized ar-
chitecture is unfeasible and a scalable distributed
processing is required. Also, storing the relevant
data, even if a small fraction of all captured data,
requires a scalable storage distributed system. Fi-
nally, in some cases a scalable network needs to
be considered, mainly if the number of sources of
information are expected to increase.
• Availability: A larger number of components in-
creases the probability that some component will
eventually fail. However, the architecture must
support acceptable levels of operation. A configu-
ration of redundant systems should be considered
if high level of availability is required.
• Evolvability: Within some limits, the surveillance
network should be able to accommodate changes,
including alterations to the hardware and changes
to the software.
• Integration: Nowadays surveillance systems usu-
ally operate in independently of other systems.
However, there is a growing need to integrate dif-
ferent systems, especially for intelligent manage-
ment of buildings. It is therefore required a per-
spective of integration with external systems.
• Security: The integration with external systems
however intensifies the need for security. A crit-
ical requirement is that the system should be ro-
bust to attacks with malicious intents. The con-
sequences of such attacks include compromising
confidential information or shutting down the sys-
tem through denial of service attacks.
2.2 Functional Requirements
The functional requirements of intelligent surveil-
lance systems include modules that perform: (1) sig-
nal processing, including audio and visual process-
ing, (2) data aggregation and higher-level semantic
analysis, (3) command, control and inspection of all
network elements, and (4) storage with browsing and
forensic analysis capabilities.
We first consider a low-level signal processing
module that receives data from sensors and gener-
ates a sparser representation of data when compared
to the raw data. For example, for the visual sen-
sors, i.e. cameras, the signal processing module in-
cludes: object detection, object classification accord-
ing to shape, color, and other properties, and object
tracking along time within individual cameras views.
In this case, the signal processing module accepts im-
ages from individual cameras as input, and produces
as output a compact representation of the content –
for example, the object trajectories. These modules
are closely related to each sensor and can be seen as a
layer just above the sensors. Depending on the hard-
ware capabilities of the sensors, the modules’ imple-
mentation could be embedded in the sensors.
The data processed for individual sensors is col-
lected by a data aggregation module that relies on the
multiple sources of data in the network to get a more
complete representation. Using the same example, for
visual sensors the data aggregation module includes:
multicamera tracking of objects across time and mul-
tiple cameras views. Also, a higher-level analysis is
performed to extract semantic knowledge, which usu-
ally requires a priori information and training. One
objective could be behavioral analysis, or in other
words, to recognize and understand the activities of
the tracked objects. The output of these modules is
typically auxiliary data (or metadata) that is stored
alongside the raw data or events to alert the human
operator.
The events triggered by the system warn about sit-
uations that eventually require close attention by the
operators. When needed, the operators use command
control, and inspection functionalities to interact with
system – e.g. examine the status of an element (e.g.
a sensor) in the network and take corrective actions.
Other examples of interactions include remote sensor
control of individual sensors in real-time, target fol-
lowing by selecting an object to follow and making a
report, and external system control namely, control-
ling the elevators system or locking the doors.
Finally, storage with browsing and forensic anal-
ysis capabilities allow an operator to efficiently find
a given event or object. Browsing or querying the
BUILDING MODULAR SURVEILLANCE SYSTEMS BASED ON MULTIPLE SOURCES OF INFORMATION -
Architecture and Requirements
315