Reference Process Model Diagrams ECSS-PMod Project ECSS Software Process M odel Root Up Down Last Parent Actions

Reference Process Model DiagramsReference Process Model Diagrams

ECSS-PMod ProjectECSS-PMod Project

ECSS Software Process M odel

Root Up Down Last ParentActions

ECSS Software Life Cycle Processes

Supporting Life Cycle Processes

LC-2M-40, M-50, E-40, Q-80

Organizational Life Cycle Processes

LC-3M-series, Q-80

Parent: NonePerspective: ALL Activity: Software Life Cycle Processes DIAG #50

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

In Triggers (IT) Out Triggers (OT) External Inputs (EI) External Outputs (EO)

Primary Life Cycle Processes

LC-1E-40

Needs

ECSS Software Artifacts:DJF, DDF, TS, RB, IRD,

ICD, CJF, MJF

Primary Life Cycle Processes

Supply Process

PLC-2

Software Development Process

PLC-4E-40 sec. 5.2, 5.3, 5.4, 5.5

Parent: Software Life Cycle Processes Perspective: Software Engineering Activity: Primary Life Cycle Processes DIAG #51

External References: ECSS-E-40 sec. 5.2, 5.3, 5.4, 5.5, 5.7, 5.8


Acquisition Process

PLC-1

Software Maintenance and Migration

PLC-5E-40 sec 5.8

Maintenance Plan

Change Justification

File

Software Operations Engineering Process

PLC-3E-40 sec 5.7 Operational

Plan

Operational Requirements

Maintenabilty Requirements

SUPPLIER

CUSTOMER

SUPPLIER/CUSTOMER

OPERATOR

MAINTAINER

ITT/RFQ

Needs Negotiated Contract

c

Proposal

DJF, DDF, TS, RB, IRD, ICD

Acquisition Process

Request for Proposal submission to supplier

AP-2

Parent: Primary Life Cycle Processes Perspective: Software Engineering Activity: Acquisition ProcessDIAG #54

External References: ECSS-M-series

In Triggers (IT) Out Triggers (OT) External Inputs (EI)EI-01: Supply Process: Proposal preparation and submission

External Outputs (EO)EO-01: Supply Process: Review of the proposalEO-02: Supply Process: Negotiation of the contract

Request for Proposal (or ITT) preparation

AP-1Contract negotiation

AP-4

Needs

Initiation

ECSS-M-series

Submitted proposals evaluation and selection

AP-3

Selected proposal

Negotiated Contract

ITT/RFQITT/RFQ

SUPPLIER/CUSTOMER

CUSTOMER CUSTOMER CUSTOMER

EO-01

EI-01

EO-02

Supply Process

Proposal Preparation and submission

SUP-2

Parent: Primary Life Cycle Processes Perspective: Software Engineering Activity: Supply ProcessDIAG #55

External References: ECSS-M-series

In Triggers (IT) Out Triggers (OT) External Inputs (EI)EI-01: Acquisition Process: Proposal preparation and submissionEI-02: Acquisition Process: Submitted proposal selection

External Outputs (EO)EO-01: Acquisition Process: Submitted proposal evaluation and selection

Review of the proposal request

SUP-1

Negotiation of the contract

SUP-3ITT/RFQ

ECSS-M-seriesSUPPLIER SUPPLIER

Negotiated Contract

SUPPLIER/CUSTOMER

EI-01EI-02

EO-01

Software Development Process

Technical Specification, Interface Control

Document, Design Justification File

Technical Specification, Interface Control

Document, Design Justification File

Customer needs

Parent: Primary Life Cycle ProcessesPerspective: Software EngineeringActivity: Software Development Process

DIAG #11

External References: ECSS-E-40


Software/System Requirement Engineering

ProcessSEP-1

E-40 sec 5.2

Software Requirement Engineering Process

SEP-2E-40 sec 5.4

Software Design Engineering Process

SEP-3E-40 sec 5.5

Requirements Baseline, Interface Requirements

Document, design Justification File

Design Definition File

Requirements Baseline, Interface Requirements

Document, design Justification 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

SUPPLIER

CUSTOMER

CUSTOMER

Project Phasing and Planning

Elements of SW Maintenance

Plan

Requirements Baseline at SRRDocumentation Standards

Design StandardsVerification and Validation

Standards

Software Project Development

Plan

Parent: Software Development Process Perspective: Software Engineering Activity: Project Phasing and PlanningDIAG #4

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

Requirements BaselineSW Project

Development PlanSUPPLIER

Software Project Development Plan

Review

EI1

EI2

EI3

Interface Management

Interface Management procedures,

Part of configuration management planECSS-M-40

Requirements

Parent: Software Development Process

Perspective: Software Management Activity: Interface ManagementDIAG #9

External References: ECSS-E-40 sec. 5.3.3.1


Definition of interface management procedures

IM-1E-40 sec. 5.3.3.1

CUSTOMER

SRR Data Package

Requirements Baseline

Technical Budget and Margin Management

Technical budgets and margin philosophy

Parent: Software Development Process

Perspective: Software ManagementActivity: Technical Budget & Margin Management

DIAG #48

External References: ECSS-E-40 sec. 5.3.4.1, 5.3.4.2


Definition of margin philosophy

IM-2E-40 sec. 5.3.4.1

Budget statusIM-3

E-40 5.3.4.2

CUSTOMERSUPPLIER

HW environment

Requirements Baseline:SRR Data Package

DJF: Technical budgets status and

margins

PDR, CDR, QR, AR

Software System Requirements Engineering

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: Software Development Process Perspective: Software Engineering Activity: Software System Requirements Engineering DIAG #12

External References: ECSS-E-40 sec. 5.2.2, 5.2.3, 5.2.4, 5.2.5


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

System Requirements Analysis

RB: Functions & Performance

RqmtsIRD: Interface

Rqmts

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

DIAG #13

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

System level integration of Software

CUSTOMER

CUSTOMER

CUSTOMER

IRD: System level integration support

requirements, product preparation requirements

