Estandar Esa

ESA PSS-05-0 Issue 2
February 1991




E S A
S O F T W A R E
E N G I N E E R I N G
S T A N D A R D S

ISSUE 2










Prepared by:
ESA Board for Software
Standardisation and Control
(BSSC)






Approved by:


The Inspector General, ESA






European Space Agency/ Agence spatiale europeenne
8-10,rue Mario-Nikis, 75738 PARIS CEDEX, France


















DOCUMENT STATUS SHEET

|DOCUMENT STATUS SHEET |
|1. DOCUMENT TITLE: ESA PSS-05-0 Software Engineering Standards ||2. ISSUE |3. REVISION |4. DATE |5. REASON FOR CHANGE |
|0 |0 |1984 |First issue of BSSC(84)1, Issue no 1 |
|1 |0 |1987 |First issue of ESA PSS-05-0, Issue 1|


Approved, 30th January 1991
Board for Software Standardisation and Control
C. Mazza, Chairman



Approved, 21st February 1991
Telematics Supervisory Board







Published by ESA Publications Division,
ESTEC, Noordwijk, The Netherlands.
Printed in the Netherlands.
ESA price code: E2
ISSN 0379 - 4059


Copyright 1991by European Space Agency
TABLA DE CONTENIDOS

INTRODUCTION 9

1 PURPOSE OF THE STANDARDS 9

2 STRUCTURE OF THE STANDARDS 9

3 CLASSES OF STANDARD PRACTICES 9
3.1 Mandatory practices 9
3.2 Recommended practices 9
3.3 Guideline practices 10

4 APPLYING THE STANDARDS 10
4.1 Factors in applying the Standards 104.2 Applying the Standards in a system development 10
4.3 Methods and tools 11

P a r t 1 P r o d u c t S t a n d a r d s 12

CHAPTER 1: THE SOFTWARE LIFE CYCLE 12

1.1 INTRODUCTION 12

1.2 PHASES, ACTIVITIES AND MILESTONES 12
1.2.1 UR phase: user requirements definition 14
1.2.2 SR phase: software requirements definition 141.2.3 AD phase: architectural design 14
1.2.4 DD phase: detailed design and production 15
1.2.5 TR phase: transfer 15
1.2.6 OM phase: operations and maintenance 15

1.3 LIFE CYCLE APPROACHES 16
1.3.1 The waterfall approach 16
1.3.2 The incremental delivery approach 16
1.3.3 The evolutionary development approach 17

1.4 PROTOTYPING17

1.5 HANDLING REQUIREMENTS CHANGE 18

CHAPTER 2: THE USER REQUIREMENTS DEFINITION PHASE 18

2.1 INTRODUCTION 18

2.2 INPUTS TO THE PHASE 19

2.3 ACTIVITIES 19
2.3.1 Capture of user requirements 19
2.3.2 Determination of operational environment 20
2.3.3 Specification of user requirements 20
2.3.4 Reviews 21

2.4OUTPUTS FROM THE PHASE 21
2.4.1 User Requirements Document 21
2.4.2 Acceptance test plans 22
2.4.3 Project management plan for the SR phase 22
2.4.4 Configuration management plan for the SR phase 22
2.4.5 Verification and validation plan for the SR phase 22
2.4.6 Quality assurance plan for the SR phase 22

CHAPTER 3: THE SOFTWARE REQUIREMENTSDEFINITION PHASE 23

3.1 INTRODUCTION 23

3.2 INPUTS TO THE PHASE 23

3.3 ACTIVITIES 23
3.3.1 Construction of the logical model 24
3.3.2 Specification of software requirements 24
3.3.3 Reviews 27

3.4 OUTPUTS FROM THE PHASE 27
3.4.1 Software Requirements Document 28
3.4.2 System test plans 28
3.4.3 Project...