best practice
Home > Software Quality Glossary > Definition - best practice
EMAIL THIS
Glossary - powered by WhatIs.com
 BROWSE ALPHABETICALLY:    A B C D E F G H I J K L M N O P Q R S T U V W X Y Z #    

best practice
A best practice is a technique or methodology that, through experience and research, has proven to reliably lead to a desired result. A commitment to using the best practices in any field is a commitment to using all the knowledge and technology at one's disposal to ensure success. The term is used frequently in the fields of health care, government administration, the education system, project management, hardware and software product development, and elsewhere.

In software development, a best practice is a well-defined method that contributes to a successful step in product development. Throughout the software industry, several best practices are widely followed. Some of the more commonly used are: an iterative development process, requirement management, quality control, and change control.

An iterative (meaning repetitive) development process, which progresses in incremental stages, helps to maintain a focus on manageable tasks and ensures that earlier stages are successful before the later stages are attempted. Requirement management addresses the problem of creeping requirements, which is a situation in which the client requests additional changes to the product that are beyond the scope of what was originally planned. To guard against this common phenomenon, requirement management employs strategies such as documentation of requirements, sign-offs, and methodologies such as the use case. Quality control is a strategy that defines objective measures for assessing quality throughout the development process in terms of the product's functionality, reliability, and performance. Change control is a strategy that seeks to closely monitor changes throughout the iterative process to ensure that records are intact for changes that have been made and that unacceptable changes are not undertaken.

A best practice tends to spread throughout a field or industry after a success has been demonstrated. However, it is often noted that demonstrated best practices can be slow to spread, even within an organization. According to the American Productivity & Quality Center, the three main barriers to adoption of a best practice are a lack of knowledge about current best practices, a lack of motivation to make changes involved in their adoption, and a lack of knowledge and skills required to do so.

Read more about it:
>>  Rational.com provides a white paper, "Rational Unified Process: Best Practices for Software Development Teams".
>>  SearchVB.com provides best practice links for program designers and developers.

Last updated on: Feb 15, 2007

WHITE PAPERS  
Business Rule Management Systems and Financial Services: Equifax as a Case Study
ILOG, Inc. (BRMS)

Sales P3: Definition and Commentary by Thought Leaders about Sales Process, Production and Performance
Landslide Technologies, Inc.

How to Start a Windows Vista Pilot Deployment
Microsoft

Presentation Transcript: Creating a Competitive Edge: Extending the Sharepoint Platform to Meet Enterprise 2.0
Vorsite Corporation

Hot Aisle Vs. Cold Aisle Containment
APC

>> More White Papers
  WHAT'S NEW
 1. Optimizing Performance in the Enterprise
 2. Requirements gathering techniques
 3. Handbook of Agile Software Craftsmanship
 4. Software testing fundamentals


About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 2006 - 2008, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts