Quality Specification

August 26, 2007 by Jim Brosseau · Comment
Filed under: Process 

This is the last of a 4-part series on determining reasonable quality attributes for your projects. In the first three parts, we identified that overall quality can be expressed in a wide range of areas, and it is better to start with this wide range rather than to start with a shorter list that was devised before your project was born. Read more

Quality Translation

August 19, 2007 by Jim Brosseau · Comment
Filed under: Process 

Thus far in this journey to determine reasonable quality requirements for our project, we have taken steps to determine which areas of quality are most important for us to focus on. Starting with a thorough landscape for quality, we are now at a point where we can reasonably identify our specific project needs. Read more

Quality Prioritization

August 12, 2007 by Jim Brosseau · Comment
Filed under: Process 

Recall that last week, we identified a broad range of areas to consider when we describe overall software quality. It is valuable to appreciate that correctness (or functionality) is just one of perhaps a dozen different attributes to look at for quality, even though in most projects this is the only perspective considered. Finally, we noted that it is important to start with a broad range of attributes (there are several similar ones to choose from) to avoid the possibility of missing an entire perspective of quality. Read more

Quality Taxonomies

August 5, 2007 by Jim Brosseau · Comment
Filed under: Process 

This is the first of a 4-part series on Software Quality Attributes, where we focus on the Taxonomy of Quality. Read more

  • Tag Cloud

  • What’s Happening

    Jan 28, 2010 - Thoroughly enjoyed an exploration of inter-cultural issues in the workplace with VanQ - 11 countries were represented, with fewer than 20 participants!
  • What People are Saying

    In our brief one day session with Clarrus, we identified the key areas to focus on, and drilled down to discuss the best approach to take in each area. Rather than a sanitary discussion of best practices, we arrived at a practical, specific set of items to implement – I think we made significant progress as a development group. — Daniel Miller, CEO, Miller Software