Archive for the ‘ALM’ Category
ClearCase users, you may find the following details very useful:
IBM Rational ClearCase Support would like to welcome you to a ClearCase Open Mic conference call.
Date: Tuesday April 21st 2009
Time: 1pm-2pm Eastern Time (GMT-5)
Topic: UCM Stream Strategies – Component vs Release Architecture
Our GoMidjets ClearEnv (An innovative utility that creates UCM environments in a click) users can also find it very useful.
For additional details on the Rational Open Mic Program please see –> Link: Rational OpenMic Landing page
AgileSparks, a company approved by the International Scrum Alliance to grant certifications in this field, is arranging a new 2-days course to start on the next February.
The course covers the Scrum framework and includes real life situation simulations and exercises, in which Scrum principles are practiced and important insights are reached.
As a Scrum master, certificated by AgileSparks, I recommend this course for anyone wanting to review and improve his skills in this field.
I got the following email – you may find it interesting:
The Jazz Ensemble
Live at Carnegie Hall
3545 Harbor Boulevard
Costa Mesa, CA 92626-1437
Just send me a flying ticket and I’m coming.
Two weeks ago, my article about this issue was published in “CM Crossroads”, the leading portal of CM world.
Here is a brief – you can read the whole article in the portal.
In Turbulent economic times such as the recent days, it is reasonable to assume that while some things will be reduced or cut, (e.g. human resources and budgets), others (e.g. documentation) will be maintained or even increased. So, what can we do to create effective and accurate CM Plans?
When I worked for one of my customers, I accomplished a new CM/ALM project in which one of the big problems was to integrate Bea AquaLogic and IBM Rational ClearCase UCM.
Bea AquaLogic BPM (aka Bea) is a set of design, development, and runtime modules for building business process management solutions. Actually, it’s a GUI dashboard of the developers, beside of other back-end dashboards like Eclipse.
ClearCase and Bea are integrated together, but while I was evaluating its integration, I’ve encountered the following issues:
- The integration is of Bea with Base ClearCase but not ClearCase UCM.
- Bea generates dozens (in fact – hundreds) of files during the compilation (“re-catalogoue”).
- Bea generates a unique XML code which is not so familiar by ClearCase merge mechanism.
You can contact me for more information and solutions.
Posted April 28, 2008on:
Configuration managers and other users may know the following situation:
You manage all your project assets in a central repository. As the project is progressed and the end of a milestone is coming, and you want to work in parallel, you have the following indecision: Whether to use the same repository for the next milestone, or open a new repository?
In this post I’m going to write my idea about this situation regarding ClearCase UCM.
In ClearCase UCM you have 2 kinds of repository: the physical (“VOB”) and the abstract (“UCM project”). In this post I refer to the abstract one. (Well, you may say that the UCM project is considered to physical also since its inrormation is written into the PVOB, but I assume you agree that it’s more abstract than physical 🙂 )
Well, as you figure out from the post title, I support the first option, so here I write the reasons plus pros and cons.
- In case of using more than one component, it’s very recommended to use more than one project, since it enables us to define one component as Read/Write, and the other component as Read-Only (and vice-versa on the other project). This definition let us change The Read-only component to elder BaseLine if necessary.
- The GUI reason: The project hierarchy is much clearer when using the Project Explorer: there are separate rows and different icons for projects, integration streams and development streams. It may sound quite stupid, but it prevents accidents like mistaken delivery or rebase by the users!
- In ClearCase 2003.06 and above, there is a new option that lets us define the policies per-stream. Using it with sub-streams project may cause accidents. When using multi-projects, it lets us define separate policies for every project, and enforce its policies automatically for all project’s streams.
- If you integrate your ClearCase UCM to ClearQuest, you can filter your ClearQuest records by the “UCM Project” field. It is much easier than filtering by sub-streams.
- If you use the “Composite Baseline” feature, managing the composite baseline and its dependencies is easier and more flexible by using multi-project option, rather than the sub-streams options.
Actually, Whatever a decision you take, in the backstage, there is no big difference between multi-projects or sub-streams: both are separate and parallel streams.