7.4 Evidence for Requirements Satisfaction (by attribute)
This section offers guidance on assessing the behavioural attributes of a software safety requirement in addition to the generic guidance specified in sections 7.1 to 7.3.
7.4.1 Specific Requirements for Evidence of Functional Properties
It is expected that an appropriate form of direct evidence will be selected from the following table in order to demonstrate that the specified functional properties have been correctly implemented.
Acceptable Sources of Evidence: Functional Properties (Choose 1 column only from the appropriate row)
AEL 1 TESTING FIELD SERVICE EXPERIENCE & Testing ANALYSIS & Testing
AEL 2 TESTING FIELD SERVICE EXPERIENCE & Testing ANALYSIS & Testing
AEL 3 ANALYSIS & Testing ANALYSIS & Testing & Field Service Experience
AEL 4 ANALYSIS & Testing ANALYSIS & Testing & Field Service Experience
AEL 5 ANALYSIS & Testing
7.4.1.1 Direct Evidence of Analysis of Functional Properties
Arguments and evidence should be available that show:
a) The source code contains a correct implementation of the functional properties of the software safety requirement, either directly or by means of intermediate design notations or stages. This includes those functional properties that have been derived from non-functional software safety requirements.
b) All parameters and constants used in conjunction with the software system have been checked for correctness and internal consistency.
7.4.2 Specific Requirements for Evidence of Timing Properties
It is expected that an appropriate form of direct evidence will be selected from the following table in order to demonstrate that the specified timing properties have been satisfied.
Acceptable Sources of Evidence: Timing Properties (Choose 1 column only from the appropriate row)
AEL 1 TESTING TESTING & Field service experience ANALYSIS & Testing
AEL 2 TESTING TESTING & Field service experience ANALYSIS & Testing
AEL 3 ANALYSIS & Testing ANALYSIS & Testing & Field Service Experience
AEL 4 ANALYSIS & Testing ANALYSIS & Testing & Field Service Experience
AEL 5 ANALYSIS & Testing
7.4.2.1 Direct Evidence from Testing of Timing Properties
Arguments and evidence should be available which show that:
a) Specified response times for the software safety requirement have been met under minimum or no load conditions, normal and maximum planned load conditions.
b) Specified throughputs for the software safety requirement have been met under minimum or no load conditions, normal and maximum planned load conditions.
7.4.2.2 Backing Evidence of Testing of Timing Properties 中国航空网 www.aero.cn 航空翻译 www.aviation.cn 本文链接地址:CAP 670 Air Traffic Services Safety Requirements 1(75)