Greg Clark has an excellent suggestion on documenting the testing
procedure. I believe this paramount to the success of this project.
Each area should be documented and the procedure should be followed for
every code change. The documentation should be written by the guys doing
the testing, not by Dave. If everyone agrees the procedure is valid,
then it should be followed until it makes sense to change the procedure
and everyone agrees it should be changed.
The documentation can be published on the datom web site. I will be
happy to be the point man on it. Most people have Word or some other
program that I can easily import in to the www.
Anyone else with software engineering experience that can help out?
73
---------- Forwarded message ----------
To: <na-user@contesting.com>
Date: Mon, 10 Nov 97 09:31:20
From: Greg Clark <g.w.clark@cummins.com>
To: "Bill Fisher, W4AN" <w4an@contesting.com>
Subject: Re: [na-user] Suggestion Box
On Sun, 09 Nov 1997 20:45:05 -0500, Bill Fisher, W4AN wrote:
>Etc... I'm sure with enough volunteers we could really make this software
>that much better. You cant expect Dave to beta test this software. WE
>have to do it. I'm all ears.
As one who works in a software development area, I agree to what you are
saying. One thing that we need to do is that if we have a piece of code to
test, the testing criteria needs to be documented...and followed.
Other than that, I think that this could be done and done well.
Sign me up.
Greg
------- End of Forwarded Message
--
Submissions: na-user@contesting.com
Administrative requests: na-user-REQUEST@contesting.com
WWW: http://www.contesting.com/datom/
Questions: owner-na-user@contesting.com
|