Scribd
Upload
17 views15 pages

Software Engineering Standards Overview

This document discusses software engineering processes for space systems. It outlines the key activities in software requirements engineering, design, validation, operations and maintenance. These activities are carried out by either the customer or supplier and involve various reviews. The document also covers software product assurance which includes configuration management to maintain consistency between a product's characteristics and requirements.

Uploaded by

Luiza Carmen Pîrvulescu
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
17 views15 pages

Software Engineering Standards Overview

This document discusses software engineering processes for space systems. It outlines the key activities in software requirements engineering, design, validation, operations and maintenance. These activities are carried out by either the customer or supplier and involve various reviews. The document also covers software product assurance which includes configuration management to maintain consistency between a product's characteristics and requirements.

Uploaded by

Luiza Carmen Pîrvulescu
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

.l. dr. ing.

LucianLucian-Florentin Brbulescu

PSS-05
05 (Procedures, Specifications and Standards)
Issue 1 1985
Issue 2 1991

ECSS (European Cooperation for Space


Standardization )
ECSS-E-ST-40 - software engineering
ECSS-Q-ST-80 - software product assurance
ECSS-M-ST-10, ECSS-M-ST
ST-40 - management
3

Bazat pe conceptul client/


client/furnizor

System Engineering
carried out by the customer
 system requirements engineering
 system integration
 system validation.

Related review: SRR (System requirements review)




Software Requirements Engineering


Carried out by the supplier
 software-requirements
requirements analysis
 software top-level
level architectural design

Related review: PDR (Preliminary design review)


May also generate SWR (Software requirement review)

Software Design Engineering


carried out by the supplier





designing of software items


coding and unit testing
Integration
validation with respect to the technical specification

Related review: CDR (Critical Design Review)

Software Validation and Acceptance


carried out by the supplier
 Validation with respect to the requirements baseline
 Related review: QR (Qualification Review)
 carried out in the suppliers environment
 Factory Acceptance Test

 Software delivery and installation

carried out by the customer


 Software acceptance
 Related review: AR (Acceptance Review)
 carried out in the operational environment
 Site Acceptance Test

10

Software Operations Engineering

preparation of software operations procedures


preparation of plans for operational testing (new releases)
software operations proper
user support

Software Maintenance

software problem analysis


software problem correction (software modification)
re-acceptance
acceptance (i.e. validation of corrections)
software migration
software retirement
11

12

Software product assurance programme


implementation




Organization and responsibility


Software product assurance programme management
Risk management and critical item control
Supplier selection and control
Procurement
Tools and supporting environment
Assessment and improvement process

Software process assurance


Software product quality assurance

13

Software process assurance


Software development life cycle
Requirements applicable to all software engineering processes
Requirements applicable to individual software engineering
processes or activities

Software product quality assurance

Product quality objectives and metrication


Product quality requirements
Software intended for reuse
Standard ground hardware and services for operational system
Firmware

14

Configuration management
establish and maintain a consistent record of a products
functional and physical characteristics compared to its design
and operational requirements.
know at any time:
Technical description
Evolution of technical description
Traceability of the evolution of the products technical description
Consistency of the internal interfaces;
Documentation is and remains the exact image of the products;
Current configuration baseline to record discrepancies detected
during production, delivery or operation;
 The operational possibilities and limitations







15

You might also like