{"text_format":"2","workbook":"xlsx","n_sheets":11,"sheets":["Front Page","PSAA","SDP","SVP","SCMP","SQAP","Standards","SRD","SDD","SCI","Integration"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":0,"defined_names":3,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Front Page","index":0,"n_rows":143,"n_cols":6,"rows_kept":143,"cut":false,"hidden":false,"merged":[[73,0,77,0],[78,1,78,2],[81,1,81,2],[80,0,80,2],[56,1,56,2],[41,0,45,0],[46,1,46,2],[49,1,49,2],[50,1,50,2],[55,1,55,2],[67,0,70,0],[71,1,71,2],[72,1,72,2],[57,0,61,0],[62,1,62,2],[65,1,65,2],[66,1,66,2],[24,1,24,2],[14,1,14,2],[3,0,6,0],[1,1,1,2],[2,1,2,2],[7,1,7,2],[8,1,8,2],[9,0,13,0],[19,0,22,0],[23,1,23,2],[17,1,17,2],[32,0,32,2],[48,0,48,2],[64,0,64,2],[51,0,54,0],[35,0,38,0],[39,1,39,2],[40,1,40,2],[25,0,29,0],[30,1,30,2],[33,1,33,2],[34,1,34,2],[18,1,18,2],[8,4,8,5],[9,3,13,3],[14,4,14,5],[16,3,16,5],[17,4,17,5],[0,3,0,5],[1,4,1,5],[2,4,2,5],[3,3,6,3],[7,4,7,5],[0,0,0,2],[16,0,16,2],[30,4,30,5],[32,3,32,5],[33,4,33,5],[34,4,34,5],[35,3,38,3],[18,4,18,5],[19,3,22,3],[23,4,23,5],[24,4,24,5],[25,3,29,3],[49,4,49,5],[50,4,50,5],[51,3,54,3],[55,4,55,5],[56,4,56,5],[39,4,39,5],[40,4,40,5],[41,3,45,3],[46,4,46,5],[48,3,48,5],[67,3,70,3],[71,4,71,5],[72,4,72,5],[73,3,77,3],[78,4,78,5],[57,3,61,3],[62,4,62,5],[64,3,64,5],[65,4,65,5],[66,4,66,5],[96,0,96,2],[97,1,97,2],[98,1,98,2],[99,0,102,0],[103,1,103,2],[88,4,88,5],[89,3,93,3],[94,4,94,5],[80,3,80,5],[81,4,81,5],[82,4,82,5],[83,3,86,3],[87,4,87,5],[94,1,94,2],[83,0,86,0],[87,1,87,2],[88,1,88,2],[82,1,82,2],[89,0,93,0],[114,1,114,2],[115,0,118,0],[119,1,119,2],[120,1,120,2],[121,0,125,0],[104,1,104,2],[105,0,109,0],[110,1,110,2],[112,0,112,2],[113,1,113,2],[135,1,135,2],[136,1,136,2],[137,0,141,0],[142,1,142,2],[126,1,126,2],[128,0,128,2],[129,1,129,2],[130,1,130,2],[131,0,134,0]]}
["PSAA",null,null,"PSAA"]
["Review Identifier","01_PAL_SW_PSAA_v1.0",null,"Review Identifier","01_PAL_SW_PSAA_v1.1"]
["Review Date","2025.06.10",null,"Review Date","2025.06.26"]
["Reviewer(s)","Name","Role","Reviewer(s)","Name","Role"]
[null,"JI, DEAHAN","Developer",null,"JI, DEAHAN","Developer"]
[null,"HAN, KOOKYI ","Verifier",null,"HAN, KOOKYI ","Verifier"]
[null,"CHOI, HYUNSIK","QA",null,"CHOI, HYUNSIK","QA"]
["Project/Program/System Name","UTM",null,"Project/Program/System Name","UTM"]
["Software/System Part Number","UTM Service",null,"Software/System Part Number","UTM Service"]
["Data Items Under Audit","Identification","Verison","Data Items Under Audit","Identification","Verison"]
[null,"PSAA",1,null,"PSAA",1.1000000000000001]
[]
[]
[]
["Standards Used"," RTCA/DO-278A",null,"Standards Used"," RTCA/DO-278A"]
[]
["SDP",null,null,"SDP"]
["Review Identifier","02_PAL_SW_SDP",null,"Review Identifier","02_PAL_SW_SDP"]
["Review Date","2025.06.10",null,"Review Date","2025.06.26"]
["Reviewer(s)","Name","Role","Reviewer(s)","Name","Role"]
[null,"JI, DEAHAN","Developer",null,"JI, DEAHAN","Developer"]
[null,"HAN, KOOKYI ","Verifier",null,"HAN, KOOKYI ","Verifier"]
[null,"CHOI, HYUNSIK","QA",null,"CHOI, HYUNSIK","QA"]
["Project/Program/System Name","UTM",null,"Project/Program/System Name","UTM"]
["Software/System Part Number","UTM Service",null,"Software/System Part Number","UTM Service"]
["Data Items Under Audit","Identification","Verison","Data Items Under Audit","Identification","Verison"]
[null,"SDP","-",null,"SDP","-"]
[]
[]
[]
["Standards Used"," RTCA/DO-278A",null,"Standards Used"," RTCA/DO-278A"]
[]
["SVP",null,null,"SVP"]
["Review Identifier","03_PAL_SW_SVP",null,"Review Identifier","03_PAL_SW_SVP"]
["Review Date","2025.06.10",null,"Review Date","2025.06.26"]
["Reviewer(s)","Name","Role","Reviewer(s)","Name","Role"]
[null,"JI, DEAHAN","Developer",null,"JI, DEAHAN","Developer"]
[null,"HAN, KOOKYI ","Verifier",null,"HAN, KOOKYI ","Verifier"]
[null,"CHOI, HYUNSIK","QA",null,"CHOI, HYUNSIK","QA"]
["Project/Program/System Name","UTM",null,"Project/Program/System Name","UTM"]
["Software/System Part Number","UTM Service",null,"Software/System Part Number","UTM Service"]
["Data Items Under Audit","Identification","Verison","Data Items Under Audit","Identification","Verison"]
[null,"SVP","-",null,"SVP","-"]
[]
[]
[]
["Standards Used"," RTCA/DO-278A",null,"Standards Used"," RTCA/DO-278A"]
[]
["SCMP",null,null,"SCMP"]
["Review Identifier","04_PAL_SW_SCMP",null,"Review Identifier","04_PAL_SW_SCMP"]
["Review Date","2025.06.10",null,"Review Date","2025.06.26"]
["Reviewer(s)","Name","Role","Reviewer(s)","Name","Role"]
[null,"JI, DEAHAN","Developer",null,"JI, DEAHAN","Developer"]
[null,"HAN, KOOKYI ","Verifier",null,"HAN, KOOKYI ","Verifier"]
[null,"CHOI, HYUNSIK","QA",null,"CHOI, HYUNSIK","QA"]
["Project/Program/System Name",null,null,"Project/Program/System Name"]
["Software/System Part Number",null,null,"Software/System Part Number"]
["Data Items Under Audit","Identification","Verison","Data Items Under Audit","Identification","Verison"]
[null,"SCMP","-",null,"SCMP","-"]
[]
[]
[]
["Standards Used"," RTCA/DO-278A",null,"Standards Used"," RTCA/DO-278A"]
[]
["SQAP",null,null,"SQAP"]
["Review Identifier","05_PAL_SW_SQAP",null,"Review Identifier","05_PAL_SW_SQAP"]
["Review Date","2025.06.10",null,"Review Date","2025.06.26"]
["Reviewer(s)","Name","Role","Reviewer(s)","Name","Role"]
[null,"JI, DEAHAN","Developer",null,"JI, DEAHAN","Developer"]
[null,"HAN, KOOKYI ","Verifier",null,"HAN, KOOKYI ","Verifier"]
[null,"CHOI, HYUNSIK","QA",null,"CHOI, HYUNSIK","QA"]
["Project/Program/System Name",null,null,"Project/Program/System Name"]
["Software/System Part Number",null,null,"Software/System Part Number"]
["Data Items Under Audit","Identification","Verison","Data Items Under Audit","Identification","Verison"]
[null,"SQAP","-",null,"SQAP","-"]
[]
[]
[]
["Standards Used"," RTCA/DO-278A",null,"Standards Used"," RTCA/DO-278A"]
[]
["Standards",null,null,"Standards"]
["Review Identifier","06_PAL_SW_SRS / 07_PAL_SW_SDS /",null,"Review Identifier","06_PAL_SW_SRS / 07_PAL_SW_SDS /"]
["Review Date","2025.06.10",null,"Review Date","2025.06.26"]
["Reviewer(s)","Name","Role","Reviewer(s)","Name","Role"]
[null,"JI, DEAHAN","Developer",null,"JI, DEAHAN","Developer"]
[null,"HAN, KOOKYI ","Verifier",null,"HAN, KOOKYI ","Verifier"]
[null,"CHOI, HYUNSIK","QA",null,"CHOI, HYUNSIK","QA"]
["Project/Program/System Name",null,null,"Project/Program/System Name"]
["Software/System Part Number",null,null,"Software/System Part Number"]
["Data Items Under Audit","Identification","Verison","Data Items Under Audit","Identification","Verison"]
[null,"SRStd","-",null,"SRStd","-"]
[null,"SDStd","-",null,"SDStd","-"]
[]
[]
["Standards Used"," RTCA/DO-278A",null,"Standards Used"," RTCA/DO-278A"]
[]
["SRD"]
["Review Identifier"]
["Review Date"]
["Reviewer(s)","Name","Role"]
[]
[]
[]
["Project/Program/System Name"]
["Software/System Part Number"]
["Data Items Under Audit","Identification","Verison"]
[]
[]
[]
[]
["Standards Used"," RTCA/DO-278A"]
[]
["SDD"]
["Review Identifier"]
["Review Date"]
["Reviewer(s)","Name","Role"]
[]
[]
[]
["Project/Program/System Name"]
["Software/System Part Number"]
["Data Items Under Audit","Identification","Verison"]
[]
[]
[]
[]
["Standards Used"," RTCA/DO-278A"]
[]
["SCI"]
["Review Identifier"]
["Review Date"]
["Reviewer(s)","Name","Role"]
[]
[]
[]
["Project/Program/System Name"]
["Software/System Part Number"]
["Data Items Under Audit","Identification","Verison"]
[]
[]
[]
[]
["Standards Used"," RTCA/DO-278A"]

{"sheet":"PSAA","index":1,"n_rows":53,"n_cols":7,"rows_kept":53,"cut":false,"hidden":false,"merged":[]}
["Plan of Software Aspect Certification Review"]
[{"$nulls":4},"2025.06.10",null,"2025.06.26"]
["Checklist Item",null,"Reference","Y / N\nNA","Comments/ Action Item #","Y / N\nNA","Comments/ Action Item #"]
["Document Format:"]
["1. Is the document under configuration control with an accurate revision history?","1. 문서가 정확한 개정 내역을 가지고 구성 관리되고 있습니까?","7.2.1","Y","Ref Cover page\nRef Revision page\nPALNETWORKS managed by Git-hub according to SCMP","Y","Ref Cover page\nRef Revision page\nPALNETWORKS managed by Git-hub according to SCMP"]
["2. Does the title page include program name, document release date, and document identification and revision level?","2. 표지에 프로그램 이름, 문서 릴리스 날짜, 문서 식별 및 개정 수준이 포함되어 있습니까?","7.2.1","Y","Ref Cover page","Y","Ref Cover page"]
["3. Is the table of contents, terms and acronyms, references, and any other applicable tables included and accurate?","3. 목차, 용어 및 약어, 참조 및 기타 적용 가능한 표가 포함되어 있고 정확합니까?",null,"Y","Ref Contents table","Y","Ref Contents table"]
["Scope","범위"]
["4. Is the document name and version number accurate on the title page?","4. 표지의 문서 이름과 버전 번호가 정확합니까?",4,"Y","comparting with 1.3, PSAA document's name and version is correct\n","Y","comparting with 1.3, PSAA document's name and version is correct\n"]
["5. Does the revision history accurately state the prior versions and authors thereof?","5. 개정 내역에 이전 버전과 저자가 정확하게 명시되어 있습니까?",4,"Y","At the bottom of the cover page, there are name and signature who involved","Y","At the bottom of the cover page, there are name and signature who involved"]
["Technical Content Items:","기술 콘텐츠 항목:"]
["6.      Does the document identification section describe the application of the document, project name, and level of criticality?","6. 문서 식별 섹션에 문서의 적용, 프로젝트 이름 및 중요도 수준이 설명되어 있습니까?","11.1.c","Y","REF 1.2 Scope\nThis document is configuration controlled as Control Category 1 data \nunder DO-278A guidelines.","Y","REF 1.2 Scope\nThis document is configuration controlled as Control Category 1 data \nunder DO-278A guidelines."]
["7.      Is there a system overview section which describes the applicable system at a high level and a figure depicting the system and its components?","7. 해당 시스템을 개략적으로 설명하는 시스템 개요 섹션과 시스템 및 구성 요소를 나타내는 그림이 있습니까?","11.1.a","Y","Ref 2. System Overveiw","Y","Ref 2. System Overveiw\nFor the System, the AL-6 and AL-4 parts are distinguished, and the System architecture, I/O definition, and communication method are written for the UTM Core, SWIM, and unauthorized Drone Detection CSCI, which are the scope of certification. In addition, the System safety of the actual scope of certification is explained."]
["8.      Are the software and Line Replaceable Units identified for application of this document?","8. 이 문서의 적용을 위해 소프트웨어 및 라인 교체 가능 유닛(LRU)이 식별되어 있습니까?",4.3,"Y","The UTM system complies with DO-278A and is a control service program, so it is installed on a hardware server. Therefore, there is no separate LRU according to the aviation software standard, DO-178c.\nHowever, PALNETWORKS sperated UTM 3 parts as UTM CORE, SWIM Service Specification and Unauthorized Drone Detection.","Y","The UTM system complies with DO-278A and is a control service program, so it is installed on a hardware server. Therefore, there is no separate LRU according to the aviation software standard, DO-178c.\nHowever, PALNETWORKS sperated UTM 3 parts as UTM CORE, SWIM Service Specification and Unauthorized Drone Detection."]
["9.      Is there a software overview section which describes the functionality and key components of the software at a high level?","9. 소프트웨어의 기능과 주요 구성 요소를 개략적으로 설명하는 소프트웨어 개요 섹션이 있습니까?","11.1.b","Y","Ref 3. Software Overview","Y","Ref 3. Software Overview"]
["Does the plan include a certification considerations section that summarizes:","계획에 다음을 요약한 인증 고려 사항 섹션이 포함되어 있습니까?"]
["10.      The certification basis, including the means of compliance, as relating to the software aspects of certification?","10.      인증의 소프트웨어 측면과 관련된 준수 수단을 포함한 인증 기준은 무엇입니까?","11.1.c","Y","Ref 4.1\tCertification Basis\nthese project comes from KAC and their requirements complying with DO-278A","Y","Ref 4.1\tCertification Basis\nthese project comes from KAC and their requirements complying with DO-278A\nIn addition, the SW level was identified as PAL_SW_FHA (Funtional Hazard Assesment) as the basis for AL-4 identification for certification."]
["11.      The justification provided by the system safety assessment process, including potential software contributions to failure conditions","11.      시스템 안전 평가 프로세스에서 제공하는 정당성, 장애 조건에 대한 잠재적 소프트웨어 기여도 포함","11.1.c","Y","Ref 1.2.1 Exclusive section\nRef 4.2\t Software Item Assurance Level (AL)\n\nPALNETWORKS don't apply for ARP4754B/4761A but they created a simplified FHA to determine software level(AL) with KAC","Y","Ref 1.2.1 Exclusive section\nRef 4.2\t Software Item Assurance Level (AL)\n\nPALNETWORKS don't apply for ARP4754B/4761A but they created a simplified FHA to determine software level(AL) with KAC"]
["12.      Who is responsible for ensuring the safety of the system and certification of the system?","12.      시스템 안전 및 시스템 인증을 보장하는 책임자는 누구입니까?",null,"N/A","this project din't consider System safety and system certification ","N/A","this project din't consider System safety and system certification "]
["13.      Is the role of Software Quality Assurance described or referenced, and does that role state that SQA is independent from Engineering?","13.      소프트웨어 품질 보증의 역할이 설명 또는 참조되어 있습니까? 해당 역할에서 SQA가 엔지니어링과 독립적임을 명시하고 있습니까?",8.1999999999999993,"Y","Ref 8.5 Quality Assurance Engineer","Y","Ref 8.5 Quality Assurance Engineer"]
["14.      Is the project schedule referenced or included?","14.      프로젝트 일정이 참조 또는 포함되어 있습니까?","11.1.f","Y","Ref 7 Schedule\nthis project was palned and considered until SOI#3\nthat's why PALNETWORKS don't process SOI#4","Y","Ref 7 Schedule\nthis project was palned and considered until SOI#3\nthat's why PALNETWORKS don't process SOI#4"]
["15.   Are critical path milestones, which must be met to achieve certification described?","15.   인증을 받기 위해 충족해야 하는 중요 경로 이정표가 설명되어 있습니까?","11.1.f","Y","Ref 7 Schedule\nat section 7. Schedule, there are plan for SOI#1 to SOI#3. \nHowever, the plan may change depending on the actual development schedule.","Y","Ref 7 Schedule\nat section 7. Schedule, there are plan for SOI#1 to SOI#3. \nHowever, the plan may change depending on the actual development schedule."]
["16.   Are there any special features that affect the certification process described?","16.   인증 프로세스에 영향을 미치는 특별한 기능이 설명되어 있습니까?","11.1.g","N/A","there are not any special features that affect the certification process","N/A","there are not any special features that affect the certification process"]
["Does the plan include a software life cycle data section, including:","계획에 다음을 포함한 소프트웨어 수명 주기 데이터 섹션이 포함되어 있습니까?"]
["17.   A description of the software life cycle data that will be produced and controlled by the software life cycle processes such as:","17. 소프트웨어 수명 주기 프로세스에서 생성 및 제어되는 소프트웨어 수명 주기 데이터에 대한 설명(예:"]
["A.     Data related to the type design (Software Requirements Data, Design Description, Source Code, Executable Object Code, Software Configuration Index, and the Software Accomplishment Summary)?","A. 유형 설계 관련 데이터(소프트웨어 요구 사항 데이터, 설계 설명, 소스 코드, 실행 가능 개체 코드, 소프트웨어 구성 인덱스 및 소프트웨어 성과 요약)?",11.1]
["B.     Software Development Plan?","B. 소프트웨어 개발 계획?",11.2,"Y","Ref 5.4\t Software Development Processes\nRef 6 Software Life Cycle data, SDP","Y","Ref 5.4\t Software Development Processes\nRef 6 Software Life Cycle data, SDP"]
["C.     Software Metrics Plan?","C. 소프트웨어 메트릭 계획?",11.5,"N/A","Even though, there is no description about PSAA but, there are Complexity metricx description on SDS\nRef 6 Software Life Cycle data, SDS","N/A","Even though, there is no description about PSAA but, there are Complexity metricx description on SDS\nRef 6 Software Life Cycle data, SDS"]
["D.     Software Configuration Management Plan?","D. 소프트웨어 구성 관리 계획?",11.4,"Y","Ref. 5.6 Software Configuration Management Process\nRef 6 Software Life Cycle data, SCMP","Y","Ref. 5.6 Software Configuration Management Process\nRef 6 Software Life Cycle data, SCMP"]
["E.     Software Quality Assurance Plan?","E. 소프트웨어 품질 보증 계획?",11.5,"Y","Ref 5.7 Software Quality Assurance Process\nRef 6 Software Life Cycle data, SQAP","Y","Ref 5.7 Software Quality Assurance Process\nRef 6 Software Life Cycle data, SQAP"]
["F.     Software Verification Plan?","F. 소프트웨어 검증 계획?",11.3,"Y","Ref 5.5 \tSoftware Verification Processes\nRef 6 Software Life Cycle data, SVP","Y","Ref 5.5 \tSoftware Verification Processes\nRef 6 Software Life Cycle data, SVP"]
["G.    Software Requirements Standards?","G. 소프트웨어 요구 사항 표준?",11.6,"Y","Ref 5.3 Software Planning Process\nRef 6 Software Life Cycle data, SRS","Y","Ref 5.3 Software Planning Process\nRef 6 Software Life Cycle data, SRS"]
["H.     Software Design Standards?","H. 소프트웨어 설계 표준?",11.7,"Y","Ref 5.3 Software Planning Process\nRef 6 Software Life Cycle data, SDS","Y","Ref 5.3 Software Planning Process\nRef 6 Software Life Cycle data, SDS"]
["I.       Software Code Standards?","I. 소프트웨어 코드 표준?",11.8,"N/A","UTM SERVICE is AL-4","N/A","UTM SERVICE is AL-4"]
["J.      Software Verification Procedures and Results?","J. 소프트웨어 검증 절차 및 결과?",11.3,"Y","Ref 5.5 Software Verification Processes\nRef 6 Software Life Cycle data, SVCP","Y","Ref 5.5 Software Verification Processes\nRef 6 Software Life Cycle data, SVCP"]
["K.     Support Software Version Description Document (Software Life Cycle Environment Configuration Index)?","K. 지원 소프트웨어 버전 설명 문서(소프트웨어 수명 주기 환경 구성 인덱스)?",11.15,"Y","Ref 6 Software Life Cycle data, SCI, SECI","Y","Ref 6 Software Life Cycle data, SCI, SECI"]
["L.      Tool Qualification Plan? Operations? Accomplishment Summary?","L. 도구 검증 계획? 운영? 성과 요약?",12.2,"N/A","Ref 1.2.1 Exclusive section\nRef 9.6.4 Compliance Deviations\nPALNETWORKS don't apply for DO-330, TQ","N/A","Ref 1.2.1 Exclusive section\nRef 9.6.4 Compliance Deviations\nPALNETWORKS don't apply for DO-330, TQ"]
["18.   A description of the relationship of the data to each other or to other data defining the system?","18. 데이터 간 관계 또는 시스템을 정의하는 다른 데이터와의 관계에 대한 설명?","11.1.e","Y","Ref 6 Software Life Cycle data, ,Trace data","Y","Ref 6 Software Life Cycle data, ,Trace data"]
["19.   A description of the software life cycle data to be submitted to the certification authority, which as a minimum is the PSAA, the SCI, and the SAS?","19. 인증 기관(최소 PSAA, SCI, SAS)에 제출할 소프트웨어 수명 주기 데이터에 대한 설명?",9.3000000000000007,"Y","Ref 5 Software Life Cycle Processes","Y","Ref 5 Software Life Cycle Processes\nThe previously written content contained wrong things, so it was replaced with the process content provided by ConsuNova."]
["20.   A description of the software life cycle data form?","20. 소프트웨어 수명 주기 데이터 양식에 대한 설명?","11.0.b","Y","Ref 5.1 Left Side – Development Phases\nRef 5.2 Right Side – Verification Phases","Y","Ref 5 Software Life Cycle Processes\nThe previously written content contained wrong things, so it was replaced with the process content provided by ConsuNova."]
["21.   A description of how software life cycle data will be made available to the certification authority?","21. 소프트웨어 수명 주기 데이터를 인증 기관에 제공하는 방법에 대한 설명?","11.1.e","Y","Ref 4.4 Certification Liaison Process","Y","Ref 4.4 Certification Liaison Process"]
["22.   Is the application of traceability matrices and configuration indices described?","22. 추적성 매트릭스 및 구성 인덱스 적용에 대한 설명이 있습니까?",11.3,"Y","Ref 11 DO-278A Planned Compliance Matrix","Y","Ref 11 DO-278A Planned Compliance Matrix"]
["23.   Does the plan address use of Parameter Data?","23. 계획에서 매개변수 데이터 사용을 다루고 있습니까?",11.22,"N/A",null,"N/A"]
["24.   Are the primary certification documents to be generated and released identified?","24. 생성 및 배포할 주요 인증 문서가 식별되어 있습니까?",11,"N/A","PALNETWORKS don't go process to SOI#4 so that they don't need to establish SAS","N/A","PALNETWORKS don't go process to SOI#4 so that they don't need to establish SAS"]
["If product service history will be used to gain some certification credit, does the plan contain:","제품 서비스 이력을 사용하여 인증 크레딧을 획득하는 경우 계획에 다음이 포함되어 있습니까?"]
["25.   An analysis of the relevance of the product service history?","25. 제품 서비스 이력의 관련성 분석이 있습니까?","12.3.4.1","N/A",null,"N/A"]
["26.   A definition of what was counted as an error and rationale for that definition?","26. 오류로 간주된 사항의 ​​정의와 그 정의에 대한 근거는 무엇입니까?","12.3.4.3","N/A",null,"N/A"]
["27.   Proposed acceptable error rates and rationale for the product service history period in relation to the system safety and proposed error rates?","27. 시스템 안전 및 제안된 오류율과 관련하여 제품 서비스 내역 기간에 대한 허용 가능한 오류율과 근거는 무엇입니까?","12.3.4.4.d","N/A",null,"N/A"]
["If the supplier intends to use alternative methods, does the supplier:","공급업체가 대체 방법을 사용하려는 경우 공급업체는 다음을 수행합니까?"]
["28.   Plan to provide evidence throughout the project that the alternative method complies with the objectives of DO‑178C?","28. 프로젝트 전반에 걸쳐 대체 방법이 DO‑178C의 목표를 준수한다는 증거를 제공할 계획입니까?","12.3.a","N/A",null,"N/A"]
["29.   Specify the impact of the proposed method on the software development process?","29. 제안된 방법이 소프트웨어 개발 프로세스에 미치는 영향을 명시합니까?","12.3.b.1","N/A",null,"N/A"]
["30.   Specify the impact of the proposed method on the software life cycle data?","30. 제안된 방법이 소프트웨어 수명 주기 데이터에 미치는 영향을 명시합니까?","12.3.b.2","N/A",null,"N/A"]
["31.   Specify the rationale for use of the alternative method which shows that the system safety objectives are satisfied?","31. 시스템 안전 목표가 충족되었음을 보여주는 대체 방법 사용의 근거를 명시합니까?","12.3.b.3","N/A",null,"N/A"]

{"sheet":"SDP","index":2,"n_rows":85,"n_cols":7,"rows_kept":85,"cut":false,"hidden":false,"merged":[[2,1,3,1]]}
["Software Development Plan Review"]
[{"$nulls":4},"2025.06.10",null,"2025.06.26"]
["Checklist Item",null,"Reference","Y / N\nNA","Comments/ Action Item #","Y / N\nNA","Comments/ Action Item #"]
[]
["Configuration Aspects"]
["Have the following Configuration aspects of this plan been achieved?"]
["1.        Is the document Revision/Baseline under Configuration?","1.        문서 개정/기준이 구성 중입니까?",null,"Y","PAL is managing the revision history on the cover page and making revisions according to SCMP.","Y","PAL is managing the revision history on the cover page and making revisions according to SCMP."]
["2.        Were the related plans (PSAC, SCMP, SQAP, SVP) configured before updating or developing this Data Item?","2.        이 데이터 항목을 업데이트하거나 개발하기 전에 관련 계획(PSAC, SCMP, SQAP, SVP)이 구성되었습니까?",null,"Y","All of Plan and STD are mentioned to\nsection 1.3 Applicable and Reference Documents","Y","All of Plan and STD are mentioned to\nsection 1.3 Applicable and Reference Documents"]
["3.        Does the title page include Program/Project name, document release date, and document identification?","3.        제목 페이지에 프로그램/프로젝트 이름, 문서 릴리스 날짜 및 문서 식별 정보가 포함되어 있습니까?",null,"Y","Refer to Cover page","Y","Refer to Cover page"]
["4.        Is the table of contents and any other applicable tables included and accurate?","4.        목차 및 기타 적용 가능한 표가 포함되어 있고 정확합니까?",1.3,"Y","Refer to 'Table of Contents'","Y","Refer to 'Table of Contents'"]
["5.        Are References stated, terms and acronyms defined?","5.        참조가 명시되어 있고 용어 및 약어가 정의되어 있습니까?","1.4.1, 1.4.2","Y","Refer to 1.3 Applicable and Reference Documents","Y","Refer to 1.3 Applicable and Reference Documents"]
["Scope"]
["1.        Is there a technical summary of the software end item(s) to be developed?","1.        개발할 소프트웨어 최종 항목에 대한 기술 요약이 있습니까?","2, 3","Y","Refer to 1.1 purpose and 1.2 Scope","Y","Refer to 1.1 purpose and 1.2 Scope"]
["2.        Is there a reference to the system specification (by part number) for the project?","2.        프로젝트에 대한 시스템 사양(부품 번호별)에 대한 참조가 있습니까?",1.3,"N/A",null,"N/A"]
["Schedules and Resources"]
["1.        Are project schedules and resources included or referenced?","1.        프로젝트 일정과 리소스가 포함되거나 참조됩니까?",5,"N","if look at section 5. Software Development Life Cycle, PAL has described at their Life cyle presenting V-model diagram\nHowever, they have to change their own V-model diagram. Because PAL's SW is AL-4 so that they don't need LLR and so on.","Y","PAL has developed the V-model considered to DO-278A and their own company processes."]
["2.        Is there an identification of Support environment, including development, integration, verification, and validation?","2.        개발, 통합, 검증 및 확인 등을 포함한 지원 환경에 대한 식별이 있습니까?",10,"Y","Refer to 5,6,7,8 section (Devleop, Verification, CM, QA)\nSection 9, the environment related to development.","Y","Refer to 5,6,7,8 section (Devleop, Verification, CM, QA)\nSection 9, the environment related to development."]
["Project Adminstration"]
["1.        Will the supplier update the project management plans to reflect all proposed changes in processes for the duration of the contract and obtain Client approval prior to implementation?","1.        공급업체는 계약 기간 동안 프로세스의 모든 제안된 변경 사항을 반영하기 위해 프로젝트 관리 계획을 업데이트하고 구현하기 전에 고객의 승인을 받을 것인가?",null,"N/A","PAL have no plan to work with supplier","N/A","PAL have no plan to work with supplier"]
["Is there a description or reference of the procedures, methods and controls for managing:"]
["2.        Incremental: \n       a. development?\n       b. reviews, including conducting a final summary session?\n       c. deliveries?","\na. 개발?\nb. 최종 요약 세션 수행을 포함한 검토?\nc. 납품?",6,"Y","In the development process, a plan is written for each activity, and activities related to VP, CMP, and QAP are confirmed by referring to each Plan document.","Y","In the development process, a plan is written for each activity, and activities related to VP, CMP, and QAP are confirmed by referring to each Plan document."]
["3.        Are there supplier plans for managing and monitoring lower‑tier contractors, including flow down of contractual agreements?","3. 계약의 하향 흐름을 포함하여 하위 계약자를 관리하고 모니터링하기 위한 공급업체 계획이 있습니까?",null,"N//A",null,"N//A"]
["4.        Is there a description of the status reporting process?","4. 상태 보고 프로세스에 대한 설명이 있습니까?",6,"Y","Refer to 7. Spftware Configuration Management Process\nRefer to SCMP","Y","Refer to 7. Spftware Configuration Management Process\nRefer to SCMP"]
["If the supplier intends to use alternative methods, does the supplier:"]
["5.        Define the alternative method and plans for its use in the project management plans? And does it include the details of the method, how it interacts with other alternative methods (if applicable), and which DO-278 objectives it will satisfy and how it will satisfy them?","5. 프로젝트 관리 계획에서 대체 방법과 그 사용 계획을 정의하세요. 그리고 방법에 대한 세부 정보, 다른 대체 방법(해당되는 경우)과의 상호 작용, 그리고 충족시킬 DO-278 목표와 그 목표를 어떻게 충족시킬 것인지가 포함되어 있나요?",null,"N/A",null,"N/A"]
["6.        Plan to provide evidence throughout the project that the alternative method complies with the intent of the objectives of DO-278?","6. 대체 방법이 DO-278 목표의 의도를 준수한다는 증거를 프로젝트 전반에 걸쳐 제공할 계획인가요?",null,"N/A",null,"N/A"]
["7.        Specify the impact of the proposed method on the software development process?","7. 제안된 방법이 소프트웨어 개발 프로세스에 미치는 영향을 명시하세요.",null,"N/A",null,"N/A"]
["8.        Specify the impact of the proposed method on the software life cycle data?","8. 제안된 방법이 소프트웨어 수명 주기 데이터에 미치는 영향을 명시하세요.",null,"N/A",null,"N/A"]
["9.        Specify the rationale for use of the alternative method which shows that the system safety objectives are satisfied?","9. 시스템 안전 목표가 충족되었음을 보여주는 대체 방법 사용의 근거를 명시하세요.",null,"N/A",null,"N/A"]
["10.     Plan to substantiate this rationale by software plans, processes, expected results, and evidence of the use of the method?","10. 소프트웨어 계획, 프로세스, 예상 결과 및 방법 사용 증거를 통해 이 근거를 입증할 계획인가요?",null,"N/A",null,"N/A"]
["11.     Plan to use formal methods and if so, are the objectives of DO-278 section 12.3.1 satisfied?","11.     공식적인 방법을 사용할 계획이며, 그렇다면 DO-278 섹션 12.3.1의 목표가 충족됩니까?",null,"N/A",null,"N/A"]
["12.     Plan to use exhaustive input testing and if so, are the objectives of DO-278 section 12.3.2 satisfied?","12.     철저한 입력 테스트를 사용할 계획이며, 그렇다면 DO-278 섹션 12.3.2의 목표가 충족됩니까?",null,"N/A",null,"N/A"]
["13.     Plan to use multiple-version dissimilar software and if so, are the objectives of DO-278 section 12.3.3 (and subsections) satisfied?","13.     여러 버전의 이기종 소프트웨어를 사용할 계획이며, 그렇다면 DO-278 섹션 12.3.3(및 하위 섹션)의 목표가 충족됩니까?",null,"N/A",null,"N/A"]
["14.     Plan to use software reliability models and if so, are the objectives of DO-278 section 12.3.4 satisfied?","14.     소프트웨어 신뢰성 모델을 사용할 계획이며, 그렇다면 DO-278 섹션 12.3.4의 목표가 충족됩니까?",null,"N/A",null,"N/A"]
["15.     Plan to use product service history and if so, are the objectives of DO-278 section 12.3.5 satisfied?","15.     제품 서비스 이력을 사용할 계획이며, 그렇다면 DO-278 섹션 12.3.5의 목표가 충족됩니까?",null,"N/A",null,"N/A"]
["16.     If the supplier intends to use Commercial off-the-shelf software, are there provisions for that software to meet the objectives of DO-278?","16. 공급업체가 상용 기성 소프트웨어를 사용하려는 경우, 해당 소프트웨어가 DO-278의 목표를 충족하도록 규정되어 있습니까?",null,"N/A",null,"N/A"]
["17.     If the supplier intends to use multiple-version dissimilar software, does the software planning process choose methods and tools that achieve the error avoidance or detection necessary to satisfy the system safety objectives?","17. 공급업체가 여러 버전의 이기종 소프트웨어를 사용하려는 경우, 소프트웨어 계획 프로세스에서 시스템 안전 목표를 충족하는 데 필요한 오류 방지 또는 감지를 달성하는 방법과 도구를 선택합니까?",null,"N/A",null,"N/A"]
["18.     If the supplier plans to use user-modifiable code, are the processes, tools, environment, and data items that substantiate the guidelines of section 5.2.3 of DO-278 specified in the software plans and standards?","18. 공급업체가 사용자가 수정할 수 있는 코드를 사용하려는 경우, DO-278 섹션 5.2.3의 지침을 입증하는 프로세스, 도구, 환경 및 데이터 항목이 소프트웨어 계획 및 표준에 명시되어 있습니까?",null,"N/A",null,"N/A"]
["19.     Does the software planning process provide for coordination between the software development and integral processes to provide consistency among strategies in the software plans?","19. 소프트웨어 계획 프로세스에서 소프트웨어 개발과 통합 프로세스 간의 조정을 제공하여 소프트웨어 계획의 전략 간 일관성을 유지합니까?",null,"Y","through Review and Analysis, Pal provide consistency among plan and development process output","Y","through Review and Analysis, Pal provide consistency among plan and development process output"]
["20.     Is the software planning process complete when the software plans and software development standards are under change control and reviews of them complete?","20. 소프트웨어 계획 및 소프트웨어 개발 표준이 변경 제어되고 이에 대한 검토가 완료되면 소프트웨어 계획 프로세스가 완료됩니까?",null,"Y","Refer to SCMP","Y","Refer to SCMP"]
["Development Process"]
["1.        Is there a description of the project processes which implement program management and software development?","1. 프로그램 관리 및 소프트웨어 개발을 구현하는 프로젝트 프로세스에 대한 설명이 있습니까?","6, 8, 9","Y","Section 5. Software Development Life Cycle which include Requirements , Design, Coding, and Integration\n\nPAL mamaged life cycle data accroding to Section 7. Software Configuration Management Process.","Y","Section 5. Software Development Life Cycle which include Requirements , Design, Coding, and Integration\n\nPAL mamaged life cycle data accroding to Section 7. Software Configuration Management Process."]
["2.        Is there a reference to the software development standards?","2. 소프트웨어 개발 표준에 대한 참조가 있습니까?","1.3, 4","Y","Refer to Section 4. Software Standards which include SRD, SDS except SCS because of AL-4\n","Y","Refer to Section 4. Software Standards which include SRD, SDS except SCS because of AL-4\n"]
["3.        Are there references to the standards for previously developed software, including COTS software, if those standards are different?","3. COTS 소프트웨어를 포함하여 이전에 개발된 소프트웨어의 표준이 다른 경우 해당 표준에 대한 참조가 있습니까?",null,"Y","There is no PDS in Pal's development process. But they will use COTS components ans also PAL already has described at section 9. Software Devleopment Environment.","Y","There is no PDS in Pal's development process. But they will use COTS components ans also PAL already has described at section 9. Software Devleopment Environment."]
["Is there a description of the project processes for the software life cycle of the software end item, including:"]
["4.        Project milestones to include TRR, FAI, and SOI1 through SOI4?","4. TRR, FAI, SOI1~SOI4를 포함하는 프로젝트 이정표가 있나요?",5,"Y","In Section 5, the diagram that defines the life cycle is marked with SOI#1~#4. The specific schedule was verified and confirmed by referring to the PSAC Schedule.","Y","In Section 5, the diagram that defines the life cycle is marked with SOI#1~#4. The specific schedule was verified and confirmed by referring to the PSAC Schedule."]
["5.        Descriptions of the tasks that fulfill each project process?","5. 각 프로젝트 프로세스를 충족하는 작업에 대한 설명이 있나요?","6, 8, 9","Y","PAL created and defined output data and Transition Criteria per each process to satisfy each process and DO-178C objectives","Y","PAL created and defined output data and Transition Criteria per each process to satisfy each process and DO-178C objectives"]
["Are there criteria for transition between software life cycle processes that includes:"]
["6.        The inputs to the process, including feedback from other processes?","6.        다른 프로세스의 피드백을 포함한 프로세스의 입력은 무엇입니까?",6,"Y","The input of each process consists of the plan output of the planning phase and the output of the previous phase.\n\nIf feedback is required, it is written considering the feedback situation with the notation 'as required' or 'when applicable'.","Y","The input of each process consists of the plan output of the planning phase and the output of the previous phase.\n\nIf feedback is required, it is written considering the feedback situation with the notation 'as required' or 'when applicable'."]
["7.        Any integral process activities that may be required to act on these inputs?","7.        이러한 입력에 따라 조치를 취하는 데 필요할 수 있는 통합 프로세스 활동은 무엇입니까?",6,"Y","refer to transition Criteria per each section, where Pal have to conduct verification , CM , PR and QA's audit. ","Y","refer to transition Criteria per each section, where Pal have to conduct verification , CM , PR and QA's audit. "]
["8.        Availability of tools, methods, plans and procedures?","8.        도구, 방법, 계획 및 절차의 가용성은 무엇입니까?",null,"Y","refer to \"PR identified\" statements at each Transition criteria section which means paln, tools and methods are managed by CMP and PR would be created by review , analysis and test according to SVP, so that availibility would be clear. \n","Y","refer to \"PR identified\" statements at each Transition criteria section which means paln, tools and methods are managed by CMP and PR would be created by review , analysis and test according to SVP, so that availibility would be clear. \n"]
["Is there a description of:"]
["9.        The structure of the software development  and support processes?","9. 소프트웨어 개발 및 지원 프로세스의 구조는 무엇입니까?",null,"Y","In 5. Software Development Life Cycle, Pal has defined their life cycle as V-Model","Y","In 5. Software Development Life Cycle, Pal has defined their life cycle as V-Model"]
["10.     Is there a description of the methods and criteria for managing and measuring module complexity at the design and source code level?","10. 설계 및 소스 코드 수준에서 모듈 복잡성을 관리하고 측정하는 방법과 기준에 대한 설명이 있습니까?",6.2,"Y","It has been verified that the contents of this checklist is related to quality at the code level and is covered in SDS and 5.3 Software Coding Process.","Y","It has been verified that the contents of this checklist is related to quality at the code level and is covered in SDS and 5.3 Software Coding Process."]
["11.     Is there a description of the methods and criteria for determining the timing margin metric?","11. 타이밍 마진 지표를 결정하는 방법과 기준에 대한 설명이 있습니까?",null,"N/A","PAL didn't consider timing margin ","N/A","PAL didn't consider timing margin "]
["12.     If applicable, is there a description of the use of previously developed software?","12. 해당되는 경우, 이전에 개발된 소프트웨어 사용에 대한 설명이 있습니까?",null,"N/A","NO PDS","N/A","NO PDS"]
["13.     Are there procedures to be used to implement software changes prior to use on a certified aircraft?","13. 인증된 항공기에 사용하기 전에 소프트웨어 변경 사항을 구현하는 데 사용할 절차가 있습니까?",null,"Y","Refer to SCMP\n","Y","Refer to SCMP\n"]
["14.     Is there a description of the methods for handling deactivated code?","14. 비활성화된 코드를 처리하는 방법에 대한 설명이 있습니까?",null,"Y","Refer to PSAA","Y","Refer to PSAA"]
["15.     If deactivated code is planned, does the software planning process describe how the deactivated code will be defined, verified and handled to achieve system safety objectives?","15. 비활성화 코드를 계획하는 경우, 소프트웨어 계획 프로세스에 시스템 안전 목표를 달성하기 위해 비활성화된 코드를 정의, 검증 및 처리하는 방법이 설명되어 있습니까?",null,"Y","Refer to PSAA","Y","Refer to PSAA"]
["16.     Do the methods and tools chosen provide for error prevention in the software development process?","16. 선택한 방법과 도구가 소프트웨어 개발 프로세스에서 오류 방지를 제공합니까?",10,"N/A","They will use LDRA for DCCC but, they don't apply for Tool Qualification, DO-330","N/A","They will use LDRA for DCCC but, they don't apply for Tool Qualification, DO-330"]
["17.     Will the processes, content, and characteristics of field-loadable software be delineated in the development documentation for the system?","17.     현장 로드 가능 소프트웨어의 프로세스, 콘텐츠 및 특성이 시스템 개발 문서에 구체적으로 설명되어 있습니까?",null,"Y","In SCI, PAL has created section for Load control","Y","In SCI, PAL has created section for Load control"]
["Target Computer"]
["1. Are there references to the target computer specification and selection?","1. 타겟 컴퓨터 사양 및 선택에 대한 참조가 있습니까?","1.3, 2, 3","Y","Rerfer to section 9, Development Environment","Y","Rerfer to section 9, Development Environment"]
["Programming Language"]
["1.        Is the programming language that the supplier plans to use identified?","1.        공급업체가 사용할 프로그래밍 언어가 확인되었습니까?",4.0999999999999996,"Y","Ref 5.3 Software Coding Process","Y","Ref 5.3 Software Coding Process"]
["Does the specified programming language have:"]
["2.        Unambiguous syntax, well understood semantics?","2.        명확한 구문과 잘 이해되는 의미론이 있습니까?",4,"N/A","Since SW is AL-4, PAL don't need coding rules","N/A","Since SW is AL-4, PAL don't need coding rules"]
["3.        Is a set of standards for source code construction and restrictions identified?","3.        소스 코드 구성 및 제한 사항에 대한 표준 세트가 식별되어 있습니까?",4,"Y","4. Software Standards에 SDS에 Coding standards가 포함되어 있다는 내용 존재","Y","4. Software Standards에 SDS에 Coding standards가 포함되어 있다는 내용 존재"]
["Verification Process"]
["1.        Is there a reference to the Verification plan?","1. 검증 계획에 대한 참조가 있습니까?","1.2.1, 1.3, 6","Y","Rerfer to 6. Software Verification Process","Y","Rerfer to 6. Software Verification Process"]
["2.        Is there a definition of (or reference to) plans for tool development and tool qualification and tool operational requirements, as applicable?","2. 도구 개발 및 도구 적격성 평가 계획과 도구 운영 요구 사항에 대한 정의(또는 참조)가 있습니까?",null,"Y","Rerfer to 6. Software Verification Process","Y","Rerfer to 6. Software Verification Process"]
["Delivery"]
["1.        Is there a description of procedures for managing deliveries during laboratory and airplane tests?","1.         실험실 및 항공기 테스트 중 배송을 관리하는 절차에 대한 설명이 있습니까?",null,"N/A",null,"N/A"]
["2.        Is there a description of how the software part number is confirmed and/or displayed?","2.        소프트웨어 부품 번호가 확인 및/또는 표시되는 방법에 대한 설명이 있습니까?",null,"N/A","Refer to SCMP","N/A","Refer to SCMP"]
["3.        Is there a description of how the load integrity is verified during software loading?","3.        소프트웨어 로딩 중 로드 무결성이 검증되는 방법에 대한 설명이 있습니까?",10,"Y","Refer to 5.4 Software Integration Process","Y","Refer to 5.4 Software Integration Process"]
["Software Development and Verification Tools"]
["To ensure suitability and quality of the software tools used in the development and verification of the software end item and their impact on the end item, will the supplier:"]
["1.        Evaluate each software tool and determine its suitability, quality, and potential impact on the software end item?","1. 각 소프트웨어 도구를 평가하고 적합성, 품질 및 소프트웨어 최종 항목에 대한 잠재적 영향을 결정합니까?",null,"N/A",null,"N/A"]
["2.        Ensure that if the tool supplements or reduces the effort of complying with DO-278, the use of the tool satisfies the intent of those requirements supplemented or reduced?","2. 도구가 DO-278 준수 노력을 보완하거나 줄이는 경우 도구를 사용하면 보완 또는 감소된 요구 사항의 의도를 충족하는지 확인하십시오.",null,"N/A",null,"N/A"]
["3.        Plan to perform required tool qualification?","3. 필요한 도구 적격성 평가를 수행할 계획입니까?",null,"N/A",null,"N/A"]
["4.        Is software development environment chosen to minimize its potential risk to the final airborne software?","4. 최종 항공 소프트웨어에 대한 잠재적 위험을 최소화하도록 소프트웨어 개발 환경을 선택했습니까?",10,"N/A",null,"N/A"]
["5.        Is software development environment chosen to achieve the necessary level of confidence that an error introduced by one part would be detected by other?","5. 한 부분에서 발생한 오류를 다른 부분에서 감지할 수 있는 필요한 수준의 신뢰를 달성하도록 소프트웨어 개발 환경을 선택했습니까?",10,"N/A",null,"N/A"]
["6.        Is the sequence of operation of the tool used for certification credit specified?","6. 인증 크레딧에 사용되는 도구의 작동 순서가 지정되어 있습니까?",10,"N/A","Refer to PSAA and SQAP","N/A","Refer to PSAA and SQAP"]
["7.        If optional features of software development tools (e.g. compilers) are chosen, are the effects of the options examined and specified?","7. 소프트웨어 개발 도구의 선택적 기능(예: 컴파일러)을 선택한 경우 옵션의 영향을 검토하고 지정했습니까?",null,"Y","Refer to SDS","Y","Refer to SDS"]
["8.        Are requirements development methods and tools specified?","8.        요구사항 개발 방법과 도구가 지정되어 있습니까?","5.1, 9.1 ","Y","Plan don't have any requirement development tool so that they just create requirements using office word","Y","Plan don't have any requirement development tool so that they just create requirements using office word"]

{"sheet":"SVP","index":3,"n_rows":50,"n_cols":7,"rows_kept":50,"cut":false,"hidden":false,"merged":[]}
["Software Verification Plan Audit Questions"]
[{"$nulls":4},"2025.06.10",null,"2025.06.26"]
["Checklist Item","체크리스트 항목","Reference","Y / N\nNA","Comments/ Action Item #","Y / N\nNA","Comments/ Action Item #"]
["Configuration Aspects","구성 측면"]
["Have the following Configuration aspects of SVP been achieved?","SVP의 다음 구성 측면이 달성되었습니까?"]
["1.        Is the document Revision/Baseline under Configuration?","1. 문서 개정/기준선이 구성 단계에 있습니까?",null,"Y","Ref Cover page and Revision section\nSVP docutment was managed by CME and also uploaded to Git-hub\nHowever, UTM Service level is AL-4 so that SVP was not remarked as sepcific version","Y","Ref Cover page and Revision section\nSVP docutment was managed by CME and also uploaded to Git-hub\nHowever, UTM Service level is AL-4 so that SVP was not remarked as sepcific version"]
["2.        Were the related plans (PSAC, SCMP, SQAP, SDP) configured before updating or developing this Data Item?","2. 관련 계획(PSAC, SCMP, SQAP, SDP)이 이 데이터 항목을 업데이트하거나 개발하기 전에 구성되었습니까?",null,"Y","Yes. After developing PSAC, SDP, SCMP ,SQAP and Standard, All of data were verified by Verifier according to SVP.","Y","Yes. After developing PSAC, SDP, SCMP ,SQAP and Standard, All of data were verified by Verifier according to SVP."]
["3.        Does the title page include Program/Project name, document release date, and document identification?","3. 제목 페이지에 프로그램/프로젝트 이름, 문서 릴리스 날짜 및 문서 식별 정보가 포함되어 있습니까?",null,"Y","Ref Cover page","Y","Ref Cover page"]
["4.        Is the table of contents and any other applicable tables included and accurate?","4. 목차 및 기타 적용 가능한 표가 포함되어 있으며 정확합니까?","1.3.2","Y","Ref Table of Contents","Y","Ref Table of Contents"]
["General Compliance","일반 준수"]
["Does the SVP include the following Contents?","SVP에 다음 내용이 포함되어 있습니까?"]
["5.        Does the plan include organizational responsibilities within the software verification process and interfaces with the other software life cycle processes?","5. 계획에 소프트웨어 검증 프로세스 내의 조직적 책임이 포함되어 있으며 다른 소프트웨어 수명 주기 프로세스와 상호 작용합니까?",2,"Y","Ref 2. Software Verification Process\nIn each Review Process and Analysis methods, there are organizational responsibilities within the software verification process.","Y","Ref 2. Software Verification Process\nIn each Review Process and Analysis methods, there are organizational responsibilities within the software verification process."]
["6.        Does the plan provide a description of the methods for establishing verification independence, as appropriate for software level?","6. 계획에 소프트웨어 수준에 따라 검증 독립성을 확립하는 방법에 대한 설명이 제공됩니까?",null,"N/A","UTM SERVICE is AL-4 so that PAL don't need to establish verification independence","N/A","UTM SERVICE is AL-4 so that PAL don't need to establish verification independence"]
["7.        Does the plan provide a description of the equipment for testing, the testing and analysis tools, and the guidelines for applying these tools and hardware test equipment?","7. 계획에는 테스트 장비, 테스트 및 분석 도구, 그리고 이러한 도구와 하드웨어 테스트 장비를 적용하기 위한 지침에 대한 설명이 포함되어 있습니까?","2.2.4","N","Not Yet\nPAL is still preparing Hardware Test Environment. \nIt will be clear until SOI#2. However DCCC coverage will be conducted by LDRA","N","PAL still has TBD for Test Environment, but it is not yet confirmed. Therefore, I registered the issue as PR and managed it, and received confirmation from QA.\nPostpone SOI#2"]
["8.        Is the transition criteria for entering the software verification process defined in this plan?","8. 이 계획에는 소프트웨어 검증 프로세스 진입을 위한 전환 기준이 정의되어 있습니까?",2,"Y","The verifier reviewed the SVP according to the Transition Criteria set in each Review process and Analysis Method.","Y","The verifier reviewed the SVP according to the Transition Criteria set in each Review process and Analysis Method."]
["Is there a description of assumptions regarding the correctness of:","다음의 정확성과 관련된 가정에 대한 설명이 있습니까?"]
["9.        Compiler? Linkage editor? Loader?","9. 컴파일러? 링키지 편집기? 로더?",null,"Y","Ref SVP 2.2.6 Software Integration Review\nEven though specific Complier, Linkage, Loader already descirbed in PSAA and SCMP, section 2.2.6, Software Integration Reivew, include how to review Build procedure and load control ","Y","Ref SVP 2.2.6 Software Integration Review\nEven though specific Complier, Linkage, Loader already descirbed in PSAA and SCMP, section 2.2.6, Software Integration Reivew, include how to review Build procedure and load control "]
["Additional Considerations:","추가 고려 사항:"]
["10.     Does the plan include, for software modifications, a description of the methods for identifying affected areas ensuring, re-verification, and elimination of reported errors? ","10. 계획에는 소프트웨어 수정에 대해 영향을 받는 영역을 식별하고 보고된 오류를 보장, 재검증 및 제거하는 방법에 대한 설명이 포함되어 있습니까?",3,"Y","Ref SVP 3. Regression Testing and Re-Review Methods\nIn Section 3, PAL engineers described the Re-Verification, Re-Review, and Regression testing methods, and Verifier verified through Review","Y","Ref SVP 3. Regression Testing and Re-Review Methods\nIn Section 3, PAL engineers described the Re-Verification, Re-Review, and Regression testing methods, and Verifier verified through Review"]
["11.     If partitioning is used, are the methods used to verify the integrity of the partitioning provided?","11. 파티셔닝을 사용하는 경우, 파티셔닝의 무결성을 검증하는 데 사용된 방법이 제공됩니까?",null,"N/A","there is no partitioning ","N/A","there is no partitioning "]
["12.     For previously developed software, is there a description of the methods to satisfy the objectives of DO-278A, if the initial compliance baseline for verification process does not comply?","12. 이전에 개발된 소프트웨어의 경우, 검증 프로세스의 초기 준수 기준이 준수되지 않을 경우 DO-278A의 목표를 충족하는 방법에 대한 설명이 있습니까?",null,"N/A","There is no PDS","N/A","There is no PDS"]
["13.     If multiple-version dissimilar software is planned, is there a description of the software verification process activities?","13. 여러 버전의 서로 다른 소프트웨어를 계획하는 경우, 소프트웨어 검증 프로세스 활동에 대한 설명이 있습니까?",null,"N/A","There is no multiple-version dissimilar software","N/A","There is no multiple-version dissimilar software"]
["14.     If alternative methods used, assurance that the alternative methods satisfy the verification requirements for the software level and verification type of the software? ","14. 대체 방법을 사용하는 경우, 대체 방법이 소프트웨어 레벨 및 검증 유형에 대한 검증 요구 사항을 충족하는지 확인합니까?",null,"N/A","PAL don't apply for alternative methods","N/A","PAL don't apply for alternative methods"]
["15.     Is there a verification method defined to detect object code that is not directly traceable to the source code and to ensure verification of that code?","15. 소스 코드로 직접 추적할 수 없는 객체 코드를 감지하고 해당 코드의 검증을 보장하는 검증 방법이 정의되어 있습니까?",null,"N/A","UTM Service is not analyzed or tracked about Codes because it is AL-4.","N/A","UTM Service is not analyzed or tracked about Codes because it is AL-4."]
["Testing and Review Methodology","테스트 및 검토 방법론"]
["Is there a description of testing methods, including:","다음을 포함하여 테스트 방법에 대한 설명이 있습니까?"]
["16.     The test case selection process and test data to be produced?","16. 테스트 케이스 선택 프로세스 및 생성할 테스트 데이터는 무엇입니까?","2.1.7, 2.1.8, 2.2","Y","Basically, PAL will test using test case on tearget wehre all of test case were based on High level requirements","Y","Basically, PAL will test using test case on tearget wehre all of test case were based on High level requirements"]
["17.     Hardware and software integration testing is performed on the target hardware containing the executable object code?","17. 실행 가능한 객체 코드가 포함된 대상 하드웨어에서 하드웨어 및 소프트웨어 통합 테스트를 수행합니까?",2.2000000000000002,"Y","Ref 2.2\t Software Testing\nEOC is implemented as a HW/SW integrated test by being installed on an actual target. The test cases used here are generated by HLR. \n2.2.2 Integration Testing Depending on the integration testing, integration tests may be conducted by the PM's decision.","Y","Ref 2.2\t Software Testing\nEOC is implemented as a HW/SW integrated test by being installed on an actual target. The test cases used here are generated by HLR. \n2.2.2 Integration Testing Depending on the integration testing, integration tests may be conducted by the PM's decision."]
["18.     If emulator or simulator used, are there considerations for differences between the target computer and the emulator or simulator, and the effects of those differences on the ability to detect errors and verify functionality?","18. 에뮬레이터 또는 시뮬레이터를 사용하는 경우, 대상 컴퓨터와 에뮬레이터 또는 시뮬레이터 간의 차이점과 이러한 차이점이 오류 감지 및 기능 검증 능력에 미치는 영향에 대한 고려 사항이 있습니까?",null,"N/A","PAL will test on Real target","N/A","PAL will test on Real target"]
["19.     Is there justification and identified means to test code that is not identical to the software end item?","19. 소프트웨어 최종 항목과 동일하지 않은 코드를 테스트하는 데 대한 정당성과 식별된 수단이 있습니까?",null,"N/A","All test codes are managed according to the baseline, and there is no reason for the code version to change because the test will be performed through the build procedure and load control with the final code version specified in SCI.","N/A","All test codes are managed according to the baseline, and there is no reason for the code version to change because the test will be performed through the build procedure and load control with the final code version specified in SCI."]
["20.     Are the non-target test environments used? ","20. 비대상 테스트 환경을 사용합니까?",null,"N/A","N/A","N/A","N/A"]
["21.     Is there a justification of the non-target environments? ","21. 비대상 환경에 대한 정당성이 있습니까?",null,"N/A","N/A","N/A","N/A"]
["22.     Are methods or test environment identified for verification of Worst-case execution time, stack usage, memory margins, resource limitations, and the means used for measuring each characteristic?","22. 최악의 경우 실행 시간, 스택 사용량, 메모리 마진, 리소스 제한 및 각 특성을 측정하는 데 사용된 수단을 검증하는 방법이나 테스트 환경이 식별되어 있습니까?","2.3.4, 2.3.5","N/A","UTM is AL-4 so that PALNETWORK don’t apply to these analysis.\nBecause the hardware is a server, it has enough capacity and has enough margin because the amount of memory is more than the processing capacity. Also, since it is Al-4, we are not planning Aanalysis like WCET.","N/A","UTM is AL-4 so that PALNETWORK don’t apply to these analysis.\nBecause the hardware is a server, it has enough capacity and has enough margin because the amount of memory is more than the processing capacity. Also, since it is Al-4, we are not planning Aanalysis like WCET."]
["23.     If Adaption Data Item (ADI) used, is there verification methods defined?","23. 매개변수 데이터 항목(ADI)을 사용하는 경우 검증 방법이 정의되어 있습니까?",null,"N/A","PAL don't apply for ADI ","N/A","PAL don't apply for ADI "]
["24.     If Field-loadable software (FLS), are the verification methods including incorrect operation of mechanism(s) used to confirm the correctness and compatibility of FLS?","24. 필드 로드 가능 소프트웨어(FLS)의 경우, FLS의 정확성과 호환성을 확인하기 위해 사용된 메커니즘의 잘못된 작동을 포함한 검증 방법이 있습니까?",null,"N/A","PLA don't apply for FLS","N/A","PLA don't apply for FLS"]
["25.     Are there Review and Analysis methods (group review, peer review, etc.) defined, including checklists references or environment to be used? ","25. 검토 및 분석 방법(그룹 검토, 동료 검토 등)이 정의되어 있습니까? 체크리스트 참조 또는 사용할 환경이 포함되어 있습니까?",2,"Y","Ref. 2.1.1 Review Methods\nIn 2.1.1 Review Methods, specify group review and peer review. It also specifies which checklists will be used in each review process.","Y","Ref. 2.1.1 Review Methods\nIn 2.1.1 Review Methods, specify group review and peer review. It also specifies which checklists will be used in each review process."]
["Are there considerations for reviews or analysis of:","다음에 대한 검토 또는 분석 고려 사항이 있습니까?"]
["The verifier reviewed the SVP according to the Transition Criteria set in each Review process and Analysis Method.","검증자는 각 검토 프로세스 및 분석 방법에 설정된 전환 기준에 따라 SVP를 검토했습니다.","2.1.2","Y","Ref SVR","Y","Ref SVR"]
["27.     Software architecture?","27. 소프트웨어 아키텍처?","2.1.4","Y","Ref 2.1.4 Software Design Review Process","Y","Ref 2.1.4 Software Design Review Process"]
["28.     System requirements and High-level requirements?","28. 시스템 요구 사항 및 상위 수준 요구 사항?","2.1.3","Y","Ref. 2.1.3 Software Requirement Review Process","Y","Ref. 2.1.3 Software Requirement Review Process"]
["29.     Low-level requirements and Detailed Design?","29. 하위 수준 요구 사항 및 상세 설계?","2.1.4","N/A","AL-4","N/A","AL-4"]
["30.     Source Code?","30. 소스 코드?","2.1.5","N/A","AL-4","N/A","AL-4"]
["31.     Correctness of Adaption Data Item?","31. 매개변수 데이터 항목의 정확성?",null,"N/A","don't apply for ADI","N/A","don't apply for ADI"]
["32.     Software Verification Cases and Procedures?","SVCPs will include specific notion/tags to identify the types of testing are performed when applicable depending on the type of requirement under test:\n","2.1.7","Y","Ref 2.1.7 Test Cases and Procedures Reviews\nRef 2.1.8 Software Verification Results Reviews","Y","Ref 2.1.7 Test Cases and Procedures Reviews\nRef 2.1.8 Software Verification Results Reviews"]
["33.     Test coverage of high-level requirements?","33. 상위 수준 요구 사항의 테스트 커버리지?","2.2.1","Y","Ref 2.3 Software Analysis Methods \nSince UTM Service is AL-4, verify the items in the two Annex tables below.\n- Table A-6: Objectives 1, 2 and 5 for Software with AL-4 designation.\n- Table A-7: Objective 4 for Software with AL-4 designation.\nIn addition, Test Coverage of Requirements comes from executing parent RBTs.","Y","Ref 2.3 Software Analysis Methods \nSince UTM Service is AL-4, verify the items in the two Annex tables below.\n- Table A-6: Objectives 1, 2 and 5 for Software with AL-4 designation.\n- Table A-7: Objective 4 for Software with AL-4 designation.\nIn addition, Test Coverage of Requirements comes from executing parent RBTs."]
["34.     Test coverage of low-level requirements?","34. 하위 수준 요구 사항의 테스트 커버리지?","2.2.3","N/A","Al-4","N/A","Al-4"]
["35.     Traceability Data? ","35. 추적성 데이터?","2.1.4, 2.1.5, 2.1.9","Y","Ref 2.1.9 Traceability Reviews","Y","Ref 2.1.9 Traceability Reviews"]
["36.     Tool Qualification Data / Results? ","36. 도구 검증 데이터/결과?",null,"N/A","PAL don't apply for DO-330, TQ and also PAL already has descirbed in PSAA","N/A","PAL don't apply for DO-330, TQ and also PAL already has descirbed in PSAA"]
["37.     Structural coverage analysis and Results?","37. 구조적 커버리지 분석 및 결과?","2.3.6","N/A","Al-4","N/A","Al-4"]
["38.     Integration Process?","38. 통합 프로세스?","2.1.6","Y","2.2.2 Integration Testing Depending on the integration testing, integration tests may be conducted by the PM's decision.","Y","2.2.2 Integration Testing Depending on the integration testing, integration tests may be conducted by the PM's decision."]

{"sheet":"SCMP","index":4,"n_rows":72,"n_cols":7,"rows_kept":72,"cut":false,"hidden":false,"merged":[]}
["Software Configuration Management Plan Audit Questions"]
[]
[]
[{"$nulls":4},"2025.06.10",null,"2025.06.26"]
["Checklist Item","체크리스트 항목","Reference","Y / N\nNA","Comments/ Action Item #","Y / N\nNA","Comments/ Action Item #"]
["Document Format:","문서 형식:"]
["1.          Is the document under configuration control with an accurate revision history?","1. 문서가 정확한 개정 내역을 포함하여 구성 관리되고 있습니까?",null,"Y","Ref Cover page and Revision section\nSVP docutment was managed by CME and also uploaded to Git-hub\nHowever, UTM Service level is AL-4 so that SVP was not remarked as sepcific version","Y","Ref Cover page and Revision section\nSVP docutment was managed by CME and also uploaded to Git-hub\nHowever, UTM Service level is AL-4 so that SVP was not remarked as sepcific version"]
["2.          Does the title page include program name, document release date, and document identification and revision level?","2. 제목 페이지에 프로그램 이름, 문서 릴리스 날짜, 문서 식별 및 개정 수준이 포함되어 있습니까?",null,"Y","Ref Cover page","Y","Ref Cover page"]
["3.          Is the table of contents and any other applicable tables included and accurate?","3. 목차 및 기타 적용 가능한 표가 포함되어 있으며 정확합니까?",null,"Y","Ref Table of Contents","Y","Ref Table of Contents"]
["4.          Are References, terms and acronyms defined?","4. 참조, 용어 및 약어가 정의되어 있습니까?",null,"Y","Ref. 1.4.1 Acronyms","Y","Ref. 1.4.1 Acronyms"]
["Scope","범위"]
["5.          Are SWCM policies and standards that establish the responsibilities of the SWCM function identified? ","5. SWCM 기능의 책임을 설정하는 SWCM 정책 및 표준이 식별되어 있습니까?",null,"Y","Ref 1.2 Scope","Y","Ref 1.2 Scope"]
["Is there a description or reference of the SCM environment to be used that includes:","사용할 SCM 환경에 대한 설명이나 참조가 있습니까? 다음을 포함합니까?",null,"Y","Ref 2 CM Environment\nPAL have plan to use Git-Hub for managing Life cycle data and REDMINE for managing Problem Reports","Y","Ref 2 CM Environment\nPAL have plan to use Git-Hub for managing Life cycle data and REDMINE for managing Problem Reports"]
["6.          Procedures, Tools, Methods, Standards, Organization, and Interfaces?","6. 절차, 도구, 방법, 표준, 조직 및 인터페이스?",null,"Y","Ref 2 CM Environment\nRef 9.1 Lifecycle Environment Control","Y","Ref 2 CM Environment\nRef 9.1 Lifecycle Environment Control"]
["7.          Software life cycle data controls?","7. 소프트웨어 수명 주기 데이터 제어?",null,"Y","Ref 12 Configuration Management Data\nRef 12.1 Data Control Categories\n12.2 Software Lifecycle Data Category","Y","Ref 12 Configuration Management Data\nRef 12.1 Data Control Categories\n12.2 Software Lifecycle Data Category"]
["8.          Are there Transition criteria for the SCM process?","8. SCM 프로세스에 대한 전환 기준이 있습니까?",null,"Y","Ref 6. Transition Criteria","Y","Ref 6. Transition Criteria"]
["Is there a definition of the software life cycle data produced by the SCM process that includes:","SCM 프로세스에서 생성되는 소프트웨어 수명 주기 데이터에 대한 정의가 있습니까? 다음을 포함합니까?",null,"Y","Ref 12.1 Data Control Categories\nRef 12.2 Software Lifecycle Data Category","Y","Ref 12.1 Data Control Categories\nRef 12.2 Software Lifecycle Data Category"]
["9.          SCM Records?","9. SCM 기록?",null,"Y","12 Configuration Management Data","Y","12 Configuration Management Data"]
["10.       Software Configuration Index?","10. 소프트웨어 구성 색인?",null,"Y","\nRef 9.1 Lifecycle Environment Control\nRef 12 Configuration Management Data","Y","\nRef 9.1 Lifecycle Environment Control\nRef 12 Configuration Management Data"]
["11.       Software Life Cycle Environment Configuration Index?","11. 소프트웨어 수명 주기 환경 구성 색인?",null,"Y","\nRef 9.1 Lifecycle Environment Control\nRef 12 Configuration Management Data","Y","\nRef 9.1 Lifecycle Environment Control\nRef 12 Configuration Management Data"]
["12.       Are there the means of applying SCM process requirements to sub-tier suppliers?","12. 하위 계층 공급업체에 SCM 프로세스 요구 사항을 적용할 수 있는 방법이 있습니까?",null,"Y","12 Configuration Management Data","Y","12 Configuration Management Data"]
["Configuration Identification and Control","구성 식별 및 제어"]
["13.       Will configuration identification be established for the software life cycle data?","13. 소프트웨어 수명 주기 데이터에 대한 구성 식별이 설정됩니까?",null,"N","3.2 Software Identification\n3.3 Product Labeling and Marking \nhowever PAL need to define section 3.1 Configuration Items in detail","Y","3.2 Software Identification\n3.3 Product Labeling and Marking \nPAL identified and numbered the CI for SW. However, the System was excluded because it was not part of their business scope."]
["14.       Will configuration identification be established for each Configuration Item (CI)?","14. 각 구성 항목(CI)에 대한 구성 식별이 설정됩니까?",null,"N","PAL need to define section 3.1 Configuration Items in detail","Y","Ref 3.1 SCMP, Configuration items \nPAL identified and numbered the CI for SW. However, the System was excluded because it was not part of their business scope."]
["Does the plan include:","계획에 다음이 포함되어 있습니까?"]
["15.       Items to be identified? When? Methods?","15. 식별할 항목? 시기? 방법?",null,"N","PAL need to define section 3.1 Configuration Items in detail","Y","Ref 3.1 SCMP, Configuration items \nPAL identified and numbered the CI for SW. However, the System was excluded because it was not part of their business scope."]
["16.       Relationship of software identification and airborne system or equipment identification?","16. 소프트웨어 식별과 항공 시스템 또는 장비 식별의 관계?",null,"N","PAL need to define section 3.1 Configuration Items in detail","Y","Ref 3.1 SCMP, Configuration items \nPAL identified and numbered the CI for SW. However, the System was excluded because it was not part of their business scope."]
["Are methods and controls described that ensure:","다음을 보장하는 방법 및 제어가 설명되어 있습니까?"]
["17.       Each item has a unique identifier, including version? ","17. 각 항목에 버전을 포함한 고유 식별자가 있습니까?",null,"Y","Refer to PSAC Section 6 SW Life cycle data where PAL described unique identifier","Y","Refer to PSAC Section 6 SW Life cycle data where PAL described unique identifier"]
["18.       The version indicator is changed when the item is changed?  ","18. 항목이 변경되면 버전 표시기가 변경됩니까?",null,"Y","When an item changes, it is changed to the appropriate version according to the Change Control Change Review.","Y","When an item changes, it is changed to the appropriate version according to the Change Control Change Review."]
["19.       Each baseline has a unique identifier? ","19. 각 기준선에 고유 식별자가 있습니까?",null,"Y","Ref 4 Baselines, Releases and Traceability","Y","Ref 4 Baselines, Releases and Traceability"]
["20.       When changes are made to a released software CI, the identifiers of higher level CIs and assemblies are changed, up to and including the level where interchangeability is established?  ","20. 릴리스된 소프트웨어 CI가 변경되면 호환성이 확립된 수준까지 상위 CI 및 어셈블리의 식별자가 변경됩니까?",null,"N","PAL need to define section 3.1 Configuration Items in detail","Y","Ref 3.1 SCMP, Configuration items \nPAL identified and numbered the CI for SW. However, the System was excluded because it was not part of their business scope."]
["Problem Report Resolution","문제 보고서 해결 방법"]
["26.       Will a problem report be prepared that describes the process non-compliance with plans, output deficiencies, software anomalous behavior, or audit discrepancies, and the corrective action taken?","26.       계획 위반, 출력 결함, 소프트웨어 이상 동작 또는 감사 불일치 사항과 취해진 시정 조치를 설명하는 문제 보고서를 작성합니까?",null,"Y","Ref 6 Problem Reporting","Y","Ref 6 Problem Reporting"]
["27.       Will problem reporting provide for configuration identification of affected CIs, or definition of affected process activities, status reporting of problem reports, and approval and closure of problem reports?","27.       문제 보고에서 영향을 받는 CI의 구성 식별, 영향을 받는 프로세스 활동 정의, 문제 보고서의 상태 보고, 문제 보고서의 승인 및 마감을 제공합니까?",null,"Y","Ref 6 Problem Reporting","Y","Ref 6 Problem Reporting"]
["28.       Will problem reports requiring corrective action of the software or outputs of life cycle processes invoke change control activity?","28.       소프트웨어 또는 수명 주기 프로세스의 출력에 대한 시정 조치를 요구하는 문제 보고서가 변경 제어 활동을 유발합니까?",null,"Y","Ref 7.1  Problem Reporting Lifecycle","Y","Ref 7.1  Problem Reporting Lifecycle"]
["Change Control","변경 제어"]
["29.       Will change control preserve the integrity of the CIs/baselines by providing protection against change?","29.       변경 제어는 변경으로부터 보호하여 CI/기준선의 무결성을 유지합니까?",null,"Y","Ref 8 Change Control and Change Review","Y","Ref 8 Change Control and Change Review"]
["Are methods and controls described that ensure that when an item under Change Control is updated:","변경 제어 중인 항목이 업데이트될 때 다음을 보장하는 방법과 제어가 설명되어 있습니까?",null,"Y","Ref 8 Change Control and Change Review","Y","Ref 8 Change Control and Change Review"]
["30.       Changes to items are traceable to a previous item by authorized PRs through the change history of the affected items?","30.       영향을 받는 항목의 변경 내역을 통해 승인된 PR이 항목 변경 사항을 이전 항목으로 추적할 수 있습니까?",null,"Y","Ref 8 Change Control and Change Review","Y","Ref 8 Change Control and Change Review"]
["31.       Only authorized changes were made to controlled items?","31.       제어되는 항목에 승인된 변경만 적용되었습니까?",null,"Y","Ref 8 Change Control and Change Review","Y","Ref 8 Change Control and Change Review"]
["32.       The item's identification and status accounting data are updated?","32.       항목의 식별 및 상태 회계 데이터가 업데이트됩니까?",null,"Y","Ref 8 Change Control and Change Review","Y","Ref 8 Change Control and Change Review"]
["33.       Will software changes be traced to their origin and the software life cycle processes repeated from the point at which the change affects their outputs?","33.       소프트웨어 변경 사항은 출처까지 추적되고 변경 사항이 출력에 영향을 미치는 지점부터 소프트웨어 수명 주기 프로세스가 반복됩니까?",null,"Y","Ref 8 Change Control and Change Review","Y","Ref 8 Change Control and Change Review"]
["34.       Throughout the change activity, will software life cycle data affected by the change be updated and will the records be maintained for the change control activity?","34.       변경 활동 전체에서 변경의 영향을 받는 소프트웨어 수명 주기 데이터가 업데이트되고 변경 제어 활동을 위해 기록이 유지됩니까?",null,"Y","Ref 8 Change Control and Change Review","Y","Ref 8 Change Control and Change Review"]
["Change Review","변경 검토"]
["Will the change review activity include:","변경 검토 활동에는 다음이 포함됩니까?",null,"Y","Ref 8 Change Control and Change Review","Y","Ref 8 Change Control and Change Review"]
["38.       Confirmation that affected CIs are configuration identified?","38. 영향을 받는 CI가 구성에서 식별되었는지 확인합니까?",null,"Y","Ref 8 Change Control and Change Review","Y","Ref 8 Change Control and Change Review"]
["39.       Assessment of the impact on safety-related requirements with feedback to the system safety assessment process?","39. 시스템 안전 평가 프로세스에 대한 피드백과 함께 안전 관련 요구 사항에 미치는 영향 평가?",null,"Y","Ref 8 Change Control and Change Review","Y","Ref 8 Change Control and Change Review"]
["40.       Assessment of the problem or change, with decisions for actions to be taken?  Feedback?","40. 문제 또는 변경 평가 및 취해야 할 조치에 대한 결정? 피드백?",null,"Y","Ref 8 Change Control and Change Review","Y","Ref 8 Change Control and Change Review"]
["Configuration Status Accounting and Reporting","구성 상태 회계 및 보고"]
["43.       Reporting on CI identification, baseline identification, problem report status, change history, and release status?","43. CI 식별, 기준선 식별, 문제 보고 상태, 변경 내역 및 릴리스 상태에 대한 보고?",null,"Y","Ref 9. onfiguration Status Accounting","Y","Ref 9. onfiguration Status Accounting"]
["44.       Definition of the data to be maintained and the means of recording and reporting status of this data?","44. 유지 관리해야 할 데이터의 정의와 이 데이터의 상태를 기록하고 보고하는 수단은 무엇입니까?",null,"Y","Ref 9. onfiguration Status Accounting","Y","Ref 9. onfiguration Status Accounting"]
["Does the plan include:","계획에 다음이 포함되어 있습니까?",null,"Y","Ref 9. onfiguration Status Accounting","Y","Ref 9. onfiguration Status Accounting"]
["45.       The data to be recorded to enable reporting configuration management status?  Where kept?  How retrieved?","45. 구성 관리 상태 보고를 위해 기록해야 할 데이터는 무엇입니까? 어디에 보관합니까? 어떻게 검색합니까?",null,"Y","Ref 9. onfiguration Status Accounting","Y","Ref 9. onfiguration Status Accounting"]
["Baselines and Traceability","기준선 및 추적성"]
["46.       Will a baseline be traceable to the baseline from which it was derived if certification credit is sought?","46. 인증 크레딧을 신청하는 경우 기준선을 파생된 기준선까지 추적할 수 있습니까?",null,"Y","Ref. 4 Baselines, Releases and Traceability","Y","Ref. 4 Baselines, Releases and Traceability"]
["47.       Will a CI be traceable to the CI from which it was derived, if certification credit is sought?","47. 인증 크레딧을 신청하는 경우 CI를 파생된 CI까지 추적할 수 있습니까?",null,"Y","Ref. 4 Baselines, Releases and Traceability","Y","Ref. 4 Baselines, Releases and Traceability"]
["48.       Will a baseline or CI be traceable either to the output it identifies or to the process with which it is associated?","48. 기준선 또는 CI를 식별하는 출력 또는 연관된 프로세스까지 추적할 수 있습니까?",null,"Y","Ref. 4 Baselines, Releases and Traceability","Y","Ref. 4 Baselines, Releases and Traceability"]
["Archive, Retrieval and Release","보관, 검색 및 릴리스"]
["51.       Will software life cycle data associated with the product be retrievable from the approved source?","51.       제품과 관련된 소프트웨어 수명 주기 데이터를 승인된 소스에서 검색할 수 있습니까?",null,"Y","Ref 4 Baselines, Releases and Traceability\nRef 8.1.1 Storage, Handling, and Delivery of Project Media\nRef 8.1.2 Backup Security","Y","Ref 4 Baselines, Releases and Traceability\nRef 8.1.1 Storage, Handling, and Delivery of Project Media\nRef 8.1.2 Backup Security"]
["Will procedures be established to ensure the integrity of the stored data by:","다음과 같이 저장된 데이터의 무결성을 보장하는 절차를 수립합니까?",null,"Y","Ref 4 Baselines, Releases and Traceability\nRef 8.1.1 Storage, Handling, and Delivery of Project Media\nRef 8.1.2 Backup Security","Y","Ref 4 Baselines, Releases and Traceability\nRef 8.1.1 Storage, Handling, and Delivery of Project Media\nRef 8.1.2 Backup Security"]
["52.       Ensuring that no unauthorized changes can be made?","52.       무단 변경이 불가능하도록 보장합니까?",null,"Y","Ref 4 Baselines, Releases and Traceability\nRef 8.1.1 Storage, Handling, and Delivery of Project Media\nRef 8.1.2 Backup Security","Y","Ref 4 Baselines, Releases and Traceability\nRef 8.1.1 Storage, Handling, and Delivery of Project Media\nRef 8.1.2 Backup Security"]
["53.       Will the duplication process be verified to produce accurate copies, and procedures exist that ensure error-free copying of the Executable Object Code?","53.       정확한 사본을 생성하기 위해 복제 프로세스를 검증합니까? 그리고 실행 가능 객체 코드의 오류 없는 복사를 보장하는 절차가 있습니까?",null,"Y","Ref 4 Baselines, Releases and Traceability\nRef 8.1.1 Storage, Handling, and Delivery of Project Media\nRef 8.1.2 Backup Security","Y","Ref 4 Baselines, Releases and Traceability\nRef 8.1.1 Storage, Handling, and Delivery of Project Media\nRef 8.1.2 Backup Security"]
["54.       Will CIs be identified and released prior to use of software manufacture and the authority for their release are established?","54.       소프트웨어 제조에 사용되기 전에 CI를 식별하고 릴리스하고 릴리스에 대한 권한을 설정합니까?",null,"Y","Ref 4 Baselines, Releases and Traceability\nRef 8.1.1 Storage, Handling, and Delivery of Project Media\nRef 8.1.2 Backup Security","Y","Ref 4 Baselines, Releases and Traceability\nRef 8.1.1 Storage, Handling, and Delivery of Project Media\nRef 8.1.2 Backup Security"]
["55.       Will data retention procedures be established to satisfy airworthiness requirements and enable software modifications?","55.       항공 안전 요건을 충족하고 소프트웨어 수정을 가능하게 하기 위해 데이터 보존 절차를 수립합니까?",null,"Y","Ref 4 Baselines, Releases and Traceability\nRef 8.1.1 Storage, Handling, and Delivery of Project Media\nRef 8.1.2 Backup Security","Y","Ref 4 Baselines, Releases and Traceability\nRef 8.1.1 Storage, Handling, and Delivery of Project Media\nRef 8.1.2 Backup Security"]
["Software Load Control","소프트웨어 부하 제어"]
["57.       Will records be kept that confirm software compatibility with the airborne system or equipment hardware?","57.        항공 시스템 또는 장비 하드웨어와의 소프트웨어 호환성을 확인하는 기록을 보관합니까?",null,"Y","Ref 11 Load Control","Y","Ref 11 Load Control"]
["58.       Does the plan include a description of the software load control safeguards and records?","58. 계획에 소프트웨어 부하 제어 안전장치 및 기록에 대한 설명이 포함되어 있습니까?",null,"Y","Ref 11 Load Control","Y","Ref 11 Load Control"]
["Software Life Cycle Environment Control","소프트웨어 수명 주기 환경 제어"]
["59.       Will configuration identification and controls be established for the Executable Object Code (or equivalent) of the tools used to develop, control, build, verify, and load software?","59. 소프트웨어 개발, 제어, 빌드, 검증 및 로드에 사용되는 도구의 실행 가능 객체 코드(또는 이에 상응하는 코드)에 대한 구성 식별 및 제어가 수립됩니까?",null,"Y","Ref 9.1 Lifecycle Environment Control","Y","Ref 9.1 Lifecycle Environment Control"]
["60.       Will tool qualification data be controlled as CC1 for software development tools?","60. 소프트웨어 개발 도구의 도구 적격성 데이터는 CC1로 관리됩니까?",null,"Y","Ref 9.1 Lifecycle Environment Control","Y","Ref 9.1 Lifecycle Environment Control"]
["61.       Will tool qualification data be controlled as CC2 for software verification tools?","61. 소프트웨어 검증 도구의 도구 적격성 데이터는 CC2로 관리됩니까?",null,"Y","Ref 9.1 Lifecycle Environment Control","Y","Ref 9.1 Lifecycle Environment Control"]

{"sheet":"SQAP","index":5,"n_rows":38,"n_cols":7,"rows_kept":38,"cut":false,"hidden":false,"merged":[]}
["Software Qualification Assurance Plan Audit Questions"]
[]
[]
[{"$nulls":4},"2025.06.10",null,"2025.06.26"]
["Checklist Item","체크리스트 항목","Reference","Y / N\nNA","Comments/ Action Item #","Y / N\nNA","Comments/ Action Item #"]
["Configuration Aspects","구성 측면"]
["Have the following Configuration aspects of this plan been achieved?","이 계획의 다음 구성 측면이 달성되었습니까?"]
["1.        Is the document Revision/Baseline under Configuration?","1.        문서 개정/기준선이 구성 단계에 있습니까?",null,"Y","Ref Cover page and Revision section\nSVP docutment was managed by CME and also uploaded to Git-hub\nHowever, UTM Service level is AL-4 so that SVP was not remarked as sepcific version","Y","Ref Cover page and Revision section\nSVP docutment was managed by CME and also uploaded to Git-hub\nHowever, UTM Service level is AL-4 so that SVP was not remarked as sepcific version"]
["2.        Were the related plans (PSAC, SCMP, SQAP, SDP) configured before updating or developing this Data Item?","2.        이 데이터 항목을 업데이트하거나 개발하기 전에 관련 계획(PSAC, SCMP, SQAP, SDP)이 구성되었습니까?",null,"Y","Yes. After developing PSAC, SDP, SCMP ,SQAP and Standard, All of data were verified by Verifier according to SVP.","Y","Yes. After developing PSAC, SDP, SCMP ,SQAP and Standard, All of data were verified by Verifier according to SVP."]
["3.        Does the title page include Program/Project name, document release date, and document identification?","3.        제목 페이지에 프로그램/프로젝트 이름, 문서 발표일 및 문서 식별 정보가 포함되어 있습니까?",null,"Y","Ref Cover page","Y","Ref Cover page"]
["4.        Is the table of contents and any other applicable tables included and accurate?","4.        목차 및 기타 적용 가능한 표가 포함되어 있으며 정확합니까?",null,"Y","Ref Table of Contents","Y","Ref Table of Contents"]
["5.        Are References stated, terms and acronyms defined?","5.        참조가 명시되어 있고 용어 및 약어가 정의되어 있습니까?",null,"Y","Ref. 1.4.1 Acronyms","Y","Ref. 1.4.1 Acronyms"]
["SQAP Details","SQAP 세부 정보"]
["Does the SQAP include or reference the following methods/processes?","SQAP에 다음 방법/프로세스가 포함되거나 참조됩니까?"]
["6.        Does the SQA follow any Organizational Level Procedures and Standards?","6.        SQA는 조직 수준의 절차 및 표준을 준수합니까?",null,"Y","Ref 2.3\tQA Responsibilities\nQAE performs audits according to established procedures of DO-278A standard in accordance with SQAP.","Y","Ref 2.3\tQA Responsibilities\nQAE performs audits according to established procedures of DO-278A standard in accordance with SQAP."]
["7.        Does the SQA follow any recognized international standards such as CMMI / ISO / IEC?","7. SQA는 CMMI/ISO/IEC와 같은 공인된 국제 표준을 준수합니까?",null,"N/A","N/A","N/A","N/A"]
["8.        SQA environment, including scope?  ","8. SQA 환경(범위 포함)은 무엇입니까?",null,"Y","Ref 2. Quality Assurance Environment\nPAL Described QA Organization, Responsibility, Interface, Methods, and Tools.","Y","Ref 2. Quality Assurance Environment\nPAL Described QA Organization, Responsibility, Interface, Methods, and Tools."]
["9.        Organizational responsibilities and interfaces?  ","9. 조직의 책임 및 인터페이스는 무엇입니까?",null,"Y","Ref. 2.2 QA Interfaces\nQA has interfaces with all departments in general\nIt is related to Developer, Verifier, CM, CA, Supplier (PAL does not have Supplier, but it is specified for scalability).\nIn addition, QA adheres to QA Procedure and Standard, and QAE establish QAR according to the process specified in DO-278A.","Y","Ref. 2.2 QA Interfaces\nQA has interfaces with all departments in general\nIt is related to Developer, Verifier, CM, CA, Supplier (PAL does not have Supplier, but it is specified for scalability).\nIn addition, QA adheres to QA Procedure and Standard, and QAE establish QAR according to the process specified in DO-278A."]
["10.        Standards, procedures, tools? ","10. 표준, 절차, 도구는 무엇입니까?",null,"Y","Ref. 2.4 QA Methods and 2.5 Tools","Y","Ref. 2.4 QA Methods and 2.5 Tools\nAlthough the content on tools was referenced in SCI, the tools used by QA were specified again according to DER's comments."]
["11.        A statement of the SQA authority, responsibility, and independence?","11. SQA 권한, 책임 및 독립성에 대한 설명은 무엇입니까?",null,"Y","Ref. 2.3 QA Responsibilities and 3 QA Authority\nQA is ultimately responsible for auditing all deliverables for process compliance. Because of this enormous responsibility, QA has the authority as outlined in section 3.","Y","Ref. 2.3 QA Responsibilities and 3 QA Authority\nQA is ultimately responsible for auditing all deliverables for process compliance. Because of this enormous responsibility, QA has the authority as outlined in section 3."]
["12.        SQA approval of software products?","12. 소프트웨어 제품에 대한 SQA 승인은 무엇입니까?",null,"Y","Finally, QA reviews all deliverables and signs them as proof of approval and also creates Conformity Review at the end","Y","Finally, QA reviews all deliverables and signs them as proof of approval and also creates Conformity Review at the end"]
["13.        SQA methods (reviews, audits, reporting, inspections)?","13. SQA 방법(검토, 감사, 보고, 검사)은 무엇입니까?",null,"Y","Ref 2.4 QA Methods","Y","Ref 2.4 QA Methods"]
["14.        Activities related to the problem reporting and change control (CCB)?","14. 문제 보고 및 변경 관리(CCB)와 관련된 활동은 무엇입니까?",null,"Y","Ref 2.3 QA Responsibilities, 2.4 QA Methods and 3.1 QA Approvals\nQAE is the member of CCB so that QAE have to participate in CCB meeting when as applicable","Y","Ref 2.3 QA Responsibilities, 2.4 QA Methods and 3.1 QA Approvals\nQAE is the member of CCB so that QAE have to participate in CCB meeting when as applicable"]
["15.     Details of software conformity review activity / process?","15. 소프트웨어 적합성 검토 활동/프로세스에 대한 세부 정보는 무엇입니까?",null,"Y","Ref 4.6.2 Conformity Review \nQAE should establish a conformance review at the SOI#4 stage where QA compliance audit is conducted. The conformance review should also include a final audit of all deliverables, classification of PSAA and SAS changes, SCI updates, Open PRs issues, and Build & Load Control as well as witness results for tests.","Y","Ref 4.6.2 Conformity Review \nQAE should establish a conformance review at the SOI#4 stage where QA compliance audit is conducted. The conformance review should also include a final audit of all deliverables, classification of PSAA and SAS changes, SCI updates, Open PRs issues, and Build & Load Control as well as witness results for tests."]
["16.     Transition criteria for entering the SQA process?","16. SQA 프로세스 진입을 위한 전환 기준은 무엇입니까?",null,"Y","Ref 5 Transition Criteria","Y","Ref 5 Transition Criteria"]
["17.     Does the timing of the SQA process activities relates to those defined in SDP, SVP and SCMP?","17. SQA 프로세스 활동의 시기가 SDP, SVP 및 SCMP에 정의된 시기와 관련이 있습니까?",null,"Y","Ref 6. Timing","Y","Ref 6. Timing"]
["18.     Is there a clear list of deliverables produced by the SQA process?","18. SQA 프로세스에서 생성된 결과물의 명확한 목록이 있습니까?",null,"Y","Ref 7. QA Records","Y","Ref 7. QA Records"]
["19.     Are there means of ensuring that suppliers’ processes and outputs will comply with the plans and standards?","19. 공급업체의 프로세스와 산출물이 계획 및 표준을 준수하도록 보장하는 수단이 있습니까?",null,"N/A","PAL don't cowork with suppliers","N/A","PAL don't cowork with suppliers"]
["SQA Process Definition:  ","SQA 프로세스 정의:"]
["20.        Does SQA process plan on reviewing Software plans and standards for compliance with DO-278A and consistency?  ","20. SQA 프로세스는 DO-278A 준수 및 일관성을 위해 소프트웨어 계획 및 표준을 검토할 계획입니까?",null,"Y","SQAR is recored by QAE and SQAR is created according to SQAP as well","Y","SQAR is recored by QAE and SQAR is created according to SQAP as well"]
["21.        Does the SQA process include audits of the software life cycle processes during the software life cycle?  ","21. SQA 프로세스에 소프트웨어 수명 주기 동안 소프트웨어 수명 주기 프로세스에 대한 감사가 포함되어 있습니까?",null,"Y","Ref. 4.6.1 Stages of Involvements (SOI)","Y","Ref. 4.6.1 Stages of Involvements (SOI)"]
["22.        Are the frequency or depth of SQA Audits identified?","22. SQA 감사의 빈도 또는 깊이가 식별되어 있습니까?",null,"Y","Ref 4 Activities\nQAE is assigned to each stage phase to write QAR. If PR is issued for each stage, an audit is conducted to see if the PR has been properly modified.","Y","Ref 4 Activities\nQAE is assigned to each stage phase to write QAR. If PR is issued for each stage, an audit is conducted to see if the PR has been properly modified."]
["23.        Does the SQA process allow to detect and track deviations from the software plans and standards?","23. SQA 프로세스를 통해 소프트웨어 계획 및 표준과의 편차를 감지하고 추적할 수 있습니까?",null,"Y","Requirement deviations are recorded and approved using the Problem Reporting system\nQA have to Audit of Trace Data from SRD to SES , SRD to SVCP, SVCP to Test Reulst\nVerifier has verified through review that these contents are written throughout the SQAP.","Y","Requirement deviations are recorded and approved using the Problem Reporting system\nQA have to Audit of Trace Data from SRD to SES , SRD to SVCP, SVCP to Test Reulst\nVerifier has verified through review that these contents are written throughout the SQAP."]
["24.        Is there a correlation of SQA activity with SCM for problem reporting, tracking, and corrective action process? ","24.         문제 보고, 추적 및 시정 조치 프로세스를 위한 SQA 활동과 SCM 사이에 상관 관계가 있습니까?",null,"Y","YES, 2\tQuality Assurance Environment, 3.1 QA Approvals and 4 QA Activities\nThrough the above reference, QA has the responsibility to audit the activities of CM.","Y","YES, 2\tQuality Assurance Environment, 3.1 QA Approvals and 4 QA Activities\nThrough the above reference, QA has the responsibility to audit the activities of CM."]
["25.        Is there a method for SQA to be involved in system processes, including the system safety assessment process?","25.        시스템 안전 평가 프로세스를 포함하여 SQA가 시스템 프로세스에 참여할 수 있는 방법이 있습니까?",null,"N/A","PAL don't apply for ARP 4754B so that PAL didn't describe it\nHowever, They analyzed safety aspects for FHA to determine SW level(AL-4,5,6)","N/A","PAL don't apply for ARP 4754B so that PAL didn't describe it\nHowever, They analyzed safety aspects for FHA to determine SW level(AL-4,5,6)"]
["26.        Does the SQA process provide assurance that software life cycle data is controlled in accordance with the control categories as defined in section 7.3 of DO-278A?","26.        SQA 프로세스는 DO-278A의 섹션 7.3에 정의된 제어 범주에 따라 소프트웨어 수명 주기 데이터가 제어된다는 보증을 제공합니까?",null,"Y","CC2","Y","CC2"]
["27.        Is SQA involved prior to the delivery of software products submitted as part of a certification application (minimum software conformity review)?","27.        인증 신청(최소 소프트웨어 적합성 검토)의 일부로 제출된 소프트웨어 제품을 제공하기 전에 SQA가 참여합니까?",null,"Y","Ref 4.6 Compliance Audits","Y","Ref 4.6 Compliance Audits"]
["28.        Does SQA have authority and independence to stop the software development process due to major deviations until such deviations are corrected?","28.        SQA는 주요 편차가 수정될 때까지 소프트웨어 개발 프로세스를 중단할 권한과 독립성이 있습니까?",null,"Y","Ref 3 QA Authority","Y","Ref 3 QA Authority"]

{"sheet":"Standards","index":6,"n_rows":49,"n_cols":6,"rows_kept":49,"cut":false,"hidden":false,"merged":[[27,0,27,3],[34,0,34,3],[35,0,35,3],[46,0,46,3],[16,0,16,3],[21,0,21,3],[22,0,22,3],[0,0,1,3],[4,0,4,3],[5,0,5,3],[11,0,11,3],[12,0,12,3]]}
["Software Standards Audit Questions"]
[]
[null,null,null,"2025.06.10",null,"2025.06.26"]
["Checklist Item","Reference","Y / N\nNA","Comments/ Action Item #","Y / N\nNA","Comments/ Action Item #"]
["Configuration Aspects"]
["Have the following Configuration aspects of Standards been achieved?"]
["1.        Is the document Revision/Baseline under Configuration?",null,"Y","Draft version","Y","Draft version"]
["2.        Were the related plans (PSAC, SCMP, SQAP, SDP) configured before updating or developing this Data Item?",null,"Y","PSAC, SCMP, SQAP, SDP, SVP are all Draft versions","Y","PSAC, SCMP, SQAP, SDP, SVP are all Draft versions"]
["3.        Does the title page include Program/Project name, document release date, and document identification?",null,"Y","The program name and document identification information are written on the cover, and the document publication date is written in the Documents Approval table","Y","The program name and document identification information are written on the cover, and the document publication date is written in the Documents Approval table"]
["4.        Is the table of contents and any other applicable tables included and accurate?",null,"Y","The text, figures, and table of contents are written, and the Applicable Documents table exists","Y","The text, figures, and table of contents are written, and the Applicable Documents table exists"]
["5.        Are References stated, terms and acronyms defined?",null,"Y","References, terms, and abbreviations are written","Y","References, terms, and abbreviations are written"]
["Software Standards Compliance"]
["High-level Requirements Standards"]
["6.        Do software requirement standards exist that comply with DO-278A?  ","FMSHDBK2508","Y","Ref SRS","Y","Ref SRS"]
["7.        Are there defined constraints on the use of requirements tools?  ",4,"Y","Ref SRS","Y","Ref SRS"]
["8.        Are there defined methods to be used for developing software requirements, such as structured methods.?",2,"Y","2. There are descriptions of syntax guidelines and each characteristic required when developing requirements in Requirements","Y","2. There are descriptions of syntax guidelines and each characteristic required when developing requirements in Requirements"]
["Are there notations / traceability to describe:"]
["9.        Allocation to system requirements?","2.2.7","Y","1.2 Scope contains the content \"This document contains a System Requirements Specification section for writing system requirements. The system requirements have the same scope as the high-level software requirements\"","Y","1.2 Scope contains the content \"This document contains a System Requirements Specification section for writing system requirements. The system requirements have the same scope as the high-level software requirements\""]
["10.     Software low-level requirements and high-level tests?  ","2.2.7.1","Y","Notation for High-level, tracing method, notation for test cases, tracing method","Y","Notation for High-level, tracing method, notation for test cases, tracing method"]
["11.     Derived requirements?  ",3.2,"Y","Notation for Derived Requirements","Y","Notation for Derived Requirements"]
["12.     Are there naming conventions for requirements?  ","2.2.7.1","N","Notation for High-level Requirements","Y","PAL sets identifier assignment(ID) rules for System, HLR, and Derived Requirements."]
["Design Standards Compliance"]
["For low-level requirements, are there notations used to describe: "]
["13.     Low-level Requirements?  ",1.2,"Y","Al-4","Y","Al-4"]
["14.     Derived low-level requirements?  ",1.2,"Y","Al-4","Y","Al-4"]
["15.     Traceability to high-level requirements?  ",1.2,"Y","Al-4","Y","Al-4"]
["16.     Traceability to low-level tests?  ",1.2,"Y","Al-4","Y","Al-4"]
["For the design, is there a description of:"]
["17.     Conditions on design methods?","5.1, 6","Y","5.1 Component definition of Software Design contains criteria that must be met when designing software, 6. Design General Guidelines contains guidelines that must be followed when designing","Y","5.1 Component definition of Software Design contains criteria that must be met when designing software, 6. Design General Guidelines contains guidelines that must be followed when designing"]
["18.     Naming conventions to be used?",null,"Y","There are no naming rules or notations related to design","Y","There are no naming rules or notations related to design"]
["19.     Conditions imposed on permitted design methods, for example, scheduling, and the use of interrupts and event-driven architectures, dynamic tasking, re-entry, global data, and exception handling, and rationale for their use?",6,"Y","Design General Guidelines contains guidelines that must be followed when designing","Y","Design General Guidelines contains guidelines that must be followed when designing"]
["20.     Constraints on the use of design tools?   ","1.1.","Y","Ref 8. CONSTRAINTS ON DESIGN TOOLS","Y","Ref 8. CONSTRAINTS ON DESIGN TOOLS"]
["21.     Constraints on design, for example, exclusion of recursion, dynamic objects, data aliases, and compacted expressions?","1.1.","Y","Ref 9. CONSTRAINTS ON DESIGN","Y","Ref 9. CONSTRAINTS ON DESIGN"]
["22.     Complexity restrictions, for example, maximum level of nested calls or conditional structures, use of unconditional branches, and number of entry/exit points of code components?","1.1.","Y","Ref 10. COMPLEXITY RESTRICTIONS","Y","Ref 10. COMPLEXITY RESTRICTIONS"]
["Coding Standards"]
["Does the Coding Standard provide?"]
["23.     Programming language(s) to be used and/or defined subset(s)?  ",7,"N/A","AL-4","N/A","AL-4"]
["24.     Reference the data that unambiguously defines the syntax, the control behavior, the data behavior, and side-effects of the language?",null,"N/A","AL-4","N/A","AL-4"]
["25.     Limitation of some features of a language? ",null,"N/A","AL-4","N/A","AL-4"]
["26.     Source Code presentation standards / style? ",7.2,"N/A","AL-4","N/A","AL-4"]
["27.     Name of author, revision history?",null,"N/A","AL-4","N/A","AL-4"]
["28.     Naming conventions for components, subprograms, variables, and constants?  ",7.2,"N/A","AL-4","N/A","AL-4"]
["29.     Conditions and constraints imposed on permitted coding conventions?  ",null,"N/A","AL-4","N/A","AL-4"]
["30.     Constraints on the use of the coding tools?  ",9,"N/A","AL-4","N/A","AL-4"]
["31.     Does the coding standard follow any known industry standards such as Misra?",1.1000000000000001,"N/A","AL-4","N/A","AL-4"]
["32.     Are the coding rules uniquely identified?","APPENDIX A","N/A","AL-4","N/A","AL-4"]
["For source code traceability, are there notations used to describe: "]
["33.     Low-level Requirements?  ","7.9.2.1, 7.9.2.2","N/A","AL-4","N/A","AL-4"]
["34.     Traceability to the module level or file level?  ",null,"N/A","AL-4","N/A","AL-4"]

{"sheet":"SRD","index":7,"n_rows":72,"n_cols":6,"rows_kept":72,"cut":false,"hidden":false,"merged":[[4,1,5,1],[4,0,5,0],[4,2,5,2],[4,3,5,3],[23,2,28,2],[23,3,28,3],[2,3,3,5],[23,5,28,5],[29,2,32,2],[29,3,32,3],[29,4,32,4],[29,5,32,5],[23,4,28,4]]}
["Software Requirement Data Question"]
[]
[null,null,null,"2026.02.06\nSRD ver 0.1"]
[]
["Checklist Item","Korean","Ref.","Applicable DAL","Y / N","Comments /"]
[{"$nulls":4},"NA","Action Item #"]
["Configuration Aspects"]
["Have the following Configuration aspects of High-Level Requirements (HLR) Data Item been achieved?","다음과 같은 상위 수준 요구사항(HLR) 데이터 항목의 구성 측면이 충족되었습니까?"]
["1.          Is the document Revision/Baseline under Configuration?","1. 문서의 개정/기준선이 구성 중입니까?","7.2.1.a, b, c","A, B, C, D","Y","Upload to Git-lab PAL_SW_SRD_v0.1"]
["2.          Were the related System Requirement Spec. configured before updating or developing this Data Item?","2. 이 데이터 항목을 업데이트하거나 개발하기 전에 관련 시스템 요구사항 사양이 구성되었습니까?","7.2.1.d","A, B, C, D","Y","Refer to PAL_SW_SES"]
["3.          Does the title page include Program/Project name, document release date, and document identification?","3. 표지에 프로그램/프로젝트 이름, 문서 배포일 및 문서 식별 정보가 포함되어 있습니까?",null,null,"Y","Refer to Cover Tap of PAL_SW_SRD "]
["4.          Are the table of contents and any other applicable tables (table of figures, table of tables, table of equations, etc...) included and accurate?","4. 목차 및 기타 관련 표(그림 표, 표의 표, 수식 표 등)가 포함되어 있고 정확합니까?",null,null,"NA"," The form is different"]
["5.          Are References stated, terms and acronyms defined?","5. 참조가 명시되어 있고 용어 및 약어가 정의되어 있습니까?",null,null,"NA","Refer to 01_PAL_SW_PSAA_20250625, The form is different"]
["Systems Aspects"]
["System Specification Readiness:"]
["6.          Is he system specification been reviewed to show functional and interface requirements that are allocated to software been analyzed for ambiguities, inconsistencies, and undefined conditions?","6. 시스템 명세 검토를 통해 소프트웨어에 할당된 기능 및 인터페이스 요구사항이 모호성, 불일치 및 정의되지 않은 조건에 대해 분석되었는지 확인했습니까?","5.1.2.a","A, B, C, D","Y","Refer to SFR-002 of PAL_SW_SES and SW-HLR-REQ-001 of PAL_SW_SRD"]
["7.          Has issues related to System Specification been detected and captured in a Change Control process?","7. 시스템 명세와 관련된 문제가 발견되어 변경 관리 프로세스에 반영되었습니까?","5.1.2.b","A, B, C, D","Y","Refer to PAL_SES ECR-002-026 of System Equipment Requirements "]
["8.          Has each system requirement that is allocated to software should be specified in the high-level requirements?","8. 소프트웨어에 할당된 각 시스템 요구사항이 상위 수준 요구사항에 명시되어 있습니까?","5.1.2.c","A, B, C, D","Y","Refer to PAL_SES"]
["Are the following requirements defined for each operating mode of the software?"]
["9.          Initialization & Power-up?  ","9. 초기화 및 전원 켜기?","6.3.3, 6.3.4,  ","A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]
["10.       Self-test, Function, and Performance?","10. 자체 테스트, 기능 및 성능?","4.4.2, 4.4.3","A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]
["11.       Are partitioning criteria and requirements for both physical and logical partitioning of the software and hardware defined?  ","11. 소프트웨어 및 하드웨어의 물리적 및 논리적 파티셔닝에 대한 파티셔닝 기준 및 요구 사항이 정의되어 있습니까?","11.9.d","A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]
["Are there target computer related requirements addressing the following:"]
["12.       Target:",null,"6.3.1","A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]
["a.      Central processing unit?","a. 중앙 처리 장치(CPU)?"]
["b.      Memory (type, size, margins, etc)?","b. 메모리(유형, 크기, 여유 용량 등)?"]
["c.      Buses or Bus Loading?","c. 버스 또는 버스 부하?"]
["d.      Computer constraints?","d. 컴퓨터 제약 조건?"]
["e.      Interface signal conditioning?","e. 인터페이스 신호 컨디셔닝?"]
["13.       Faults:",null,11.1,"A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]
["a.      Tolerance features?","a. 허용 오차 기능은 무엇인가요?"]
["b.      Redundancy features?","b. 이중화 기능은 무엇인가요?"]
["c.      Hardware error detection/reporting features?","c. 하드웨어 오류 감지/보고 기능은 무엇인가요?"]
["High Level Software Requirements (HLR) Aspects:"]
["Do the requirements for built-in testing OR monitoring include Detection, Isolation, Reporting, or Recovery of:"]
["14.       Software failures, Hardware failures?","14. 소프트웨어 오류, 하드웨어 오류?",11.9,"A, B, C, D","Y","   Software failures"]
["Do the requirements address the abnormal conditions of:"]
["15.       Auto-restart conditions, Power failures, Transients?","15. 자동 재시작 조건, 정전, 과도 현상?","6.4.3.a","A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]
["General Requirements Qualities"]
["16.       Is there related Hardware Data/Drawing, ICDs?  ","16. 관련 하드웨어 데이터/도면, ICD가 있습니까?","2.2.2, 2.2.3","A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]
["17.       Are Requirements organized such that logically or functionally related or grouped and include descriptions of their relationships and relationships with other groups?","17. 요구사항이 논리적 또는 기능적으로 관련되거나 그룹화되어 있고, 요구사항 간의 관계 및 다른 그룹과의 관계에 대한 설명이 포함되어 있습니까?","6.4.3.b","A, B, C, D","Y","Refer to division in PAL_SW_SRD "]
["18.       Is each requirement uniquely identified? ","18. 각 요구사항이 고유하게 식별됩니까?","5.1.1.a","A, B, C, D","Y","Refer to SW High Level Requirements ID of PAL_SW_SRD "]
["19.       Does the requirements satisfy each applicable requirement in the system requirements? ","19. 요구사항이 시스템 요구사항의 모든 해당 요구사항을 충족합니까?","6.3.1.f","A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]
["20.       Functional, Performance, and Interface requirements?  ","20. 기능, 성능 및 인터페이스 요구사항이 포함되어 있습니까?","5.1.2","A, B, C, D","NA","There is no Performance Because KAC UTM SW level is AL-4, low level  is not described"]
["21.       Is there a description of the allocation of system requirements to software, with attention to safety-related requirements and potential failure conditions?","21. 안전 관련 요구사항 및 잠재적 오류 조건을 고려하여 시스템 요구사항을 소프트웨어에 할당하는 방법에 대한 설명이 있습니까?","2.6.a.1, 11.9.a","A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]
["22.       Do the high-level requirements conform to the Software Requirements Standards?","22. 상위 수준 요구사항이 소프트웨어 요구사항 표준을 준수합니까?","5.1.1.a, 5.1.2.e","A, B, C","Y","Refer to PAL_SW_SES "]
["Are the high-level requirements:","상위 수준 요구사항은 다음과 같은 조건을 충족합니까?"]
["23.       Unambiguous, Complete, Consistent?","23. 명확하고, 완전하며, 일관성이 있습니까?","5.1.2.a, e","A, B, C, D","Y","Refer to Detailed requirements description of PAL_SW_SRD "]
["24.       Verifiable by analysis or test?","24. 분석 또는 테스트를 통해 검증 가능합니까?","5.1.2e.","A, B, C","Y","Refer to Detailed requirements description of PAL_SW_SRD "]
["25.       Stated in quantitative terms with tolerances, where applicable?","25. 해당되는 경우 허용 오차를 포함하여 정량적으로 명시되었습니까?","5.1.2.f","A, B, C, D","Y","Refer to Detailed requirements description of PAL_SW_SRD "]
["26.       Do the high-level requirements not describe design or verification detail, except for specified and justified design constraints?","26. 명시되고 정당화된 설계 제약 조건을 제외하고, 상위 수준 요구 사항에 설계 또는 검증 세부 사항이 설명되어 있지 않습니까?","5.1.2.g","A, B, C, D","Y","Refer to Detailed requirements description of PAL_SW_SRD "]
["27.       Are high-level requirements that address system requirements allocated to software to preclude system hazards defined?","27. 시스템 위험을 방지하기 위해 소프트웨어에 할당된 시스템 요구 사항을 다루는 상위 수준 요구 사항이 정의되어 있습니까?","5.1.2.d","A, B, C, D","Y","Refer to division of PAL_SW_SRD "]
["28.       Are the functional and operational requirements defined for each mode of operation?","28. 각 작동 모드에 대한 기능 및 운영 요구 사항이 정의되어 있습니까?","11.9.b","A, B, C, D","Y","Refer to division of PAL_SW_SRD "]
["Are the following processing requirements defined?","다음 처리 요구 사항이 정의되어 있습니까?"]
["29.       Accuracies and Precision?  ","29. 정확도 및 정밀도?","11.9.c","A, B, C, D","Y","Refer to SW-HLR-REQ-082 of Detailed requirements description in PAL_SW_SRD"]
["30.       Timing margins, Transfer and Refresh rates?","30. 타이밍 마진, 전송 및 새로 고침 속도?","11.9.d","A, B, C, D","Y","Refer to SW-HLR-REQ-073 of Detailed requirements description in PAL_SW_SRD"]
["31.       Allowable response times and priorities?  ","31. 허용 가능한 응답 시간 및 우선순위?","11.9.d","A, B, C, D","Y","Refer to SW-HLR-REQ-157 of Detailed requirements description in PAL_SW_SRD"]
["32.       The frequency and synchronization of processes or computations?  ","32. 프로세스 또는 계산의 빈도 및 동기화?","11.9.d","A, B, C, D","Y","Refer to SW-HLR-REQ-071 of Detailed requirements description in PAL_SW_SRD"]
["33.       Are memory size constraints defined?","33. 메모리 크기 제약 조건이 정의되어 있습니까?","11.9.e","A, B, C, D","Y","Refer to SW-HLR-REQ-150 of Detailed requirements description in PAL_SW_SRD"]
["Are the following hardware and software interfaces defined?","다음 하드웨어 및 소프트웨어 인터페이스가 정의되어 있습니까?"]
["34.       Protocols, Formats?","34. 프로토콜, 포맷은 무엇인가요?","11.9.f","A, B, C, D","Y","Refer to SW-HLR-REQ-001 of Detailed requirements description in PAL_SW_SRD, JSON and REST-based API"]
["35.       Frequency of inputs and outputs?","35. 입력 및 출력 빈도는 어떻게 되나요?","11.9.f","A, B, C, D","Y","Refer to SW-HLR-REQ-068 of Detailed requirements description in PAL_SW_SRD"]
["36.       Are the failure detection requirements defined?","36. 오류 감지 요구사항이 정의되어 있나요?","11.9.g","A, B, C, D","Y","Refer to SW-HLR-REQ-118 of Detailed requirements description in PAL_SW_SRD"]
["37.       Are the safety monitoring requirements defined?","37. 안전 모니터링 요구사항이 정의되어 있나요?","11.9.g","A, B, C, D","Y","Refer to SW-HLR-REQ-101 and SW-HLR-REQ-103 of Detailed requirements description in PAL_SW_SRD"]
["If the system includes requirements for partitioning, are the following items addressed:","시스템에 파티셔닝 요구사항이 포함된 경우, 다음 항목들이 다뤄졌나요?"]
["38.       Are the partitioning requirements that are allocated to software defined?","38. 소프트웨어에 할당되는 파티셔닝 요구사항이 정의되어 있나요?","11.9.h","A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]
["39.       Is there a description of how the partitioned software components interact with each other?","39. 파티셔닝된 소프트웨어 구성 요소들이 서로 어떻게 상호 작용하는지에 대한 설명이 있나요?","11.9.h","A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]
["40.       Is the software level of each partition defined?","40. 각 파티션의 소프트웨어 레벨이 정의되어 있나요?","11.9.h","A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]
["41.       Are requirements for built-in testing and monitoring defined, including detection, isolation, and reporting?","41. 감지, 격리 및 보고를 포함한 내장 테스트 및 모니터링 요구사항이 정의되어 있나요?",null,null,"NA","KAC UTM SW level is AL-4, low level  is not described"]
["42.       Are requirements for recovery from hardware and software failures defined?","42. 하드웨어 및 소프트웨어 오류 복구 요구사항이 정의되어 있나요?",null,null,"NA","KAC UTM SW level is AL-4, low level  is not described"]
["43.       Are requirements for recovery from abnormal conditions defined, including auto-restart and power-fail and transients?","43. 자동 재시작, 전원 차단 및 과도 현상을 포함한 비정상 상태 복구에 대한 요구 사항이 정의되어 있습니까?",null,null,"NA","KAC UTM SW level is AL-4, low level  is not described"]
["44.       Have derived high level requirements been provided to the System and Safety assessment process?","44. 도출된 상위 수준 요구 사항이 시스템 및 안전성 평가 프로세스에 제공되었습니까?","5.1.1.i","A, B, C, D","NA","KAC UTM SW level is AL-4, low level  is not described"]

{"sheet":"SDD","index":8,"n_rows":64,"n_cols":6,"rows_kept":64,"cut":false,"hidden":false,"merged":[[3,0,4,0],[3,2,4,2],[3,3,4,3],[3,1,4,1],[2,3,2,5]]}
["Software Design Description Question"]
[]
[null,null,null,"2026.02.06\nSDD ver 0.1"]
["Checklist Item","Korean","Ref.","Applicable DAL","Y / N","Comments /"]
[{"$nulls":4},"NA","Action Item #"]
["Configuration Aspects","구성 측면"]
["Have the following Configuration aspects of Low Level Requirements (LLR) or Design Data Item been achieved?","다음과 같은 하위 수준 요구사항(LLR) 또는 설계 데이터 항목의 구성 측면이 충족되었습니까"]
["1.          Is the document Revision/Baseline under Configuration?","1. 문서의 개정/기준선이 구성 중입니까?","7.2.1.a, b, c","A, B, C, D","Y","Upload to GitLab PAL_SDD_v0.1"]
["2.          Was the related High-Level Requirement Spec. configured before updating or developing this Data Item?","2. 이 데이터 항목을 업데이트하거나 개발하기 전에 관련 상위 수준 요구사항 명세서가 구성되었습니까?","7.2.1.d","A, B, C, D","Y","Refer to SRD 3.0 SOFTWARE REQUIREMENTS IDENTIFICATION"]
["Software Architecture and Design Assessments","소프트웨어 아키텍처 및 설계 평가"]
["Does the SW Architecture and Design Contain the following?","소프트웨어 아키텍처 및 설계에 다음 사항이 포함되어 있습니까?"]
["3.          Does the SDD show that the software architecture and design satisfy High-Level requirements? ","3. 소프트웨어 설계 문서(SDD)에서 소프트웨어 아키텍처 및 설계가 상위 수준 요구사항을 충족함을 보여줍니까?","5.2.1.a, 6.3.3.a","A, B, C, D","Y","Refer to PAL_SDD_v0.1 Internal Documents"]
["4.          Were software architecture and low-level requirements developed from the high-level requirements.","4. 상위 수준 요구사항으로부터 소프트웨어 아키텍처 및 하위 수준 요구사항이 개발되었습니까?","5.2.1.a","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["5.          Does a correct relationship exist between the components of the software architecture?","5. 소프트웨어 아키텍처 구성 요소 간에 올바른 관계가 존재합니까?","6.3.3.b","A, B, C, D","Y","Refer to SDD 2 Software Architecture"]
["6.          Do software component relationships exist via data flow and control flow?","6. 데이터 흐름 및 제어 흐름을 통해 소프트웨어 구성 요소 간의 관계가 존재합니까?","6.3.3.b","A, B, C, D","Y","Refer to 2.1 Data and Control Flow and SDD 2.3 Inputs and Outputs "]
["7.          Are initialization, asynchronous operation, synchronization, and interrupts between the software architecture and the hardware/software features of the target computer compatible?","7. 소프트웨어 아키텍처와 대상 컴퓨터의 하드웨어/소프트웨어 기능 간의 초기화, 비동기 동작, 동기화 및 인터럽트가 호환됩니까?","6.3.3.c","A, B, C, D","Y","Refer to SDD 2.5 Scheduling Producers and Inter-Processor Task Communication"]
["Is there a description of the scheduling and communication mechanisms for?","스케줄링 및 통신 메커니즘에 대한 설명이 있습니까?"]
["8.          Sequence?  Interrupt structure?","8. 순서 및 인터럽트 구조는 어떻게 됩니까?","11.10.f","A, B, C, D","Y","Refer to SDD 2.5.Scheduling procedures and inter-processor/inter-task communication"]
["Does the description of the interrupt structure include?","인터럽트 구조에 대한 설명에 다음 내용이 포함되어 있습니까?"]
["9.          Timing constraints?  ","9. 타이밍 제약 조건이 있습니까?","11.10.e","A, B, C, D","Y ","Refer to SDD 2.5.Scheduling procedures and inter-processor/inter-task communication"]
["10.       Is there a description of (or reference to) interrupt handlers and inter-module control flow showing conditions in which a module is activated?  ","10. 인터럽트 핸들러 및 모듈 간 제어 흐름에 대한 설명(또는 참조)이 있으며, 모듈이 활성화되는 조건이 표시되어 있습니까?","11.10.f","A, B, C","Y","Refer to SDD 2.5.Scheduling procedures and inter-processor/inter-task communication"]
["Software Design and Low-Level Requirements","소프트웨어 설계 및 저수준 요구사항"]
["Design and Low-Level Requirements – General Aspects","설계 및 저수준 요구사항 – 일반적인 측면"]
["11.       Were the Software Design Standards followed during the software design process and deviations from the standards justified.","11. 소프트웨어 설계 과정에서 소프트웨어 설계 표준을 준수했으며, 표준에서 벗어난 부분은 정당한 이유가 있습니까?","6.3.2.e","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["12.       Is there a reasonable and clear traceability from Low-Level requirements to high-level requirements and derived High-Level requirements?","12. 저수준 요구사항에서 고수준 요구사항 및 파생된 고수준 요구사항으로의 합리적이고 명확한 추적성이 확보되어 있습니까?","6.3.2.f","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["13.       Are Derived low-level requirements defined and provided to the system processes, including the system safety assessment process?","13. 파생된 저수준 요구사항이 정의되어 시스템 안전성 평가 프로세스를 포함한 시스템 프로세스에 제공되었습니까?","5.2.1.b","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["14.       Are Derived low-level requirements and the reason for their existence defined and analyzed to ensure that the High-Level requirements are not compromised","14. 파생된 저수준 요구사항과 그 존재 이유가 정의되고 분석되어 고수준 요구사항이 손상되지 않도록 보장되었습니까?","5.2.2.b","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["15.       Was each Low-Level requirement uniquely Identified?  ","15. 각 저수준 요구사항이 고유하게 식별되었습니까?","5.2.1.a","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["Are Low-Level requirements and constraints included for:","저수준 요구사항 및 제약 조건에 다음 사항이 포함되었습니까?"]
["16.       Fault tolerance and Safety monitoring?","16. 내결함성 및 안전 모니터링?","5.2.2.f, g","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["17.       Previously developed software? ","17. 이전에 개발된 소프트웨어?","11.10.i","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["18.       Deactivated code? ","18. 비활성화된 코드?","11.10.k","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["19.       Description of the allocation of requirements to modules, tasks, and processors?  ","19. 모듈, 작업 및 프로세서에 대한 요구사항 할당 설명?","11.10.a, f","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["20.       Is floating point arithmetic used for real number computations, if supported by the target computer?  ","20. 대상 컴퓨터에서 지원하는 경우 실수 계산에 부동 소수점 연산이 사용되었습니까?","6.3.4.f","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["Is there a description of (or reference to):","다음 사항에 대한 설명(또는 참조)이 있습니까?"]
["21.       Input and output data flow including control flow?","21. 입력 및 출력 데이터 흐름(제어 흐름 포함)","11.10.c, d","A, B, C","Y","Refer to 2.1 Data and Control Flow and SDD 2.3 Inputs and Outputs "]
["22.       If two or more channels are used to perform the same function, are the interface mechanisms described? ","22. 두 개 이상의 채널이 동일한 기능을 수행하는 경우 인터페이스 메커니즘이 설명되어 있습니까?","11.10.f","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["For user-modifiable software, does the software design ensure that:","사용자 수정 가능 소프트웨어의 경우, 소프트웨어 설계는 다음을 보장합니까?"]
["23.       The software can be modified only as specified in the requirements?  ","23. 소프트웨어는 요구 사항에 명시된 대로만 수정할 수 있습니까?","5.2.3.a","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["24.       Non-modifiable software is protected?  ","24. 수정 불가능 소프트웨어는 보호됩니까?","5.2.3.a","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["25.       The validity and integrity of user modifications are checked?  ","25. 사용자 수정 사항의 유효성과 무결성이 검사됩니까?","5.2.3.b","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["26.       For option-selectable software, does the software design ensure that only specified combinations of options and configurations can be selected?  ","26. 옵션 선택 가능 소프트웨어의 경우, 소프트웨어 설계는 지정된 옵션 및 구성 조합만 선택할 수 있도록 보장합니까?","5.2.3b","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["For field-loadable software:","현장 설치 가능 소프트웨어의 경우:"]
["27.       Is it partitioned from non-loadable software? ","27. 현장 설치 불가능 소프트웨어와 구분되어 있습니까?","6.4.3.a","A, B, C, D","NA","Refer to 01_PAL_SW_PSAA_20250625 5.4.1.1 Field Loadable Software, it was decided not to distinguish it from non-field loadable software"]
["28.       Does the software design provide a mechanism for verifying the software part number each time the software is loaded? ","28. 소프트웨어 설계는 소프트웨어가 로드될 때마다 소프트웨어 부품 번호를 확인하는 메커니즘을 제공합니까?","7.2.1.e","A, B, C","N","Refer to SCI but not finished"]
["29.       Does the software design ensure that loads satisfy the error detection integrity requirement? ","29. 소프트웨어 설계는 로드가 오류 감지 무결성 요구 사항을 충족하도록 보장합니까?","11.1.g","A, B, C","N","Refer to SRD but not finished"]
["30.       Does the software design ensure that incorrect and corrupted software loads and incompatible software and hardware combinations are detected? ","30. 소프트웨어 설계는 잘못되었거나 손상된 소프트웨어 로드, 그리고 호환되지 않는 소프트웨어와 하드웨어 조합을 감지하도록 보장합니까?","2.4.1, 2.5.1","A, B, C","N","Refer to SRD but not finished"]
["31.       For partitioning, does the software design ensure that only specified interactions between partitions are allowed?  ","31. 파티셔닝의 경우, 소프트웨어 설계는 파티션 간에 지정된 상호 작용만 허용하도록 보장합니까?","5.5.2","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["If partitioning is used, does the description of the partitioning design include:","파티셔닝을 사용하는 경우, 파티셔닝 설계 설명에 다음 사항이 포함됩니까?"]
["32.       Partitions' verification type and software level?  ","32. 파티션 검증 유형 및 소프트웨어 레벨?","11.3.f","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["33.       The partitioning mechanism and protection provided?  ","33. 제공되는 파티셔닝 메커니즘 및 보호 기능?","6.3.3.f","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["34.       The extent and scope of partitions' interactions in terms of hardware device use and failure modes, control coupling, and data coupling?  ","34. 하드웨어 장치 사용 및 고장 모드, 제어 결합, 데이터 결합 측면에서 파티션 상호 작용의 범위 및 규모?","11.9.h","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]
["Detailed Design Aspects","상세 설계 측면"]
["Are memory maps of the software included that show:","다음 사항을 보여주는 소프트웨어의 메모리 맵이 포함되어 있습니까?"]
["35.       An allocation at the module level of code?  ","35. 모듈 레벨 코드의 할당?","6.3.5.a","A, B, C","N","There is no section about memory map"]
["36.       Other data to available memory?  ","36. 사용 가능한 메모리에 대한 기타 데이터? 다음 사항에 대한 설명이나 참조가 있습니까?","11.10.e","A, B, C","N","There is no section about memory map"]
["Is there a description of or reference to:","다음 사항에 대한 설명이나 참조가 있습니까?"]
["37.       Each module's algorithmic design?  ","37. 각 모듈의 알고리즘 설계?","11.10.a","A, B, C","N","There is no section about algorithmic design of module"]
["38.       Data structures, including tables and databases?  ","38. 테이블 및 데이터베이스를 포함한 데이터 구조?","11.10.a","A, B, C","Y","Refer to SDD 2.3.1 UTM CORE Data Dictionary and 2.3.2.\tSWIM SERVICE Data Dictionary"]
["39.       Definition of limitations, including data rates, error handling, and calculation limitations due to overflow, underflow, or loss of numerical significance?  ","39. 데이터 전송률, 오류 처리, 오버플로, 언더플로 또는 수치적 의미 손실로 인한 계산 제한을 포함한 제한 사항 정의?","6.3.4.f","A, B, C","Y","Refer to SDD 2.3 Inputs and Outputs and 2.1 Data Flow and Control Flow"]
["Is the scope of each data element?","각 데이터 요소의 범위는 어떻게 됩니까?"]
["40.       Limited within a computer program to those modules that require visibility of the data element to perform their function(s)?  ","40. 컴퓨터 프로그램 내에서 해당 기능을 수행하기 위해 데이터 요소에 대한 가시성이 필요한 모듈로 제한됩니까?","6.6.a","A, B, C","Y","Refer to SDD 2.3 Inputs and Outputs and 2.1 Data Flow and Control Flow"]
["Is the design free of:","설계에 다음 사항이 없습니까?"]
["41.       Recursive or Reentrant invocation of modules?  ","41. 모듈의 재귀적 또는 재진입적 호출?","6.3.3.d","A, B, C","NA","KAC UTM SW level is AL-4, low level  is not described"]

{"sheet":"SCI","index":9,"n_rows":47,"n_cols":6,"rows_kept":47,"cut":false,"hidden":false,"merged":[[5,1,6,1],[5,0,6,0],[5,2,6,2],[5,3,6,3],[4,4,4,5]]}
["Software Configuration Index Question"]
[]
[]
[]
[{"$nulls":4},"2026.02.06\nSCI ver 0.1"]
["Checklist Item","Korean","Ref.","Appl. DAL","Y / N","Comments /"]
[{"$nulls":4},"NA","Action Item #"]
["Document Format:","문서 형식:"]
["1.        Is the document under configuration control with an accurate revision history?","1. 문서가 정확한 개정 이력을 가진 구성 관리 하에 있습니까?","7.2.1.d","ABCD","Y","This document is under configuration control with an accurate revision history."]
["2.        Does the title page include program name, document release date, and document identification and revision level?","2. 표지에 프로그램 이름, 문서 배포일, 문서 식별 번호 및 개정 수준이 포함되어 있습니까?","7.2.1.a","ABCD","Y","The title page includes the program name, document release date, document identification, and revision level."]
["3.        Is the table of contents and any other applicable tables, terms & acronyms, and reference included?","3. 목차 및 기타 관련 표, 용어 및 약어, 참조가 포함되어 있습니까?",null,"ABCD","Y","The table of contents, acronyms, and references are included in this document."]
["General Content","일반 내용"]
["4.        Is the product identified?","4. 제품이 식별되어 있습니까?","11.16.a","ABCD","Y","The product is identified in the cover page and Section 1.1."]
["5.        Is the associated system identified by name and by supplier part number? ","5. 관련 시스템이 이름과 공급업체 부품 번호로 식별되어 있습니까?","7.2.1","ABCD","Y","The associated system is identified by name in the document. Supplier part number is not applicable."]
["6.        Is the configuration identification of the executable object code specified?","6. 실행 가능한 오브젝트 코드의 구성 식별 번호가 명시되어 있습니까?","11.16.b","ABCD","Y","The configuration identification of the executable object code is specified in Section 4."]
["7.        Are the individual source code modules of this delivery identified?","7. 이 납품의 개별 소스 코드 모듈이 식별되어 있습니까?","11.16.c","ABCD","Y","The individual source code modules are identified in Section 3."]
["8.        Is any previously developed software code identified?","8. 이전에 개발된 소프트웨어 코드가 식별되어 있습니까?","11.16.d","ABCD","N/A","Previously developed software code is not applicable to this project, as described in Section 5."]
["Is the current version of the following FAI data package items identified:","다음 FAI 데이터 패키지 항목의 현재 버전이 식별되어 있습니까?"]
["9.        SWD plan? SWCM? SWQA? Verification?","9. SWD 계획? SWCM? SWQA? 검증?","11.16.e","ABCD","N/A","Software development, configuration management, quality assurance, and verification plans are not applicable to this SCI."]
["10.     Updated project schedules and resources?","10. 업데이트된 프로젝트 일정 및 리소스?","11.16.e","ABCD","N/A","Updated project schedules and resource information are not applicable to this SCI."]
["11.     Software development standards? ","11. 소프트웨어 개발 표준?","11.16.e","ABCD","N/A","Software development standards are not identified in this SCI."]
["12.     Supplier system requirements, if applicable? ","12. 해당되는 경우 공급업체 시스템 요구 사항?","11.16.e","ABCD","N/A","Supplier system requirements are not applicable to this project."]
["13.     SWRD?  SWDD?  Data Dictionary?  VDD?","13. SWRD? SWDD? 데이터 사전? VDD?","11.16.e","ABCD","N/A","SWRD, SWDD, Data Dictionary, and VDD are not applicable to this SCI."]
["14.     All Applicable Traceability Data? ","14. 모든 관련 추적성 데이터가 포함되어 있습니까?","11.16.e","ABCD","N/A","Traceability data are not applicable to this SCI."]
["15.     Requirements verification matrix and requirements verification analysis data? ","15. 요구사항 검증 매트릭스 및 요구사항 검증 분석 데이터가 포함되어 있습니까?","11.16.e","ABCD","N/A","Requirements verification matrix and verification analysis data are not applicable to this SCI."]
["16.     Target computer selection rationale? ","16. 대상 컴퓨터 선정 근거가 있습니까?","11.16.e","ABCD","N/A","Target computer selection rationale is not applicable to this SCI."]
["17.     Compiler selection rationale? ","17. 컴파일러 선정 근거가 있습니까?","11.16.e","ABCD","N/A","Compiler selection rationale is not identified in this SCI."]
["18.     Target computer programming manual? ","18. 대상 컴퓨터 프로그래밍 매뉴얼이 포함되어 있습니까?","11.16.e","ABCD","N/A","Target computer programming manual is not applicable to this project."]
["19.     Design verification analysis data? ","19. 설계 검증 분석 데이터가 포함되어 있습니까?","11.16.e","ABCD","N/A","Design verification analysis data are not applicable to this SCI."]
["20.     Source code & Verification analysis?","20. 소스 코드 및 검증 분석 데이터가 포함되어 있습니까?","11.16.e","ABC","N/A","Source code verification analysis data are not applicable to this SCI."]
["21.     Test procedures?  Coverage?  Reports?","21. 테스트 절차, 테스트 범위, 보고서가 포함되어 있습니까?","11.16.e","ABCD","N/A","Test procedures, coverage data, and test reports are not applicable to this SCI."]
["22.     Integration verification analysis data? ","22. 통합 검증 분석 데이터가 포함되어 있습니까?","11.16.e","ABCD","N/A","Integration verification analysis data are not applicable to this SCI."]
["23.     Tool development and qualification data, if applicable?","23. 해당되는 경우, 툴 개발 및 검증 데이터가 포함되어 있습니까?","11.16.e","ABCD","N/A","Tool development and qualification data are not applicable to this SCI."]
["24.     PR summary? ","24. PR 요약이 포함되어 있습니까?","11.16.e","ABCD","N/A","No problem reports are associated with this delivery."]
["25.     Any other software-related data item listed in the SDRL and contractual agreements? ","25. SDRL 및 계약서에 명시된 기타 소프트웨어 관련 데이터 항목이 있습니까?","11.16.e","ABCD","N/A","No additional software-related data items are identified for this delivery."]
["26.     Is the support environment software, including executable object code generation tools, command files, Parameter Data Item Files, and tool qualification data, identified? ","26. 실행 가능한 오브젝트 코드 생성 도구, 명령 파일, 파라미터 데이터 항목 파일 및 툴 검증 데이터를 포함한 지원 환경 소프트웨어가 식별되어 있습니까?","11.16.b","ABCD","N/A","Support environment software and related items are not applicable, as SECI is not included in this SCI."]
["27.     Are the master, archived and release media identified? ","27. 마스터, 아카이브 및 릴리스 미디어가 식별되어 있습니까?","11.16.f","ABCD","N/A","Master, archived, and release media are not applicable, as described in Section 8."]
["28.     Are change authorizations and PRs resolved by this delivery identified? ","28. 이번 납품에서 해결된 변경 승인 및 PR이 식별되어 있습니까?","7.2.5","ABCD","N/A","Change authorizations and problem reports are not applicable to this delivery, as described in Section 9."]
["29.     Are the object code CRC (or equivalent) generation procedure and value identified? ","29. 오브젝트 코드 CRC(또는 이에 상응하는 검사) 생성 절차 및 값이 명시되어 있습니까?","11.16.i","ABCD","N/A","Object code CRC generation procedures and values are not applicable to AL-4."]
["30.     Are compiling procedures, compiler optimization features used, and options identified?","30. 컴파일 절차, 사용된 컴파일러 최적화 기능 및 옵션이 명시되어 있습니까?","11.16g","ABCD","N/A","Compiling procedures, compiler optimization features, and options are not identified in this SCI."]
["31.     Are linking procedures identified? ","31. 링크 절차가 명시되어 있습니까?","11.16.g","ABCD","N/A","Linking procedures are not explicitly identified in this SCI."]
["32.     Are the procedures used to recover the software for regeneration, testing, and modification identified?","32. 소프트웨어 복구, 재생성, 테스트 및 수정 절차가 명시되어 있습니까?","11.16.g","ABCD","N/A","Procedures for software recovery are not applicable to this SCI."]
["33.     Are the data integrity checks for the Executable Object Code identified?","33. 실행 가능한 오브젝트 코드에 대한 데이터 무결성 검사가 명시되어 있습니까?","11.16.i","ABCD","N/A","Data integrity checks for executable object code are not applicable to AL-4."]
["For field-loadable software, are there identification of:","필드 로드 가능 소프트웨어의 경우 다음 사항이 명시되어 있습니까?"]
["34.     Is the software life cycle environment hardware and operating system identified?","34. 소프트웨어 수명 주기 환경의 하드웨어 및 운영 체제가 명시되어 있습니까?","11.15.a","ABCD","N/A","Software life cycle environment hardware and operating system identification is not applicable to this SCI"]
["35.     Is the test environment used to verify the software product identified?","35. 소프트웨어 제품 검증에 사용된 테스트 환경이 명시되어 있습니까?","11.15.c","ABCD","N/A","This document does not identify a separate test environment for software verification."]
["36.     Are the qualified tools and their associated tool qualification data identified?","36. 검증된 도구와 관련 도구 검증 데이터가 명시되어 있습니까?","11.15.d","ABCD","N/A","No qualified tools are used in this project."]

{"sheet":"Integration","index":10,"n_rows":28,"n_cols":6,"rows_kept":28,"cut":false,"hidden":false,"merged":[[9,4,14,4],[9,5,14,5],[5,1,6,1],[5,0,6,0],[5,2,6,2],[5,3,6,3],[9,2,14,2],[9,3,14,3]]}
["Software Integration Question"]
[]
[]
[]
[]
["Checklist Item","Korean","Ref.","Applicable DAL","Y / N","Comments /"]
[{"$nulls":4},"NA","Action Item #"]
["Configuration Aspects","구성 측면"]
["Have the following Configuration aspects of Software been achieved?","다음과 같은 소프트웨어 구성 측면이 충족되었습니까?"]
["1.          Are the following Data Items Under CM?","1. 다음 데이터 항목이 CM에 포함되어 있습니까?","7.2.1.a, b, c","A, B, C, D","Y","Source code is under configuration management using GitLab."]
["a.      Source Code including BSP","a. BSP를 포함한 소스 코드"]
["b.      Software Requirements","b. 소프트웨어 요구 사항"]
["c.      Software Design","c. 소프트웨어 설계"]
["d.      SCI and SECI","d. SCI 및 SECI"]
["e.      Parameter Data Files (if used)","e. 파라미터 데이터 파일(사용하는 경우)"]
["2.          Were the related System Requirement Specifications configured before updating or developing this Data Item?","2. 이 데이터 항목을 업데이트하거나 개발하기 전에 관련 시스템 요구 사항 사양이 구성되었습니까?","7.2.1.d","A, B, C, D","Y","\nWe've compiled your requirements and started development."]
["Integration Activities","통합 활동"]
["Software Compilation:","소프트웨어 컴파일:"]
["3.          Has source code been complied and linked without any errors or un-justified warnings?","3. 소스 코드가 오류나 불필요한 경고 없이 컴파일 및 링크되었습니까?","5.4.2.a","A, B, C, D","NA","Compilation and linking verification results are not applicable to this SCI."]
["4.          Has the Parameter Data File been generated?","4. 파라미터 데이터 파일이 생성되었습니까?","5.4.2.a","A, B, C, D","NA","Parameter Data Files are not used in this project."]
["5.          Has the executable object code been generated for the Target Computer using SCI/SECI?","5. SCI/SECI를 사용하여 대상 컴퓨터용 실행 가능한 오브젝트 코드가 생성되었습니까?","5.4.2.b","A, B, C, D","NA","Executable object code generation for a target computer using SCI/SECI is not applicable to this SCI."]
["6.          Is the integration being used for a SW Patch?","6. 통합이 SW 패치에 사용되고 있습니까?","5.4.2.e","A, B, C, D","NA","This integration is not used for a software patch."]
["Software Load Process:","소프트웨어 로드 프로세스:"]
["7.          Has the software been loaded successfully to the Target Computer using the SCI/SECI?  ","7. SCI/SECI를 사용하여 대상 컴퓨터에 소프트웨어가 성공적으로 로드되었습니까?","5.4.2.c","A, B, C, D","NA","Software loading to a target computer using SCI/SECI is not applicable, as described in Section 7."]
["8.          During the system re-start, does the software correctly initialize the target system/hardware to the correct initialization state/values?  ","8. 시스템 재시작 시 소프트웨어가 대상 시스템/하드웨어를 올바른 초기화 상태/값으로 정확하게 초기화합니까?","5.4.2.c","A, B, C, D","NA","Target system or hardware initialization during restart is not applicable to this SCI."]
["Perform SW/SW and/or SW/HW Integration Tests:","SW/SW 및/또는 SW/HW 통합 테스트 수행:"]
["9.          If there was any issued identified, has inadequate or incorrect compilation, inputs, or test results of the integration process documented in a Change Control process?","9. 문제가 발견된 경우, 통합 프로세스의 부적절하거나 잘못된 컴파일, 입력 또는 테스트 결과가 변경 관리 프로세스에 문서화되었습니까?","5.4.2.d","A, B, C, D","NA","No integration issues were identified; therefore, change control documentation is not applicable."]
["10.       If the SW Integration is for the delivery of software products submitted as part of a certification application, has a software conformity review been performed or witnessed by SQA?","10. SW 통합이 인증 신청의 일부로 제출된 소프트웨어 제품 제공을 위한 것인 경우, SQA에서 소프트웨어 적합성 검토를 수행했거나 참관했습니까?","8.2.g, h","A, B, C, D","NA","This software integration is not part of a certification application; therefore, software conformity review by SQA is not applicable."]