Development Landscapes 

A development landscape consists of multiple development tracks that come after each other in a sequence. Independent software components are developed in each track. Software components that are developed in subsequent tracks can base themselves on the software components of predecessor tracks, and define dependencies.

 

Example

The version of software component A is used as a basis for the development of software component B. After the assembly step, version 1 of software component A is delivered to the development track of software component B.

Software component A continues to be developed at the same time as software component B. To make the development work in track B consistent, the component gets new versions of the software component from track A at regular intervals (weekly, for example).

If a serious error is discovered in component A while software component B is being developed, then you must create a patch in a parallel repair track and import this patch into the development track of component B. This is because, from now on, any further developments made to A could be incompatible with B, or A could be too unstable a basis for B.

The patches are created on request and imported into the development track of B.

Any repairs made in the weekly versions of a software component version can be imported back into the original track with the resolve function of the Design Time Repository.