1. Refined ECSS Software Process Model Elements SD-TN-AI-0570, Issue 5 APPENDIX D

2. Software Reuse Developing SW for Intended Reuse Reusing SW from other Projects HCI Software Critical Software Real Time Software Simulation Software Tailored ECSS Software Process Model Elements App. D 2 0f 34

3. HCI Software Validation against the Technical Specification HCI Testing HCI Software HCI Software Process Model Tailoring Project Phasing & Planning Definition of HCI Engineering Standards HCI Software System Requirements Engineering HCI System Requirements Analysis HCI Software Requirements Engineering Process App. D 3 0f 34

4. Elements of SW Maintenance Plan Requirements Baseline at SRR Documentation Standards Design Standards Verification and Validation Standards Software Project Development Plan Parent: HCI Software Development Process Perspective: Software Engineering Activity: Project Phasing and Planning Diagram: 4 / HCI External References: ECSS-E-40, ECSS-Q-80 In Triggers (IT)Out Triggers (OT)External Inputs (EI) EI1: SW PA Plan Review EI2: SW PA Procedures & Standards Review EI3: SW PA Life Cycle Review External Outputs (EO) Requirements Baseline at SRR Software Project Development Plan (Life cycle, tools and methods definition) Software Life Cycle Definition (milestones, reviews and maintenance planning) SLC-1 E-40: 5.3.2.1 Documentation/Inputs- Output Process definition for each phase and Milestone SLC-3 E-40: 5.3.2.2 SRR SUPPLIER ECSS-M-30 PROJECT RQMTS ECSS-E_40 Sec 4.5 System vs Software Requirements Requirements Baseline SW Project Development Plan SUPPLIER Definition of Software Engineering Standards SLC-2 E-40: 5.3.2.11 Requirements Baseline SW Project Development Plan SUPPLIER Software Project Development Plan Review EI1 EI2 EI3 HCI Software - Tailored Project Phasing & Planning ProcessT Definition of HCI Engineering Standards T HCI Standards and selected HCI Design & Development Methodologies (CUSTOMER) / SUPPLIER

5. HCI Software - Tailored SW System Requirements Engineering ProcessT Overall System Requirements RB (inputs to) IRD (inputs to) RB (System partition with definition of items; System Configuration list) IRD (SW/HW interface requirements) DJF (Traceability to system partitioning) Parent: HCI Software Development ProcessPerspective: Software Engineering Activity: HCI SW System Requirements Engineering Diagram: 12 / HCI External References: ECSS-E-40 sec. 5.2.2, 5.2.3, 5.2.4, 5.2.5 In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) System level Rqmts for SW Verification and Validation SE –3 E-40 sec. 5.2.4 SRR System Requirements Analyis SE –1 E-40 sec. 5.2.2 System Partitioning SE-2 E-40 sec. 5.2.3 CUSTOMER System level Integration of Software SE –4 E-40 sec. 5.2.5 CUSTOMER SRR Data Package RB, IRD DJF RB: V&V Process requirements RB (inputs to) IRD (inputs to) Reviewed SRR Data Package RB, IRD DJF Usability & Learnability Requirements Analysis T Usability & Learnability Test Planning T

6. HCI Software - Tailored System RequirementsAnalysis ProcessT RB: Functions & Performance Rqmts IRD: Interface Rqmts Parent: HCI SW System Requirement Engineering Process Perspective: Software Engineering Activity: HCI System Requirements Analysis Diagram: 13 / HCI External References: ECSS-E-40 sec. 5.2.2.1, 5.2.2.2, 5.2.6.2 In Triggers (IT) Out Triggers (OT) External Inputs (EI)External Outputs (EO) Definition of system functionalities and interfaces SYS-1 E-40 sec. 5.2.2.1 Overall system reqmts Operations and Maintenance Requirements Definition SYS-2 E-40 sec. 5.2.2.1, 5.2.6.2 V&V Rqmts and Design Constraints SYS-3 E-40 sec. 5.2.2.1 System Criticality / Critical Functions Definition SYS-4 E-40 sec. 5.2.2.2 RB:- Safety & Reliability Rqmts - Critical functions identification RB: Design Constraints V&V requirements - SW Eng. Standards RB: Operations and maintenance requirement RB (inputs to) IRD (inputs to) CUSTOMER Human Factors Engineering (HFE) Requirements Definition T RB: HFE Requirements CUSTOMER