RB: Sys level data interfaces, development constraints

RB: SW Observability requirements

IRD: System level interface requirements

Parent: Software System Requirements Engineering

Perspective: Software Engineering Activity: System level integration of Software DIAG #14

External References: ECSS-E-40 sec. 5.2.5.1, 5.2.5.2, 5.2.5.3, 5.2.5.4, 5.2.5.5, 5.2.5.6, 5.2.5.7


SW additional requirements definition

SLI-1E-40 sec. 5.2.5.1, 5.2.5.2

Definition of customer products provision to

supplierSLI-3

E-40 sec. 5.2.5.5, 5.2.5.6, 5.2.5.7

Interface Data Medium Definition and

Development constraintsSLI-2

E-40 sec. 5.2.5.3, 5.2.5.4System level Requirements

IF SW product integrated in

system

IF SW product integrated in

system


SW Requirements Engineering Process

Activity: SW Requirements Engineering Process DIAG.#15

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)


Software Top Level Architectural Design

R-2E-40 sec.5.4.3

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.2eSystem Level Functional

AnalysisSW RAMS Analysis

Higher Level Safety Plan

SW Requirements Analysis

Preliminary Functional and

Capability Specification

Interface Control Document (external

interfaces)SUPPLIER

External References: ECSS-E-40 sec.5.4.2.1, 5.4.2.2, 5.4.2.3

Parent: SW Requirements Engineering ProcessPerspective: Software Engineering

Verify Software RequirementsDocumentsE-40 sec. 5.4.2.3

Activity: SW Requirements AnalysisDIAG #16

In Triggers (IT) Out Triggers (OT) External Inputs (EI)EI1: SW PA Requirements

External Outputs (EO)EO1. Test case spec & procs

SRR Docs:IRDRB

DeliveredBaseline


Specification

EO1

External Interfaces identification

RA-2E-40 sec. 5.4.2.1

Preliminary Requirements Establishment

RA-1E-40 sec. 5.4.2.1, 5.4.2.2

SUPPLIER

EI1

SW Top-Level Architectural Design


SpecificationEO1

IRD

Preliminary PDR Data Package

RB

RB

Preliminary ICD

SW Top level

Architecture

Preliminary SW

Integration test plan

Preliminary Operation manual

SUPPLIER

Definition of Preliminary Test

Requirements and Plan for SW Integration

AD-4E-40 sec. 5.4.3.4

External References: ECSS-E-40 sec.5.4.3.1, 5.4.3.2, 5.4.3.3, 5.4.3.4, 5.4.3.5, 5.4.3.6

Parent: Software Requirement Engineering Process

Perspective: Software Engineering

ArchitecturalDesign

DefinitionAD-1

E-40 sec. 5.4.3.1

Verify Software Design

E-40 sec. 5.4.3.5

Activity: SW Top-Level Architectural Design DIAG #17

In Triggers (IT) Out Triggers (OT) External Inputs (EI) External Outputs (EO)1. Integration SW/SW

SoftwareRequirements

Document

Preliminary(Top Level )

Interface DesignAD-2

E-40 sec. 5.4.3.2

Preliminary Operation Manual Definition

AD-3E-40 sec. 5.4.3.3

SUPPLIER

SUPPLIER

Numerical Error Report

SUPPLIER

PDR Data Package

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 DIAG #18


Coding and Testing

SD-2E-40 sec. 5.5.3

SUPPLIER

Design of Software Items

SD-1E-40 sec. 5.5.2

Integration

SD-3E-40 sec. 5.5.4

SUPPLIERSoftwareArchitectural

DesignDocument

Detailed design DP

Numerical Error Report

SW Validationagainst the TS

SD-4E-40 sec. 5.5.5

Critical DesignReview

E-40 sec. 5.5.4.5

DeliveredCDR Data

PackageReviewedCDR Data Package

CDR ReportCDR Data

Package

InspectionQ-80 sec. 3.2.5k

Design Complexity & Modularity

MeasurementQ-80 sec. 3.3.2d, 4.18

Safety AnalysisQ-80 sec. 3.3.2

Critical Module Handling

Q-80 sec. 3.3.2

Design of SW Items

Detailed design DP

DeliveredDetailed

Design Data Package

Detailed Design

document

SW Integration Test Plan

SW Unit Test Plan

ICD

Operation Manual Update

Update of Test Requirements and Plan

for SW IntegrationSD-5

E-40 sec. 5.5.2.5

External References: ECSS-E-40 sec.5.5.2.1, 5.5.2.2, 5.5.2.3, 5.5.2.4, 5.5.2.5, 5.5.2.6 , ECSS-Q-80 sec. 3.3.2

Parent: Software Design Engineering ProcessPerspective: Software Engineering

Verify Software Design

E-40 sec. 5.5.2.6

Activity: Design of SW ItemsDIAG #19

In Triggers (IT) Out Triggers (OT) External Inputs (EI)1. Coding and Testing.Unit Test Execution


SoftwareArchitectural

DesignDocument

Detailed Interface Design (external)

SD-2E-40 sec. 5.5.2.2


SD-3E-40 sec. 5.5.2.3

SW Unit Test Planning

SD-4E-40 sec. 5.5.2.4

EI1Detailed Design

DefinitionSD-1

E-40 sec. 5.5.2.1

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

Coding and Testing

EO1

Code,Unit tests

Documentation

SW Code

Unit Test Plan

SUPPLIER

SUPPLIER

modify

Unit Testing feedback

SW Integration Test Plan

SW Unit Test Report


Update of Test Requirements and Plan

for SW Integration SC-5

E-40 sec. 5.5.3.4

External References: ECSS-E-40 sec. 5.3.3.1, 5.3.3.2, 5.3.3.3, 5.3.3.4, 5.3.3.5, ECSS-Q-80 sec. 3.3.3, 3.3.4d, 3.3.4r, 3.3.4g


Verify Software Code

E-40 sec. 5.5.3.5s

Activity: Coding and TestingDIAG #20

