Observatory Control System Test Plan Steve Wampler High-Level Software

Transcription

1 Project Documentation Document PROC-0029 Rev A Observatory Control System Test Plan Steve Wampler High-Level Software June 6, 2016

2 REVISION SUMMARY: 1. Date: 6 June 2016 Revision: Rev A Changes: Initial version PROC-0029 Rev A Page 1 of 208

3 1. TEST FRAMEWORK The OCS uses the CSF-supplied software Quality Assurance Framework (QAF) to verify compliance with requirements found in the DRD. Each requirement is verified with a separate test. Requirements that are not user-interface requirements are tested using Python scripts within that framework. User interface requirement tests consist of detailed instructions on the steps a user it to take to test the requirement. No attempt is made to automate GUI testing. For the non-gui aspects of the OCS, the testing framework developed for use with the TCS is adapted for use with the TCS. This discussion draws heavily from the TCS description of its testing facility. Tests are first run using the DKIST High-Level Software end-toend test bed prior to delivery. After summit delivery the tests are repeated using the summit systems. Using the QAF allows the tests to make full use of the available services present in the CSF while keeping the testing mechanism detached from the application. This makes writing tests and updating tests easy, without the need to recompile any code. Using QAF ensures that the tests are standardized. The testing framework provides class definitions that the test scripts subclass. The testing classes ensure test comments are logged into the log database using tags that can easily be retrieved. The QAF runs each test and compares the result to the expected result, producing a summary of all test results. The required test scripts are supplied as part of the OCS deliverables and are then matched to the specific requirement that each tests in the compliance matrix (see Section 6). The testing framework provides class definitions that the test scripts subclass. The testing classes ensure test comments are logged into the log database using tags that can easily be retrieved, and also put results using predefined names that allow specialized JES widgets to pick up and display the results. Coupled with another JES widget that allows selection and execution of the test scripts results in all testing being carried out within a standard CSF environment, making use of standard CSF services and recording all test results to standard CSF logging facilities. The testing framework script locations are added to the scripting widget (relative to $(ATST) so they are portable between CSF installations) such that the test scripts themselves can simply import the required python modules. If any operator input is required, then the test scripts can invoke dialog boxes through jython as no command line interfaces are available. The available classes and methods of the testing framework are presented in the table below. Method Parameters Return Description TestStep class subclass and override the Run method. Log message void Logs the message using the CSF log service. Also posts the message and stores it into the cache for use (e.g. JES widgets). Fail message void Fail the current test step. The step is logged as failing with the reason given. The step exits at this point. Get Set component, table component, table table void Call get() on the specified component. The table is an attribute table filled with the names of attributes to get. The returned table contains the filled in values. Call set on the specified component. The table is an attribute table filled with the names and values of attributes to set. PROC-0029 Rev A Page 2 of 208

4 Submit BlockSubmit Request controller, configuration controller, configuration message, table int int table Call submit() on the specified controller. The configuration is submitted to the controller and the submit return value is returned. This does not block. Call submit() on the specified controller. The configuration is submitted to the controller and the final status of the command is returned. This does block until the action is completed/aborted/cancelled. Request user input. The names of the values requested are provided in the table input (attribute table format) and the return attribute table contains the names and values that were entered. This method blocks the test until the user has closed the popup. Message message void Open a popup to display a message to the user. This method blocks until the user has closed the popup. Test class create, add test steps and then Run the test. Test ID, description, requirements, details void Constructor for a test object. Create a test object, add the required steps to it and then run it to perform the test. AddStep Step void Add another step to this test. Run table void Execute the test, running through each step in order. An attribute table is returned that contains the report for the test, each step is included along with its pass/fail state and any failure message. Whenever a test script is executed the testing framework requests a unique ID from the CSF ID service. This ID is appended to the original test ID (that is defined as part of the test script) and all messages are logged with this unique ID. The ID is also presented to the operator making the task of retrieving old test logs in the future much easier (using standard SQL search queries). For example, if the test is called TEST.OCS.0001 and the uniquely generated ID is then every log message for this test starts with [TEST.OCS ] Details on the QAF and its use are found in PROC-0015 (Software Test Plan). PROC-0029 Rev A Page 3 of 208

