LEO Configuration Management is a robust, tried and tested software tool that provides support for configuration, change and release management in the context of a specific product, activity or service.
LEO Configuration Management manages the the process of creating software modules and the location and access to these modules in one or more vaults (as required).
Each individual module can have many attributes recorded. The module can also have parameters associated with it to allow for engineering searches for like software modules.
System Hierarchical Structure Definition
The LEO object data structure allows an item to be defined to as many levels as required, thereby modelling the real-life hierarchy. Hierarchical families can be the subject of full issue control or issue control may be affected using the baseline extract module.
All changes, versions and issues are recorded as unique records to enable a full product history to be maintained.
Problem and Change Management
LEO Configuration Management enables a problem to be raised on any defined design object. LEO conducts the management of the problem process against a user definable workflow. A problem may result in a change being proposed. A change may incorporate many problems.
User workspaces may be defined at project or user level. They can be defined by personal or shared, locally or served from a remote file server.
Vaults may be defined anywhere on the corporate network on any kind of file server with logical or physical division by project, date range or owner.
Task Management and Cost Tracking
Task management allows activities and costs to be apportioned by project, task, sub-task or software product.
Operating System Independent
The LEO Configuration Management sits on top of the Oracle Developer toolset. Generic application level commands such as file copies are invoked by the Oracle toolset layer rather than the application layer, thus providing environment independence.
LEO creates an audit trail invisibly for all major transactions capturing who did what and when.
The baselining module allows a snapshot to be taken of an object at any time in its lifecycle. A baseline can be extracted from the LEO database for any number of user definable reasons - for example:
- To release a build to manufacturing
- To deliver a build to a customer
- To conduct a project review
Views of Data by Customer, Project, Task, Object Hierarchy and File Type
Data can be viewed via an "explorer type" hierarchy tool starting at any entry point such as customer, project, task or software product.
Configuration Management Defined
"Configuration Management is the process of identifying and defining the items in the system, controlling the change of these items throughout their lifecycle, recording and reporting the status of items and change requests, and verifying the completeness and correctness of items."
Describes the system structure, the nature of its elements, their identity, and gives access to each item version.
Organises versions and changes to system items while keeping coherency and consistency on the complete system.