Articles

Please enter an article title, author, or keyword
Partnership For Success

Abstract
No one wants to deliver a poor-quality product. But our projects often seem like a struggle between the Quality Assurance personnel and those who have other jobs. Do some people really not care about quality? If that is not the case, then why does it so often seem that way?

Alan S. Koch
Avoiding Continuous Integration Build Breakage Patterns

Continuous integration is an automatic re-building of project code base that is triggered by new changes to ensure that new changes integrate well into the existing code base. Continuous integration gains popularity among software organizations for its ability to provide quick feedback on quality of new changes. This feedback is used to deliver timely fixes if the changes don’t integrate well and break the project code base.

TechWell Contributor's picture TechWell Contributor
Anti-Patterns of a Private Workspace

There are key advantages of having a private workspace for development. With this in mind, it is critical that the private workspace is used in the context of the project and the forces influencing the project and programmer are understood. Understanding the concepts of anti-patterns and how they can disrupt the adoption of good practice will lead to establishing practices that fit within a group.

Mario  Moreira's picture Mario Moreira
Workspace Management Front and Center

Workspace management has been an increasingly important component of CM over the years. Gone are the days when the only workspace operations were checkout, checkin, build/make, and the occasional file merge operation. Today, the workspace is at the center of a developer's interaction with the CM tool. Ideally, it is not just a file holder, but rather embodies an entire development context. More and more that context is accessed through a richer CM tool interface, from an IDE environment, or even through the file system. In the modern CM tool, the workspace must actively provide guidance to the developer rather than lying dormant waiting for a developer to manage it.

Joe Farah's picture Joe Farah
To Branch or Not To Branch (and Merge/Test)

I don't like merging. When I merge I've got to retest. This is especially difficult if the merging occurs a few days/weeks after the original change. Come to think of it, I don't really like branching, but that depends. Do I have to merge whenever I branch? Do I use branching for a specific discipline or is it a catch-all operation which gives me all sorts of capabilities in return for a spaghetti-like spider web of branches and merges? What about all the labeling that goes with it? There must be a better way, a way to reduce branching, and merging, while increasing automation and reducing complexity. What is it?

Joe Farah's picture Joe Farah
An Agile Perspective on Branching and Merging

This article focuses on branching and merging. We present some background for branching and merging, and consider some of the implications for agile development in particular. We also hope to reduce some of the suspicion that many agile developers have of branching. The article assumes some overall branching knowledge and yet revisits some particular details that often seem to confuse people. This is a fertile area which we will continue to expand on in future articles.

Planning Projects for Enterprise CM

Effectively planning and setting realistic expectations before you start your CM project can mean the difference between actual and perceived success and failure. Here are some great tips to help you sell the success of your project and avoid costly pitfalls.

TechWell Contributor's picture TechWell Contributor
Security As A Distributed Platforms SCM Change Control Mechanism

Ineffective operating system level security can jeopardize your entire SCM operations and the hundreds of millions of dollars of software assets you are trying to control. It is important to match SCM to your company’s security model and use OS security to exercise control over application runtime environments, which CCM tools typically do not control. Here are some important guidelines for using operating system security to provide robust SCM for Windows and *NIX platforms.

TechWell Contributor's picture TechWell Contributor
Automating CM or Application Lifecycle Management

Automation is at the heart of excellence in the field of configuration management. Unless a wider definition of CM is used, that of application lifecycle management, automation will fall far short of the mark. As we enter this still young millennium and look back at the progress of CM, it's clear that the industry has, for the most part, been creating tools to fight fires and to avoid them. Spot solutions originally dealing with version control, change management, problem/issue/defect tracking, etc., have given way to more integration. Yet as a whole, the industry has fallen far short of the mark required for CM, or ALM, automation.

Joe Farah's picture Joe Farah
ABCs of Requirements Engineering

Requirements engineering plays a fundamental role in the establishment of a release.  Requirements engineering can be described as having five key areas of focus.  This includes the ability to elicit requirements, document requirements, approve and baseline requirements, manage the requirements after approval, and trace from the requirements thru test.

 

Mario  Moreira's picture Mario Moreira

Pages

Upcoming Events

Jun 02
Sep 22
Oct 13