CM Crossroads provides original content, articles and regular columns from industry thought leaders, analysts and software providers on a wide variety of configuration management and application lifecycle management topics. Below you will find links directly to our columns and articles or you may use the search box to scan for a particular topic or writer.
|
|
CM Basics
|
|
Sunday, 04 January 2009 |
 Real-World Reasons for Investing in CM
At CM Crossroads, most discussion is about software CM.
Many SCM practitioners are looking for help on-line, and SCM tool vendors keep
adding more and more features to their products, pushing the envelope of CM.
But no matter how far the envelope is pushed, software configuration management
will remain a subspecialty of "plain old" configuration management.
|
|
Last Updated ( Sunday, 04 January 2009 )
|
|
|
CM Basics
|
|
Sunday, 04 January 2009 |
 CruiseControl is a popular
open source tool for implementing Continuous Integration (CI) of Java
applications. The idea behind CI is simple. Build, regression test, and deploy
your software application to a test environment every time a code change is
committed to version control. If the code change causes the build to break, the
regression test to fail, or a problem with the deployment, identify and correct
the problem promptly.
CruiseControl is ideally
suited for CI. It is a reliable tool that provides real value to Java development
teams of any size. While CruiseControl is easy to install, it takes some effort
to configure. Fortunately, this challenge can be overcome by understanding the
structure and content of the CruiseControl configuration file. After reading
the discussion below, you should be able to configure CruiseControl to
implement a CI build.
|
|
Last Updated ( Sunday, 04 January 2009 )
|
|
|
CM Basics
|
|
Sunday, 04 January 2009 |
 Many companies are required to utilize Standards and Frameworks as part of their software development practices. What does this mean to you and what do CM practitioners need to know about them?
|
|
Last Updated ( Sunday, 04 January 2009 )
|
|
|
CM Journal
|
|
Sunday, 14 December 2008 |
 As a piece of Christmas cheer we bring you a traditional olde English carol. It is believed that this particular carol was sung to programmers by configuration managers to earn additional money during the Christmas season. The lyrics (including mention of Mil-STD-973 and CMM among other themes) are reputed to date back to the 15th century although the author is unknown. We have been lucky enough to track down a recording of this traditional carol - click the start button...
|
|
Last Updated ( Thursday, 18 December 2008 )
|
|
|
CM Journal
|
|
Sunday, 14 December 2008 |
 CM Planning is all about communicating the rules of the road for how your team should successfully complete their Configuration Management related tasks. This includes build engineering, release (packaging) management, change control, and, of course, deployment. Sadly, many people don't bother to spend the time to do effective CM Plans and they usually suffer from miscommunication and bad releases as a direct result. It is also true that writing volumes of documentation is a total waste of time and will actually encourage your team to ignore CM processes. The key is to require just enough process to get the job done effectively. Your CM plans should reflect the Configuration Management related tasks that MUST be done in order for your team to be successful. The CM Plan should also help your team be more Agile. Read on if you would like to understand how to write CM Plans that can help your team be more successful without any unnecessary (extra) steps.
|
|
Last Updated ( Tuesday, 16 December 2008 )
|
|
|
CM Journal
|
|
Sunday, 14 December 2008 |
 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?
In this article I'd like to show some essential points for effective CM planning, which can offer a solution of reducing costs, based on the IEEE 828 standards. Basically, the goal is to reduce quantity but not quality.
|
|
Last Updated ( Wednesday, 17 December 2008 )
|
|
|
CM Journal
|
|
Sunday, 14 December 2008 |
 I've seen countless sets of requirements and RFIs come my way for
acquiring new CM/ALM tools. However, it is a very rare occasion when I
see a company actually publish (and send out) the project CM Plan to
potential tool vendors. In my most recent encounter of this approach
the pitch was: How would you change this plan based on your CM/ALM
solution for us? This project has it right - not just a set of
requirements, but an actual CM Plan. And not so much "what does your
tool do" as "what will our CM Plan look like with your solution".
|
|
Last Updated ( Tuesday, 16 December 2008 )
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>
|
| Results 1 - 11 of 699 |
