Home Random Page


CATEGORIES:

BiologyChemistryConstructionCultureEcologyEconomyElectronicsFinanceGeographyHistoryInformaticsLawMathematicsMechanicsMedicineOtherPedagogyPhilosophyPhysicsPolicyPsychologySociologySportTourism






MANDATORY PRACTICES

DD01 DD phase activities shall be carried out according to the plans defined in the AD phase.

The detailed design and production of software shall be based on the following three principles:

DD02 • top-down decomposition;

DD03 • structured programming:

DD04 • concurrent production and documentation.

DD05 The integration process shall be controlled by the software configu­ration management procedures defined in the SCMP.

DD06 Before a module can be accepted, every statement in a module shall be executed successfully at least once.

DD07 Integration testing shall check that all the data exchanged across an interface agrees with the data structure specifications in the ADD.

DD08 Integration testing shall confirm that the control flows defined in the ADD have been implemented.

DD09 System testing shall verify compliance with system objectives, as stated in the SRD.

DD10 When the design of a major component is finished, a critical design review shall be convened to certify its readiness for implementation.

DD11 After production, the DD Review (DD/R) shall consider the results of the verification activities and decide whether to transfer the software.

DD12 All deliverable code shall be identified in a configuration item list.

DD13 The DDD shall be an output of the DD phase.

DD14 Part 2 of the DDD shall have the same structure and identification scheme as the code itself, with a 1:1 correspondence between sections of the documentation and the software components.

DD15 The DDD shall be complete, accounting for all the software require­ments in the SRD.

DD16 A table cross-referencing software requirements to the detailed design components shall be placed in the DDD.

DD17 A Software User Manual (SUM) shall be an output of the DD phase.

 

C-2 ESAPSS-05-05 Issue 1 (May 1992) MANDATORY PRACTICES

This page is intentionally left blank.

 

ESAPSS-05-05 Issue 1 (May 1992) D-1 REQUIREMENTS TRACEABILITY MATRIX

APPENDIX D REQUIREMENTS TRACEABILITY MATRIX

REQUIREMENTTS TRACEABILITY MATRIX DATE:
DDD TRACED TO SRD <YY-MM-DD>
  PAGE 10F <nn>
PROJECT: <TITIE OF PROJECT>  
SRD IDENTIFIER DDD IDENTIFIER SOFTWARE REQUIREMENT
     
       

 

 

D-2 ESAPSS-05-05 Issue 1 (May 1992) REQUIREMENTS TRACEABILITY MATRIX

This page is intentionally left blank.

 

ESA PSS-05-05 Issue 1 (May 1992) INDEX

APPENDIX E INDEX

 

E-2 ESA PSS-05-05 Issue 1 (May 1992) INDEX

This page is intentionally left blank.

 

ESA PSS-05-05 Issue 1 (May 1992) E-3

acceptance test

plan, 3

practice for, 21

acceptance test specification, 87

Ada, 10,37

assertion, 17

audit, 86

 

backtracking, 33,40

backward chaining, 33

baseline, 46



block structuring, 31

bottom-up integration, 21,43

 

Ñ, 36

C++,38

CASE tool, 45

change control, 46,57

COBUL, 35

 

complexity measure, 18

configuration management

 

see SCM

cyclomatic complexity, 49

 

data dictionary, 45

DD/R, 1

DD01 4,85

DD02 5

DD03 14

DD04 14

DD05 21

DD06 20

DD07 21

DD08 21

DD09 21

DD10 11

DD11 22

DD12 21,67

DD13 55

DD14 55,58

DD15 55,58

DD16 67

DD17 69

DDD, 3,55

debugger, 20

declarative, 32

defect, 22

 

diagnostic code, 20

driver, 43

 

dynamic analysers, 20

dynamic binding, 32

 

embedded system, 22

 

flowcharts, 26

formal review, 22

FORTRAN, 34

forward chaining, 33

 

help, 74

hypertext, 75

Horn Clause logic, 39

ICD.66

IEEE

Std 1016,58

Std 1028,23

Std 1063.69

inheritance. 32

integration test

see also test

purpose. 21

 

Jackson Structured Programming, 29

LISP, 38

 

media control, 86

messages, 32

method, 56

 

quality assurance of, 86

methods, 25

metric, 86

ML. 39

Modula-2,37

module

acceptability, 20

header, 19

integration, 43

 

PA

 

seeSQA

Pascal, 36

polymorphism, 32

precompiler, 46

problem reporting, 86

product assurance

 

seeSQA

 

Program Design Language, 28

progress report, 4,85

project management

 

seeSPM

Prolog, 39

prototyping, 11

pseudo code, 7,12,14,26,28

 

quality assurance

see SQA

 

recursion, 31

review

 

quality assurance of, 86

RID, 23

 

risk analysis, 86

risk management, 86

 

SCM, 45,85

 

in integration, 21

SCM06.63

SCM15,15

SCM16,15

SCM17,15

SCM18,15

SCM46,85

SCM49,85

SCMP

 

E-4

ESA PSS-05-05 Issue 1 (May 1992)

DD phase. 85

TR phase, 3, 22, 85

simulator,22

Smalltalk,38

software configuration management

 

seeSCM

software project management

 

seeSPM

software quality assurance

 

seeSQA

SPM.85

SPM13.85

SPMP

DD phase, 14,85

TR phase, 3. 22, 85

SQA, 85,86

SQA10.86

SQA11,86

SQAP

DD phase, 85,86

TR phase, 3,22

stepwise refinement, 26

strong typing, 31

Structured Programming, 26

SUM, 3.69

SW17,87

SW19,13,87

SW20,14.87

SW21,14,87

SWP

DD phase, 85

integration tests, 21

system tests, 22

TR phase, 3

unit tests, 20

SWP/IT, 20

system test

see also test

purpose, 21

 

test

see also acceptance test

black box, 19

quality assurance of, 86

white box, 19

test coverage, 52

tool, 53,56

 

quality assurance of. 86

tools, 45

 

top-down integration, 21, 43

TR phase, 85

traceability, 45

training, 86

 

unit test, 19

see also test

 


Date: 2016-01-03; view: 650


<== previous page | next page ==>
ACCEPTANCE TEST SPECIFICATION | CHARACTER GENERATION
doclecture.net - lectures - 2014-2024 year. Copyright infringement or personal data (0.009 sec.)