In Triggers (IT) Out Triggers (OT) External Inputs (EI) External Outputs (EO)1. Design of SW Item.SW Component Design Document

Detailed Design

DeliveredCode & Unit

tests

Unit Test Procedures and Data Definition

SC-2E-40 sec. 5.5.3.1


SC-4E-40 sec. 5.5.3.3

SW Unit Testing

SC-3E-40 sec. 5.5.3.2

EO1 SW Unit Coding

SC-1E-40 sec. 5.5.3.2 SUPPLIER

SUPPLIER

Review & Check Coverage

Q-80 sec. 3.3.4g,q

SUPPLIER

SW Function Integration to Unit

SC-6E-40 sec. 5.5.4

SUPPLIER

Integration

EI2

SW CodeUnit test

documentation

EI1

SW Integration Test Report

SW Validation Testing specification


Validation test case and procedure

definitionIN-3

E-40: 5.6.7.1

External References: ECSS-E-40 sec. 5.5.4.1, .5.5.4.2, 5.5.4.3, 5.5.4.4, 5.5.4.5, ECSS-Q-80 sec.3.3.4, 3.3.4d


Verify Software Integration

E-40 sec. 5.5.4.4

Activity: IntegrationDIAG #21

In Triggers (IT)1. Qualification.Validation Plan Def.

Out Triggers (OT) External Inputs (EI)1. SW Req. Analysis.SW Requirements Document2. SW Top Level Srch. Design.Architectural Design


Unit/Unit Integration (former SW/SW)

IN-1E-40: 5.5.4.2


IN-2E-40 sec. 5.5.4.3

IT1

SUPPLIER

SUPPLIER

SUPPLIER

Check Coverage

Q-80 sec. 3.3.4g

SW Validation against the TS

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/S)

SW Validation Testing Spec

Parent:Software Design Engineering ProcessPerspective: Verification & Validation Engineering Activity: SW Validation against TSDIAG #56

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


Software Validation testing Specification

DefinitionVI-1

E-40 sec. 5.5.5.1 (cr)

Update and prepare the deliverables SW

productVI-5

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

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

SW Design/Code

CheckCoverage

Q-80-3.3.gt

Software Operations Engineering

EO-01

Problem Report

Modification Request

SW ready for operations

ECSS-M-10

Problem ReportModification

Request

EO-01

RB[Operations and

Maintenance Requirements]

Operational Plan

OPERATOR

ECSS-M-40

Activity: Software Operations Engineering DIAG #22

Perspective: Software Engineering Parent: Primary Life Cycle Processes

External References: ECSS-E-40 sec.5.7.3, 5.7.4, 5.7.5, 5.7.6.1, 5.7.6.2, 5.7.6.3, 5.2.6.2, 5.2.6.1ECSS-M-40

In Triggers (IT) Out Triggers (OT) External Inputs (EI)EI-01: Software from SW Maintenance Process EI02: Software from Validation ProcessEI-03: User Request

External Outputs (EO)EO-01: Problem Report /Modification Request to Software Maintenance ProcessEO-02: Workaroud to User

Operational Testing

OP-2E-40 sec. 5.7.4

Operational Plan and Standards

DefinitionOP-1

E-40 sec. 5.7.3.1, 5.7.3.25.7.3.3

OPERATOR

ORR

System Operation

OP-3E-40 sec. 5.7.5

User AssistanceOP-4

E-40 sec. 5.7.6.1

OPERATOR

OPERATOR

EI-01

EI-02

Operations Manual

EI-03

Archive of User’s

Request

Analysis of User’s Request

OP-5E-40 sec. 5.7.6.2,

5.7.6.3Problem Report

Modification Request

OPERATOR

Work-around Solution

EO-01

EO-02

Software Operations

OP-0E-40 sec. 5.2.6.2

CUSTOMER

SW Operator Identification

OP-00E-40 sec. 5.2.6.1

CUSTOMER

SW Maintenance and Migration

Sw/Environment

External References: ECSS-E-40 sec.5.8.2, 5.8.3, 5.8.4, 5.8.5, 5.8.6, 5.8.7, ECSS-M-30, ECSS-M-40

Parent: Primary Life Cycle ProcessesPerspective: Software EngineeringActivity: SW Maintenance and Migration

DIAG #23

In Triggers (IT) Out Triggers (OT) External Inputs (EI)EI-01; Problem Report,Modification Request from Maintenance Process

External Outputs (EO)EO-01: Modified SW to Operations Process

Software MaintenanceImplementation

MM-1E-40 sec. 5.8.2RB, ECSS-M-40

MAINTAINER

Modified SW environment

Software Migration

MM-2E-40 sec. 5.8.6

Software Retirement

MM-3E-40 sec. 5.8.7

Software Retirement Decision

SW

Modified SW

Start of Maintenance

SW

MAINTAINER

MAINTAINER

MJF

CJF-Baseline for

changes

Software Maintenance Implementation

Change Justification File

-Problem AnalysisReport

MAINTAINER

RB[Operations

and Maintenance

Requirements]

ECSS-M-40EI-01

Parent: Software Maintenance and Migration Perspective: Software Engineering

Activity: Software MaintenanceImplementation DIAG #24

External References: ECSS-E-40 sec. 5.8.2, 5.8.3.1, 5.8.3.2, 5.8.3.3, 5.8.3.4, 5.8.4.1, 5.8.4.2, ECSS-M-30, ECSS-M-40

In Triggers (IT) Out Triggers (OT) External Inputs (EI)EI-01; Problem Report, Modification Request from Software Operations Engineering Process

External Outputs (EO)EO-01: Modified SW to Operations Process

Maintenance Planning, Problem

Recording Procedures Definition

MA-1E-40 sec. 5.8.2.2,

5.8.2.3

Maintenance Plan-Plans and Procedures

-Problem Reportingand handling

Problem or Modification

AnalysisMA-2

E-40 sec. 5.8.3.1


File-Modification identification

CustomerApproval

E-40 sec. 5.8.3.5

Analysis of affected product

(Sw &documents)

MA-3