7. HCI Software - Tailored Software Requirements Engineering ProcessT Activity: HCI SW Requirements Engin.ng Process DIAG.#15 / HCI Functional and Capability Specification SUPPLIER External References: ECSS-E-40 sec.5.4.2, 5.4.3, 5.4.4 Parent: HCI Software Development Process Perspective: Software Engineering In Triggers (IT)Out Triggers (OT)External Inputs (EI) EI1: SW PA Requirements (diag. 26) External Outputs (EO) Software Requirements Analysis R-1 E-40 sec. 5.4.2 SUPPLIER SRR Docs: IRD RB EI1 Preliminary Design Review E-40 sec. 5.4.3.6 Delivered PDR DP Reviewed PDR DP PDR Data Package PDR Report Reliability and System Analysis Q-80 sec. 3.3.2e System Level Functional Analysis SW RAMS Analysis Higher Level Safety Plan Software Top Level Architectural Design R-2 E-40 sec.5.4.3 HCI SW Prototyping E-40 6.5.1.3

8. HCI Software - Tailored Software TS-Validation ProcessT SW design and test evaluation report Validation Plan, Validation Reqs Validation Testing reports, Non conformance reports, Problem reports, Validated Software SW Product, Validation Environment (HW/SW) SW Validation Test Spec.n Parent: HCI Software Design Engineering Process Perspective: Verification & Validation Engineering Activity: SW Validation against TS Diagram: 56 / HCI External References: ECSS-E-40 sec. 5.5.xx, ECSS-Q-80 sec. 3.3.4q, 3.3.4g, 3.3.4r In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) Software TS-Validation Testing Specification Definition VI-1 E-40 sec. 5.5.5.1 (cr) Update and prepare the SW product release VI-5 E-40 sec. 5.5.5.6 (cr) Evaluate the design, code, test and operation manual VI-4 E-40 sec. 5.5.5.6 (cr) Validation testing against the TS VI-2 E-40 sec. 5.5.5.2 (cr) Update the operation manual VI-3 E-40 sec. 5.5.5.4 (cr) SW on delivery media, SW release doc., Baseline deliverables Operation manual (update) Test Readiness Review Q-80 sec. 3.3.4f Test Readiness Review Board Q-80 sec. 3.3.4t Verify Test E-40 sec. 5.6.6.6 Analysis and Inspection VI-6 E-40 sec. 5.5.5.3 (cr) CDR Data Package Analysis and Inspection reports SW Specification SUPPLIER SW Design/Code Check Coverage Q-80-3.3.gt HCI Testing T

9. HCI Software - Specific HCI Testing ProcessT Parent: HCI SW Validation against TS Perspective: Verification & Validation Engineering Activity: HCI Testing Diagram: 56 / 1-HCI1 External References: In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) HCI Special Tests input to: Validation Testing reports, Non conformance reports, Problem reports, Validated Software SW Product, Validation Environment (HW/SW) SW Validation Test Spec.n Perform HCI Robustness & Stress Tests T Perform Interactive Sessions HCI Testing T Perform Usability Tests T Test Readiness Review Q-80 sec. 3.3.4f HCI TS- Validation Test Specification HCI Interactive Test Specification Special HFE derived Test Specification HCI SW Test Subjects Readiness HCI Robustness & Stress Tests Reports HCI Interactive Tests Report with Test Subjects Learnability Feedback HFE Test Report

10. Critical Software Critical Software Process Model Elements Project Phasing & Planning Definition of Engineering Standards for Critical Software Critical Software System Requirements Engineering System Requirements Analysis of Critical Software Critical Software Requirements Engineering Process App. D 10 0f 34

11. Critical Software - Tailored Project Phasing & Planning ProcessT Elements of SW Maintenance Plan Requirements Baseline at SRR Documentation Standards Design Standards Verification and Validation Standards Software Project Development Plan Parent: Critical Software Development Process Perspective: Software Engineering Activity: Project Phasing and Planning Diagram: 4 / CRT External References: ECSS-E-40, ECSS-Q-80 In Triggers (IT)Out Triggers (OT)External Inputs (EI) EI1: SW PA Plan Review EI2: SW PA Procedures & Standards Review EI3: SW PA Life Cycle Review External Outputs (EO) Requirements Baseline at SRR Software Project Development Plan (Life cycle, tools and methods definition) Software Life Cycle Definition (milestones, reviews and maintenance planning) SLC-1 E-40: 5.3.2.1 Documentation/Inputs- Output Process definition for each phase and Milestone SLC-3 E-40: 5.3.2.2 SRR SUPPLIER ECSS-M-30 PROJECT RQMTS ECSS-E_40 Sec 4.5 System vs Software Requirements Requirements Baseline SW Project Development Plan SUPPLIER Definition of Software Engineering Standards SLC-2 E-40: 5.3.2.11 Requirements Baseline SW Project Development Plan SUPPLIER Software Project Development Plan Review EI1 EI2 EI3 Definition of specific Standards for Critical Software T Dependability & Safety specific Standards & Process Requirements (CUSTOMER) / SUPPLIER

12. Critical Software - Tailored Software System Requirements Engineering ProcessT Overall System Requirements RB (inputs to) IRD (inputs to) RB (System partition with definition of items; System Configuration list) IRD (SW/HW interface requirements) DJF (Traceability to system partitioning) Parent: Critical Software Development ProcessPerspective: Software Engineering Activity: Critical SW System Requirements Eng.ng Diagram: 12 / CRT External References: ECSS-E-40 sec. 5.2.2, 5.2.3, 5.2.4, 5.2.5 In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) System level Rqmts for SW Verification and Validation SE –3 E-40 sec. 5.2.4 SRR System Requirements Analyis SE –1 E-40 sec. 5.2.2 System Partitioning SE-2 E-40 sec. 5.2.3 CUSTOMER System level Integration of Software SE –4 E-40 sec. 5.2.5 CUSTOMER SRR Data Package RB, IRD DJF RB: V&V Process requirements, including Test Requirements for Critical SW RB (inputs to) IRD (inputs to) Reviewed SRR Data Package RB, IRD DJF Software Criticality Analysis T Test Planning for Critical Software T Software Criticality Analysis Consolidation for Products Categorisation T

13. Activity: Critical SW System Requirements Analysis Diagram: 13 / CRT Critical Software - Tailored System Requirements Analysis ProcessT RB: Functions & Performance Rqmts IRD: Interface Rqmts Parent: Critical SW System Requirement Engineering Process Perspective: Software Engineering External References: ECSS-E-40 sec. 5.2.2.1, 5.2.2.2, 5.2.6.2 In Triggers (IT) Out Triggers (OT) External Inputs (EI)External Outputs (EO) Definition of system functionalities and interfaces SYS-1 E-40 sec. 5.2.2.1 Overall system reqmts Operations and Maintenance Requirements Definition SYS-2 E-40 sec. 5.2.2.1, 5.2.6.2 V&V Rqmts and Design Constraints SYS-3 E-40 sec. 5.2.2.1 System Criticality / Critical Functions Definition SYS-4 E-40 sec. 5.2.2.2 RB:- Safety & Reliability Rqmts - Critical functions identification RB: Design Constraints V&V requirements - SW Eng. Standards RB: Operations and maintenance requirement RB (inputs to) IRD (inputs to) CUSTOMER Dependability & Safety Specific Requirements Definition for Critical Software T RB: Dependability/Safety Requirements for Critical SW Requirements CUSTOMER

14. Critical Software - Tailored Software Requirements Engineering ProcessT Activity: SW Requirements Engineering Process DIAG.#15 / CRT Functional and Capability Specification SUPPLIER External References: ECSS-E-40 sec.5.4.2, 5.4.3, 5.4.4 Parent: Critical Software Development Process Perspective: Software Engineering In Triggers (IT)Out Triggers (OT)External Inputs (EI) EI1: SW PA Requirements (diag. 26) External Outputs (EO) Software Requirements Analysis R-1 E-40 sec. 5.4.2 SUPPLIER SRR Docs: IRD RB EI1 Preliminary Design Review E-40 sec. 5.4.3.6 Delivered PDR DP Reviewed PDR DP PDR Data Package PDR Report Reliability and System Analysis Q-80 sec. 3.3.2e System Level Functional Analysis SW RAMS Analysis Higher Level Safety Plan Software Top Level Architectural Design R-2 E-40 sec.5.4.3 SW Prototyping for Critical Components T

15. Real Time Software Real Time Software Process Model Elements Software Validation against the Technical Specification Project Phasing & Planning Definition of Engineering Standards for Real Time Software Real Time Software System Requirements Engineering System Requirements Analysis of Real Time Software Real Time Software Requirements Engineering Process SEEA Process App. D 15 0f 34

16. Elements of SW Maintenance Plan Requirements Baseline at SRR Documentation Standards Design Standards Verification and Validation Standards Software Project Development Plan Parent: Real-Time Software Development Process Perspective: Software Engineering Activity: Project Phasing and Planning Diagram: 4 / RT External References: ECSS-E-40, ECSS-Q-80 In Triggers (IT)Out Triggers (OT)External Inputs (EI) EI1: SW PA Plan Review EI2: SW PA Procedures & Standards Review EI3: SW PA Life Cycle Review External Outputs (EO) Requirements Baseline at SRR Software Project Development Plan (Life cycle, tools and methods definition) Software Life Cycle Definition (milestones, reviews and maintenance planning) SLC-1 E-40: 5.3.2.1 Documentation/Inputs- Output Process definition for each phase and Milestone SLC-3 E-40: 5.3.2.2 SRR SUPPLIER ECSS-M-30 PROJECT RQMTS ECSS-E_40 Sec 4.5 System vs Software Requirements Requirements Baseline SW Project Development Plan SUPPLIER Definition of Software Engineering Standards SLC-2 E-40: 5.3.2.11 Requirements Baseline SW Project Development Plan SUPPLIER Software Project Development Plan Review EI1 EI2 EI3 Real-Time Software - Tailored Project Phasing & Planning ProcessT Definition of HRT / RT Engineering & Test Standards T Specific Standards and selected Design & Development Methodologies for RT and HRT SW (CUSTOMER) / SUPPLIER Assess HW-SW AIV Needs & Requirements T Dependencies

17. Real-Time Software - Tailored Software System Requirements Engineering ProcessT Overall System Requirements RB (inputs to) IRD (inputs to) RB (System partition with definition of items; System Configuration list) IRD (SW/HW interface requirements) DJF (Traceability to system partitioning) Parent: RT Software Development ProcessPerspective: Software Engineering Activity: RT SW System Requirements Engineering Diagram: 12 / RT External References: ECSS-E-40 sec. 5.2.2, 5.2.3, 5.2.4, 5.2.5 In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) System level Rqmts for SW Verification and Validation SE –3 E-40 sec. 5.2.4 SRR System Requirements Analyis SE –1 E-40 sec. 5.2.2 System Partitioning SE-2 E-40 sec. 5.2.3 CUSTOMER System level Integration of Software SE –4 E-40 sec. 5.2.5 CUSTOMER SRR Data Package RB, IRD DJF RB: V&V Process requirements RB (inputs to) IRD (inputs to) Reviewed SRR Data Package RB, IRD DJF RT Performance Requirements specific Analyses T HRT - RT SW Test-Bed and Test Scenario requirements T