5 2. STAGED TESTING Tests for the OCS are implemented in stages corresponding to the development schedule: Summit Management Support tests are implemented first Experiment Management Support test sare then implemented Operation Interface Support tests are implemented last. This staged testing allows for compliance testing to be conducted as part of the OCS' release cycles. All rests are repeated on OCS development completion. PROC-0029 Rev A Page 4 of 208

6 3. TEST COVERAGE The OCS tests are derived directly from the OCS Compliance Matrix (CMX-008) that, in turn, derives from the requirements found in the OCS Design Requirements Document (SPEC-0161). Each requirement that can be validated by a test has a separate test procedure documented Section 4. PROC-0029 Rev A Page 5 of 208

7 4. TEST DESCRIPTIONS This section describes the steps necessary to verify all requirements where the verification method was listed as either inspection or manual-test in the OCS Compliance Matrix. Those tests with a verification method of auto-test include an automated test (see OCS source tree $ATST/src/jython/atst/ocs/qa/tests) which include details of what the requirement is, what the test steps are and what conditions have to be met for the test to be considered successful. An example of one such test is provided in Appendix A, however in order to avoid double dimensioning the details for all of those tests is not repeated in this document. 4.1 BASIC SETUP Most of the requirement verification relies on the same basic setup; rather than repeat that information for each requirement the standard setup is captured here. Verifications which rely on a non-standard setup call that out in their pre-conditions section. Unless otherwise stated the OCS and its dependencies should be installed part of a DKIST End-to-End testbed. See SPEC-0022 for details on the pkgdevel framework and how to configure a system and the OCS Manual for an explanation of the OCS s pkgdevel options. The instructions here assume the use of the Tucson End-to-End testbed, but another testbed may be substituted. The OCS and the rest of the End-to-End testbed systems should be in the running state for all of its tests and unless otherwise noted may remain running between tests. The End-to-End test bed should be started following the instructions in the OCS manual. See the OCS manual for details on starting and stopping the test bed. 4.2 TESTS See the tests, one per page, on the following pages. PROC-0029 Rev A Page 6 of 208

8 4.2.1 OCS Definition Type Desugb Requirement PROC-0029 Rev A Page 7 of 208

9 4.2.2 Operator Support System Definition Type Design Requirement PROC-0029 Rev A Page 8 of 208

10 4.2.3 Experiment Execution System Definition Type Design Requirement PROC-0029 Rev A Page 9 of 208

11 4.2.4 Summit Management System Definition Type Design Requirement PROC-0029 Rev A Page 10 of 208

12 4.2.5 Best Software Practices Type Inspection Requirement PROC-0029 Rev A Page 11 of 208

13 4.2.6 Summit Software Management Type Test Requirement The OCS is running, the rest of the End-to-End testbed systems are not. Using the OCS Control screen, click on the Start Control GUIs button Using the Startup/Shutdown tab, click on the Start Tucson E2E button. HLS systems come up as configured. Some systems may not start due to lack of a simulator in the testbed, or because they must be controlled separately (e.g. the FCS). PROC-0029 Rev A Page 12 of 208

14 4.2.7 Application of Information Type Auto-test Requirement The End-to-End testbed, including the OCS, is running. PROC-0029 Rev A Page 13 of 208

15 4.2.8 Time to Accept or Reject a Comand Type Auto-test Requirement PROC-0029 Rev A Page 14 of 208

16 4.2.9 Boot Time Requirement PROC-0029 Rev A Page 15 of 208

17 Computer Resources Requirement PROC-0029 Rev A Page 16 of 208

18 Time Standard Type Auto-test Requirement PROC-0029 Rev A Page 17 of 208

19 Time Synchronization Type Auto-test Requirement PROC-0029 Rev A Page 18 of 208

20 Traceability Type Auto-test Requirement PROC-0029 Rev A Page 19 of 208

21 Logging Type Auto-test Requirement PROC-0029 Rev A Page 20 of 208

22 System States Type Auto-test Requirement PROC-0029 Rev A Page 21 of 208

23 Default State Type Auto-test Requirement PROC-0029 Rev A Page 22 of 208

24 Restart Type Auto-test Requirement PROC-0029 Rev A Page 23 of 208

25 Health Type Auto-test Requirement PROC-0029 Rev A Page 24 of 208

26 Health Check Type Inspection Requirement PROC-0029 Rev A Page 25 of 208

27 Health Report Type Auto-test Requirement PROC-0029 Rev A Page 26 of 208

