TMG-L Archives
Archiver > TMG > 2002-04 > 1018402105
From: "Douglas and Elena Husemann" <>
Subject: [TMG] Lifecycle of a software Package.
Date: Tue, 9 Apr 2002 20:29:00 -0500
References: <7c.25f3ebfe.29e3e34e@aol.com> <002601c1dfd8$34d52b40$02efd7c3@pladderballe> <3CB3A59F.2E2CC67A@jump.net>
A very simplified view:)
1)Define the project.
define the feature set, review the feature set.
review priorities. etc.
2) Write the project,
3) test the project
from test go to 2, until test is sufficient for 4.
4)release the project.
5)the ultimate test, also known as the gamma test.
take reports,
6) goto step one.
2 other things. There is never a completely bug free program
Until it has gone through gamma test a significant number of times
without there being new features added. (unless the platform is a known
platform, (IE, one set of hardware, one set of software that is known and
known not to change)
The trick is to get to stage 4 with stage 5 having very few reports. And
Bob
has strived to do that Better than any other company that I know.
with these goals in mind. Data Integrity, Data integrity, and data
integrity
and to provide the best platform for a event based family research with
sources.
For those concerned. The last I checked, I have about 20 books of genealogy
information
to still enter. I can use the interface in 4.x, even though it may not look
like a modern day
program. It is usable. (yes even in XP). Of course I also have to find a
new Job which has
pulled me away from alot of things, something about having a house and food
drives that need.
So do the best thing, enter the data you have. scour the data you have now
for errors.
Enjoy life. And worry about v5 when it comes out.
Douglas
This thread:
| [TMG] Lifecycle of a software Package. by "Douglas and Elena Husemann" <> |