SOFTWARE CHANGE MANAGEMENT
Continuity in an up-to-date IT infrastructure is of vital importance for any organisation. Changes and
improvements to software should not disturb or reduce the availability of IT Services. The Software Lifecycle Support (SLS) process using TD/OMS is essentially aimed at providing control over these changes.
Organisations using TD/OMS have the necessary controls to all aspects of their application development, thus supporting the ISO9001 standard as well as being able to meet regulatory requirements guidelines such as SOX, Basel II or CLERP 9.
Modules of TD/OMS
TD/OMS is divided into several modules, each suited for a specific task. The modules can be distinguished into 5 categories:
1. The base modules of TD/OMS consist of Kernel and Work Management.
- The Kernel holds all definitions at the application level, a complete survey of the objects to be managed, which includes the corresponding source (if any) and the inter-object relationships.
The Work Management module contains:
- The Helpdesk functionality which is employed to register every incident with their forthcoming actions. Similar incidents can be collected, settled or sent to a central processing point in an organisation. This module can be used locally as well as in a network.
- The Request Management functionality registers confirmed requests, tasks that follow from a request, and the objects belonging to a task. This module provides information on the status of requests and tasks.
- The Source Compare & Merge functionality enables the user to determine differences between two versions of a source and integrate them into a next version. This module uses the source as a base and is especially suited to manage situations of dual maintenance.
- The Object Transfer functionality provides in the local transfer of objects and guards possible exceptions per object.
2. The Distribution module contains the functionality for Object Distribution and Object Receiving in the Enterprise and take care of the distribution of all objects to remote servers or partitions. Once the controlling definitions have been entered, the transport and installation of objects on remote machines can be managed centrally. A network can be treated as a logical unit. Objects can be distributed using TCP/IP, SNADS or tape.
3. Distribution modules for non-System i components: Client deployment modules. The client
deployment modules incorporate the management of objects on the Windows and Unix/ Linux client and server platforms.
4. The Impact Analysis module generates an overview of components related to software change, supporting the user in the preparation of complex adjustments or enhancements.
5. Modules for interfaces with fourth generation languages. These include CA 2E, CA PLEX, AS/SET, Powerhouse, LANSA, IDDOS and agic. These modules enable the user to manage at function level.
YES, I would like a Product demonstration ...
Click here for more Info ....