ModificationImplementationAnd regression

TestingMA-4

E-40 sec. 5.8.4


File-Baseline for

changes

Maintenance Review

E-40 sec. 5.8.5Start of Maintenance

EO-01

MAINTAINERMAINTAINER

MAINTAINER

Modified SW

Software Migration

Review Results availability to user’s

Archives of old environment

Migration Plan

Migration Justification

File

Parent: Software Maintenance and Migration Perspective: Software EngineeringActivity: Software Migration

DIAG #25

External References: ECSS-E-40 sec. 5.8.6.2, 5.8.6.3, 5.8.6.4, 5.8.6.5, 5.8.6.7, ECSS-M-40


Definition of migration plan

MI-1E-40 sec. 5.8.6.1,

5.8.6.2

Preparation of notification

documentation for the users

MI-3E-40 sec. 5.8.6.3

Implementation of Migration

MI-2E-40 sec. 5.8.6.5

Post OperationReview

E-40 sec. 5.8.6.6

E-405.8.6.1

Archive of old environment

MI-4E-40 sec. 5.8.6.7

Notification to user

MI-5E-40 sec. 5.8.6.5

Support of new & old environment

MI-6E-40 sec. 5.8.6.4

MAINTAINER

MAINTAINERMAINTAINER

MAINTAINER

MAINTAINER

MAINTAINER

Modified SW environment

Supporting Life Cycle Processes

Parent: Software Life Cycle ProcessesPerspective: ALL

Activity: Supporting Life Cycle Processes DIAG #52

External References:


SW Documentation ProcessSLC-1M-50

Verification and Validation Processes

SLC-2E-40 sec. 5.6.2, 5.6.3

SW Product AssuranceSLC-4

Q-80

Problem Resolution ProcessSLC-3

E-40 sec. 5.6.6.7, 5.6.7.6Q-80 sec. 2.3.5, 2.3.6

Joint Review ProcessSLC-6

E-40 sec. 5.6.8

Audit ProcessSLC-7

E-40 sec. 5.6.7.7

Software Configuration Management

Plan

Software Configuration Management Process

SLC-5M-40A

ECSS-M-40 Requirements

SUPPLIERCUSTOMER

Project Plans

Technical Review Reports

Audit Plan and Report

Available Documentation

SW Development plan

M-50 reqs

Traceability matrix, Verification/Validation

reports

Verification/Validation plan

RB, TS, Interface

Requirements

SUPPLIERCUSTOMER

SUPPLIER

SW PA Reports

SW docs & standards

SW Documentation Process

Parent: Supporting Life Cycle ProcessesPerspective: ALL Activity: SW Documentation ProcessDIAG #57

External References: ECSS-M-50


Definition of documentation

management Process for the project

DOC-1M-50 sec. 6

Documentation storage/assessing

DOC-2

SUPPLIER/CUSTOMER

Available Documentation

Accessible/stored Documentation

Implementation plan for Documentation Management

SW Development plan

M-50 reqs

SUPPLIER/CUSTOMER

Software C.M. Process

External References: ECSS-Q-80 sec. 2.3.6a, 2.3.5, ECSS-M-40 sec. 5.5

Parent: Supporting Life Cycle Processes Perspective: Software Configuration ManagementActivity: Software C.M. Process

DIAG #10


SW Configuration Management Procedures

definitionSCM-1

M-40 sec. 5.5

SW Configuration Item identification

SCM-2M-40 sec. 5.1

SW Configuration Control

SCM-3M-40 sec. 5.2

SW Configuration Status accounting

SCM-4M-40 sec.5.3

Product Assurance of CM Procedures

Product Assurance of CI Identification

Product Assurance of SW Configuration

Control

Product Assurance of SW Configuration

accounting

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

SW Configuration File

Identified SW Item and relevant documentation

SW Configuration Management Plan

SW Item evolution, change proposal, deviation/waiver

M-40 reqs

Developed SW

Software Configuration Control


Parent: Software C.M. ProcessPerspective: Software Configuration Management Activity: Software Configuration Control DIAG #58


Configuration control of the SW

SCC-1

Insertion of the SW in the Master Library

SCC-2

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

Development library: SW

Item

Archive SWSCC-3

SW on mediaSCC-4

Configuration Control of the Documentation

SCC-5

Insertion of the documents in the Master

LibrarySCC-6

SUPPLIERSUPPLIER

Documentation library: SW documents

SW under Configuration

Control

SW in the Master library

SW in the archive library

E.g. tape

Documents under

Configuration Control

Documents in the Master

library

Joint Review Process

Parent: Supporting Life Cycle ProcessesesPerspective: Software Management Activity: Joint Review ProcessDIAG #5



Software Support to Joint Technical

ReviewsREV-1

E-40 sec. 5.6.8.1

Milestone Review Reports

Project Plan (ECSS-M-30)

CUSTOMERSUPPLIER

SoftwareTechnical Reviews

REV-2E-40 sec. 5.6.8.2

Technical ReviewsReport

Software Development Plan

CUSTOMERSUPPLIER

Software Support to Joint Technical Reviews

Customer Approval of DDF; DJF; Operations Manual; design

of system interfaces

Customer Approval of Accepted

state

Parent: Joint Review ProcessPerspective: Software ManagementActivity: SW Support to Joint Technical Reviews

DIAG #6



SRR: Review of the Requirements Baseline

SRR-1E-40 sec. 5.3.2.4 SRR Milestone

Review Reports

RB

CUSTOMERSUPPLIER

PDR: Review of TS and Software Top Level

Architecture

PDR-1E-40 sec. 5.3.2.6;

5.4.3.6

PDR Milestone

Review Report

RB;TS;ICD;DDF;DJF

Customer Approval of RB

Customer Approval of TS and Top Level

Archtecture

CDR: Review of DDF; Operations

Manual; DJF

CDR-1E-40 sec. 5.3.2.7;

5.5.4.5

CDR Milestone Review Reports

CUSTOMERSUPPLIER

AR: Acceptance of software wrt operational

environment

