BS EN 54-20:2006 pdf download.Fire detection and fire alarm systems —— Part 20: Aspirating smoke detectors.
5.12.2 Software documentation
5.12.2.1 The manufacturer shall submit documentation to the testing authority which gives an overview of the software design. This documentation shall be in sufficient detail for the design to be inspected for compliance with this standard and shall include at least the following:
a) functional desaiption of the main program flow (e.g. as a flow diagram or structograni) including:
1) brief description of the modules and the functions that they pe.lom,
2) way In wh the modules interact.
3) overall hierarchy of the program,
4) way in which the sol’tware interacts with the hardware of the detector,
5) way In which the modules are called, including any interrupt processing:
b) description of which areas of memory are used for the various purposes (e.g. the program, site specific data and running data):
c) designation, by which the software and its version can be uniquely identified.
5.12.2.2 The manufacturer shall also have available detailed design documentation, which only needs to be provided if required by the testing authority. It shall comprise at least the following:
a) overview of the whole system configuration, including all software and hardware components:
b) description of each module of the program, containing at least:
1) name of the module,
2) description of the tasks performed,
3) descrIption of the Interfaces. mdud.ng the type of data transfer, the valid data range and the checking for valid data:
c) full source code listings, as hard copy or in machine-readable form (e.g. ASCII-code), including global and local vanables. constants and labels used, and suffloent comment for the program flow to be recognized;
d) details of any software tools used in the design and implementation phase (e.g. CASE-Tools. Compilers)
5.12.3 Software design
To ensure the reliability of the detector, the following requirements for software design shall apply:
a) software shall have a modular structure.
5.12.2.1 The manufacturer shall submit documentation to the testing authority which gives an overview of the software design. This documentation shall be in sufficient detail for the design to be inspected for compliance with this standard and shall include at least the following:
a) functional desaiption of the main program flow (e.g. as a flow diagram or structograni) including:
1) brief description of the modules and the functions that they pe.lom,
2) way In wh the modules interact.
3) overall hierarchy of the program,
4) way in which the sol’tware interacts with the hardware of the detector,
5) way In which the modules are called, including any interrupt processing:
b) description of which areas of memory are used for the various purposes (e.g. the program, site specific data and running data):
c) designation, by which the software and its version can be uniquely identified.
5.12.2.2 The manufacturer shall also have available detailed design documentation, which only needs to be provided if required by the testing authority. It shall comprise at least the following:
a) overview of the whole system configuration, including all software and hardware components:
b) description of each module of the program, containing at least:
1) name of the module,
2) description of the tasks performed,
3) descrIption of the Interfaces. mdud.ng the type of data transfer, the valid data range and the checking for valid data:
c) full source code listings, as hard copy or in machine-readable form (e.g. ASCII-code), including global and local vanables. constants and labels used, and suffloent comment for the program flow to be recognized;
d) details of any software tools used in the design and implementation phase (e.g. CASE-Tools. Compilers)
5.12.3 Software design
To ensure the reliability of the detector, the following requirements for software design shall apply:
a) software shall have a modular structure.
