Term |
Definition |
Access Control List (ACL) |
Optional attribute of a package interface. If present, it specifies which client packages are granted access to the package interface. |
Access Object |
Identifies a set of packages (service) that is allowed to access objects in certain client interfaces. These client interfaces must be associated with that access object. |
Client Interface |
Interface a client of an access object can use to expose certain objects for use by that access object. |
Component Object |
Object relevant for the package check that appears as part of a composite object. |
Composite Object |
Object relevant for the package check that contains other objects that are relevant for the package check. |
Dependency Control List (DCL) |
A dependency control list is a set of packages or interfaces to which the current package has declared a usage. The dependency can be an inclusion or an exclusion. Moreover the dependency can be limited to one or more sub packages of the current package. |
Encapsulation Level |
The development objects that are added into one or more interface are the exposed objects. |
Exposed Objects / Visible Elements |
Package that is created by a generating application to contain the generated objects. It is attached to a target package and can access the same objects as the target package. Additionally, it has access to a generator-specific runtime environment that is not accessible by the target package. |
Generation Append Package |
Local generation append package: A generation append package that exists only locally in the system and cannot be transported. It replaces generating into $TMP. |
Package Interface List |
A list of package interfaces belonging to the same package. It is provided by the server package to facilitate the declaration of the client’s dependency control list. |
Package Interface |
A list of exposed objects to be used by client packages. The exposed objects can originate from the same package or from another package interface whose contents is propagatable. |
Usability |
A development object is said to be usable to a surrounding package if the containing interface has not defined any usage restrictions to the surrounding package. |
Usage Type |
Attribute of the exposure of an object at a package interface or a client interface. It defines the most superior way in which the object can be used. A usage type maps to a set of usage operations. |
Usage Operation |
Technical identifiable way of using an object, for example using a protected section of a superclass. A Usage Operation may be contained in one or more usage types. Actual package checking is based on usage operations. |
Visibility |
A development object is said to be visible to the surrounding packages if it exposed in an interface of the package. |