1. Document Tracking and the Related Process Andria Roney Rob Mead Andy Fry Andrew Onken

2. Document Tracking Objective Recommend an effective approach to provide linking between documents to ensure alignment Recommend a process to maintain the alignment

3. Document Linking Strategy Add linking in DOORS for: E2E documents Use Cases Standards Documents (only applicable sections)

4. FPR ESSD WSSD SSSD DCNSD ERAM-DCNS IRD ERAM-TDLS IRD TDLS-SDB-WAS WSRD TDLS-CSP IRD DCNSM-SMS- WSRD RMS-RMLS IRD Routes E2E (Contains most loadable msgs) Initial and Full Services Use Cases CONOPS [includes Tower CONUSE En Route CONUSE) Avionics Test Procedures S1P2 Op Scenario Doc Scenarios System Models Mappings Gap Analysis DCL E2E for Production Satisfies System Requirements Interface Requirements SSSs SRSs Satisfies System Implementation Requirements Interface Implementation Requirements ERAM TDLS ICD ERAM- DCNS ICD ARINC 618 ARINC 620 DO-258A Conform. Stmt. DO-350 Conform. Stmt. ARINC 622 ARINC 631 DO-352 Conform. Stmt. Standards Documents DOORS Stakeholder Requirements Satisfies Implements S1P2 Session and Frequency Mgmt E2E Descrip STDDS TDLS IRD ERAM TIMS ICD TDLS CSP ICD DCNSM JMSDD ICD RLMS CMHP ICD TDLS RMLS ICD ** ** These docs are in DOORS but not yet linked Tests SI&T SSSD VRTM OT&E Test Requirements Tests ESSD VRTM WSSD VRTM DCNS VRTM requirements/design verified indirectly at ICD level Tests IRD VRTMs Tests S1P1 Integration Gap Analysis Report RTCA Standards Subscriber Database IRD Subscriber Database ICD Flight Deck Guidance Flight Deck Local Procedures AOC Local Procedures Tower Local Procedures GOLD (Global Operational Data Link Document) By reference Direct linking Tests Related To Key (up/toward) Maps to/Satisfies; Derived from

5. Document Change Process Origin of Changes The field - Sites/WJHTC Testing Addition of new capabilities DCIT recommendations OPRs Domestic OPRs International Current process in place to manage change within FAA realm Need to add DCIT stakeholders into current process Impact analysis Document updates to maintain consistency

6. FPR ESSD WSSD SSSD DCNSD ERAM-DCNS IRD ERAM-TDLS IRD TDLS-SDB-WAS WSRD TDLS-CSP IRD DCNSM-SMS- WSRD RMS-RMLS IRD Routes E2E (Contains most loadable msgs) Initial and Full Services Use Cases CONOPS [includes Tower CONUSE En Route CONUSE) Avionics Test Procedures S1P2 Op Scenario Doc Scenarios System Models Mappings Gap Analysis DCL E2E for Production Satisfies System Requirements Interface Requirements SSSs SRSs Satisfies System Implementation Requirements Interface Implementation Requirements ERAM TDLS ICD ERAM- DCNS ICD ARINC 618 ARINC 620 DO-258A Conform. Stmt. DO-350 Conform. Stmt. ARINC 622 ARINC 631 DO-352 Conform. Stmt. Standards Documents DOORS Stakeholder Requirements Satisfies Implements S1P2 Session and Frequency Mgmt E2E Descrip STDDS TDLS IRD ERAM TIMS ICD TDLS CSP ICD DCNSM JMSDD ICD RLMS CMHP ICD TDLS RMLS ICD ** ** These docs are in DOORS but not yet linked Tests SI&T SSSD VRTM OT&E Test Requirements Tests ESSD VRTM WSSD VRTM DCNS VRTM requirements/design verified indirectly at ICD level Tests IRD VRTMs Tests S1P1 Integration Gap Analysis Report RTCA Standards Subscriber Database IRD Subscriber Database ICD Flight Deck Guidance Flight Deck Local Procedures AOC Local Procedures Tower Local Procedures GOLD (Global Operational Data Link Document) By reference Direct linking Tests Related To Key (up/toward) Maps to/Satisfies; Derived from

7. Change -The field -Testing -Addition of new capabilities -DCIT -OPRs -Domestic -International ER Board Change reviewed. For considered changes Impact Analysis requested. In addition to current items should include: DCIT document impacts DCIT Operational Impacts Change Tracking Process ER Board Impacts reviewed – decision made. If any changes are made to initial change or how it should be implemented then DCIT is notified of results including any changes. DCIT Add Change and impacted documents to SharePoint Document Issue List for update tracking. FAA Documents (Req, design, etc.), SW, Test artifacts, etc. are updated DCIT Documents are reviewed by DCIT stakeholders AND FAA for consistency with FAA documents/implementation FAA Documents (Req, design, etc.), SW, Test artifacts, etc. are reviewed per process. FAA - CCB Approval per process. DCIT Final updated documents approved by Plenary FAA/DCIT Approved documents are baselined. A B A B Recommend DCIT Leads added to ER Board

8. Going Forward Leverage DCIT to identify links between DCIT documents to current DOORS documents/modules Leverage Use Case team/NUT/FAA Engineering to identify links between Use Cases to current DOORS documents/modules Leverage SE to identify links between CONOPS and Standards to current DOORS documents/modules Recommend linking to either SSSD OR SSD level and not both. Use DOORS to show relationship between SSSD and SSD levels. i.e., CONOPS currently shown as linking to both ESSD, WSSD and SSSD