Advertenties
Praesideo 4.3
Clause / Requirement
14 Additional design requirements for software
controlled VACIE
14. 1 General requirements and manufacturer's
declarations
In order to fulfill requirements of this European Standard the
VACIE may contain elements which are controlled by
software. In this case, the VACIE shall comply with the
requirements of Clause 13 Design requirements and this
clause where relevant to the technology used.
14.2 Software documentation
14.2. 1 The manufacturer shall prepare documentation that
gives an overview of the software design, which shall be
submitted to the testing authority together with the VACIE.
This documentation shall be in sufficient detail for the
design to be inspected for compliance with this European
Standard and shall comprise at least the following:
a
functional description, using a clear methodology
appropriate to the nature of the software, e.g. graphical
representations of the system design, data flows and
control flows and of the main program flow, including:
1
a brief description of each module and the tasks it
performs,
2
the way in which the modules interact,
3
the way in which the modules are called, including
any interrupt processing, and
4
the overall hierarchy of the program;
b
a description of which areas of memory are used for the
various purposes (e.g. the program, site specific data
and running data);
c
a description of how the software interacts with the
hardware of the VACIE.
Where dynamic memory management is employed, a
separation shall be implemented between the program, site
specific data and running data and this shall be described
in connection with the method of memory allocation.
14.2.2 The manufacturer shall prepare and maintain
detailed design documentation. This need not be submitted
to the testing authority but shall be available for inspection
in a manner which respects the manufacturer's rights of
confidentiality. This documentation shall comprise at least
the following:
a
a description of each module of the program, as it is
implemented in the source code of the program,
containing:
1
the name of the module, and
2
the identification of the author(s);
b
the source code listing, including all global and local
variables, constants and labels used, and sufficient
comment for the program flow to be recognized;
Bosch Security Systems B.V.
Compliance
Praesideo is compliant.
The Praesideo system is centrally controlled by the
software running on the network controller.
Praesideo is compliant.
The software design documentation is available for testing
authorities. It is in sufficient detail for the design to be
inspected for compliance.
An extensive set of architecture documents and software
design documents are available and maintained.
Architecture documents are available.
Architecture and design documents are available.
Architecture and design documents are available.
Architecture documents are available.
Memory usage is described in the system architecture
document.
Hardware software interaction is described in a set of
Hardware-Software Interface documentation.
The program is located in separate Flash EPROMs that are
reserved for the program executable.
The message data is stored on a separate Flash card.
The site specific configuration data is stored on the Flash
file system.
The running data (static variables, stacks and heap data) is
stored in RAM.
After loading the program executable from Flash EPROM
into RAM, the code space and the running data are
separated from each other: the code space is in the bottom
area of the RAM and the running data takes up the
remainder. Dynamic memory is allocated from the heap
using the VxWorks (first fit policy based) memory manager.
The file system that, apart from storing the site specific
data, also stores the logging information and configuration
web pages, is a Flash EPROM based DOS FAT file system
that is managed by the VxWorks Flash file system manager.
The software design documents contain detailed design
documentation. Furthermore code comments also contain
detailed design documentation.
The Praesideo software component descriptions (module
descriptions) are available from the software architecture
documents. These documents contain the names of the
components. The author information can be obtained from
the version manager (Merant Version Manager) used for the
documentation.
All of the source code listing (including all global and local
variables, constants and labels used) can be obtained from
the version manager (Merant Version Manager) used for the
code. All of the Praesideo code is commented.
Installatie- en Gebruikershandleiding
Signature
IUI-PRAESIDEO_4.3 | V1.0 | 2015.02
nl | 76
Advertenties
