|
Telelogic Synergy is a suite of tools for task-based Change Management and Configuration Management. Synergy provides lifecycle control for a company's digital assets (i.e. source code), enabling the assessment and authorization of change requests, from both internal and external sources, using a customizable change control workflow.
Task-Based Configuration Management The Task-based approach is a main notion in Synergy. It allows teams to create work tasks or assignments that may be linked to defects or change requests. When developers work on tasks, impacted objects are automatically linked to the task and delivered into the process with it. Configurations and releases are created by selecting the tasks to include. The objective of this approach is to provide top-down traceability (how change requests were implemented) and bottom-up traceability (what changes are included in a build). Traceability can be viewed to original requirements for DO-178B initiatives.
Transparent CM Synergy includes a user interface know as "ActiveCM". The version control commands run in the background to automatically tracking edits, additions, deletions or renames in the file system. This feature is targeted at non-developers and integrations to third-party products.
Features * The Synergy Suite also includes Telelogic Change, a Change request, problem tracking and workflow solution. * Synergy also includes MultiSite functionality, known as DCM. This feature enables different sites to exchange source code, tasks, change requests and process definitions. The elements that are exchanged can be defined by the GUI and filtered so only the desired information is sent to the other sites. * Synergy comes with a set of out-of-the-box models for common processes, such as agile software development and CMMI.
Reactions Telelogic Synergy has been recognized as a higher-end change and configuration management solution by analysts (cf. Ovum evaluates - Configuration management) and received the Yphise Award for Best Application Change Management Solution in 2006.
|
|
|