28 Availability Requirement PROC-0029 Rev A Page 27 of 208

29 Persistence of Data Requirement PROC-0029 Rev A Page 28 of 208

30 User Interfaces Type Inspection Requirement PROC-0029 Rev A Page 29 of 208

31 User Interface Interaction Type Inspection Requirement PROC-0029 Rev A Page 30 of 208

32 Simultaneous Use Requirement PROC-0029 Rev A Page 31 of 208

33 Configuration Tracking Type Auto-test Requirement PROC-0029 Rev A Page 32 of 208

34 Events Type Auto-test Requirement PROC-0029 Rev A Page 33 of 208

35 Alarms Type Auto-test Requirement PROC-0029 Rev A Page 34 of 208

36 Host Computers and Operating Systems Type Design Requirement PROC-0029 Rev A Page 35 of 208

37 Computer Hardware Type Inspection Requirement PROC-0029 Rev A Page 36 of 208

38 Add-on Packages Type Inspection Requirement PROC-0029 Rev A Page 37 of 208

39 Computer Connectivity Requirement PROC-0029 Rev A Page 38 of 208

40 Acceptance Testing Traceability Type Auto-test Requirement PROC-0029 Rev A Page 39 of 208

41 Acceptance Test Failure Type Analysis Requirement PROC-0029 Rev A Page 40 of 208

42 Authorized Access Requirement PROC-0029 Rev A Page 41 of 208

43 IT Infrastructure Reliance Type Inspection Requirement PROC-0029 Rev A Page 42 of 208

44 Telescope Control System Interface Type Inspection Requirement PROC-0029 Rev A Page 43 of 208

45 Instrument Control System Interface Type Inspection Requirement PROC-0029 Rev A Page 44 of 208

46 Data Handling System Interface Type Inspection Requirement PROC-0029 Rev A Page 45 of 208

47 Operations Interface Type Inspection Requirement PROC-0029 Rev A Page 46 of 208

48 Global Interface System Interface Type Inspection Requirement PROC-0029 Rev A Page 47 of 208

49 Facility Control System Interface Type Inspection Requirement PROC-0029 Rev A Page 48 of 208

50 Facility Control System Monitoring Requirement PROC-0029 Rev A Page 49 of 208

51 Facility Control System Commands Requirement PROC-0029 Rev A Page 50 of 208

52 Health Reporting Requirement PROC-0029 Rev A Page 51 of 208

53 Health Reporting Rate Requirement PROC-0029 Rev A Page 52 of 208

54 Health Reporting User Interface Requirement PROC-0029 Rev A Page 53 of 208

55 Health Reporting Hierarchy Requirement PROC-0029 Rev A Page 54 of 208

56 Health Reporting Content Requirement PROC-0029 Rev A Page 55 of 208

57 Alarm Reporting Requirement PROC-0029 Rev A Page 56 of 208

58 Alarm Reporting Rate Requirement PROC-0029 Rev A Page 57 of 208

59 Alarm Reporting User Interface Requirement PROC-0029 Rev A Page 58 of 208

60 Alarm Reporting Hierarchy Requirement PROC-0029 Rev A Page 59 of 208

61 Alarm Reporting Content Requirement PROC-0029 Rev A Page 60 of 208

62 Alarm Reporting Response Requirement PROC-0029 Rev A Page 61 of 208

63 System Status Reporting Requirement PROC-0029 Rev A Page 62 of 208

64 System Status Display Availability Requirement PROC-0029 Rev A Page 63 of 208

65 Simultaneous Monitoring Requirement PROC-0029 Rev A Page 64 of 208

66 Scope Type Inspection Requirement PROC-0029 Rev A Page 65 of 208

67 Operational Behavior Requirement PROC-0029 Rev A Page 66 of 208

68 Default Operational Behavior Requirement PROC-0029 Rev A Page 67 of 208

69 Automatic Execution Type Design Requirement PROC-0029 Rev A Page 68 of 208

70 Manual Operation Type Design Requirement PROC-0029 Rev A Page 69 of 208

71 Experiment Management Type Design, Inspection Requirement PROC-0029 Rev A Page 70 of 208

72 Common Services Management Type Design, Inspection Requirement PROC-0029 Rev A Page 71 of 208

73 User Interaction Management Type Design, Inspection Requirement PROC-0029 Rev A Page 72 of 208

