Edit
Attach
P
rintable
r17 - 2015-06-09 - 16:39:46 - Main.sbeard
You are here:
TWiki
>
Deployment Web
>
DeploymentIntegrating
>
CollaborativeLifecycleManagementPlus
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!!Collaborative Lifecycle Management plus (CLM+), version 5.0.2 %DKGRAY% Authors: Main.AmySilberbauer <br> Build basis: CLM+ version 5.0.2 %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> The Rational solution for Collaborative Lifecycle Management (CLM) provides integrations across Jazz-based products to connect the work of analysts with development and test teams. Cross-product links support traceability, web-like navigation, review, commenting, and status tracking across project repositories. CLM integrations build on the Jazz Foundation to provide a common approach to artifact linking, dashboards, security, and user interface frameworks. CLM integrations provide the following capabilities: * Link to existing artifacts across repositories in integrated products; for example, test cases are linked to work items and requirements. * Hover over links to quickly check the status of associated work; for example testers can monitor the status of a defect that they reported to the development team. * Add a widget to a dashboard to report query results from associated projects; for example, you can display requirements that have not been assigned test plans. * Add comments to any artifact in an integrated repository. Team members can use CLM integrations to achieve business objectives across the application lifecycle, as shown in the following figure and examples: Figure 1. The Rational solution for Collaborative Lifecycle Management connects analysts, developers, and testers [[https://jazz.net/wiki/pub/Deployment/CollaborativeLifecycleManagementPlus/calm_3.gif]] In *IBM® Rational® DOORS® Requirements Professional:* * Requirements are implemented by iteration plans in Rational Team Concert and validated by test plans in Rational Quality Manager. * Analysts and other team members develop requirements that drive development work items, test plans and test cases. In *IBM Rational Team Concert:* * Project managers and development managers use iteration plans to implement Rational DOORS Requirements Professional requirements in the context of a development schedule. * Iteration plan stories and other work items implement individual requirements. * Developers work on defects that are submitted by testers as a result of test execution. In *IBM Rational Quality Manager:* * The test team links requirements to test plans and test cases. * Testers link test cases to development work items to track development progress. * Testers submit defects in Rational Team Concert and verify the status of a defect or a build. ---++ Starting topics ---+++[[https://jazz.net/products/clm/][CLM project page on Jazz.net]] The Rational solution for Collaborative Lifecycle Management is a set of seamlessly integrated tools that work together as one: Rational Team Concert, Rational Quality Manager, IBM Rational Requirements Composer and now extended with Design Management. ---+++ [[https://jazz.net/wiki/bin/view/Main/BeCALMBook][BeCALMBook]] How to provide CLM integrations C/ALM enables integration of all kind of tools. It is not limited to tools that are based on Jazz Foundation. The following guidelines apply to both tools that are based on Jazz Foundation and other tools. The following guidelines distinguish between: * Integrated with Jazz [ IwJ ] - Independent products that are integrated with other Jazz products using the C/ALM integration patterns. They can take advantage of common Jazz services while retaining their own infrastructure. * Built with Jazz [ BwJ ] - Products built on top of the Jazz Foundation that use the Jazz infrastructure for collaboration, automation, and reporting Guidelines that apply to only 'built with' Jazz are tagged with [ BwJ ]; all the other guidelines apply to both. Guidelines which are targeted as part of the C/ALM 2010 effort follow at the end. ---+++ [[http://open-services.net/bin/view/Main/CalmHome][Collaborative ALM Scenarios]] This page is the launching point for exploring the OSLC resources through scenarios. Relationships between resources are defined through scenarios. ---+++++!! Related topics: None ---+++++!! External links: * None ---+++++!! Additional contributors: None <sticky></div></sticky>
Edit
|
Attach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
:
r19
<
r18
<
r17
<
r16
<
r15
|
More topic actions...
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.