AR-1E-40 sec. 5.3.2.10;

5.6.2.2AR Milestone

Review Report

RB;TS;ICD;DDF;DJF

RB;TS;ICD;DDF;DJF

QR: Review of Summary of tests

reports and operation manual

QR-1E-40 sec. 5.3.2.9;

5.6.2.1

QR Milestone Review Report

RB;TS;ICD;DDF;DJF

Customer Approval of Qualified state

CUSTOMERSUPPLIER

CUSTOMERSUPPLIER

CUSTOMERSUPPLIER

Review Procedure

CUSTOMERSUPPLIER

Parent: Software Support to Joint Technical ReviewsPerspective: Software Engineering Activity: Review Procedure (*)DIAG #7

External References: ECSS-M-40, M-30


Document ReviewRP-1

ECSS-M-40:4.1

Pre-BoardRP-4

RIDs Evaluation and Disposition

RP-2

BoardRP-5

ECSS-M-30: 4.1

RIDs Discussion(Review)

RP-3

CUSTOMER

RIDs

(*) This Process is applicable to each Joint Technical Reviews

SUPPLIER

Proposal RIDs

Disposition

CUSTOMERSUPPLIER

CUSTOMERSUPPLIER

Rids Status List

List of Actions and Closeout Dispositions

Open and Major RIDs

Major Problem

Customer Approval/ Proceed to Next Phase,

Technical Review Report

SW Development

plan

SW Technical Reviews

CUSTOMERSUPPLIER

Parent: Joint Review ProcessPerspective: Software Engineering Activity: SW Technical Reviews (*)DIAG #47

External References: ECSS-E-40


SoftwareDocumentation Review

TR-1ECSS-M-40:4.1

Software ReviewPre-Board

TR-4

RIDs Evaluation and Disposition

TR-2

Software ReviewBoard

TR-5ECSS-M-30: 4.1

RIDs Discussion(Review)

TR-3

CUSTOMER

RIDs

(*) This Process is applicable to each Software Technical Reviews

SUPPLIER

Proposal RIDs

Disposition

CUSTOMERSUPPLIER

CUSTOMERSUPPLIER

Rids Status List

List of Actions and Closeout Dispositions

Open and Major RIDs

Major Problem Customer Approval/ &

Authorization to Proceed with the Next Phase

SW Review Data Package

Problem Resolution Process

Parent: Supporting Life Cycle ProcessesPerspective: ALL Activity: Problem Resolution ProcessDIAG #59



Problem categorization

PRP-1

Problem Resolution

PRP-4

Problem Analysis

PRP-2 SW Review Board

PRP-3

Major

Minor

Cost/Schedule estimate

SPAR

BoardDecision

Identified problem

SUPPLIER

SUPPLIER SUPPLIER

SUPPLIER/CUSTOMER

Verified SW Documentation

Problem Resolution

Parent: Problem Resolution ProcessPerspective: ALL Activity: Problem ResolutionDIAG #60



Documentation Update

PR-4

SW Modification

PR-2

Regression Testing

PR-3SPAR

Board Decision

SUPPLIERSUPPLIER SUPPLIER

Modified SW Verified SW

Modified SWDocumentation

Verification and Validation Processes

Traceability matrix, Verification reports

Parent: Supporting Life Cycle ProcessesPerspective: Verification and Validation EngineeringActivity: Verification and Validation Processes

DIAG #35

External References: ECSS-E-40 sec. 5.4.4.1, 5.6.4, 5.6.5, 5.6.6.,5.6.7, Q-80 sec. 3.2.5p, 3.2.5a, 3.2.5d, 3.2.1


Verification Process Implementation

VP-1E-40 sec. 5.4.4.1, 5.6.4

Verification Process

VP-2E-40 sec. 5.4.4.1, 5.6.6

SUPPLIER

SUPPLIER

Verification plan

Non-Conformance, Problem Reports

Requirement Baseline, Technical Specification, Interface Requirements

Technical Specification, Design Definition File, Design Justification File

Software Validation Test Specification

Validation plan at PDR; TSValidation Process Implementation

VLP-1E-40 sec. 5.6.5,Q-80 sec. 3.3.4

Validation Process

VLP-2E-40 sec. 5.6.7,Q-80 sec. 3.3.4

Validation Test Reports

Non Conformance,

Problem ReportsSoftware on Delivery

Media, Software Release Documentation

Operation Manual

Requirement Baseline, Technical Specification, Interface Requirements

Technical Specification, Design Definition File, Design Justification File

SUPPLIER

Verification Process Implementation

Requirement Baseline, Technical

Specification, Interface

Requirements

Verification plan at PDR,Technical Specification

Verification plan: methods

& tools

Verification plan:criticality and effort

Verification plan: project organization

Parent: Verification and Validation ProcessesPerspective: Verification & Validation Engineering Activity: Verification Process Implementation

DIAG #36

External References: ECSS-E-40 sec.5.6.4, ECSS-Q-80 sec 3.2.5p, 3.2.5a


Determine the verification effort for

the projectVPP-1

E-40 sec. 5.6.4.1

Establish the verification Process

VPP-2E-40 sec. 5.6.4.2

Select the organization responsible for conducting the

verificationVPP-3

E-40 sec. 5.6.4.3

Determine the activities/SW products that require verification

VPP-4E-40 sec. 5.6.4.4

Develop and document a verification plan

VPP-5E-40 sec. 5.6.4.5

Verification plan

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIERSUPPLIER

Verification Process

Test Spec. Evaluation

Problem and non-conformance

Reports

SW integration Report

Traceability matrix,Top-level architectural

Design Verification report

Traceability matrix, Design Verification report

Preliminary detailed Design Data Package

Project documentation

Test specification evaluation

SW Integration Verification report

Traceability matrix,Code Verification report

Traceability matrix, Requirements Verification

report

Verification plan

Verification plan

Verification plan

Parent: Verification and Validation Processes Perspective: Verification and Validation Engineering Activity: Verification Process

DIAG #37

