Software Configuration Management Strategies and IBM Rational ClearCase: A Practical Introduction
Bibliographic record
Abstract
Foreword. Preface. Acknowledgments. 1. What Is Software Configuration Management? SCM Best Practices. SCM Tools and SCM Process. 2. Growing into Your SCM Solution. Dealing with Changing Project Requirements. Evolution of SCM Tools. Summary. 3. An Overview of the Unified Change Management Model. What Is UCM? What Is ClearCase? ClearCase UCM Process Overview. The Architect: Defining the Implementation Model. The Configuration Manager: Setting Up the SCM Environment. The Project Manager: Managing a Project. The Developer: Joining a Project and Doing Development. The Integrator: Integration, Build, and Release. The UCM Baseline+Change Model. 4. A Functional Overview of ClearCase Objects. The Repository: Versioned Object Base. Workspaces: Dynamic and Snapshot Views. Project Management: Projects, Streams, Activities. Versioned Objects: Elements, Branches, and Versions. Component Management: Components and Baselines. Process: Labels, Attributes, Hyperlinks, Triggers. Building: ClearMake, Derived Objects, Configuration Records. 5. Establishing the Initial SCM Environment. ClearCase Architecture Basics. ClearCase Hardware Resource Requirements. Defining the Implementation Model. Creating the VOBs. Baseline Promotion Levels. 6. Project Management in ClearCase. What Is a ClearCase Project? Creating a ClearCase Project. 7. Coordinating Multiple Project Teams and Other Scenarios. Organizing Large Multiproject Development Efforts. Coordinating Cooperating Projects: Independent Components. Coordinating Cooperating Projects: Shared Components. Coordinating Multiple Parallel Releases. Coordinating IS/IT Development Projects. Coordinating Documentation Projects or Small Teams. Using UCM without Activity-Based SCM. 8. Development Using the ClearCase UCM Model. A Developer's Perspective of UCM. Joining a Project. Making Changes. Delivering Changes to the Project. Rebasing Your Development Stream. Dealing with Conflicting Changes. 9. Integration, Build, and Release. Software Integration. Isolation and Integration with ClearCase. Building and Baselining with ClearCase UCM. Staging and Release. 10. Geographically Distributed Development. Distributed Development Challenges. How Does ClearCase Support Distributed Development? Multiple Teams: Producer/Consumer Scenario. Multiple Teams: Shared Source Scenario. Single Team: Distributed Members Scenario. Other Uses for ClearCase MultiSite. 11. Change Request Management and ClearQuest. What Is Change Request Management? What Are Change Requests? The Change Request Management Process. What Is ClearQuest? How Do I Use ClearQuest Data? How Does ClearQuest Support UCM? Glossary. Bibliography. Index. 0201604787T04062001
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.004 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.003 | 0.005 |
| Scholarly communication | 0.009 | 0.015 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.004 | 0.004 |
| Insufficient payload (model declined to judge) | 0.035 | 0.012 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".