Bosch Praesideo 4.0 - Инструкция (Страница 70)

Praesideo 4.0 en | 80
Bosch Security Systems B.V. IUI-PRAESIDEO_4.0 | V1.0 | 2013.01 Installation and User Instructions
Clause / Requirement Compliance Signature
14 Additional design requirements for software
controlled VACIE
14.1 General requirements and manufacturer's
declarations
Praesideo is compliant.
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.
The Praesideo system is centrally controlled by the
software running on the network controller.
14.2 Software documentation Praesideo is compliant.
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:
The software design documentation is available for
testing authorities. It is in sufficient detail for the design to
be inspected for compliance.
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:
An extensive set of architecture documents and software
design documents are available and maintained.
1 a brief description of each module and the tasks
it performs,
Architecture documents are available.
2 the way in which the modules interact, Architecture and design documents are available.
3 the way in which the modules are called,
including any interrupt processing, and
Architecture and design documents are available.
4 the overall hierarchy of the program; Architecture documents are available.
b a description of which areas of memory are used for
the various purposes (e.g. the program, site specific
data and running data);
Memory usage is described in the system architecture
document.
c a description of how the software interacts with the
hardware of the VACIE.
Hardware software interaction is described in a set of
Hardware-Software Interface documentation.
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.
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.
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:
The software design documents contain detailed design
documentation. Furthermore code comments also
contain detailed design documentation.
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);
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.
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;
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.