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

Refined ECSS Software Process

Model Elements

SD-TN-AI-0570, Issue 5

APPENDIX D

Software Reuse

Developing SW forIntended Reuse

Reusing SW fromother Projects

HCI Software

Critical Software

Real TimeSoftware

SimulationSoftware

Tailored ECSS Software Process Model Elements

App. D 2 0f 34

HCI Software Validation against the Technical SpecificationHCI Testing

HCI Software

HCI Software Process Model Tailoring

Project Phasing & PlanningDefinition of HCI Engineering Standards

HCI Software System Requirements Engineering

HCI System Requirements Analysis

HCI Software Requirements Engineering Process

App. D 3 0f 34

Elements of SW Maintenance

Plan

Requirements Baseline at SRRDocumentation Standards

Design StandardsVerification and Validation

Standards

Software Project Development

Plan

Parent: HCI Software Development Process Perspective: Software Engineering Activity: Project Phasing and PlanningDiagram: 4 / HCI

External References: ECSS-E-40, ECSS-Q-80

In Triggers (IT) Out Triggers (OT) External Inputs (EI)EI1: SW PA Plan ReviewEI2: SW PA Procedures & Standards ReviewEI3: SW PA Life Cycle Review

External Outputs (EO)

Requirements Baseline at SRRSoftware 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-3E-40: 5.3.2.2

SRRSUPPLIERECSS-M-30PROJECT RQMTSECSS-E_40 Sec 4.5System vs Software Requirements

Requirements BaselineSW Project

Development Plan

SUPPLIER

Definition of Software

Engineering Standards

SLC-2E-40: 5.3.2.11


Development PlanSUPPLIER

Software Project Development Plan

Review

EI1

EI2

EI3

HCI Software - Tailored Project Phasing & Planning Process T

Definition of HCI


T

HCI Standards and selected HCI Design &

Development Methodologies

(CUSTOMER) / SUPPLIER

HCI Software - Tailored SW System Requirements Engineering Process T

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 Process Perspective: 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-2E-40 sec. 5.2.3

CUSTOMER CUSTOMER

CUSTOMER

System level Integration of

SoftwareSE –4

E-40 sec. 5.2.5

CUSTOMER

SRR Data PackageRB, IRD

DJF

RB: V&V Processrequirements


Reviewed SRR Data PackageRB, IRD

DJF

Usability & LearnabilityRequirements Analysis

T

Usability & LearnabilityTest Planning

T

HCI Software - Tailored System RequirementsAnalysis Process T

RB: Functions & Performance

RqmtsIRD: Interface

Rqmts

Parent: HCI SW System Requirement Engineering ProcessPerspective: 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


Definition of system functionalities and

interfacesSYS-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-3E-40 sec. 5.2.2.1

System Criticality / Critical Functions

Definition

SYS-4E-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


CUSTOMER

CUSTOMER

CUSTOMER

CUSTOMER

Human Factors Engineering (HFE)

Requirements Definition T RB: HFE Requirements

CUSTOMER

HCI Software - Tailored Software Requirements Engineering Process T

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)


Software Requirements Analysis

R-1E-40 sec. 5.4.2

SUPPLIER

SRR Docs:IRDRB

EI1

Preliminary DesignReview

E-40 sec. 5.4.3.6

DeliveredPDR DP

ReviewedPDR DP

PDR Data PackagePDR Report

Reliability and System Analysis

Q-80 sec. 3.3.2e

System LevelFunctionalAnalysis

SW RAMS Analysis

Higher Level Safety Plan

Software Top Level Architectural Design

R-2E-40 sec.5.4.3

HCI SW Prototyping

E-40 6.5.1.3

HCI Software - Tailored Software TS-Validation Process 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: HCI Software Design Engineering ProcessPerspective: Verification & Validation Engineering Activity: SW Validation against TSDiagram: 56 / HCI

External References: ECSS-E-40 sec. 5.5.xx , ECSS-Q-80 sec. 3.3.4q, 3.3.4g, 3.3.4r


Software TS-Validation Testing Specification

DefinitionVI-1

E-40 sec. 5.5.5.1 (cr)

Update and prepare the SW product release

VI-5E-40 sec. 5.5.5.6 (cr)

Evaluate the design, code, test and

operation manualVI-4

E-40 sec. 5.5.5.6 (cr)

Validation testingagainst the TS

VI-2E-40 sec. 5.5.5.2 (cr)

Update the operation manual

VI-3E-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 BoardQ-80 sec. 3.3.4t