18. Real-Time Software - Tailored System RequirementsAnalysis ProcessT RB: Functions & Performance Rqmts IRD: Interface Rqmts Parent: RT SW System Requirement Engineering Process Perspective: Software Engineering Activity: RT System Requirements Analysis Diagram: 13 / RT External References: ECSS-E-40 sec. 5.2.2.1, 5.2.2.2, 5.2.6.2 In Triggers (IT) Out Triggers (OT) External Inputs (EI)External Outputs (EO) Definition of system functionalities and interfaces SYS-1 E-40 sec. 5.2.2.1 Overall system reqmts Operations and Maintenance Requirements Definition SYS-2 E-40 sec. 5.2.2.1, 5.2.6.2 V &V Rqmts and Design Constraints SYS-3 E-40 sec. 5.2.2.1 System Criticality / Critical Functions Definition SYS-4 E-40 sec. 5.2.2.2 RB:- Safety & Reliability Rqmts - Critical functions identification RB: Design Constraints V&V requirements - SW Eng. Standards RB: Operations and maintenance requirement RB (inputs to) IRD (inputs to) CUSTOMER Control System RT Requirements & Operational Constraints Definition T RB: RT Control System and Performance Requirements CUSTOMER Assessments of the needs for Test Support SW and Simulation Models T

19. Real Time Software - Tailored Software Requirements Engineering ProcessT Activity: SW Requirements Engineering Process DIAG.#15 / CRT Functional and Capability Specification SUPPLIER External References: ECSS-E-40 sec.5.4.2, 5.4.3, 5.4.4 Parent: RT Software Development Process Perspective: Software Engineering In Triggers (IT)Out Triggers (OT)External Inputs (EI) EI1: SW PA Requirements (diag. 26) External Outputs (EO) Software Requirements Analysis R-1 E-40 sec. 5.4.2 SUPPLIER SRR Docs: IRD RB EI1 PDR Delivered PDR DP Reviewed PDR DP PDR Report Reliability and System Analysis Q-80 sec. 3.3.2e System Level Functional Analysis SW RAMS Analysis Higher Level Safety Plan Software Top Level Architectural Design R-2 E-40 sec.5.4.3 RT SW Prototyping for Critical Controls & Algorithms T Numerical Analysis of required Algorithms T Dynamic Modelling of Design (e.g. Petri-Net Model) T

20. External References In Triggers (IT) Out Triggers (OT) External Inputs (EI) External Outputs (EO) Parent: RT SW Requirements Engineering Process Perspective: SW Product Assurance Activity: RT SW SEEA Diagram: 15.1 T Analyse RT Software Design for Propagation & Errors Effects 15.1.1 T Recommend Designs for Minimisation of SW Errors Effects 15.1.2 T Provide Recommendations for RT SW Validation 15.1.3 T DJF: SEAA Reports TS DDF-DJF Real Time Software - Tailored Software Requirements Engineering ProcessT SW RAMS Analysis RT SW Design Analysis Design Recommendation Validation Recommendation

21. T SW design and test evaluation report Validation Plan, Validation Reqs Validation Testing reports, Non conformance reports, Problem reports, Validated Software SW Product, Validation Environment (HW/SW) SW Validation Test Spec.n Parent: RT Software Design Engineering Process Perspective: Verification & Validation Engineering Activity:RT SW Validation against TS Diagram: 56 / RT External References: ECSS-E-40 sec. 5.5.xx, ECSS-Q-80 sec. 3.3.4q, 3.3.4g, 3.3.4r In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) Software TS-Validation Testing Specification Definition VI-1 E-40 sec. 5.5.5.1 (cr) Update and prepare the SW product release VI-5 E-40 sec. 5.5.5.6 (cr) Evaluate the design, code, test and operation manual VI-4 E-40 sec. 5.5.5.6 (cr) Validation testing against the TS VI-2 E-40 sec. 5.5.5.2 (cr) Update the operation manual VI-3 E-40 sec. 5.5.5.4 (cr) SW on delivery media, SW release doc., Baseline deliverables Operation manual (update) Test Readiness Review Q-80 sec. 3.3.4f Test Readiness Review Board Q-80 sec. 3.3.4t Verify Test E-40 sec. 5.6.6.6 Analysis and Inspection VI-6 E-40 sec. 5.5.5.3 (cr) CDR Data Package Analysis and Inspection reports SW Specification SUPPLIER SW Design/Code Check Coverage Q-80-3.3.gt Real-Time Software - Tailored Software TS-Validation Process RT Closed-Loop Testing on Target T Test-bed

22. Simulation Software Process Model Elements Simulation Software Simulation Software Design Process Design of Software Items Simulation Software Requirements Engineering Process App. D 23 0f 34

23. External References In Triggers (IT)Out Triggers (OT): OT1: Activities @ Re-use Process External Inputs (EI) EI1: from SSSW Process EI0: From the SRR Process External Outputs (EO) Simulation SW Requirements Analysis GSSW-3-1-1-1 RM-15 Simulation High Level Modelling T RB: SW PA Requirements (SIM SW) System Specification SW IF Requirements Document SIM SW Requirements Specification SIM SW Design Document SIM SW Integration Test Plan SIM SW Operation Manual SIM SW ICD EI1: Flight SW ICDs Flight System and HW Documentation RT W Req.s Spec. E10: SIM SW Development Plan TS-DDF-DJF-ICD Design to Requirements Engineering Feedback. Generate Simulation Models Design Hierarchy for Autocode T Tailoring for Simulation SW Specification Phase, using Tools supporting Simulation Models Design & Generation Simulation Algorithms Numerical Analysis T ECSS-Q-80 4.1.11/12 Parent: SIM SWDevelopment Process Perspective: Software Engineering Activity: SIM SWRequirements Eng.ng Process Diagram 15 / SIM OT1: Re-use Process Simulation SW Top Level Architectural Design GSSW-3-1-1-2 RM-15 Simulation Software - Tailored Software Requirements Engineering ProcessT EI1: Flight SW ICDs Flight System and HW Documentation

24. External References In Triggers (IT)Out Triggers (OT): OT1: Activities @ Re-use Process External Inputs (EI) EI1: from SSSW Process EI0: From the SRR Process External Outputs (EO) Tailoring for Simulation SW Design Phase, using Tools supporting Simulation Models Code Generation Parent: SIM SWDevelopment Process Perspective: Software Engineering Activity: SIM SW Design of SW Items Diagram: 19 / SIM Code, Unit tests Documentation Coding and Testing GSSW-3-1-2-2 SD-2 Coding and Testing GSSW-3-1-2-2 SD-2 Integration GSSW-3-1-2-3 SD-1 Detailed Design CDR Report Numerical Analyses Report Design and Generation of Software Items SD-1 /T Design and Generation of Software Items SD-1 /T Autocode Artifacts Design of Software Items GSSW-3-1-2-1 SD-1 Design of Software Items GSSW-3-1-2-1 SD-1 PDR Outputs OT1: Re-use Process Simulation Software - Tailored Design of Software Items ProcessT

25. Developing Software for Intended Reuse Tailoring the Software Requirements Engineering Process Reuse of Software from other Projects Tailoring the Software Requirements Engineering Process Tailoring the Software Design Process Software Reuse Developing SW for Intended Reuse Reusing SW from other Projects Software Reuse Process Model Elements App. D 26 0f 34

26. Software Reuse Technical Specification, Interface Control Document, Design Justification File Customer needs Parent: SW Development Process Perspective: Software Engineering Activity: Software Development Process Diagram: 11 External References: ECSS-E-40 In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) Software/System Requirement Engineering Process SEP-1 E-40 sec 5.2 Software Requirement Engineering Process SEP-2 / T E-40 sec 5.4 Software Design Engineering Process SEP-3 / T E-40 sec 5.5 Requirements Baseline, Interface Requirements Document, design Justification File Design Definition File Requirements Baseline, Interface Requirements Document, design Justification File Interface Management SEP-5 E-40 sec. 5.3.3 Hardware Environment Interface Management Procedures Design Justification File ECSS-M-30 Project Requirements Project Phasing and Planning SEP-4 ECSS-M-30A ECSS-E-40 sec. 5.3.2 SUPPLIER Requirements Baseline ECSS-M-40 Requirements Technical Budget and Margin Management SEP-6 E-40 sec 5.3.4 HW Environment DJF: Technical budgets status and margin SUPPLIER/ CUSTOMER SUPPLIER CUSTOMER T for both Intended reuse and reuse from other projects for reuse from other projects

