Software configuration management a clear case for IBM Rational ClearCase and ClearQuest UCM
This IBM Redbook describes configuration management in general and how it is implemented in the Rational products ClearCase and ClearQuest. The target audience for this redbook is anyone considering a software configuration management (SCM) solution, and in particular, project managers and configura...
| Autor Corporativo: | |
|---|---|
| Otros Autores: | |
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Research Triangle Park, N.C. :
IBM
c2004.
|
| Edición: | 1st ed |
| Colección: | IBM redbooks.
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627304406719 |
Tabla de Contenidos:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 Introduction to SCM
- Chapter 1. The quest for software lifecycle management
- Stories from the wild
- Software asset management
- Better software configuration management means better business
- Seven keys to improving business value
- Safety
- Stability
- Control
- Auditability
- Reproducibility
- Traceability
- Scalability
- Good SCM is good business
- Chapter 2. Choosing the right SCM strategy
- The questions
- A version control strategy
- Delta versioning
- A configuration control strategy
- A process management strategy
- A problem tracking strategy
- Chapter 3. Why ClearCase and ClearQuest
- Introduction
- IBM Rational Team Unifying Platform
- IBM Rational ClearCase
- ClearCase LT
- ClearCase
- ClearCase MultiSite
- Unified Change Management
- IBM Rational ClearQuest
- Chapter 4. Mapping and terminology of the IBM Rational product set
- Mapping of the IBM Rational product set to SCM areas
- Base ClearCase
- ClearQuest
- ClearCase UCM
- ClearCase UCM + ClearQuest
- Terminology
- Basic terminology
- Element
- Version
- Versioned object base
- Views
- Checkout model
- Base ClearCase terminology
- Branch
- Version label
- Configuration specification
- UCM terminology
- Project
- Component
- Activity
- Work areas and streams
- Baselines
- ClearQuest terminology
- Schemas
- Schema repositories
- User databases
- Database sets and connections
- State transition model
- Chapter 5. Planning for software configuration management
- Planning for ClearCase and ClearQuest
- Writing an SCM plan
- Introduction
- Purpose
- Scope
- Definitions, acronyms, and abbreviations
- References
- Overview
- The SCM framework.
- Organization, responsibilities, and interfaces
- Tools, environment, and infrastructure
- Administration and maintenance
- The SCM process
- Configuration identification
- Configuration and change control
- Configuration status accounting
- Milestones
- Training and resources
- Subcontractor and vendor software control
- Rules for the road
- Why projects fail and succeed
- Roadmap
- Where are we?
- Step 1: Establish the current state of your SCM systems
- Where are we going?
- Step 2: Develop high-level future SCM goals
- Step 3: Decide upon Base ClearCase or UCM
- Step 4: Understand the terminology
- Step 5: Do the deployment planning
- How do we get there?
- Step 6: Set up the environment
- Step 7: Define roles, responsibilities, and policies
- Step 8: Install and configure
- Step 9: Rollout to end-users
- Step 10: Integrate with other development environments
- Step 11: Be prepared for change
- Strategies for getting started
- Start now
- Manage expectations
- Involve the end users and other stake holders early
- Start small but keep an eye on what is next
- Expect to iterate
- Start now (again)
- Part 2 Implementing ClearCase
- Chapter 6. Planning for ClearCase
- Roles and responsibilities
- Education and training
- ClearCase environment overview
- Networkwide release host
- ClearCase LT hosts
- ClearCase hosts
- Define your SCM infrastructure
- Right sizing your network
- Right sizing your servers
- Supported architectures
- Supported platforms for ClearCase Web servers and interface
- Platform requirements for ClearCase mainframe connectors
- Supported file systems
- VOB server
- Processor capacity
- Physical memory
- Disk capacity
- Network interface
- Improving VOB server performance
- View server
- Build server
- Client hosts
- Some words on RAID levels
- Review security policies.
- Administration and maintenance
- Backup strategies
- VOB and view backup tools requirements
- VOB backup strategies
- View backup strategies
- Registry backup strategies
- Software planning
- License management
- Base ClearCase or ClearCase UCM
- Basic software requirements
- Required operating system patches
- Additional software tools
- Sources of information
- Chapter 7. Setting up ClearCase
- Start now
- Setting up a playground environment
- The playground
- Moving on to a serious test environment
- Minimal test environment
- Setting up your environment
- Network infrastructure
- Setting up ClearCase
- Servers first
- Server connections
- Registry server
- ClearCase registry
- ClearCase region
- Accessing VOBs or views from another region
- ClearCase registry services in a nutshell
- License server
- VOB and view servers
- About sizing of a server
- Prepare for change
- Changing the license server
- Changing the registry server
- Moving a VOB to another server
- Moving a view to another server
- Relocating the release area
- UNIX servers and Windows clients
- SMB (CIFS) on the UNIX server
- NFS in the clients
- NAS or SAN for storage areas
- Use of snapshot views
- Clients
- Client for Samba or TAS specials
- Handling the 04:30am storm
- Backup and recovery
- VOBs
- Views
- Registry
- License and var
- Release area
- Restore
- MultiSite as backup
- Standard maintenance
- Disaster recovery for ClearCase
- Migrating code into ClearCase
- Rollout to users
- Training
- Hands-on
- Staging
- Successful rollout
- Get help
- Part 3 Implementing ClearQuest for UCM
- Chapter 8. Planning for ClearQuest
- Background
- What is ClearQuest?
- Schemas, repositories, databases, and other terms
- How ClearQuest works
- Roles and responsibilities in ClearQuest
- ClearQuest administrator.
- Schema designer
- Database administrator
- Architect or project manager
- Designer or engineer
- Tester
- Change control board
- Requester
- User
- Submitter
- Project lead
- ClearQuest infrastructure
- General issues and the code page
- License server
- ClearQuest database server (vendor database server)
- ClearQuest MultiSite shipping server
- Administration client
- ClearQuest Web server
- ClearQuest server
- ClearQuest (native) clients
- ClearQuest Web client
- ClearQuest mail
- Disk space provider
- Planning the infrastructure
- Planning the process
- Planning the installation
- Estimating storage for installation
- Estimating database size
- Sources of information
- Chapter 9. Setting up ClearQuest
- Plan your environment
- Have a test environment
- Reasons to have a test environment
- Start it now
- Database server
- Set up the database server
- Set up and test backup and recovery routines
- Standard maintenance
- Disaster recovery for ClearQuest
- Installation
- Rollout to users
- Who will take part
- Training
- Train for change
- Successful rollouts
- Example 1: The big bang
- Example 2: Step by step
- Part 4 Implementing Unified Change Management
- Chapter 10. Implementing UCM
- UCM background
- UCM objects
- UCM lifecycle
- UCM policies
- UCM ClearQuest integration
- UCM schemas
- Enabling ClearQuest integration
- UCM change request workflow
- UCM process policies
- UCM design overview
- UCM configuration component design
- Defining component scope
- Managing component sets and hierarchies
- Managing component reuse
- Implementing components
- Component design constraints
- UCM project design
- Project organization
- Project design constraints
- UCM stream design
- Private development streams
- Single-stream projects
- Shared-stream projects
- Stream hierarchies.
- Projects versus streams
- Special-purpose streams
- Slightly-parallel development
- Physical VOB definition
- Baseline naming conventions
- Integrating ClearQuest with UCM
- UCM with and without ClearQuest
- Customizing the change management lifecycle
- ClearQuest UCM policy customization
- Defining parent-child activities
- ClearQuest security control
- Multiple user databases
- ClearQuest design constraints
- UCM watch list of common design problems
- Moving to private streams too early
- Moving to private streams too late
- Too many UCM projects
- Letting streams go stale
- Over-complicated state models
- Using substreams or new projects
- UCM infrastructure
- Administrative considerations for UCM
- Managing UCM datasets
- Manage old views
- Project creation process
- Managing old objects
- Getting started: setting up a UCM playground
- Playground overview
- Step 1-Infrastructure setup
- Set up an account on developerWorks
- Collect installation prerequisites
- Download the latest ClearCase software
- Turn off any virus scanning software
- Install the Microsoft Loopback Adapter
- Install ClearCase
- Step 2-Establish UCM repositories and components
- Create storage locations for VOBs and views
- Create a VOB, view, and a couple of components
- Step 3-Create a UCM project
- Step 4-Walk through the standard UCM development lifecycle
- Step 5-Install ClearQuest and create a data set
- Fetch ClearQuest software and license
- Install the Rational license server and ClearQuest
- Create a ClearQuest data set
- Set the code page for the data set
- Document the ClearQuest database definitions
- Step 6-Integrate the UCM project with ClearQuest
- Converting activity records to UCM
- Creating activities in a ClearQuest-enabled project
- Next steps
- Additional information
- Chapter 11. Managing complexity.
- Building software is not like building bridges.
