 This is the second in a series of blog posts exploring characteristics of development projects to consider when choosing a Software Configuration Management system.
Variant Management It is common for a software system to be used in multiple products. For example, an app might have a free version for personal use and a more powerful version for corporate deployment. Thus, there is a free variant and a corporate variant. They share most of the software but have variant-specific code for each. The SCM system must provide a way to share common code while isolating variant-specific code. This must account for past and future releases of the needed variants as well as merging defect fixes forward to the appropriate contexts.
0 Comments
 ClearCase has proven its mettle as advanced software configuration management solution for many years now. With Rational ClearCase - Cadence Virtuoso Integration, ClearCase brings its enterprise configuration management capabilities to analog or mixed signal designers. This integration enables designers to take advantage of core capabilities of ClearCase, without leaving their familiar design environment. This integration allows custom chip designers to complete ClearCase actions from within Cadence Virtuoso.
 Tired of entering your password? I know I am. If I didn’t have to type in my password 20 times every day, I would have finished fixing all the defects in ClearQuest. Ok, that’s hyperbole, but it really is a pain, isn’t it? Wouldn’t it be great if you could log in once to access all your applications? The good old people writing security standards have been nice enough to give us a solution. It is called “single sign on”. With more and more DevOps products integrating with each other it is becoming even more important to have a centralized identity management solution where you can sign in once, and access multiple applications.
 WHAT'S THE PROBLEM?
ClearCase administrators often need to set up access controls on VOB elements to meet their companies' information security policy. Operating system groups are a popular way to manage protections: users are assigned to groups, and those groups are used for element access checks. This works nicely when groups are used for VOB element access control lists (ACLs), introduced in ClearCase 8.0.1, or for UNIX-style mode bit checks based on the VOB element's group ownership. However, it only works as long as a single user only needs 16 or fewer groups to access all authorized elements.  This is the first in a series of blog posts exploring characteristics of development projects to consider when choosing a Software Configuration Management system.
A Software Configuration Management (SCM) system is an essential part of almost any effective software development project. It can provide solutions to different challenges faced by the many roles in a development team. These roles include software engineers/developers, project leaders, release engineers, process engineers, engineering managers, and even engineering executives. |
Archives
October 2018
CategoriesHelpful Links
Open RFEs Knowledge Center IBM Marketplace
|
RSS Feed