GM1 to AMC 20-115D -- Software change impact analyses (CIAs)

• ED Decision 2017/020/R found in: AMC-20 Amdt 21 - Airworthiness of Products, Parts and Appliances (Apr 2021)

GM1 to AMC 20-115D — Software change impact analyses (CIAs) ED Decision 2017/020/R a.         These practices provide complementary information to ED-12C/DO-178C and ED-12B/DO-178B, Sections 12.1.1, 12.1.2, and 12.1.3, and [AMC 20-115D](#_DxCrossRefBm421436784), subparagraph 9(b)(4). The applicant may use these practices when they need to conduct a software CIA. b.         A CIA identifies the released software baseline upon which the proposed software is to be built, providing: 1.         a summary of the changes and the impact of those changes; 2.         a listing and descriptions of the problem reports to be corrected as part of the intended change and/or change requests related to those changes; and 3.         a listing of new functions to be activated and/or implemented. c.         A CIA addresses changes to the following items, where applicable: 1.         the software level; 2.         the development or verification environment; 3.         the software processes; 4.         the tools (e.g. when a new tool version is introduced or a tool’s use is modified); 5.         the processor or other hardware components and interfaces; 6.         the configuration data, especially when activating or deactivating functions; 7.         the software interface characteristics and input/output (I/O) requirements; and 8.         the software requirements, design, architecture, and code components, where such changes are not limited to the modified life cycle data, but should also consider the items affected by the change. d.         For each applicable item of subparagraph 13(c) above, a CIA describes the resulting impact of the change(s) and identifies the activities to be performed to satisfy ED-12C/DO-178C or ED-12B/DO-178B and continue to satisfy the requirements for safe operation. [Amdt 20/14] GM1 to AMC 20-115D — Software change impact analyses (CIAs) ED Decision 2017/020/R a.         These practices provide complementary information to ED-12C/DO-178C and ED-12B/DO-178B, Sections 12.1.1, 12.1.2, and 12.1.3, and [AMC 20-115D](#_DxCrossRefBm1926189222), subparagraph 9(b)(4). The applicant may use these practices when they need to conduct a software CIA. b.         A CIA identifies the released software baseline upon which the proposed software is to be built, providing: 1.         a summary of the changes and the impact of those changes; 2.         a listing and descriptions of the problem reports to be corrected as part of the intended change and/or change requests related to those changes; and 3.         a listing of new functions to be activated and/or implemented. c.         A CIA addresses changes to the following items, where applicable: 1.         the software level; 2.         the development or verification environment; 3.         the software processes; 4.         the tools (e.g. when a new tool version is introduced or a tool’s use is modified); 5.         the processor or other hardware components and interfaces; 6.         the configuration data, especially when activating or deactivating functions; 7.         the software interface characteristics and input/output (I/O) requirements; and 8.         the software requirements, design, architecture, and code components, where such changes are not limited to the modified life cycle data, but should also consider the items affected by the change. d.         For each applicable item of subparagraph 13(c) above, a CIA describes the resulting impact of the change(s) and identifies the activities to be performed to satisfy ED-12C/DO-178C or ED-12B/DO-178B and continue to satisfy the requirements for safe operation. [Amdt 20/14] GM1 to AMC 20-115D — Software change impact analyses (CIAs) ED Decision 2017/020/R a. These practices provide complementary information to ED-12C/DO-178C and ED-12B/DO-178B, Sections 12.1.1, 12.1.2, and 12.1.3, and [AMC 20-115D](#_DxCrossRefBm1701657978), subparagraph 9(b)(4). The applicant may use these practices when they need to conduct a software CIA. b. A CIA identifies the released software baseline upon which the proposed software is to be built, providing: 1. a summary of the changes and the impact of those changes; 2. a listing and descriptions of the problem reports to be corrected as part of the intended change and/or change requests related to those changes; and 3. a listing of new functions to be activated and/or implemented. c. A CIA addresses changes to the following items, where applicable: 1. the software level; 2. the development or verification environment; 3. the software processes; 4. the tools (e.g. when a new tool version is introduced or a tool’s use is modified); 5. the processor or other hardware components and interfaces; 6. the configuration data, especially when activating or deactivating functions; 7. the software interface characteristics and input/output (I/O) requirements; and 8. the software requirements, design, architecture, and code components, where such changes are not limited to the modified life cycle data, but should also consider the items affected by the change. d. For each applicable item of subparagraph 13(c) above, a CIA describes the resulting impact of the change(s) and identifies the activities to be performed to satisfy ED-12C/DO-178C or ED-12B/DO-178B and continue to satisfy the requirements for safe operation. [Amdt 20/14]