Adopting the IBM Continuous Engineering (CE) solution Configuration Management Capability

copy 2015 2016 IBM Corporation

Adopting the IBM CE solution Configuration Management Capability

October 2016

Tim Feeney (tfeeneyusibmcom)Unleash the Labs ndash IBM trfeeneywordpresscom

Kathryn Fryer (fryerkcaibmcom)Unleash the Labs ndash IBM

copy 2015 2016 IBM Corporation2 May 2 2023 Adopting the IBM CE Solution Configuration Management Capability

DISCLAIMER

IBMrsquos statements regarding its plans directions and intent are subject to change or withdrawal without notice at IBMrsquos sole discretion Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision

The information mentioned regarding potential future products is not a commitment promise or legal obligation to deliver any material code or functionality Information about potential future products may not be incorporated into any contract The development release and timing of any future features or functionality described for our products remains at our sole discretion

copy Copyright IBM Corporation 2016 All rights reserved


Topics

bull Configuration management overviewbull Trade-offs and considerations ndash as of current release (602)

bull Primary factorsbull Reportingbull OSLC integrationsbull Linkingbull QM utilitiesbull Additional considerations

bull Enabling configuration managementbull Upgrade and migration

bull Adoption path and additional resources

copy 2015 2016 IBM Corporation4 May 2 2023

Linked Lifecycle Data


Zooming In


What if you have multiple versions of your artifacts

Which version to use

Which version to link to


Configurations define the correct artifact versions

Tests

QM Release AEach tool defines streams (changeable) and baselines (frozen) to select the correct artifact versions

Requirements

ValidatesTests

RM Release A

QM Release A

How do we know which RM stream belongs with which QM stream


Global configurations provide context

Requirements

Validates

Tests

Global configuration- Release A

RM Release A

QM Release A

The global configuration defines which streams andor baselines from the various applications belong together for a particular variant or version


Global configurations reference local configurations

AMR MobileUS 10 GA

AMR (QM) Mobile US

AMR (RM) 10 USGA

AMR (DMMobile US

AMR (SCM) Mobile US

Global Configuration Management

Requirements Management

Quality Management

Design Management

Source control

AMR Mobile component

AMR Mobile US


Global Configurations provide context


Global Configurations ndash building reusable components

bull A GC component can contribute to a higher-level GC componentbull By developing a hierarchy the GC structure can reflect build-up of a product or system

bull A GC component can contribute to more than one higher-level componentbull Build variant productssystemsbull Families of similar-but-different productssystems

Model v11

Engine v11

Pump 21 Spark v31

Gear v21

Global configurations


GC ComponentStreamContributions

A contribution from QM

Contribution from another GC component stream

13

Sports model convertible

Sports model coupe

Sports Model

Car X Model Time

GL Model

Putting it all together Speeding up delivery of highly customized Innovation

Work in a development stream that spans tools Baseline across tools Branch to create new variants or releases Compare across configs Control delivery of changes across configs Reuse without copying making updates and impact analysis much easier

Function

Stream

Baseline

= Baseline

= Branch

= Artifact propagation

Requirements

Architecture

Test

Implementation

Car X Model

Power Train X

GearBox X Engine X

Body X

Requirements

Architecture

Test

Implementation

Requirements

Architecture

Test

Implementation


Why adopt configuration management Extend the value of versioning and configurations across

lifecycle and disciplines Increase reuse speed of delivery and reliability in recreating

releases Improve quality and reduce cost


Trade-offs to consider(for projects adopting configuration management)

bull Configuration management capabilities come with some trade-offsbull Behavior changes from ldquonon-enabledrdquo projectsbull Limitations in the initial releases (fewer with each new release)bull Some inconsistencies across the products

bull One must be aware of all factors and carefully consider whether to enable configuration management for a project areabull Most critical considerations are described on

self-serve page on jazznet when obtaining an activation keybull Guided discussions with Support or other client-facing SMEs are

encouraged especially before production decisionbull Strongly encourage pilot before any production decision

bull Because once you enable configuration management for a project area you cannot disable it


Primary factorsbull Must upgrade everything to consistent v6 level

bull In general need consistent level to take advantage of newgrowing cross-application capabilities

bull v5 applications donrsquot understand versioning and configurationsbull Working with mixed versions is not practical beyond a short transition

bull Additional infrastructure requiredbull GCM and LDX applications ndash include on (expanded) JTS or separate

serverbull LQE server ndash 8-32 cores 16-256G RAMbull Potential impacts to other servers depending on repository size and shape

number of users usage patternshellipbull If RM or QM project areas are linked enable all or none of them

bull Enabling only some linked projects is not practical beyond a short transitionndash Links between them are frozenndash Cannot create new linksndash Links from the non-enabled project may not resolve correctly


Reporting considerations

bull Configuration-enabled projects use the LQE data source for reportingbull Once enabled projects do not send data to the data warehouse

(DW) but use LQE instead existing DW data is archivedndash Exception RTC which does not ldquoenablerdquo projects continues to

populate the DWbull Existing DW-based reports (BIRT RRDI dashboard widgets) must

be recreated or replaced ndash Exception RTC reports that do not include data from versioned

artifactsbull Rational Publishing Engine report templates can be reused specify

the target configuration



bull Some data is not yet available for configuration-aware reportingbull Time-based trending databull DNG view query resultsbull QM lab management resources (eg jobs requests reservations)bull RTC build informationbull Note some data is not available in either LQE or DW

ndash DNG reviews module hierarchy change set informationndash RTC SCM information plan resources WI comments

bull Some data available only by writing custom SPARQL queriesbull DM resourcesbull Local configurationsbull Link validity data bull QM lab resources (machines)

bull Project-area level access control not implemented for Link Validity (can be set manually in LQE)

bull Sample reports based on JKE sample available on Jazznet for evaluation no OOTB reports yet


OSLC Integrations

bull Most OSLC-based integrations outside the CLM applications do not yet support versioned artifactsbull Requires support for OASIS OSLC Configuration Management

spec (draft) expect list of supporting applications to grow over timebull Integrations to RTC work items continue to work as expected

because work items arenrsquot versioned

bull Several RQM test execution adapters have been verified to work correctly with enabled projects

bull IBM ClearQuest V80110 introduced initial support for global configurations see the CQ documentation for details

bull Progress made with other IBM and third-party applications expect more announcements in coming months


Changes related to linking

bull New Link Validity service replaces ldquosuspect linksrdquo in enabled projectsbull Automatic ldquosuspectrdquo assertion on changebull User assertion (validinvalidsuspect) bull No support yet for ldquoprofilesrdquo (canrsquot specify which properties affect

validity)bull In QM views you cannot filter on RTC work item and plan

traceability links


Additional considerations

bull QM Mobile application for offline execution not yet availablebull New roles and permissions to manage configurationsbull Behavior changes include

bull Working in global configuration contextbull DNG change sets and reviewsbull RTC configuration to determine configuration context

bull See appendix for additional behavior changes and minor limitations

bull A complete list of limitations and workarounds by release is available on jazznet bull View the 602 queries for workarounds and limitationsbull View the pending workaround articles for 602 from each productrsquos

release notes


Enabling Configuration Management

bull Rhapsody DM and RTC already support Configuration Management ndash no further action needed

bull Two-step process to fully enable configuration management for DNG and RQM 1 Enter activation key in application settings

ndash Advanced Properties gt Local Versioning Componentndash Obtain key from self-serve page on jazznet (for pilot) or contact IBM

Support (especially for production)2 Enable in project area property for a specific RM or QM project

areandash Configuration Management section gt click to enable

bull Once you enable Configuration Management for a Project Area you cannot disable it


When you click ldquoenablerdquo for DNGRQM projectshellip

bull Reporting switches to a new configuration-aware solution using LQEbull Project area stops feeding the DW and existing DW data is archivedbull BIRT and RRDI reports no longer work and are removed Dashboard

widgets that use report resources stop working

bull Backlinks are removed directional links created in and referenced from Link Index Servicebull May take some time to fully index especially for large projects

bull Existing links from external sources resolve to default configuration

bull QM snapshots become ldquoreference onlyrdquo use baselines instead


Upgrade and Migrationbull New components in v6x to enable configuration management

bull GCM application LQE data source Link Index service (LDX)bull Refer to new topology diagrams on deployment wikibull Be sure to consider related changes to production infrastructure requirements

bull All v6x upgrades require migrating to new RQM and DNG repository schemas regardless of configuration management use

bull Offline migrationbull Might take some time depending on repository sizeshape and network latency to the

database serverbull No additional online steps needed

bull Upgrades between 6x releases require re-indexing LQE data which might take timebull Reporting is unreliable during re-index

bull Performance of non-configuration management enabled projects expected to be consistent with previous versions

bull Additional repository updates happen when you enable Configuration Management for a project area (as previously described)


Adoption path

Explore and define how YOUR organization should implementbull Process definition is criticalbull Define usage model including roles stream strategies change

management and cross-stream deliveryhellipbull Assess reporting needs and implementation options

Conduct one or more pilot projectsbull Validate and modify usage scenarios and processes bull Consider both new and existing projects

Roll out selectively and progressivelybull Carefully select initial projects to enable bull Manage environment changesbull Train users on processes conventions tool changes


Global Configuration Management Adoption Service Offering

Achieve Strategic Reuse using Global Configurations

Benefits FeaturesComplete a smooth transition to Global

Configuration ManagementSpeed up adoption and avoid common

missteps by working with our knowledgeable experts

Benefit from the knowledge standard practices and proven repeatable processes brought by our experts

Build skills quickly and effectively with expert advice and information sharing directly from our experienced consultants

Preparing for enabling Global Configuration Management

Prepare the environment and users for the activities to enable the new capability

Supporting the activities to enable the new capability

Support upgrades and installations Verify successful operation

Supporting users transitioning to Global Configuration Management

Perform mentoring on usage updates and planning for enabling additional projects

Backed by world class Analytics Services Experts


For more information

bull Configuration management playlists on youtubebull Based on these lab exercisesbull Introductory series

bull Jazznet article 1492 links to many valuable resources including videos and blogs

bull Try it out httpsjazznetproductssandbox


ICE -IBM Continuous Engineering Event

Website httplearnquestconferencecomiceiot16


copy Copyright IBM Corporation 2015 All rights reserved The information contained in these materials is provided for informational purposes only and is provided AS IS without warranty of any kind express or implied IBM shall not be responsible for any damages arising out of the use of or otherwise related to these materials Nothing contained in these materials is intended to nor shall have the effect of creating any warranties or representations from IBM or its suppliers or licensors or altering the terms and conditions of the applicable license agreement governing the use of IBM software References in these materials to IBM products programs or services do not imply that they will be available in all countries in which IBM operates Product release dates andor capabilities referenced in these materials may change at any time at IBMrsquos sole discretion based on market opportunities or other factors and are not intended to be a commitment to future product or feature availability in any way IBM the IBM logo Rational the Rational logo and other IBM products and services are trademarks of the International Business Machines Corporation in the United States other countries or both Other company product or service names may be trademarks or service marks of others


Appendix A Additional considerations and behavior changes for Configuration Management


Reporting considerationsbull When reporting across versioned artifacts and RTC work items carefully consider filtering

bull Filtering by configuration will yield correct results for versioned artifactsbull Filter work items based on Planned-For or Found-In fields as they have no direct association to a configuration

bull When reporting on DNG artifactsbull As of 602 reverse traceability is now supported for custom link types as well as for OSLC RM-defined links bull If you customize data types (new types or attributes) you need to add them to the initial RM stream for them to

be visible for reportingndash Alternatively use custom SPARQL queries for customized types that are not in the initial stream

bull LQE indexes all projects no UI to select or exclude projects (to reduce volume)bull Current scale is 2 million versioned resources per LQE instance with 15725 configurations bull Where concerns arise IBM can assist with configuring LQE to index only selected project areas

bull Upgrade notes bull When upgrading from v60 (where configuration-aware reporting was Tech Preview only)

ndash Uninstall the v60 LQE component and reinstall with v602 upgradendash Configure RB data sources to add LQE (httpsserverportrssetup)

bull When upgrading from v601ndash Rebase the DNG TRS feeds (instructions in the Interactive Upgrade Guide)ndash Re-index the TRS feeds from DNG RTC and data sources (httpsserverportlqewebadmindata-sources)


RTC considerationsbull Work items are not versioned tracking and planning artifacts are not part

of GC contributionsbull RTC work items are targeted to a single Release and therefore a single

GC bull Each supported OSLC link type is associated with a single attribute specifying

the Release target (Planned For Found In or some custom attribute)bull When you set or change the Release target (and GC) for a WI you must save

the work item to make the context change take effectbull If you change the Release gt GC association in the RTC project area the

versioned links will not work correctlybull If there is no GC associated with a Release links resolve to the default

configurationbull Child iterations can inherit Release setting from the parent or have their own

(eg Sprints under a main iteration can contribute to the same Release and GC)

bull If you are working in a Personal Stream RTC cannot resolve the configuration context and therefore cannot filter artifacts by configuration when you create links


Managing and delivering changebull DNG and DM have change sets RQM doesnrsquot

bull If necessary create separate RQM stream to model changes before delivering to main stream (note that this requires additional stream management and manual work with a Personal Stream)

bull Can create link from DNG or DM change set to change request (eg RTC work item)bull DNG now allows you to enforce

bull Requiring change set for any changes bull Requiring change set be linked to an approved change request in an OSLC change

management provider (like RTC)bull Delivering changes varies

bull Within DNGndash If you deliver changes from the Manage Configurations view you can only deliver between

parentchild in the stream hierarchyndash If you deliver from an artifact view you can choose any stream as the target (Deliver changes) or

source (Accept changes) and start from either directionndash You can select one or more change sets conflicts are highlighted and can be mergedndash As of 602 you can choose to automatically deliver changes providing inputs on how to resolve

conflicts (as well as returning to manual mode in case of conflict)bull RQM merges changes from a source baseline to the current stream selected by the GC

merge can be selectivendash Start operation from the target not the source of the changes ndash In effect you accept changes from a source baseline into the current configuration


More tips for change setsbull In DNG you cannot create a review against a change setbull Your DNG change set is automatically added to your Personal Stream (PS) at creation and

removed at deliverydiscardbull Only one change set per DNG configuration in the PS at one time creating a second

change set for the same configuration replaces the first in the PS and requires manual changes to switch between them

bull You can manually add someone elsersquos change set to your PS (previous point still applies)bull Personal Streams persist and are reused for future change sets

ndash In 602 when you deliver your change set the configuration context remains set to your Personal Stream

bull RTC does not recognize the context of a Personal Stream when you create links from an artifact in a PS to an RTC artifact filtering based on configuration context will not work

bull DNG change set content is not visible after you deliverbull Before delivering you can compare the change set to the existing baseline or stream to identify

the changes it contains bull If you link the change set to a WI you can manually describe the changes in the WIbull Use naming conventions to indicate content or reason for change

bull Use naming conventions so you can recognize change sets at delivery timebull If you need to deliver across streams use explicit change sets

bull Implicit change sets are hard to identify and differentiate


Consider security and permissions

bull To reference a GC you must be a member of the GC project area (in GCM application)bull Even to set the GC context in your RMQMDM applicationbull Can use lifecycle projects to ease user administration bull Members who need to create Personal Streams must have

permission to do sobull GC Configuration Leads must be members of RMQMCCMDM

project areas in order to access streams and baselinesbull Must have project permissions to create streamsbaselines

bull Assign roles and permissions for creating streams and baselines in local applications as well as GCMbull For DNG this includes permissions related to change sets owned

by yourself and by others


GCM considerations

bull GCM application has no project associationsbull You can define it as part of Lifecycle Project but it just makes

adding all the users easier no other effectbull A GC may include more than one contribution from a component

or project area (ldquocomponent skewrdquo)bull Resolves to first configuration found in list of contributions or

hierarchybull Use component skew reports to identify skew and ensure

configurations are ordered as intended ndash especially for large or complex hierarchies


Deployment considerations

bull Single GCM application per JTS bull A project area canrsquot contribute to multiple GCM applications bull A project area can contribute to more than one GC component or

project within a single GCM applicationbull GC components are at granularity of project area ndash define

project areas accordinglybull The project area is used in the configuration as a single unit ndash the

entire project area is included in a stream or baseline and as a contribution to a GC You canrsquot subdivide a project area and contribute only part of it

bull For more information including recommended deployment topologies see the Deployment Wiki


Appendix C Architectural changes from 5x to 6x (reference)


Rational Team

Concert

CLM Architecture 5x

Rational Quality Manager

DOORs Next Generation(

RRC)

Rational Design

Manager

CLM Web Client

RTC VS EclipseClient

Rhapsody DM

Client

Relational DB Server

JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting

bull User Project Adminbull Authorizationbull Repository Servicesbull Process


CLM Architecture 6x (w PLE)

Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

Config Aware OSLC Integration wo backlinks

Reporting


Lifecycle Query

Engine

Global Config Service

Backlink Index

Service

Additions or restructured to support multiple configurations

Fundamental rework of the query

and repository services

Reorganization of the RQM and DNG data into schema that supports configurations

Restructuring of the OSLC cross product linkages

to support configuration

Requires removal of ldquobacklinksrdquo

Rework of the web UIs to allow selection of configuration and maintain config as user

navigates app to app

Add configuration management to RQM and DNG Includes reworking storage layers adding compare and

merge UIs

Modify trackingplanning to work with

versioned CLM resources


OSLC Links and Configuration Managementbull In 5x and earlier creating a link from artifact A to artifact B typically

resulted in the creation of a link in the reverse direction ndash a lsquobacklinkrsquobull In 60 configuration management enabled projects to link between

versioned resources the configuration is used to determine the right version of the target artifactbull A single link is stored in the artifact of the application owning the link

(not necessarily the one that created it) A backlink is no longer created and stored ndash RTC owns all links involving RTCndash RQM owns all links between QM and RMDMndash DM owns links between DM and RM

bull A new Link Index Service is used to determine if incoming links to an artifact version exist and thus visiblenavigable from that artifact

bull In 60 projects that configuration management is NOT enabled the linking storagebehavior is the same as that used in 5x ie backlinks are created

Adopting the IBM CE solution Configuration Management Capabilit

Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10



Putting it all together Speeding up delivery of highly custom

Why adopt configuration management

Trade-offs to consider (for projects adopting configuration man

Primary factors



OSLC Integrations





Upgrade and Migration

Adoption path



Slide 28

Slide 29

Appendix A Additional considerations and behavior changes for

Reporting considerations (2)

RTC considerations

Managing and delivering change

More tips for change sets


GCM considerations



CLM Architecture 5x


OSLC Links and Configuration Management


DISCLAIMER

IBMrsquos statements regarding its plans directions and intent are subject to change or withdrawal without notice at IBMrsquos sole discretion Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision

The information mentioned regarding potential future products is not a commitment promise or legal obligation to deliver any material code or functionality Information about potential future products may not be incorporated into any contract The development release and timing of any future features or functionality described for our products remains at our sole discretion

copy Copyright IBM Corporation 2016 All rights reserved


Topics








Zooming In







Tests


Requirements

ValidatesTests

RM Release A

QM Release A




Requirements

Validates

Tests


RM Release A

QM Release A




AMR MobileUS 10 GA

AMR (QM) Mobile US

AMR (RM) 10 USGA

AMR (DMMobile US

AMR (SCM) Mobile US



Quality Management

Design Management

Source control


AMR Mobile US







Model v11

Engine v11

Pump 21 Spark v31

Gear v21






13


Sports model coupe

Sports Model

Car X Model Time

GL Model



Function

Stream

Baseline

= Baseline

= Branch


Requirements

Architecture

Test

Implementation

Car X Model

Power Train X

GearBox X Engine X

Body X

Requirements

Architecture

Test

Implementation

Requirements

Architecture

Test

Implementation




































OSLC Integrations











traceability links







release notes


























Adoption path

















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x




Topics








Zooming In







Tests


Requirements

ValidatesTests

RM Release A

QM Release A




Requirements

Validates

Tests


RM Release A

QM Release A




AMR MobileUS 10 GA

AMR (QM) Mobile US

AMR (RM) 10 USGA

AMR (DMMobile US

AMR (SCM) Mobile US



Quality Management

Design Management

Source control


AMR Mobile US







Model v11

Engine v11

Pump 21 Spark v31

Gear v21






13


Sports model coupe

Sports Model

Car X Model Time

GL Model



Function

Stream

Baseline

= Baseline

= Branch


Requirements

Architecture

Test

Implementation

Car X Model

Power Train X

GearBox X Engine X

Body X

Requirements

Architecture

Test

Implementation

Requirements

Architecture

Test

Implementation




































OSLC Integrations











traceability links







release notes


























Adoption path

















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x






Zooming In







Tests


Requirements

ValidatesTests

RM Release A

QM Release A




Requirements

Validates

Tests


RM Release A

QM Release A




AMR MobileUS 10 GA

AMR (QM) Mobile US

AMR (RM) 10 USGA

AMR (DMMobile US

AMR (SCM) Mobile US



Quality Management

Design Management

Source control


AMR Mobile US







Model v11

Engine v11

Pump 21 Spark v31

Gear v21






13


Sports model coupe

Sports Model

Car X Model Time

GL Model



Function

Stream

Baseline

= Baseline

= Branch


Requirements

Architecture

Test

Implementation

Car X Model

Power Train X

GearBox X Engine X

Body X

Requirements

Architecture

Test

Implementation

Requirements

Architecture

Test

Implementation




































OSLC Integrations











traceability links







release notes


























Adoption path

















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x









Tests


Requirements

ValidatesTests

RM Release A

QM Release A




Requirements

Validates

Tests


RM Release A

QM Release A




AMR MobileUS 10 GA

AMR (QM) Mobile US

AMR (RM) 10 USGA

AMR (DMMobile US

AMR (SCM) Mobile US



Quality Management

Design Management

Source control


AMR Mobile US







Model v11

Engine v11

Pump 21 Spark v31

Gear v21






13


Sports model coupe

Sports Model

Car X Model Time

GL Model



Function

Stream

Baseline

= Baseline

= Branch


Requirements

Architecture

Test

Implementation

Car X Model

Power Train X

GearBox X Engine X

Body X

Requirements

Architecture

Test

Implementation

Requirements

Architecture

Test

Implementation




































OSLC Integrations











traceability links







release notes


























Adoption path

















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x





Requirements

Validates

Tests


RM Release A

QM Release A




AMR MobileUS 10 GA

AMR (QM) Mobile US

AMR (RM) 10 USGA

AMR (DMMobile US

AMR (SCM) Mobile US



Quality Management

Design Management

Source control


AMR Mobile US







Model v11

Engine v11

Pump 21 Spark v31

Gear v21






13


Sports model coupe

Sports Model

Car X Model Time

GL Model



Function

Stream

Baseline

= Baseline

= Branch


Requirements

Architecture

Test

Implementation

Car X Model

Power Train X

GearBox X Engine X

Body X

Requirements

Architecture

Test

Implementation

Requirements

Architecture

Test

Implementation




































OSLC Integrations











traceability links







release notes


























Adoption path

















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x





AMR MobileUS 10 GA

AMR (QM) Mobile US

AMR (RM) 10 USGA

AMR (DMMobile US

AMR (SCM) Mobile US



Quality Management

Design Management

Source control


AMR Mobile US







Model v11

Engine v11

Pump 21 Spark v31

Gear v21






13


Sports model coupe

Sports Model

Car X Model Time

GL Model



Function

Stream

Baseline

= Baseline

= Branch


Requirements

Architecture

Test

Implementation

Car X Model

Power Train X

GearBox X Engine X

Body X

Requirements

Architecture

Test

Implementation

Requirements

Architecture

Test

Implementation




































OSLC Integrations











traceability links







release notes


























Adoption path

















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x









Model v11

Engine v11

Pump 21 Spark v31

Gear v21






13


Sports model coupe

Sports Model

Car X Model Time

GL Model



Function

Stream

Baseline

= Baseline

= Branch


Requirements

Architecture

Test

Implementation

Car X Model

Power Train X

GearBox X Engine X

Body X

Requirements

Architecture

Test

Implementation

Requirements

Architecture

Test

Implementation




































OSLC Integrations











traceability links







release notes


























Adoption path

















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x







13


Sports model coupe

Sports Model

Car X Model Time

GL Model



Function

Stream

Baseline

= Baseline

= Branch


Requirements

Architecture

Test

Implementation

Car X Model

Power Train X

GearBox X Engine X

Body X

Requirements

Architecture

Test

Implementation

Requirements

Architecture

Test

Implementation




































OSLC Integrations











traceability links







release notes


























Adoption path

















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x






































OSLC Integrations











traceability links







release notes


























Adoption path

















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x







traceability links







release notes


























Adoption path

















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x









release notes


























Adoption path

















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x




























Adoption path

















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x















































































GCM considerations
















Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x













Rational Team

Concert

CLM Architecture 5x



RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation

OSLC Integration

Reporting




Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x





Rational Team

Concert

Rational Quality

Manager


RRC)

Rational Design

Manager

CLM Web Client


Rhapsody DM

Client


JAFDB

RTCDB

RQMDB

DNGDB

RDMDB

Application Server

Jazz Foundation


Reporting


Lifecycle Query

Engine


Backlink Index

Service











merge UIs











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x











Slide 2

Topics

Slide 4

Slide 5

Slide 6




Slide 10






Primary factors



OSLC Integrations






Adoption path



Slide 28

Slide 29



RTC considerations




GCM considerations



CLM Architecture 5x



Adopting the IBM Continuous Engineering (CE) solution Configuration Management Capability

Software

Transcript of Adopting the IBM Continuous Engineering (CE) solution Configuration Management Capability