Skip to content

A gradual release of Avioverse begins in October 2026. Request early access →

GM1 to AMC6 ATM/ANS.OR.C.005(a)(2) Safety support assessment and assurance of changes to the functional system

ANNEX III COMMON REQUIREMENTS FOR SERVICE PROVIDERS (Part-ATM/ANS.OR) · Regulation (EU) 2017/373 · EAR revision 12 Mar 2025

GMGuidance material

GM1 to AMC6 ATM/ANS.OR.C.005(a)(2) Safety support assessment and assurance of changes to the functional system

ASSURANCE — SOFTWARE ASSURANCE PROCESS

(a)The term ‘correct and complete software verification’ is understood to be all software safety requirements, which correctly state what is required of the software component by the risk assessment and mitigation process and their implementation is demonstrated to the level required by the software assurance level.

(b)The term ‘software timing performances’ is understood to be the time allowed for the software to respond to given inputs or to periodic events, and/or the performance of the software in terms of transactions or messages handled per unit time.

(c)The term ‘software capacity’ is understood to be the ability of the software to handle a given amount of data flow.

(d)The term ‘software accuracy’ is understood to be the required precision of the computed results.

(e)The term ‘software resource usage’ is understood to be the amount of resources within the computer system that can be used by the application software.

(f)The term ‘software robustness’ is understood to be the behaviour of the software in the event of unexpected inputs, hardware faults and power supply interruptions, either in the computer system itself or in connected devices.

(g)The term ‘overload tolerance’ is understood to be the behaviour of the system in the event of, and in particular its tolerance to, inputs occurring at a greater rate than expected during normal operation of the system.

(h)The term ‘software life cycle data’ is understood to be the data that is produced during the software life cycle to plan, direct, explain, define, record, or provide evidence of activities; this data enables the software life cycle processes, system or equipment approval and post-approval modification of the software item.

(i)The term ‘COTS’ is understood to be a commercially available application sold by vendors through public catalogue listings and not intended to be customised or enhanced.

GM — Regulation (EU) 2017/373 · ED Decision 2019/022/R · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025