74 Telescope Control System Type Design, Manual-test Requirement PROC-0029 Rev A Page 73 of 208

75 Instrument Control System Type Design, Manual-test Requirement PROC-0029 Rev A Page 74 of 208

76 Facility Control System Type Design, Manual-test Requirement PROC-0029 Rev A Page 75 of 208

77 Data Handling System Type Design, Manual-test Requirement PROC-0029 Rev A Page 76 of 208

78 Software Resources Type Design, Manual-test Requirement PROC-0029 Rev A Page 77 of 208

79 OCS Databases Type Design, Manual-test Requirement PROC-0029 Rev A Page 78 of 208

80 Summit Database Management Type Design, Manual-test Requirement PROC-0029 Rev A Page 79 of 208

81 Import from DKIST Experiment Database Requirement PROC-0029 Rev A Page 80 of 208

82 Export to DKIST Experiment Database Requirement PROC-0029 Rev A Page 81 of 208

83 Facility Task Properties Requirement PROC-0029 Rev A Page 82 of 208

84 Facility Task Management Requirement PROC-0029 Rev A Page 83 of 208

85 Facility Task Automation Requirement PROC-0029 Rev A Page 84 of 208

86 Facility Task Step-wise Execution Requirement PROC-0029 Rev A Page 85 of 208

87 Facility Task GUI Requirement PROC-0029 Rev A Page 86 of 208

88 Facility Task -- Startup Requirement PROC-0029 Rev A Page 87 of 208

89 Facility Task Startup Completion State Requirement PROC-0029 Rev A Page 88 of 208

90 Facility Task Solar Open Requirement PROC-0029 Rev A Page 89 of 208

91 Facility Task -- Close Requirement PROC-0029 Rev A Page 90 of 208

92 Facility Task -- Shutdown Requirement PROC-0029 Rev A Page 91 of 208

93 Facility Task Non-Solar Open Requirement PROC-0029 Rev A Page 92 of 208

94 Facility Task -- Standby Requirement PROC-0029 Rev A Page 93 of 208

95 Observing Program Execution Requirement PROC-0029 Rev A Page 94 of 208

96 Observing Program Execution Scripting Language Requirement PROC-0029 Rev A Page 95 of 208

97 Observing Program Execution Script Support Requirement PROC-0029 Rev A Page 96 of 208

98 Observing Program Execution - Completion Requirement PROC-0029 Rev A Page 97 of 208

99 Observing Program Execution Time to Completion Requirement PROC-0029 Rev A Page 98 of 208

100 Observing Program Execution Testing at Night Requirement PROC-0029 Rev A Page 99 of 208

101 Observing Program Execution Testing During the Day Requirement PROC-0029 Rev A Page 100 of 208

102 Observing Program Execution TCS Passive Requirement PROC-0029 Rev A Page 101 of 208

103 Observing Program Status Tracking Requirement PROC-0029 Rev A Page 102 of 208

104 Observing Program Status Override Requirement PROC-0029 Rev A Page 103 of 208

105 Observing Program Execution Tracking Requirement PROC-0029 Rev A Page 104 of 208

106 Instrument Program Status Tracking Requirement PROC-0029 Rev A Page 105 of 208

107 Instrument Program Execution Tracking Requirement PROC-0029 Rev A Page 106 of 208

108 Observing Program Test Tracking Requirement PROC-0029 Rev A Page 107 of 208

109 Observing Program Modification Tracking Requirement PROC-0029 Rev A Page 108 of 208

110 Target Modification Tracking Requirement PROC-0029 Rev A Page 109 of 208

111 Experiment List Selection Requirement PROC-0029 Rev A Page 110 of 208

112 Experiment Selection Requirement PROC-0029 Rev A Page 111 of 208

113 Observing Program Selection Requirement PROC-0029 Rev A Page 112 of 208

114 Instrument Program Display Requirement PROC-0029 Rev A Page 113 of 208

115 Test and TCS Passive Selection Requirement PROC-0029 Rev A Page 114 of 208

116 Data Save Selection Requirement PROC-0029 Rev A Page 115 of 208

117 Observing Program Execution Selection Requirement PROC-0029 Rev A Page 116 of 208

118 Summit Experiment Repository Searching Requirement PROC-0029 Rev A Page 117 of 208

119 Observing Program TCS Control Requirement PROC-0029 Rev A Page 118 of 208

