1 / 11

IBM Rational ClearCase & ClearQuest Unified Change Management (UCM)

IBM Rational ClearCase & ClearQuest Unified Change Management (UCM). Arizona Rational Users Group Eric J. Ostrander, Spectrum Astro Inc. http://ejostrander.com. So, this guy walks into a bar wearing a duck on his head …*. * (wait for laughter). What are ClearCase and ClearQuest?.

audra-ford
Download Presentation

IBM Rational ClearCase & ClearQuest Unified Change Management (UCM)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IBM RationalClearCase & ClearQuestUnified Change Management (UCM) Arizona Rational Users Group Eric J. Ostrander, Spectrum Astro Inc. http://ejostrander.com

  2. So, this guy walks into a bar wearing a duck on his head …* * (wait for laughter)

  3. What are ClearCase and ClearQuest? … to establish and maintain the integrity of the products of the software project throughout the project's life cycle. • Integrated Configuration and Change Management • ClearCase: version control • ClearQuest: defect, enhancement, and issue tracking • Both MultiSite

  4. What is Unified Change Management (UCM)? • Out-of-the-box industry best practices • developed over many, many years of doing SCM • see Brian White’s “Software Configuration Management Strategies for Rational ClearCase” • Parallel development of projects and components • Workspace (stream) management • Activity based development • with or without ClearQuest integrated • Baseline management • No extra licenses required • Easily set and enforce policies • Whole new world of terminology, methodology, automation, etc …

  5. When is it appropriate to use UCM? • Useful for large or small teams • Gives a robust, easy-to-use, best-practice environment that developers can “ramp up on” in a short time • Works on Windows, Unix and Linux, command-line, GUI, API, and web interfaces • Can start from scratch, convert from an existing ClearCase environment, or import from another version control tool • ClearCase UCM 5.0 or higher appropriate for all projects

  6. In what “modes” can UCM be used? • Standard integration stream w/ one development stream per developer • Sub-development streams (sub-teams) • Shared development stream • Integration stream development only • UCM helps manage SCM complexities • Complexity cannot be any less than project requirements • Developer confusion in highly paralleled development environment can be significantly reduced

  7. Should ClearQuest be integrated? • Integrates w/ or w/o UCM • Activities have a life cycle • Transfer of information is automatic • Easier metrics gathering • Greater control over activities • Easier automation between tools

  8. Breakout sessions http://ejostrander.com • Demo station 1: RequisitePro, Project Console • Demo station 2: ClearCase, ClearQuest, RequisitePro • What’s new in UCM 2002.05.00? • What’s new in UCM 2003.06.00? • UCM technical discussions

  9. What’s new in UCM 2002? • Development stream hierarchies • Interproject delivers • Non-default deliver policies • Deliver from a baseline instead of LATEST • Deliver preview • Composite baselines • Multi-component VOBs • Triggers on most UCM commands • Web support for UCM

  10. What’s new in UCM 2003? • Significant performance improvements • UCM view creation from the web • Graphical merges allowed even if no conflicts • Single-stream projects • Read-only streams • Share components between PVOBs • Baseline naming templates • Display the activities of a deliver • Checkin by activity • Create sub-VOB components from the GUI

  11. UCM Technical Discussion • One PVOB per software program – don’t share • Move an activity between streams – w/ or w/o ClearQuest • Share activities – w/ or w/o ClearQuest • Roll back to a previous point in time • Full, incremental, and composite baselines • Master project concept • Retire a project • Rename a baseline or integration stream • Recover hidden elements • Evil twins • Work associated with the wrong activity, stream, or project • NEVER remove UCM objects, unless …

More Related