Verify Test

E-40 sec. 5.6.6.6

Analysis and InspectionVI-6

E-40 sec. 5.5.5.3 (cr)

CDR Data Package

Analysis and Inspection reports

SW Specification

SUPPLIERSUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

SW Design/Code

CheckCoverage

Q-80-3.3.gt

HCI Testing

T

HCI Software - Specific HCI Testing Process T

Parent: HCI SW Validation against TSPerspective: Verification & Validation Engineering Activity: HCI TestingDiagram: 56 / 1-HCI1

External References:


HCI Special Testsinput to:



SW Product,Validation Environment

(HW/SW)


Perform HCIRobustness & Stress

Tests T

Perform InteractiveSessions HCI Testing

T

Perform Usability Tests

T


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

Critical Software

Critical Software Process Model Elements

Project Phasing & PlanningDefinition 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

Critical Software - Tailored Project Phasing & Planning Process T


Plan



StandardsSoftware Project

Development Plan

Parent: Critical Software Development Process Perspective: Software Engineering Activity: Project Phasing and PlanningDiagram: 4 / CRT








planning)SLC-1

E-40: 5.3.2.1



SLC-3E-40: 5.3.2.2

SRR

SUPPLIER

ECSS-M-30PROJECT RQMTSECSS-E_40 Sec 4.5System vs Software Requirements


Development Plan

SUPPLIER



SLC-2E-40: 5.3.2.11 Requirements Baseline

SW Project Development Plan

SUPPLIER


Review

EI1

EI2

EI3

Definition of specific

Standards for Critical Software

T

Dependability & Safety specific Standards &

Process Requirements


Critical Software - Tailored Software System Requirements Engineering Process T

Overall System

Requirements


RB (System partition with definition of items; System Configuration list)

IRD (SW/HW interface requirements)DJF (Traceability to system

partitioning)

Parent: Critical Software Development Process Perspective: Software Engineering Activity: Critical SW System Requirements Eng.ng Diagram: 12 / CRT





E-40 sec. 5.2.4

SRR

System Requirements

Analyis SE –1

E-40 sec. 5.2.2

System Partitioning

SE-2E-40 sec. 5.2.3

CUSTOMER CUSTOMER

CUSTOMER


SoftwareSE –4

E-40 sec. 5.2.5

CUSTOMER


DJF

RB: V&V Processrequirements, including Test Requirements for Critical SW


Reviewed SRR Data Package

RB, IRDDJF

Software CriticalityAnalysis

T

Test Planning

for Critical Software

T

Software CriticalityAnalysis

Consolidation forProducts Categorisation

T

Activity: Critical SW System Requirements Analysis Diagram: 13 / CRT

Critical Software - Tailored System Requirements Analysis Process T


RqmtsIRD: Interface

Rqmts

Parent: Critical SW System Requirement Engineering ProcessPerspective: Software Engineering




interfacesSYS-1

E-40 sec. 5.2.2.1




E-40 sec. 5.2.2.1, 5.2.6.2

V&V Rqmts and Design Constraints

SYS-3E-40 sec. 5.2.2.1


Definition

SYS-4E-40 sec. 5.2.2.2


identification

RB: Design Constraints

V&V requirements- SW Eng. Standards



CUSTOMER

CUSTOMER

CUSTOMER

CUSTOMER

Dependability & Safety Specific Requirements Definition for Critical

Software T

RB: Dependability/Safety Requirements for Critical

SW Requirements

CUSTOMER

Critical Software - Tailored Software Requirements Engineering Process T

Activity: SW Requirements Engineering Process DIAG.#15 / CRT


Specification

SUPPLIER


Parent: Critical Software Development Process Perspective: Software Engineering




R-1E-40 sec. 5.4.2

SUPPLIERSRR Docs:IRDRB

EI1


E-40 sec. 5.4.3.6

DeliveredPDR DP

ReviewedPDR DP

PDR Data PackagePDR Report


Q-80 sec. 3.3.2e


SW RAMS Analysis



R-2E-40 sec.5.4.3

SW Prototypingfor Critical

Components T

Real TimeSoftware

Real Time Software Process Model Elements

Software Validation against the Technical Specification

Project Phasing & PlanningDefinition 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 ProcessSEEA Process

App. D 15 0f 34


Plan



Standards

Software Project Development

Plan

Parent: Real-Time Software Development Process Perspective: Software Engineering Activity: Project Phasing and PlanningDiagram: 4 / RT








planning)SLC-1

E-40: 5.3.2.1



SLC-3E-40: 5.3.2.2

SRRSUPPLIERECSS-M-30PROJECT RQMTSECSS-E_40 Sec 4.5System vs Software Requirements


Development Plan

SUPPLIER



SLC-2E-40: 5.3.2.11


Development PlanSUPPLIER


Review

EI1

EI2

EI3

Real-Time Software - Tailored Project Phasing & Planning Process T

Definition of HRT / RT

Engineering & Test Standards

T

Specific Standards and selected Design &

Development Methodologies for RT

and HRT SW


Assess HW-SW AIVNeeds & Requirements T

Dependencies

Real-Time Software - Tailored Software System Requirements Engineering Process T

Overall System

Requirements


RB (System partition with definition of

items; System Configuration list)

IRD (SW/HW interface

requirements)DJF (Traceability

to system partitioning)

Parent: RT Software Development Process Perspective: Software Engineering Activity: RT SW System Requirements Engineering Diagram: 12 / RT





E-40 sec. 5.2.4

SRR

System Requirements

Analyis SE –1

E-40 sec. 5.2.2

System Partitioning

SE-2E-40 sec. 5.2.3

CUSTOMER CUSTOMER

CUSTOMER


SoftwareSE –4

E-40 sec. 5.2.5

CUSTOMER


DJF

RB: V&V Processrequirements


Reviewed SRR Data PackageRB, IRD

DJF

RT PerformanceRequirements

specific Analyses T

HRT - RT SW Test-Bed and Test

Scenario requirements

T

Real-Time Software - Tailored System RequirementsAnalysis Process T


RqmtsIRD: Interface

Rqmts

Parent: RT SW System Requirement Engineering ProcessPerspective: Software Engineering Activity: RT System Requirements Analysis

Diagram: 13 / RT




interfacesSYS-1

E-40 sec. 5.2.2.1




E-40 sec. 5.2.2.1, 5.2.6.2

V &V Rqmts and Design Constraints

SYS-3E-40 sec. 5.2.2.1


Definition

SYS-4E-40 sec. 5.2.2.2


identification

RB: Design ConstraintsV&V requirements

- SW Eng. Standards



CUSTOMER

CUSTOMER

CUSTOMER

CUSTOMER

Control System RT Requirements &

Operational ConstraintsDefinition

T

RB: RT Control System and Performance Requirements

CUSTOMER

Assessments of theneeds for Test Support

SW and Simulation Models

T

Real Time Software - Tailored Software Requirements Engineering Process T

Activity: SW Requirements Engineering Process DIAG.#15 / CRT


Specification

SUPPLIER


Parent: RT Software Development Process Perspective: Software Engineering




R-1E-40 sec. 5.4.2

SUPPLIERSRR Docs:IRDRB

EI1

PDR

DeliveredPDR DP

ReviewedPDR DP

PDR Report


Q-80 sec. 3.3.2e


SW RAMS Analysis

Higher LevelSafety Plan


R-2E-40 sec.5.4.3

RT SW Prototypingfor Critical Controls &

Algorithms T

Numerical Analysisof required Algorithms

TDynamic Modelling

of Design (e.g. Petri-Net Model)

T

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 Designfor Propagation &

Errors Effects

15.1.1 TRecommend Designs for

Minimisation of SW Errors Effects

15.1.2 T

ProvideRecommendations for

RT SW Validation

15.1.3 T

DJF:

SEAA Reports

TS

DDF-DJF

Real Time Software - Tailored Software Requirements Engineering Process T

SW RAMSAnalysis

RT SW Design Analysis

Design Recommendation

Validation Recommendation

T

SW design and test

evaluation report

Validation Plan,Validation Reqs



SW Product,Validation

Environment (HW/SW)


Parent: RT Software Design Engineering ProcessPerspective: Verification & Validation Engineering Activity:RT SW Validation against TSDiagram: 56 / RT

External References: ECSS-E-40 sec. 5.5.xx , ECSS-Q-80 sec. 3.3.4q, 3.3.4g, 3.3.4r


Software TS-Validation Testing Specification

DefinitionVI-1

E-40 sec. 5.5.5.1 (cr)

Update and prepare the SW product release

VI-5E-40 sec. 5.5.5.6 (cr)

Evaluate the design, code, test and

operation manualVI-4

E-40 sec. 5.5.5.6 (cr)

Validation testingagainst the TS

VI-2E-40 sec. 5.5.5.2

(cr)

Update the operation manual

VI-3E-40 sec. 5.5.5.4

