Best Practices for CLM Usage Models
Authors: TimFeeneyBuild basis: The Rational solution for Collaborative Lifecycle Management (CLM) and the Rational solution for systems and software engineering (SSE) v6.0.x.
Each of the CLM applications includes extensive value-added capabilities that when used properly help customers improve their development processes and meet their business goals. As with many applications, there are multiple ways to accomplish the same outcome. The CLM applications are no different in that regard. They too can be configured in optimal and not so optimal ways.
How customers use and configure a CLM application is called a usage model. This page is a collection point for gathering various usage best practices.
CLM
Rational DOORS Next Generation
Rhapsody Model Manager
- RMM is powered by RTC SCM
Rational Team Concert
- Rational Team Concert process fundamentals
- RTC Plan Loading Best Practices
- Using Rational Team Concert for source code management in Jenkins jobs
Rational Quality Manager
Jazz Reporting Services
Global Configuration Management
General
- Best practices for CLM global configuration management
- Adoption guidance and practices
- Configuration Management FAQs
- Defining your component strategy
- Patterns for stream usage
Deployment
- Non-functional considerations when adopting IBM ELM solution for global configuration management (coming soon)
- Scaling the configuration-aware reporting environment (coming soon)
DOORS Next
- Maintaining the DNG type system in a configuration management environment (Part 1 - manual procedures)
- Configuration management: Best practices for collaborating with ReqIF between DNG instances
ETM
EWM

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.