27. Software Reuse - Tailored Software Development Process Technical Specification, Interface Control Document, Design Justification File Customer needs Parent: SW Development Process Perspective: Software Engineering Activity: Software Development Process Diagram: 11 External References: ECSS-E-40 In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) Software/System Requirement Engineering Process SEP-1 E-40 sec 5.2 Software Requirement Engineering Process SEP-2 / T E-40 sec 5.4 Software Design Engineering Process SEP-3 / T E-40 sec 5.5 Requirements Baseline, Interface Requirements Document, design Justification File Design Definition File Requirements Baseline, Interface Requirements Document, design Justification File Interface Management SEP-5 E-40 sec. 5.3.3 Hardware Environment Interface Management Procedures Design Justification File ECSS-M-30 Project Requirements Project Phasing and Planning SEP-4 ECSS-M-30A ECSS-E-40 sec. 5.3.2 SUPPLIER Requirements Baseline ECSS-M-40 Requirements Technical Budget and Margin Management SEP-6 E-40 sec 5.3.4 HW Environment DJF: Technical budgets status and margin SUPPLIER/ CUSTOMER SUPPLIER CUSTOMER T

28. Software Reuse -Reuse of SW from other projects Technical Specification, Interface Control Document, Design Justification File Customer needs Parent: SW Development Process Perspective: Software Engineering Activity: Software Development Process Diagram: 11 External References: ECSS-E-40 In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) Software/System Requirement Engineering Process SEP-1 E-40 sec 5.2 Software Requirement Engineering Process SEP-2 / T E-40 sec 5.4 Software Design Engineering Process SEP-3 / T E-40 sec 5.5 Requirements Baseline, Interface Requirements Document, design Justification File Design Definition File Requirements Baseline, Interface Requirements Document, design Justification File Interface Management SEP-5 E-40 sec. 5.3.3 Hardware Environment Interface Management Procedures Design Justification File ECSS-M-30 Project Requirements Project Phasing and Planning SEP-4 ECSS-M-30A ECSS-E-40 sec. 5.3.2 SUPPLIER Requirements Baseline ECSS-M-40 Requirements Technical Budget and Margin Management SEP-6 E-40 sec 5.3.4 HW Environment DJF: Technical budgets status and margin SUPPLIER/ CUSTOMER SUPPLIER CUSTOMER T

29. Developing Software for Intended Reuse - Tailored SW Development Process Activity: SW Requirements Engineering Process DIAG.#15-R-1 Functional and Capability Specification SUPPLIER External References: ECSS-E-40 sec.5.4.2, 5.4.3, 5.4.4 Parent: Software Development Process Perspective: Software Engineering In Triggers (IT)Out Triggers (OT)External Inputs (EI) EI1: SW PA Requirements (diag. 26) External Outputs (EO) Software Top Level Architectural Design R-2 E-40 sec.5.4.3 Software Requirements Analysis R-1 E-40 sec. 5.4.2 SUPPLIER SRR Docs: IRD RB EI1 Preliminary Design Review E-40 sec. 5.4.3.6 Delivered PDR DP Reviewed PDR DP PDR Data Package PDR Report Reliability and System Analysis Q-80 sec. 3.3.2e System Level Functional Analysis SW RAMS Analysis Higher Level Safety Plan T Intended SW Re-use Process SW-R-110 Intended SW Re-use Process SW-R-110

30. Design for re-use SW Specifications Design for-reuse-justification methods and tools, Documentation Organization Evaluation of re-use potential Parent:SW Requirement Engineering Process Perspective: SW Reuse Activity:Intended SW reuse process Diagram: SW-R-110 External References In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) CUSTOMER Definition of Design Constraints & Requirements (SW Requirements Specification) SW-R-112 [ECSS-E-40,Sec 6.4.1.2] Definition of documentation Standard, Testing and CM Tools (as part of SDP) SW-R-113 [ECSS-E-40,Sec 6.4.1.2] Design for re-use System Specification SUPPLIER Evaluation of re-use Potential SW-R-114 [ECSS-E-40,Sec 6.4.1.2] PDR Data Package Design guidelines SUPPLIER Definition of special Requirements for re-use (System Specification) SW-R-111 [ECSS-E-40,Sec 6.4.1.1] Reuse needs & constraints (from the Customer) Developing Software for Intended Reuse - Tailored Software Development ProcessT

