SD 7.1-SW: Integration into SW Component



		SD 7.1-SW: Integration into SW Component

SE7.1-SW - Zur SW-Komponente integrieren

Contents
Product Flow
Handling
Explanation

Roles
Tools Requirements
External Norms

Contents		Product Flow Handling Explanation		Roles Tools Requirements External Norms

Product Flow

From		Product		to		Methods	Tool Req.	Ext. Norms
Activity	State	Chapter	Title	Activity	State	Methods	Tool Req.	Ext. Norms
SD6-SW	accepted	All	Implementation Document: SW Modules	-	-
		-	SW Modules
		All	Implementation Document: Database
		All	Database
SD4-SW	accepted	All	Integration Plan	-	-
-	-	All	Implementation Document: SW Component	SD7.2-SW	being proc.
-	-	-	SW Component	SD7.2-SW	being proc.		SSD16

+ "Chapter" are extra columns from the original printed version of GD 250

An SW substructure ⁽¹⁾ may include one or several SW Modules, Databases or SW Components. An SW substructure may also contain dummies (stubs or drivers). These dummies will be replaced by iterated runs through SD 7.1-SW "Integration into SW Component"-at the latest, however, when being integrated into the SW Unit-by the corresponding operational SW Modules. During each execution of this activity, a new SW substructure of a higher integration level is created from one or several given SW substructures. This can be achieved by

integration of substructures that have not been connected until now,
exchange of dummies with operational substructures,
replacement of substructures by improved versions,
integration of off-the-shelf products,
dissolving of prototypes,
exchange of simulators or emulators by operative hardware or software.

For integrational purposes it might become necessary to generate code or to write procedures in addition to the available SW Modules.

The SW Components must then be submitted to a self-assessment (SD7.2 - Self-Assessment of SW Component) one by one. When doing this, the SW Component may still include dummies.

Explanation

The order of the SW Modules, Databases, and SW Components in the product structure suggests a bottom-up integration strategy. However, this is only one of several possible methods. Other examples for integration strategies are:

top-down integration,
sandwich integration,
early integration of critical and important functions,
integration sequence based on organizational facts and responsibilities,
integration oriented on the functions or processes of the SW Unit,
early integration of the core system (of all central, repeatedly used functions),
integration according to the dependency of the integration objects.

The SW substructure is apparent only for a certain period of time during the SD7 - SW Integration. It is a temporary construction which allows SW Integration according to arbitrary strategies. The end of the SW Integration is the SW Unit, with its structuring into SW Components and SW Modules or Databases.

The individual steps of the SW Integration have been set up in the Integration Plan.

Roles

Role	Participation
SW Developer	responsible

Tools Requirements

Product	Functional Tools Requirements
SW Component	SSD16 - Linking

External Norms

Being defined

Note:

(1) An SW substructure is an interim product that only occurs with activity SD7.1 - Integration into SW Component and thus is not integrated into another activity.

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