RE.3.3.11 c) Implementation Documents: Module



		RE.3.3.11 c) Implementation Documents: Module (ImplD)

Implementierungsdokumente - SW Modul

Contents
Introduction
Document Index
Document Structure

Contents		Introduction Document Index Document Structure

Introduction

The Implementation Documents for Module contain references to the code of the Module, as well as command procedures for the code generation, installation, etc., and also listings and protocols of compile, link and load runs.

Such a product exists for each Module (of each Segment in the System).

It is possible to combine several Implementation Documents into one document, for example for a SW Unit.

Document Index

1. General Information
2. Code
2.1. Source Code
2.2. Reference to the Object Code
2.3. Reference to the Executable Code
3. Procedures
3.1. Compile Procedure
3.2. Link Procedure
3.3. Load Procedure
3.4. Installation Procedure
4. Listings/Protocols
4.1. Compile Protocol
4.2. Link Protocol
4.3. Load Protocol
4.4. Cross-Reference Listings
4.5. Other Generation Listings

Document Structure

1. General Information

See schema 1. General Information.

2. Code

There are references to the location of files (data media) and how they have been named (more information in product CM Plan, section Conventions with Regard to the Identification).

2. 1. Source Code

The source code itself is derived from the product SW Design (Module), SW Design (Database). The text consists of the program header and the statements section.

The program header contains the following information:

SW Module or SW Component name
file name
version and variant
person in charge/date
project identification
brief description, possibly descriptors for reuse
programming language
calling statement, possibly with parameter list
input data
output data
global data
local data
constants
calling SW Component(s)
called SW Component(s)/SW Module(s)/Database(s)
characteristic quantities
other related products, e. g. files that have been included into the code together with data definitions, standard routines
notes

The statements section consists of statements with comments.

2. 2. Reference to the Object Code

This contains references to files and data media.

2. 3. Reference to the Executable Code

This contains references to files and data media.

3. Procedures

These should contain-apart from the statements section-a suitable procedure header with the following information:

procedure name
file name
version and variant
identification of the tool (compiler, linker, etc.), exact name, statement of vendor and version
person in charge/date
project identification
calling statement, possibly with parameter list
brief description in the form of a comment

3. 1. Compile Procedure

3. 2. Link Procedure

3. 3. Load Procedure

3. 4. Installation Procedure

4. Listings/Protocols

This contains references to files and data media, if required.

4. 1. Compile Protocol

4. 2. Link Protocol

4. 3. Load Protocol

4. 4. Cross-Reference Listings

4. 5. Other Generation Listings

GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster