This is preceded by the analysis of the application objects affected by a development service. It is assumed that the developer has access to his own database schema of the application. In devcontrol there is always a development task for the developer to process.
The objects which are relevant for the development can be reserved for a DT in devcontrol. If the source code for the appropriate object has been versioned in Source Control System, the current version is checked out in the file system. Neither process is compulsory; the metadata object does not have to subject to the version check or can also be reserved in another DT.
devcontrol is not a tool for editing source codes. Tools from Oracle® and other providers are available for the database. This is even more valid for manufacturers of linked source codes such as Oracle® Forms, Borland Delphi, Oracle® JDeveloper or Microsoft Visual Studio. An exception to this applies to database-based objects: these can also be modified in devcontrol and the corresponding scripts generated with the object generator. Changes to the developer in the database schema are automatically logged by devcontrol and assigned to a DT.
When the development services in a DT are finished, the file system-based source codes will be assigned to the DT and the metadata aligned with the respective object parser. For database-based objects, the metadata is aligned with the object parser because of the logged schema changes. Until this point, objects in devcontrol do not need to have been reserved. All changes can only be present in the schema of the developer or in the file system. After the metadata alignment, changes can still be deleted, because they have only appeared in the schema by chance and have no relation to the development service.
When a development task is concluded, the changes for database objects and source code objects are transferred to the metadata repository. The source codes are versioned in the source control system. Upstream check routines can block the completion of a DT. This can affect object properties which are to be processed manually (description of a column) and also relations which are to be maintained manually (assignment of a table to a database role).
During the check-in of a development task, the changes are logged in the metadata of the application repository. In this way, the application version can be restored before or after any DT.
The assessment of the changes to the metadata repository by a development task gives an overview of the development services.
