Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!sunybcs!boulder!ncar!asuvax!mcdphx!mcdchg!att!cbnews!military
From: military@cbnews.ATT.COM (William B. Thacker)
Newsgroups: sci.military
Subject: The 2167 development spec
Message-ID: <11332@cbnews.ATT.COM>
Date: 11 Nov 89 06:20:26 GMT
Organization: AT&T Bell Laboratories
Lines: 24
Approved: military@att.att.com



From: uunet!sagpd1!jharkins (Jim Harkins)
You've all been having fun talking about the interesting stuff like planes,
ships, guns, etc.  How about some of the real-life military stuff for a while.
Like, say, the 2167 software development spec.  Are there any books out
there that will help develop software under this spec?  Even better would
be a book that explains techniques for developing the 29.3 pounds of paper
that goes with each page of source code.  I'm reading the spec itself trying
to figure out what exactly they want, but I'm not sure my interpretation matches
what they are trying to say.  Can't ask for help here cause this is the
company's first project under 2167 so we're all in the same boat.

Those of you with experience with 2167, do you think it helps create better
software?  From what I see so far its purpose is more CYA as opposed to
software quality.

jim
jharkins@sagpd1

"This subparagraph shall be numbered 3.3.W.2.X.2 (beginning with 3.3.1.2.1.2).
When not provided in a separate DBDD, this subparagraph shall identify and
state the purpose of the data that originate in LLCSC X and are not used by
any other architectural elements of the CSCI."