Articles

Please enter an article title, author, or keyword
Testing's Role in the Software Configuration Management Process

In this article, the authors cover how testing can support any SCM environment and how testing can be part of the SCM process. They outline at patterns, roles, automation, and the never-ending search for simplicity.

The Definition of "Done" in Software Development

Getting all of the necessary people together to define what "done" means in a software development project will be difficult. Facilitating such a task will probably be a challenge, but there is nothing like working in an organization that works like a well-oiled machine, where everyone knows what is expected of him or her and just naturally does it.

Alan S. Koch
SDLC phases and activities Requirements Engineering: Our Best Practices

This article focuses on a methodology adopted during a requirements and functional specification phase of a project. The chosen model for requirements engineering was founded on a combination of six sigma techniques and a set of best practices adopted from within the organization.

Bonney Joseph
Agile Strategies for Geographically Distributed Quality Management

Geographically Distributed Development (GDD) is a common strategy in the software world today. Organizations are gaining experience in developing software globally and are discovering that the competitive demand for best-in-class, high quality applications requires greater agility in quality management. Unfortunately, IT budgets are not keeping up with the staff required for quality management and the response is to accelerate quality management by leveraging global teams. This article compares and contrasts agile GDD testing strategies for affecting quality management.

Scott W. Ambler's picture Scott W. Ambler
GNU Make path handling

Ask Mr. Make discusses how GNU Make handles paths.

John Graham-Cumming's picture John Graham-Cumming
Hidden Messages

A defect management system contains data such as how many defects have been raised, the priority and severity of individual defects, and even who is raising them. This information is regularly used by program and test management to guide decision making. In this article, Dan Minkin proves that an experienced test manager can gather useful information by looking at more than just the defect management system's data.

Dan Minkin
Top 10 Best Practices in Configuration Management

Joe Farah identifies the top ten "best" practices in configuration management and goes even further by listing ten more runner-up practices.

Joe Farah's picture Joe Farah
Constructing a Configuration Management Best Practice

The construct of a practice can be a good way to help an organization understand and execute on a process. A good practice construct will include the components that are needed to implement a process within an organization in a successful manner for adoption. To move forward on a practice, there are areas of focus to attain a "best" practice.

Mario  Moreira's picture Mario Moreira
Don't Let the Engine Run out of Fuel

Clarke Ching's friend Gary is one of those quietly clever people who hated school, so he left as soon as he could to go work in a factory. Nowadays, years after their schoolboy days in New Zealand, Clarke works in Europe as a management consultant and Gary owns and runs a small farm in New Zealand. Their lives couldn't be more different, yet Gary taught Clarke one of the most valuable lessons Clarke has learned during his career. In this article, Clarke describes that lesson and how it has changed his approach toward dealing with customers and key players in developing a product.

Clarke Ching's picture Clarke Ching
one way to categorize and organize questions Capturing Implied Requirements

Sometimes the user, project sponsor, and other key stakeholders haven't provided in the requirements documentation all the expectations of the software you're building. Instead, these expectations are only implied. In a perfect requirements-gathering process, there would be no such thing as an "implied requirement" because every requirement would be captured in the document. But no process is perfect, in theory or in practice. This article should help you look for and recognize the presence of implied requirements and learn how to capture them and convert them to documented requirements.

Robert Rose-Coutre's picture Robert Rose-Coutre

Pages

Upcoming Events

Sep 22
Oct 13
Apr 27