(cr)

SW on delivery media,SW release doc.,

Baseline deliverables

Operation manual (update)


Q-80 sec. 3.3.4f

Test Readiness Review BoardQ-80 sec. 3.3.4t

Verify Test

E-40 sec. 5.6.6.6

Analysis and InspectionVI-6

E-40 sec. 5.5.5.3 (cr)

CDR Data Package

Analysis and Inspection reports

SW Specification

SUPPLIERSUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

SW Design/Code

CheckCoverage

Q-80-3.3.gt

Real-Time Software - Tailored Software TS-Validation Process

RT Closed-LoopTesting on Target

T

Test-bed

Simulation Software Process Model Elements

SimulationSoftware

Simulation Software Design ProcessDesign of Software Items

Simulation Software Requirements Engineering Process

App. D 23 0f 34

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


Simulation SWRequirements

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 SimulationModels Design

Hierarchy for Autocode T

Tailoring for Simulation SW Specification Phase, using Tools supporting Simulation Models Design & Generation

SimulationAlgorithms

Numerical Analysis T

ECSS-Q-80 4.1.11/12

Parent: SIM SWDevelopment ProcessPerspective: Software Engineering Activity: SIM SWRequirements Eng.ng Process

Diagram 15 / SIM

OT1: Re-use Process OT1: Re-use Process

Simulation SWTop Level

Architectural Design

GSSW-3-1-1-2 RM-15

Simulation Software - Tailored Software Requirements Engineering Process T

EI1: Flight SW ICDs

Flight System and HW Documentation

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


Tailoring for Simulation SW Design Phase, using Tools supporting Simulation Models Code Generation

Parent: SIM SWDevelopment ProcessPerspective: Software Engineering Activity: SIM SW Design of SW Items Diagram: 19 / SIM

Code,Unit tests

Documentation

Coding and TestingGSSW-3-1-2-2

SD-2

Coding and TestingGSSW-3-1-2-2

SD-2

Integration

GSSW-3-1-2-3SD-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

AutocodeArtifacts

Design of Software ItemsGSSW-3-1-2-1

SD-1

Design of Software ItemsGSSW-3-1-2-1

SD-1PDR Outputs

OT1: Re-use Process

OT1: Re-use Process

Simulation Software - Tailored Design of Software Items Process T

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 forIntended Reuse

Reusing SW fromother Projects

Software Reuse Process Model Elements

App. D 26 0f 34

Software Reuse

Technical Specification, Interface Control

Document, Design Justification File



Customer needs

Parent: SW Development ProcessPerspective: Software EngineeringActivity: Software Development Process

Diagram: 11

External References: ECSS-E-40


Software/System Requirement Engineering

ProcessSEP-1

E-40 sec 5.2

Software Requirement Engineering Process

SEP-2 / TE-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



Interface ManagementSEP-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-4ECSS-M-30A

ECSS-E-40 sec. 5.3.2

SUPPLIER

Requirements Baseline

ECSS-M-40 Requirements

Technical Budget and Margin Management

SEP-6E-40 sec 5.3.4

HW Environment

DJF: Technical budgets status and margin

SUPPLIER/CUSTOMER

SUPPLIER

SUPPLIERCUSTOMER

CUSTOMER

T

for both Intended reuse and reuse from

other projects

for reuse from other projects

Software Reuse - Tailored Software Development Process





Customer needs


Diagram: 11




ProcessSEP-1

E-40 sec 5.2


SEP-2 / TE-40 sec 5.4


SEP-3 / T E-40 sec 5.5







E-40 sec. 5.3.3




File

ECSS-M-30 Project

Requirements


SEP-4ECSS-M-30A


SUPPLIER




SEP-6E-40 sec 5.3.4

HW Environment


SUPPLIER/CUSTOMER

SUPPLIER

SUPPLIERCUSTOMER

CUSTOMER

T

Software Reuse -Reuse of SW from other projects





Customer needs


Diagram: 11




ProcessSEP-1

E-40 sec 5.2


SEP-2 / TE-40 sec 5.4


SEP-3 / T E-40 sec 5.5







E-40 sec. 5.3.3




File

ECSS-M-30 Project

Requirements


SEP-4ECSS-M-30A


SUPPLIER




SEP-6E-40 sec 5.3.4

HW Environment


SUPPLIER/CUSTOMER

SUPPLIER

SUPPLIERCUSTOMER

CUSTOMER

T

Developing Software for Intended Reuse - Tailored SW Development Process

Activity: SW Requirements Engineering Process DIAG.#15-R-1


Specification SUPPLIER


Parent: Software Development Process Perspective: Software Engineering




R-2E-40 sec.5.4.3


R-1E-40 sec. 5.4.2

SUPPLIER

SRR Docs:IRDRB

EI1


E-40 sec. 5.4.3.6

DeliveredPDR DP

ReviewedPDR DP

PDR Data Package

PDR Report


Q-80 sec. 3.3.2eSystem Level Functional

AnalysisSW RAMS Analysis


T

IntendedSW Re-use

ProcessSW-R-110

IntendedSW Re-use

ProcessSW-R-110

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


CUSTOMER

Definition of Design Constraints & Requirements

(SW Requirements Specification)

SW-R-112[ECSS-E-40,Sec 6.4.1.2]

Definition of documentationStandard, 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]

PDRData Package

Design guidelines

SUPPLIER

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 Process T

Reused SW coverage of

Requirements

Software Reuse from other Projects - Tailored SW Development Process

Activity: SW Requirements Engineering Process DIAG.#15-R2


Specification SUPPLIER


Parent: Software Development Process Perspective: Software Engineering




R-2E-40 sec.5.4.3


R-1E-40 sec. 5.4.2

SUPPLIER

SRR Docs:IRDRB

EI1


E-40 sec. 5.4.3.6

DeliveredPDR DP

ReviewedPDR DP

PDR Data Package

PDR Report


Q-80 sec. 3.3.2eSystem Level Functional

AnalysisSW RAMS Analysis


T

Selection ofReusable SW

SW-R-210

Selection ofReusable SW

SW-R-210

Justification for Reused

SW

Re-used software Modifications andReuse 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 Process Perspective: Software Engineering Activity: SW Design Engineering Process Diagram: 18


SUPPLIER

Integration

SD-3E-40 sec. 5.5.4

SUPPLIER

SoftwareArchitectural

DesignDocument

Detailed design DP

Numerical Error Report

Coding and TestingSD-2

E-40 sec. 5.5.3

Design of New Software Items

SD-1 / TE-40 sec. 5.5.2

SW Validationagainst the TS

SD-4E-40 sec. 5.5.5

DeliveredCDR Data Package

Reviewed CDR Data Package

CDR ReportCDR Data

Package

Design Complexity & Modularity

MeasurementQ-80 sec. 3.3.2d, 4.18

Safety AnalysisQ-80 sec. 3.3.2

Critical Modules Handling

Q-80 sec. 3.3.2

Design Engineering for Reused SW

Items

SW-R-220

SUPPLIER

SUPPLIER

Critical DesignReview

E-40 sec. 5.5.4.5

InspectionQ-80 sec. 3.2.5k

Reusable softwareArtifacts

ECSS-Q-803.2.7

Perspective: Software Reuse Activity: Selection of to be Reused SWDiagram: SW-R-210

External References


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 forre-use wrt RBSUPPLIER

COTS/MOTSProcess Implementation

SW-R-215[ECSS-E-40,Sec 6.4.2.2]

Acquired COTS/MOTS

ProductsSoftware Acquisition

Process Definition

Re-use request

PDRData Package

Specification of intended re-use

Identification of reused SW use

CUSTOMERSUPPLIER

SUPPLIER

Quality evaluation of identified reusable

components SW-R-213

[ECSS-E-40,Sec 6.4.2.1]

Request forRe-use of software

SW-R-211[ECSS-E-40,Sec 6.4.2.1]

Software Reuse from other Projects - Tailored Software Development Process T

Parent: Reusing Software from other Projects

Activity: Design Engineering for Reused SW ItemsDiagarm: SW-R-220

External References:

Parent: Software Reuse from other ProjectsPerspective: Software Reuse


Software Reuse from other Projects - Design Engineering for Reused SW Items T

Detailed Design(s) & Interfaces Design

UpdatingDiagram: 19 SD-1/2 T

SW-R-221

Re-used software Modifications and

Reuse Determined status

SUPPLIERJustification for Reused

SW

Reusable softwareArtifacts

Contribution toDetailed Design Data Package

Updating of Operation Manual Information

DIAG #19 SD-3 TSW-R-222

Updating of Unit Tests and Integration Documentation

DIAG #19 SD-4 / 5 TSW-R-223

Verify ModifiedItems DesignE-40 5.5.2.6

ConsolidateInputs to

DD Data Package for Modified SW

SW-R-224

SUPPLIER

SUPPLIER

SUPPLIER

Documents

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