120 Observing Program ICS Control Requirement PROC-0029 Rev A Page 119 of 208

121 Observing Program ICS/TCS Sequencing Requirement PROC-0029 Rev A Page 120 of 208

122 Observing Program Execution Requirement PROC-0029 Rev A Page 121 of 208

123 Observing Program Execution Abort/Cancel Requirement PROC-0029 Rev A Page 122 of 208

124 Observing Program Instrument Execution -- Abort/Cancel Requirement PROC-0029 Rev A Page 123 of 208

125 Observing Program AO Lock-Point Adjust Requirement PROC-0029 Rev A Page 124 of 208

126 Observing Program Script Status Display and Reporting Requirement PROC-0029 Rev A Page 125 of 208

127 Telescope Mosaicking Support Requirement PROC-0029 Rev A Page 126 of 208

128 Mosaic Target Representation Requirement PROC-0029 Rev A Page 127 of 208

129 Mosaic Position Representation Requirement PROC-0029 Rev A Page 128 of 208

130 Telescope Mosaicking Interaction Requirement PROC-0029 Rev A Page 129 of 208

131 Telescope Mosaicking Coordinate System Requirement PROC-0029 Rev A Page 130 of 208

132 Manual System Control Requirement PROC-0029 Rev A Page 131 of 208

133 Manual System Control Access Requirement PROC-0029 Rev A Page 132 of 208

134 Manual System Instrument Program Modification Requirement PROC-0029 Rev A Page 133 of 208

135 Manual Execution Data Save Requirement PROC-0029 Rev A Page 134 of 208

136 Manual Instrument Control Requirement PROC-0029 Rev A Page 135 of 208

137 Manual Instrument Control Instrument Control Access Requirement PROC-0029 Rev A Page 136 of 208

138 Manual Instrument Control Instrument Program Abort/Cancel Requirement PROC-0029 Rev A Page 137 of 208

139 Experiment Operators Tool Requirement PROC-0029 Rev A Page 138 of 208

140 Operator Telescope Control Tools Requirement PROC-0029 Rev A Page 139 of 208

141 Operator Target Selection Tool Requirement PROC-0029 Rev A Page 140 of 208

142 Operator Target Selection Target Details Requirement PROC-0029 Rev A Page 141 of 208

143 Operator Target Selection -- Target Detail Modification Requirement PROC-0029 Rev A Page 142 of 208

144 Operator Target Selection Target Repositioning Requirement PROC-0029 Rev A Page 143 of 208

145 Operator Target Selection Target Selection Mosaicking Support Requirement PROC-0029 Rev A Page 144 of 208

146 Operator Target Selection Target Additions Requirement PROC-0029 Rev A Page 145 of 208

147 Operator Target Selection Target Persistence Requirement PROC-0029 Rev A Page 146 of 208

148 Operator Target Selection Predefined Target Selection Requirement PROC-0029 Rev A Page 147 of 208

149 Operator Target Selection Target Loading Requirement PROC-0029 Rev A Page 148 of 208

150 Operator Target Selection Target Association Requirement PROC-0029 Rev A Page 149 of 208

151 Operator Target Selection Non-Solar Pointing Requirement PROC-0029 Rev A Page 150 of 208

152 Operator Target Selection -- Ephemerides Requirement PROC-0029 Rev A Page 151 of 208

153 Operator Target Selection Tracking Mode Selection Requirement PROC-0029 Rev A Page 152 of 208

154 Operator Target Selection Target Order Requirement PROC-0029 Rev A Page 153 of 208

155 Target Selection Tool Observing Program Interaction Requirement PROC-0029 Rev A Page 154 of 208

156 Target Selection Tool -- Target Modification Scope Requirement PROC-0029 Rev A Page 155 of 208

157 Target Selection Tool Image Data Requirement PROC-0029 Rev A Page 156 of 208

158 Target Selection Tool TAS Image Display Requirement PROC-0029 Rev A Page 157 of 208

159 Target Selection Tool WCCS Image Display Requirement PROC-0029 Rev A Page 158 of 208

160 Target Selection Tool Remote Image Display Requirement PROC-0029 Rev A Page 159 of 208

161 Target Selection Tool Time Corrections Requirement PROC-0029 Rev A Page 160 of 208

162 Target Selection Tool Field of View Display Requirement PROC-0029 Rev A Page 161 of 208

