GM2 Article 15(1)(b) Conditions for
obtaining a certificate
ED Decision 2022/022/R
SOFTWARE ASSURANCE — USE OF EXISTING INDUSTRY STANDARDS
The applicant is responsible for defining the software assurance processes. The applicant may directly develop its own method, provided it allows to properly structure the software activities and addresses the key software engineering principles and associated software life cycle data upon which the software process assurance is built:
(a) software specification (requirements and design information);
(b) software verification;
(c) traceability (between items);
(d) configuration and change management; and
(e) quality assurance.
Nevertheless, it is recommended that the applicant consider the guidance material contained in existing industry standards for software assurance considerations. It should be considered that not all standards address all aspects required, and the applicant may need to define additional software assurance processes.
Guidance material typically includes:
(f) objectives of the software life cycle processes;
(g) activities to meet the objectives;
(h) description of the evidence, in the form of software life cycle data, which indicates that the objectives have been met; and
(i) particular aspects (e.g. previously developed or COTS software) that may be applicable to certain applications.
Loading collections...