31. Reused SW coverage of Requirements Software Reuse from other Projects - Tailored SW Development Process Activity: SW Requirements Engineering Process DIAG.#15-R2 Functional and Capability Specification SUPPLIER External References: ECSS-E-40 sec.5.4.2, 5.4.3, 5.4.4 Parent: Software Development Process Perspective: Software Engineering In Triggers (IT)Out Triggers (OT)External Inputs (EI) EI1: SW PA Requirements (diag. 26) External Outputs (EO) Software Top Level Architectural Design R-2 E-40 sec.5.4.3 Software Requirements Analysis R-1 E-40 sec. 5.4.2 SUPPLIER SRR Docs: IRD RB EI1 Preliminary Design Review E-40 sec. 5.4.3.6 Delivered PDR DP Reviewed PDR DP PDR Data Package PDR Report Reliability and System Analysis Q-80 sec. 3.3.2e System Level Functional Analysis SW RAMS Analysis Higher Level Safety Plan T Selection of Reusable SW SW-R-210 Selection of Reusable SW SW-R-210 Justification for Reused SW

32. Re-used software Modifications and Reuse Determined status Software Reuse from Other Projects - Tailored SW Design Engineering Process Code, Unit tests Documentation SUPPLIER External References: ECSS-E-40 sec.5.5 Parent: Software Development ProcessPerspective: Software EngineeringActivity: SW Design Engineering Process Diagram: 18 In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) SUPPLIER Integration SD-3 E-40 sec. 5.5.4 SUPPLIER Software Architectural Design Document Detailed design DP Numerical Error Report Coding and Testing SD-2 E-40 sec. 5.5.3 Design of New Software Items SD-1 / T E-40 sec. 5.5.2 SW Validation against the TS SD-4 E-40 sec. 5.5.5 Delivered CDR Data Package Reviewed CDR Data Package CDR Report CDR Data Package Design Complexity & Modularity Measurement Q-80 sec. 3.3.2d, 4.18 Safety Analysis Q-80 sec. 3.3.2 Critical Modules Handling Q-80 sec. 3.3.2 Design Engineering for Reused SW Items SW-R-220 SUPPLIER Critical Design Review E-40 sec. 5.5.4.5 Inspection Q-80 sec. 3.2.5k Reusable software Artifacts

33. ECSS-Q-80 3.2.7 Perspective: Software Reuse Activity: Selection of to be Reused SW Diagram: SW-R-210 External References In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) CUSTOMER Identification of components to be re-used SW-R-212 [ECSS-E-40,Sec 6.4.2.1] COTS/MOTS Process Tailoring SW-R-214 [ECSS-E-40,Sec 6.4.2.2] Justification for re-use wrt RB SUPPLIER COTS/MOTS Process Implementation SW-R-215 [ECSS-E-40,Sec 6.4.2.2] Acquired COTS/MOTS Products Software Acquisition Process Definition Re-use request PDR Data Package Specification of intended re-use Identification of reused SW use CUSTOMER SUPPLIER Quality evaluation of identified reusable components SW-R-213 [ECSS-E-40,Sec 6.4.2.1] Request for Re-use of software SW-R-211 [ECSS-E-40,Sec 6.4.2.1] Software Reuse from other Projects - Tailored Software Development ProcessT Parent: Reusing Software from other Projects

34. Activity: Design Engineering for Reused SW Items Diagarm: SW-R-220 External References: Parent: Software Reuse from other Projects Perspective: Software Reuse In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) Software Reuse from other Projects - Design Engineering for Reused SW ItemsT Detailed Design(s) & Interfaces Design Updating Diagram: 19 SD-1/2 T SW-R-221 Re-used software Modifications and Reuse Determined status SUPPLIER Justification for Reused SW Reusable software Artifacts Contribution to Detailed Design Data Package Updating of Operation Manual Information DIAG #19 SD-3 T SW-R-222 Updating of Unit Tests and Integration Documentation DIAG #19 SD-4 / 5 T SW-R-223 Verify Modified Items Design E-40 5.5.2.6 Consolidate Inputs to DD Data Package for Modified SW SW-R-224 SUPPLIER