DOD-STD-2167A in machine-readable format?

DOD-STD-2167A in machine-readable format?

[Mike Bates]

Does anyone know of an anonymous ftp site that has a copy
of DOD-STD-2167A?  I'd like to be able to search through
for key words and phrases to get a better sense of how the 
various documents fit together.  I'd also like to be able 
to extract paragraphs for inclusion in other documents
without retyping.  I've tried ajpo.sei.cmu.edu
without luck, and I can't get through to SIMTEL20.

If ftp isn't possible, are there any government agencies or
private companies that might be able to sell me a copy on
DOS floppies?  Any leads would be greatly appreciated.

Mike Bates
mbates@tusun2.mcs.utulsa.edu

Re: DOD-STD-2167A in machine-readable format?

[Mike Bates]

In article <5650@uafhp.uark.edu>, bbs00576@uafcseg.uucp (Mike Bates) writes:
> 
> Does anyone know of an anonymous ftp site that has a copy
> of DOD-STD-2167A?  I'd like to be able to search through
> for key words and phrases to get a better sense of how the 
> various documents fit together.  I'd also like to be able 
> to extract paragraphs for inclusion in other documents
> without retyping....
> 

I still have no leads on the whereabouts of machine-readable 2167A.
I have gotten a few replies from other frustrated government contractors
who would like to find 2167A and other MIL-STDs on the network.

Here's a request/suggestion for the folks at the Software Engineering
Institute: Since your mandate is to transfer software engineering knowledge 
to industry and academia, why not take it upon yourselves to put DOD-STD-2167A
and any other standards pertaining to software development on your ftp
site?  I suspect the SEI would know where to go to find the standards in
machine-readable format, or they could always type them in themselves.

One other suggestion: Some ftp site (perhaps SEI) should help relieve
traffic on SIMTEL20 by carrying the Ada Software Repository, in the
same way that wuarchive carries a mirror of SIMTEL20's MSDOS collection.
How about it?  These are small, practical things SEI could do to help
out a lot of people who are involved with software development for the
government.

Mike Bates
mbates@tusun2.mcs.utulsa.edu