External References: ECSS-E-40 sec. 5.6.6, ECSS-Q-80 sec. 3.2.5d, 3.2.1


VerifyCode

VPI-3E-40 sec. 5.6.6.3

Verify SWIntegration

VPI-4E-40 sec. 5.6.64

Verify SW Documentation

VPI-5E-40 sec. 5.6.6.5

Verify SW Design

VPI-2E-40 sec. 5.6.6.2

Verify SW Requirements

VPI-1E-40 sec. 5.6.6.1

Verification plan

Verification plan

Preliminary PDR Data Package

Delivered code

Problems and non-conformances Handling

VPI-6E-40 sec. 5.6.6.7Verification plan:

criticality and effort

Evaluate Test SpecVPI-7

E-40 sec. 5.6.6.6

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

Preliminary functional & capability spec

Verify SW Requirements

Requirements Verification report

Traceability matrix, Requirements

Verification report

Parent: Verification Process ImplementationPerspective: Verification and Validation EngineeringActivity: Verify SW Requirements

DIAG #38



Verify Consistency, Feasibility and

Traceability to system Requirements

VR-1E-40 sec. 5.6.6.1a

Verify SW Requirements in terms of safety, security and

criticalityVR-2

E-40 sec. 5.6.6.1b

Preliminary functional & capability spec, Verification plan

Traceability matrix, Requirements

Verification reports

SUPPLIER

SUPPLIER

v

Verify SW Design

SUPPLIER

Design Verification report, non

conformance report

Design Verification report, non conformance report

Verification plan, Design Data Package

Traceability Matrix, Design Verification report, non

conformance report

Traceability Matrix

Parent: Verification Process ImplementationPerspective: Verification and Validation EngineeringActivity: Verify SW Design

DAG #39

External References: ECSS-E-40 sec. 5.6.6.2, ECSS-Q-80 sec. 3.2.5n, 3.2.5d, 3.2.5g


Verify the SW Design in terms of safety,

security and criticalityVD-4

E-40 5.6.6.2d

Verify the Design derivability from the

RequirementsVD-3

E-40 5.6.6.2c

Verify the RAMS and budget Requirements

VD-2E-40 sec. 5.6.6.2b

Verify the Design to Requirements

traceabilityVD-1

E-40 sec. 5.6.6.2a

Design Verification report, non conformance report

SUPPLIER

SUPPLIER

SUPPLIER

Verify Code

Traceability matrix,Code Verification report,

Problem & non conformance report

Code Verificationreport

Code Verification report

Traceability Matrix

Delivered code,

Verification plan

Parent: Verification Process ImplementationPerspective: Verification and Validation EngineeringActivity: Verify Code

DIAG #40

External References: ECSS-E-40 sec. 5.6.6.3, ECSS-Q-80 3.2.5.n, 3.2.5d, 3.2.5g


Verify if the code implement criticality

VC-4E-40 sec. 5.6.6.3b

Verify if the code can be derived from design

and requirementsVC-3

E-40 sec. 5.6.6.3b

Verify if RAMS requirements and budgets have been

correctly implementedVC-2

E-40 sec. 5.6.6.3b

Verify the code traceability to design

and requirementsVC-1

E-40 sec. 5.6.6.3a

Code Verification report

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

Verify SW Integration

Integration Verification report

Parent: Verification Process ImplementationPerspective: Verification and Validation EngineeringActivity: Verify SW Integration

DIAG #41



Verify if the SW units have been completely

and correctly integrated into the SW item

VI-1E-40 sec. 5.6.6.4

SW Integration Report,

Verification plan

SUPPLIER

Validation Process Implementation

Validation plan: methods

& tools

Parent: Verification and Validation Processes Perspective: Verification & Validation Engineering Activity: Validation Process Implementation DIAG #43

External References: ECSS-E-40 sec. 5.6.5, ECSS-Q-80 sec.3.3.4ab


Validation plan:

organization

Validation plan:effort & independence

Independent Validation plan:

project organization

Determine the validation effort for the

projectPLAN-1

E-40 sec. 5.6.5.1

Establish the validation Process

PLAN-2E-40 sec. 5.6.5.2

Select the organization responsible for conducting the

validationPLAN-3

E-40 sec. 5.6.5.3

Develop and document a validation plan

PLAN-4E-40 sec. 5.6.5.4

Validation plan

Validation Plan, TS; at PDR

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

Validation Process

Validation Plan,Validation Reqs

SW design and test

evaluation report

Validation testing reports,Non conformance reports,

Problem reports,Validated Software

SW product,Validation

environment (HW/SW)

SW Validation Testing Spec

Parent: Verification and Validation Processes Perspective: Verification & Validation Engineering Activity: Validation Process DIAG #44

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


Software Validation testing Specification

DefinitionVI-1

[E-40 sec. 5.6.7.1]

Update and prepare the deliverables SW

productVI-5

[E-40 sec. 5.6.7.5]

Evaluate the design, code, test and

operation manualVI-4

[E-40 sec. 5.6.74]

Validation Testingagainst the RB

VI-2[E-40 sec. 5.6.7.2]

Update the operation manual

VI-3[E-40 sec. 5.6.7.3]

SW on delivery media,SW release

documentation,Baseline deliverables

SW product

Operation manual (update)

Test Readiness Review

Q-80 sec. 3.3.4f

Test Readiness Review BoardQ-80 sec. 3.3.4t

SUPPLIERSUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER

Check Coverage

Q-80 sec. 3.3.gt

Support Customer Acceptance

VLP-3[E-40 sec. 5.6.7.7,

Q-80 sec. 3.3.4]

Customer Requirements

Training Material

Acceptance Testing Documentation

QRE-40 5-6-1

Support Customer Acceptance

Parent: Validation ProcessPerspective: Verification and Validation Activity: Support Customer AcceptanceDIAG #45

External References: ECSS-E-40 sec. 5.6.7.7, 5.6.7.8, ECSS-Q-80 sec. 3.3.5, ECSS-Q-20 sec. 4.6.4.4, 8.3, 2.6


Support Customer’s Acceptance Review

AS-2E-40 sec. 5.6.7.7

Acceptance Testing Documentation

Support Customer’s Acceptance Testing

AS-1E-40 sec. 5.6.7.7, Q-80 sec.

3.3.5

Provide training and support

AS-3E-40 sec. 5.6.7.8

Training MaterialTS

SUPPLIER

SUPPLIER SUPPLIER

CustomerRequirements

Support Customer’s Acceptance Testing

Parent: Support Customer Acceptance Perspective: Verification and Validation

Activity: Support Customer’s Acceptance Testing DIAG #46

External References: Q-80 sec. 3.3.5


Acceptance Test Execution

SWAC-4Q-80 sec. 3.3.5d/e/f/g

Preparation of Acceptance Material

SWAC-3Q-80 sec. 3.3.5c

Customer’s approval

Acceptance Test Plan Definition

SWAC-2Q-80 sec. 3.3.5b

Planning of SW Installation

SWAC-1Q-80 sec. 3.3.5a

Customer’s approval

SUPPLIER

SUPPLIER SUPPLIER SUPPLIER/CUSTOMER

Installation Plan

Acceptance test Plan

Acceptance test Report

SW ADPSW code

SW configuration file

Customer Reqs

Audit

Audit Plan

SUPPLIER

Parent: Supporting Life Cycle ProcessesPerspective: Software Product AssuranceActivity: Audit

DIAG #31


Audit PlanningPA-20

Q-80 sec.2.3.3 , Q-20 sec 2.6.2.

Audit ConductionPA-21

Q-80 sec.2.3.3, Q-20 sec. 2.6.1

Audit Report

CUSTOMERSUPPLIER

External References: ECSS-Q-20: 2.6, ECSS-Q-30: 2.5, ECSS-Q-80:2.3.3

Software P.A. Process

Parent: Supporting Life Cycle Processes Perspective: Software P.A. Activity: Software P.A. ProcessDIAG #26


In Triggers (IT) Out Triggers (OT)OT1: trigger to Model # 7 (5.3.2)OT2: trigger to Model # 7(5.3.2)OT3: trigger to Model # 7 (5.3.2)

External Inputs (EI) External Outputs (EO)

Software P.A. Planning

PA-1

Software P.A. System Process

PA-2

Software P.A. Monitoring and

ReportingPA-3

Project Plans Review

PA-4

Software Life Cycle Review

PA-6

Software Procedures and Standards

ReviewPA-5

Project Plans

Input to Software

P.A. Report

Input to Software

P.A. Report

Input to Software P.A. Report

Software Life Cycle

Definition

Procedures and Standards

OT2

OT3

OT1

SRR Documentation Software P.A. Plan

SUPPLIER

SUPPLIER

SUPPLIER

SUPPLIER SUPPLIER

SUPPLIERCUSTOMER

ALERT ORIGINATOR

Software Criticality Analysis Software PA

RequirementsInput to Contract

System Level Functional

Analysis, List of Critical Functions

Software PA Report

Audit plan/report

AlertNon Conformance Report

Software Documentation

Failure/Problem,Non Conformance

Purchased Software Process

PA-7

SUPPLIER

System Requirements Software Component

List

Receiving Inspection Report

Buy Decision

Software P.A. Planning

Software P.A. Plan or Compliance

Matrix to the Upper Level Software P.A.

Plan (*)

SUPPLIER

External References: ECSS-Q-80 sec. 2.3.1, 2.3.5c, 2.5.2b, 3.2.2I, 3.2.4c, 3.3.4c, 3.3.4i

Parent: SW P.A. ProcessPerspective: Software Product Assurance

Customer Approval of Software Product Assurance Plan

Documents

Activity: Software P.A. PlanningDIAG #27


SRR Docs:IRDRB

Customer SW P.A. RequirementsSystem Reliability, Safety, Maintainability and Quality

Requirements

SW P.A. Plan

Baseline

Definition & Planning of Software P.A.

activitiesPA-8

Contract (3.2.1)

Higher Level P.A. Plan

(*) To be updated before each milestone (2.3.1c)

Software P.A System Process

Activity: Software P.A System Process DIAG #28

External References: ECSS-E-40 sec. 6.2.1.1, ECSS-Q-80 sec. 3.2.2.f, 3.2.2h, 3.2.2i

Parent: Software P.A. ProcessPerspective: Software Product Assurance

In Triggers (IT) Out Triggers (OT) External Inputs (EI) External Outputs (EO)EO1: SW PA requirements (input to Software Specification)EO-2: Design and Test Quality Reqs

Software Criticality Analysis

System Level Functional Analysis

List of Critical Functions (FTA, FMECA, HSIA)

Definition of Software Criticality Analysis

PA-9Q-80 sec. 3.2.2f

SRR

Verification of SW P.A. Requirements

for Critical SWPA-11

Q-80 sec. 2.2

Input to SW P.A. ReportSoftware

P.A. Plan

Identification of Measures for

Handling Critical Modules

PA-10Q-80 sec. 3.2.2h

Design and Test Quality Requirements

RBSUPPLIER SUPPLIER

SUPPLIERContract Process

PA-12Q-80 sec. 3.2.2i

CUSTOMER

P.A. Input to Contract

System Requirements

EO-1

EO-2

Software P.A. Monitoring and Reporting Activities

Start Validation and Acceptance testing

Activity: Software P.A. Monitoring and Reporting Activities DIAG #29

External References: ECSS-Q-80

Parent: Software P.A. ProcessPerspective: Software Product Assurance

Software P.A. Assurance&

Reporting ActivitiesPA-13

In Triggers (IT)IT1: trigger from Model #IT2: trigger from Model #

Out Triggers (OT) External Inputs (EI) External Outputs (EO)

Supplier Monitoring and Control

PA-16

Alert Process

PA-17

Procedures and StandardsProject Plans

Software Documentation Software

P.A. Report

SUPPLIER

Software Documentation

Input to Software P.A.

PlanInput to Software

P.A. Report

CUSTOMERAlert

Failure/Problem

Assurance of activities during validation and

acceptance test

PA-27Test Certification

Test Documentation

Inspection

PA-28Input to SPA Report

SW Code

Supplier Monitoring and Control

Activity: Supplier Monitoring and Control DIAG #30

Input SW P.A. Plan

SWPA

External References: ECSS-Q-80 sec. 2.5.1, 2.5.2

Parent: Software P.A. Monitoring and Reporting ActivitiesPerspective: Software Product Assurance

Software Product Assurance

Subcontractor Monitoring Activities

PA-19Q-80 sec. 2.5.2


SRR Docs:IRDRB

Customer Approval of SW

P.A. Requirements

Definition of Software P..A. Requirements for

SubcontractorPA-18

Q-80 sec. 2.5.1

SWPA

Input to Software

P.A. Report

Alert Process

Preliminary Alert

Information

SUPPLIERALERT ORIGINATOR

Parent: Software P. A. Monitoring and Reporting ActivitiesPerspective: Software Product AssuranceActivity: Alert Process

DIAG #32


Alert Detection and Submission

PA-22Q-80 sec. 2.3.4,

Q-20 3.7.2

Alert Investigation

PA-23Q-80 sec. 2.3.4

Q-20 3.7.2

CUSTOMERSUPPLIERALERT ORIGINATOR

External References: ECSS-Q-20: 3.7.2, ECSS-Q-80:2.3.4

Failures/ProblemAlert Distribution

PA-24Q-80 sec. 2.3.4

Q-20 3.7.2

Alert Immediate Measures Alert

CUSTOMER

Inspection

Parent: SW PA Monitoring and Reporting ActivitiesPerspective: Software Product AssuranceActivity: Inspection

DIAG #61


External References: ECSS-Q-80 sec. 3.3.3, 3.2.5, 4.1.8, 4.1.12

Check Code tools use & Standards Conformance

INS-1Q-80 sec. 3.3.3g

Numerical Analysis Report

INS-6Q-80 sec. 4.1.12

Size Monitoring

INS-2Q-80 sec. 4.1.8 Code Engineering

InspectionINS-3

Q-80 sec. 3.2.5i

Check use of languageINS-4

Q-80 sec. 3.3.3eComplexity Monitoring

INS-5Q-80 sec. 3.3.3f, 4.1.8

Input to SPA ReportSW Code

SWPA

SWPA

SWPA

SWPA

SWPA

SWPA

SW Standards

Purchased SW Process

Software Component

List

SUPPLIER

Parent: Software P. A. ProcessPerspective: Software Product AssuranceActivity: Purchased SW Process

DIAG #33


Market Survey

PA-25Q-80 sec. 4.4.1, 4.4.2

COTS Incoming Inspection

PA-26Q-80 sec. 4.4.3, 4.4.4

SUPPLIER

System Requirements

Customer Approval

Constraints depending on development and future

useSRR

Inspection Criteria

Receiving Inspection

Report

Buy Decision

External References: ECSS-Q-80:4.4.1, 4.4.2, 4.4.3, 4.4.4

Organizational Life Cycle Processes

Parent: Software Life Cycle Processes Perspective: ALL Activity: Organizational Life Cycle Processes DIAG #53

External References: ECSS-E-40 sec.


Infrastructure Process

OLC-3

Training Process

OLC-2Q-00, Q-80

Software Management Process

OLC-1M-series

SW Life Cycle Improvement Process

OLC-4

SUPPLIER/CUSTOMER

Historical data

SW Life Cycle in the organization

Proposal for Process improvement

(I.e. technology adv.)

Process assessment procedure and records

Records of Training/Experience

WBS

Constraints Reqs

(Contract)

Customer Reqs

Constraints Reqs

(Contract)

Customer Reqs

Records of Training

/Experience

Residual Risk Accepted

Schedule reports

SW Project Development

plan

Configured Environment

Software Management Process

WBS

Constraints Reqs

(Contract)

Customer Reqs

Records of Training

/Experience

SUPPLIERRisk

Close-out

Activity:Software Management Process DIAG #2

Parent: Organizational Life Cycle Processes

Perspective: Software Management



Project Break Down Structure

SM-1ECSS-M-10A

Risk Management

SM-7ECSS-M-00A sec.6.3.4

Project Organization

SM-2ECSS-M-20-A

Cost and Schedule Management

SM-6ECSS-M-60A

SUPPLIER

Residual Risk Accepted

SUPPLIERSUPPLIER

Criteria for Risk Identification

Project Data

Schedule reports

Risk Management

Criteria for identification

including project

constraintsList of Actions

SUPPLIER

Risk Policy

List of Potential Risk causes and Consequences

SUPPLIER

Parent: Software Management Process Perspective: Software Management


Risk Identification

RM-1M-00 sec. 6.3.3

Risk Assessment Evaluation and Classification

RM-2M-00 sec. 6.3.3

SUPPLIER

External Reference: ECSS-M-00: 6.3, ECSS-Q-80:2.4

Action Implementation for Risk Elimination or

ReductionRM-4

M-00 sec. 6.3.3

Verification of the Risk Reduction

EffectsRM-5

M-00 sec. 6.3.3

Risk Acceptance

RM-6M-00 sec. 6.3.3

Decision for Risks

RM-3M-00 sec. 6.3.3

Quantified Risk

Expected Risk

Reduction effects

Classified Risk

Critical Items

Residual Risks

Accepted

Risks Close Out

Validation of Risk

Reduction effects

SUPPLIERSUPPLIER

SUPPLIER

Activity: Risk Management DIAG #8

Training Process

Training Plan

Parent: Software Management Process

Perspective: Software Management Activity: Training ProcessDIAG #3



Training PlanningPO-2

Q-00: 3.3.2d

Training Activities

PO-3Q-80: 2.1.5a

SUPPLIER

SUPPLIER

Records of Training/Experience

Project Organization Selection

PO-1WBS

Constraints Reqs

(Contract)

Customer Reqs

SUPPLIER

Project Organization