Term

Description

access control list

A list that specifies which users or system components are allowed to access a resource.

activity

Used to represent a single logical change, where an activity tracks all the resources that were modified to effect that single logical change. When a resource is checked out, the user specifies which activity should be associated with a new version that will be created.

ancestor

If a check-in version in the DTR is connected to another version across several predecessors, the first one is an ancestor of the latter.

branch

All the versions created in the same workspace form a branch with increasing sequence numbers on the versions.

branch relation

A version relation between the first version on a branch and its predecessor version.

build process

The process of creating the compiled entities of a development component.

build variant

One of multiple different outputs of a build process.

compartment

Part of a development configuration storing a certain state of a software component. Compartments may contain source states and built states of a software component.

component definition file

Special file stored in the DTR describing the attributes and dependencies of development or software components.

descendant

If a check-in version in the DTR is connected to another version across several predecessors, the last version is a descendant of the first version. Descendant is the opposite of ancestor.

Design Time Repository (DTR)

Versioning source repository from SAP. The DTR is based on a file and folders paradigm and uses standard protocols (HTTP, DAV, and DeltaV) for access.

development configuration

Collects a set of states of software components required for developing, building and testing of a certain software component, providing the information needed to resolve dependencies between development components.

development object 

File that contributes to a software product and is developed actively, for example a JAVA source file, a Web Dynpro view, a table definition, database content, or a JSP page. Development entities are stored in a suitable source format in a versioning Design Time Repository (DTR). Development objects are part of development components.

equal relation

Two different versions coming from different workspaces, but with the same contents. When trying to check them into one workspace instead of a conflict you have equal relation.

fusion

This is a type of resource, which is used as an alternative to a folder. A fusion can contain files and folders in any hierarchy but it cannot contain other fusions. Everything that is contained in a single fusion is versioned together. You can check out an entire fusion, but not a single fusion element. If there is an integration conflict for a file located in a fusion, the whole fusion is marked as conflicting versions.

localization

Language-dependent variant of a development component.

merge relation

A version relation that indicates that the contents of the source of the version relation were merged into the target version of the relation.

modification

Change made to the development components by a particular customer. In the event of changes made by SAP, modified development components must be reviewed and, where necessary, adapted.

predecessor

A version immediately preceding another version created by the check-in to the DTR.

produced entity

Unit of production that has been generated from a development object (or other produced objects) and may generate further produced objects, for example a Java class file, a library or a deployable Java EE archive. Produced objects are not usually stored in a versioning source repository.

public part

Publicly visible interface of a development component, containing an arbitrary number of development objects or produced entities.

release

State of a software component that represents an important milestone or a considerable enhancement of a software component's functionality.

resource

File, folder or fusion.

root version

The version of the resource that is the ancestor of all the versions of the resource.

propagation

This means that you can propagate changes into different workspaces that reside in different repositories if you physically transport the changes done in the source workspace. The changes done in the context of an activity are exported from the source repository and are imported into the target repository.

After importing all the changes into the target repository, you can integrate the activity into one or more target workspaces. This makes the changes visible in the target workspace.

successor

A version immediately following another version created by the check-in to the DTR.

top-level component

Development component without an enclosing parent component. Top-level components that are assigned directly to software components.

use dependency

Dependency between components with the meaning component A uses functionality of B.

version

A distinct state of a development or software component.

version control

A definition of a set of rules on how a development resource can be updated. A development resource under version control can either be in a checked-in or in a checked-out state.

version relation

A predecessor-successor relation between two versions of a version-controlled resource graphically represented by a line in the Design Time Repository perspective in the SAP NetWeaver Developer Studio.

version-controlled resource

When a resource is put under version control, it becomes a version-controlled resource.

workspace

A collection that contains multiple versioned resources but at most one version of each resource. Hence, the workspace contains a certain state of a set of resources. Workspaces behave like folders that contain pointers to the embedded versioned files and folders. In the DeltaV specification, these pointers are called version-controlled resources.

workspace folder

A folder that contains workspaces. Workspace folders are not-versioned resources.