Title
by Paul Hazelden


Introduction

Written 11/11/93.

Whose fault is it when the software crashes? (Computer Weekly, 30 September 1993) goes halfway to addressing the problem. Even if the same person is doing the job of both analyst and programmer, proper documentation must be created and maintained. There is still a potential conflict as the question of what the specification should cover is not addressed. When I started programming, all the specifications written by the analysts looked like this: 3.1. Increment register 7 by 1. 3.2. If register 7 = 66 Then go to paragraph 3.3 Else print... Read next record. Go to paragraph 3.1.

 

This page last updated 21 October 1999.
Copyright © 1999 Paul Hazelden.

Comments?  Feedback?  Let me know what you think.
Home | Personal | Ministry | Writings | Links | Index
You are welcome to create a link to this page or to print it for your personal use, but if you would like to use some or all of it in any other way, please contact me first.