163 Target Selection Tool Image Annotation Requirement PROC-0029 Rev A Page 162 of 208

164 Target Selection Tool Coordinate Entry Requirement PROC-0029 Rev A Page 163 of 208

165 Target Selection Tool Coordinate Display Requirement PROC-0029 Rev A Page 164 of 208

166 Target Selection Tool Image Data Rate Requirement PROC-0029 Rev A Page 165 of 208

167 Adaptive Optics Lock Point Identification Requirement PROC-0029 Rev A Page 166 of 208

168 Adaptive Options Lock Point Association Requirement PROC-0029 Rev A Page 167 of 208

169 Adaptive Options Lock Point Control Requirement PROC-0029 Rev A Page 168 of 208

170 Adaptive Optics Default Lock Point Requirement PROC-0029 Rev A Page 169 of 208

171 Environment Monitoring Requirement PROC-0029 Rev A Page 170 of 208

172 Environment Monitoring Update Rate Requirement PROC-0029 Rev A Page 171 of 208

173 Environment Monitoring Graphical Display Requirement PROC-0029 Rev A Page 172 of 208

174 Data Association Requirement PROC-0029 Rev A Page 173 of 208

175 Remote Operations Building Capabilities Requirement PROC-0029 Rev A Page 174 of 208

176 Multi-Instrument Operations Requirement PROC-0029 Rev A Page 175 of 208

177 Synchronized Data Acquisition Requirement PROC-0029 Rev A Page 176 of 208

178 Pacing Instruments Requirement PROC-0029 Rev A Page 177 of 208

179 Pacing Instrument -- Delivery Requirement PROC-0029 Rev A Page 178 of 208

180 Non-Solar Targets Requirement PROC-0029 Rev A Page 179 of 208

181 Non-Solar Targets -- Coordinates Requirement PROC-0029 Rev A Page 180 of 208

182 Non-Solar Targets -- Tracking Requirement PROC-0029 Rev A Page 181 of 208

183 Pointing Accuracy Requirement PROC-0029 Rev A Page 182 of 208

184 Data Tagging Requirement PROC-0029 Rev A Page 183 of 208

185 Completion Assessment Support Requirement PROC-0029 Rev A Page 184 of 208

186 Triggered Log Entries Requirement PROC-0029 Rev A Page 185 of 208

187 Periodic Log Entries Requirement PROC-0029 Rev A Page 186 of 208

188 Periodic Log Entry Rate Requirement PROC-0029 Rev A Page 187 of 208

189 Weather Station Log Entry Rate Requirement PROC-0029 Rev A Page 188 of 208

190 Internet-derived Log Entry Rate Requirement PROC-0029 Rev A Page 189 of 208

191 Manual Log Entries Requirement PROC-0029 Rev A Page 190 of 208

192 Software Facility Management Requirement PROC-0029 Rev A Page 191 of 208

193 Software Framework Lifecycle Control Requirement PROC-0029 Rev A Page 192 of 208

194 Connection Service Control Requirement PROC-0029 Rev A Page 193 of 208

195 Event Service Control Requirement PROC-0029 Rev A Page 194 of 208

196 Experiment Service Control Requirement PROC-0029 Rev A Page 195 of 208

197 Property Service Control Requirement PROC-0029 Rev A Page 196 of 208

198 Log Service Control Requirement PROC-0029 Rev A Page 197 of 208

199 Engineering Archive Service Control Requirement PROC-0029 Rev A Page 198 of 208

200 Health Service Control Requirement PROC-0029 Rev A Page 199 of 208

201 Alarm Service Control Requirement PROC-0029 Rev A Page 200 of 208

202 Database Access Requirement PROC-0029 Rev A Page 201 of 208

203 Subsystem Deployment Control Requirement PROC-0029 Rev A Page 202 of 208

204 Engineering Archive Behavior Requirement PROC-0029 Rev A Page 203 of 208

205 Engineering Archive Command Tracking Requirement PROC-0029 Rev A Page 204 of 208

206 Engineering Archive Persistence Requirement PROC-0029 Rev A Page 205 of 208

207 Engineering Archive Export Requirement PROC-0029 Rev A Page 206 of 208

208 Simulation Support Requirement PROC-0029 Rev A Page 207 of 208

209 Simulation Management Requirement PROC-0029 Rev A Page 208 of 208