Defining Programming Standards   
for Professional Programmers 
  

         

Home

Contents

1: Standards

2: Psychological Factors

3: General Principles

4: Commenting

5: Naming

6: Code Layout

7: File Layout

8: Language Usage

9: Data Usage

10: Programming Usage

11: Implementing Standards

A: Example Standard

B: References

C: Glossary

Syque

About

Share this page:

Google
C Style
syque.com
Web

 

 

Books and
more at:

USA:

In association with amazon.com

UK:

In Association with Amazon.co.uk

Canada:

In Association with amazon.ca

 

 

CHAPTER 11 : Implementing Standards

PART 5 : IMPLEMENTATION

CHAPTER 11 : Implementing Standards
11.1 Raising awareness of the need for standards
11.2 'Disadvantages' of coding standards
11.3 Getting the standards defined
11.4 What should the standards contain?
11.5 Getting the standards into use
11.6 Prove the value
11.7 Keeping the standards alive
11.8 Making sure the standards are used
11.9 Summary

<--Prev page | Next page -->

 

11.8  Making sure the standards are used

Sadly, unless given the appropriate encouragement, people tend either not to follow standards or to drift: first on small points, then on more important points.

Rather than check for conformance to standards separately, the best approach is to combine this with checking for defects in the coding. Reviews and inspections are widely regarded as an excellent defect detection and prevention method. These need only have an extra checklist for conformance to coding standards. Where you have different people reviewing different aspects of the code, then one of these is given a focus on coding standards.

 

<--Prev page | Next page -->

 

 

 

  © Syque 1995-2006

Massive Content -- Maximum Speed