2136 Gallows Road, Suite F, Dunn Loring, VA 22027 Phone: 1-703-208-9120 Fax: 1-703-852-7939 Business Analyst Training 1 Module 5.2 Rational ClearCase.

Slides:



Advertisements
Similar presentations
1 GOES-R AWG Products Processing Framework Configuration Management Yunhui Zhao.
Advertisements

Software Configuration Management Donna Albino LIS489, December 3, 2014.
Revision Control Systems Amin Tootoonchian Kian Mirjalali.
1 Software Configuration Management METU Computer Engineering CEng 492 Spring'2004.
Sy config. SY Non-Student machines –SYTS Team system –SY01 Sql Server Student machines –SY02 –SY03 –SY04 –SY05 –SY06 –SY07 –SY08.
CVS Selim Çıracı Ahmet Kara Metin Tekkalmaz. CVS – Open Source Version Control System Outline What are Version Control Systems? And why do we need them?
CS 501 : An Introduction to SCM & GForge An Introduction to SCM & GForge Lin Guo
Hands-On Microsoft Windows Server 2003 Administration Chapter 5 Administering File Resources.
Low level CASE: Source Code Management. Source Code Management  Also known as Configuration Management  Source Code Managers are tools that: –Archive.
Microsoft Visual Source Safe 6.01 Microsoft Visual Source Safe (MVSS) Presented By: Rachel Espinoza.
1 Copyright © 2014 Tata Consultancy Services Limited Source Code Management using Rational Team Concert IBM Rational, Alliance & Technology Unit 2 July.
Chapter 12 Reading assignment n From “Running Linux”, on reserve at PSU Main library (2-hour checkout) Chapter 1 (pages 1 through 41)Chapter 1 (pages 1.
1 of 5 This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2006 Microsoft Corporation.
Configuration Management
Source Code Management Or Configuration Management: How I learned to Stop Worrying and Hate My Co-workers Less.
Source Control Repositories for Enabling Team Working Svetlin Nakov Telerik Corporation
Software Configuration Management CSC-532 Chandra Shekar Kandi Chandra Shekar Kandi.
Working with SharePoint Document Libraries. What are document libraries? Document libraries are collections of files that you can share with team members.
By Steven Campbell and Erik Boone.  Sharing projects by putting them into a central repository.  Checking out copies of projects from the repository.
Version Control with git. Version Control Version control is a system that records changes to a file or set of files over time so that you can recall.
Software Configuration Management (SCM)
Version Control with Subversion. What is Version Control Good For? Maintaining project/file history - so you don’t have to worry about it Managing collaboration.
Software Engineering Modern Approaches
Subversion, an Open Source Version Control System An Introduction.
1 Lecture 19 Configuration Management Software Engineering.
Configuration Management (managing change). Starter Questions... Which is more important?  stability  progress Why is change potentially dangerous?
02 | Install and Configure Team Foundation Server Anthony Borton | ALM Consultant, Enhance ALM Steven Borg | Co-founder & Strategist, Northwest Cadence.
Prepared by: Steve Teo Contributors: Tong Huu Khiem.
Chapter 13 Users, Groups Profiles and Policies. Learning Objectives Understand Windows XP Professional user accounts Understand the different types of.
Version control Using Git Version control, using Git1.
…using Git/Tortoise Git
Git workflow and basic commands By: Anuj Sharma. Why git? Git is a distributed revision control system with an emphasis on speed, data integrity, and.
Information Systems and Network Engineering Laboratory II DR. KEN COSH WEEK 1.
Object-Oriented Analysis & Design Subversion. Contents  Configuration management  The repository  Versioning  Tags  Branches  Subversion 2.
ClearCase Basics XML presentation.
Alliance Maintenance Integration Process Claude SAAM / Yves GRILL / Denis SCHITTER 29/Feb/2008.
(Sub)Version Control. 2 Keep large teams working on the same code Back up your work so you don't lose it all Compare changes to previous versions Revert.
Subversion (SVN) A Revision Control System Successor to CVS Carlos Armas Hervey Allen.
SENG 403 Tutorial 1 1SENG 403 – Winter Agenda Version Control Basics Subversion Basic actions in Subversion Some examples 2SENG 403 – Winter 2012.
DireXions – Your Tool Box just got Bigger PxPlus Version Control System Using TortoiseSVN Presented by: Jane Raymond.
CSE 219 Computer Science III CVS
05 | Administer Version Control Steven Borg | Co-founder & Strategist, Northwest Cadence Anthony Borton | ALM Consultant, Enhance ALM.
Microsoft Visual SourceSafe “(VSS) does not eliminate the need for discipline and coordination. It only makes discipline and coordination easier to live.
ClearCase Concepts and Terminology
CPSC 871 John D. McGregor Change management Module 2 Session 3.
1 MSTE Visual SourceSafe For more information, see:
Intro to Git presented by Brian K. Vagnini Hosted by.
L.T.E :: Learning Through Experimenting Using google-svn for MtM Docs Development Denis Thibault Version 3.2 Mar 12 th, 2009.
Software Configuration Management (SCM) Source: Pressman, R., Software Engineering: A Practitioner ’ s Approach. Boston: McGraw Hill, Inc., 2005; Ghezzi,
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Hyperion Artifact Life Cycle Management Agenda  Overview  Demo  Tips & Tricks  Takeaways  Queries.
WinCVS Training è Basic Concepts è Download & Setup è Importing a new module into CVS Repository è Getting new module from CVS è Getting Latest version.
22 Copyright © 2008, Oracle. All rights reserved. Multi-User Development.
Excercises: CM with ClearCase Sirkka-Liisa Juoperi Exercises: Configuration Management with ClearCase.
TEAM FOUNDATION VERSION CONTROL AN OVERVIEW AND WALKTHROUGH By: Michael Mallar.
Information Systems and Network Engineering Laboratory I DR. KEN COSH WEEK 1.
IPEmotion License Management PM (V1.2).
Source Control Repositories for Enabling Team Working Doncho Minkov Telerik Corporation
1 Ivan Marsic Rutgers University LECTURE 2: Software Configuration Management.
Xxx Presentation, No 1 Copyright © TAC AB Engineering Classic Networks1.
Information Systems and Network Engineering Laboratory II
Software Configuration Management CSC-532
LECTURE 2: Software Configuration Management
RTC – Source Control Management
Concurrent Version Control
Configuration Management (managing change)
LECTURE 3: Software Configuration Management
Microsoft Visual Source Safe How & Why
Software Configuration Management
Presentation transcript:

2136 Gallows Road, Suite F, Dunn Loring, VA Phone: Fax: Business Analyst Training 1 Module 5.2 Rational ClearCase

BA Training Module 5.2 | Rational ClearCase v3.0 2 Rational ClearCase  Repository management for project-wide artifacts Release documents Review documents Technical design documents Deployment Code  Provides Accountability Version control Controlled accesss  Just a sophisticated Explorer!

BA Training Module 5.2 | Rational ClearCase v3.0 3 Rational ClearCase  What is ClearCase?  ClearCase is a comprehensive  software version control and  configuration management system,  designed for development teams  working in a local network.

BA Training Module 5.2 | Rational ClearCase v3.0 4 Rational ClearCase-View

BA Training Module 5.2 | Rational ClearCase v3.0 5 Rational ClearCase

BA Training Module 5.2 | Rational ClearCase v3.0 6 Rational ClearCase  ClearCase Overview  Provides versioning of all types of files & directories  Records and reports history  Guarantees accurate reproduction of every release  Provides traceability & reproducibility  Provides powerful branch-and-merge tools  Assures integrity of all software elements

BA Training Module 5.2 | Rational ClearCase v3.0 7 History Of Folder

BA Training Module 5.2 | Rational ClearCase v3.0 8 When and By Whom?

BA Training Module 5.2 | Rational ClearCase v3.0 9 Clearcase-Check in

BA Training Module 5.2 | Rational ClearCase v Rational ClearCase Checked-out

BA Training Module 5.2 | Rational ClearCase v Rational ClearCase  ClearCase Version Control Features  Easy checkout-edit-checkin model –  Adding folders or files –Checkin  Reserved for modification-Checkout  Intelligent merge utility automatically merges non-conflicting changes  Graphical compare and merge tools  Two modes of work with Dynamic and Snapshot Views

BA Training Module 5.2 | Rational ClearCase v Check Out

BA Training Module 5.2 | Rational ClearCase v Version Tree

BA Training Module 5.2 | Rational ClearCase v First Version

BA Training Module 5.2 | Rational ClearCase v N-th Version

BA Training Module 5.2 | Rational ClearCase v To See All Versions Click here to see all Versions Compare- Specific Version Compare- Previous Version Birds Eye-Shows the Version you see

BA Training Module 5.2 | Rational ClearCase v Rational ClearCase  What is a VOB? Versioned Object Base the whole database consists of several VOBs  A read-only repository of ClearCase elements  A network-wide, file system resource which stores version-controlled data  A user accessible repository that resides:  on a Windows NT system, or  on a UNIX system

BA Training Module 5.2 | Rational ClearCase v Rational ClearCase  Basic Actions for an Element  Checkout - a new editable version is created - only one person can edit the file at the same time  Checkin - the version that was created by checkout command is saved to the VOB and is then visible to the other views - the element changes to write-protected mode  Undocheckout - undo operation for checkout  These Options can be selected when right clicked on the application.  Rational ClearCase  Workspace Management - Views  Dynamic Views  Snapshot Views

BA Training Module 5.2 | Rational ClearCase v Other Options

BA Training Module 5.2 | Rational ClearCase v Rational ClearCase  WHAT IS A VIEW?  Workspace for an individual developer or closely coordinated group.  Selects versions of Versioned Object Base (VOB) directories and files.  Allows developers to work without interfering with others.  File checkout by particular user is reserved fro him to modify.No other user can access that folder for modification unless its modified and checked in.

BA Training Module 5.2 | Rational ClearCase v Rational ClearCase  Version Selection by Views  A view selects versions of elements  What is seen is the result of an ordered  Set of rules called a configuration specification  Selected versions appear in a standard  Directory tree with recognizable file names. Eg:R0234/Business/System Checkout d1046/Development/System Design

BA Training Module 5.2 | Rational ClearCase v Rational ClearCase  What is a Configuration Specification? Each view has a config spec that defines a set of rules for selecting versions of file and directory elements  A default config spec is automatically set whenever you create a new view The default config spec selects files or directories that are:  checked out, or  the latest version on the main branch of the version tree  The Default Config Spec:  element * CHECKEDOUT  element * \main\LATEST Update View gives latest config spec.

BA Training Module 5.2 | Rational ClearCase v Update View

BA Training Module 5.2 | Rational ClearCase v Rational ClearCase  When To Use Snapshot Views  You want to work with source files that are under ClearCase control while disconnected from network  You prefer to use a view that is updated only at your request  You want to access a view from a machine that is not a ClearCase host

BA Training Module 5.2 | Rational ClearCase v Rational ClearCase  Dynamic Views  Transparent access to elements - access to virtually any version of any element. -Always up-to-date  Minimal copying  Provides build auditing – Whenever new build done by CM group.

BA Training Module 5.2 | Rational ClearCase v Rational ClearCase  Snapshot View vs. Dynamic View Similar  Use config specs rules to select element versions  Follow the checkout, edit, checkin paradigm  Allow reserved or unreserved checkouts

BA Training Module 5.2 | Rational ClearCase v Rational ClearCase  As development progress, a snapshot view becomes out of date and must be explicitly updated  A checkout of an element may use the version loaded into the view, not necessarily the latest version in the VOB  To check in such an element, you may have to perform a merge  If the element version is not the latest version, you are asked to confirm which version to checkout