comp.lang.ada
 help / color / mirror / Atom feed
From: milo!grebyn!daily!margono@uunet.uu.net  (Johan Margono)
Subject: Re: Open comment to Ted Holden
Date: 20 Apr 92 17:08:01 GMT	[thread overview]
Message-ID: <1992Apr20.170801.28192@grebyn.com> (raw)

In article <1745@nic.cerf.net> jonesm@nic.cerf.net (Matthew Jones) writes:
>And for my 2 cents.
>
>[deleted stuff ...]
>
>Defense contractors take a lot of criticism for producing expensive 
>bug riddled products. Many people ask why doesn't mil equipment 
>work as well as commercial stuff. I think that people should consider
>that Microsoft for example had 50,000 people beta test Windows 3.1
>and the people are still having problems with it. Does
>the defense department have 50,000 people to test their equipment?
>For free? Does the Dod have a Dr. Dobbs Journal or many of the 
>equivalents to help them work over technical issues. 
>That is paid for by the user community?
>If a Word processor has a FATAL bug it in that probably means that
>it might destroy some data on your hard disk. A FATAL error in 
>a mil system may mean that many people will die. Are these two really
>comparable?
>
>To me that largest problem with Ada is that it doesn't have a large
>customer base. So the Ada Compiler/development systems are not checked
>out as well as its commerial counterparts. How many beta test sites
>are there for the average C compiler? How many for Ada? And keep in mind
>that Ada is a lot more complicated than C. Borland has sold hundreds
>of thousands of their C (and C++) compilers, how many has Meredian
>or Alsys sold for the PC?
>
>End of 2 cents.
>
>Matthew Jones
>jonesm@cerf.net

This argument reminds me of the following software development guidelines
which seem so pervasive in our industry:

  1. Order T-shirts for the development team
  2. Announce availability
  3. Write the code
  4. Write the manual
  5. Hire a Product Manager
  6. Spec the s/w (writing the specs after the code helps to
     ensure that your s/w meets the specs)
  7. Ship
  8. Test (the customers are a BIG help here)
  9. Identify bugs as potential enhancements
 10. Announce the upgrade program

-------------------------------------------------------------------------------
-
 Johan Margono
 Computer Sciences Corporation
 email: jmargono@starlab.csc.com
-------------------------------------------------------------------------------
-

             reply	other threads:[~1992-04-20 17:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-04-20 17:08 Johan Margono [this message]
  -- strict thread matches above, loose matches on Subject: below --
1992-04-21 18:29 Open comment to Ted Holden Mark Fausett
1992-04-21 16:35 Charles H. Sampson
1992-04-20 14:32 munck
1992-04-20  2:38 news
1992-04-18  6:35 sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!nstar!towers!grafted!dappe
1992-04-16 17:27 snorkelwacker.mit.edu!spool.mu.edu!olivea!news.bbn.com!kirin!mfausett
1992-04-15  4:33 cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!nstar!towers!grafted
1992-04-14 20:27 news.u.washington.edu!milton.u.washington.edu!mfeldman
1992-04-14 17:44 micro-heart-of-gold.mit.edu!wupost!uwm.edu!ogicse!henson!hearne
1992-04-14 15:59 cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!nic!jonesm
1992-04-13 21:34 Ha rry Koehnemann
1992-04-13 17:28 cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uwm.edu!news.bbn.com!kirin!m
1992-04-11  7:18 news
1992-04-10 17:08 Dan Vanderwerken
1992-04-09 20:52 Brian Hanafee
1992-04-09 17:40 cis.ohio-state.edu!zaphod.mps.ohio-state.edu!qt.cs.utexas.edu!cs.utexas.e
1992-04-09 16:58 david.c.willett
1992-04-09 15:53 cis.ohio-state.edu!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!uwm.edu!za
1992-04-09 15:24 Gregory Aharonian
1992-04-08 13:56 SAHARBAUGH
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox