Software Engineering

Author

DoD-2167A

SKA

2005-10-10, 3:57 am

Hi all

Does anyone know if DoD 2167A is available in www or pdf format
anywhere. Appreciate any help.

Best regards
SKA

Wayne Woodruff

2005-10-10, 7:59 am

On 9 Oct 2005 23:36:49 -0700, "SKA" <stika@hotmail.com> wrote:

>Hi all
>
>Does anyone know if DoD 2167A is available in www or pdf format
>anywhere. Appreciate any help.
>
>Best regards
>SKA

Did you try google?

Wayne Woodruff
http://www.jtan.com/~wayne

SKA

2005-10-10, 7:59 am

Yes I did. Managed to find parts of it, descriptions of it and so on. I
would really like to have the complete standard.

Mike Bandor

2005-10-10, 9:56 pm

SKA wrote:
> Hi all
>
> Does anyone know if DoD 2167A is available in www or pdf format
> anywhere. Appreciate any help.
>
> Best regards
> SKA
>
Try this link:
http://www.tecnet.jcte.jcs.mil/htdo...t/ds2167a.html.
Just out of curiosity, why this one? It's been obsolete for years
(replaced by Mil-Std-498, which was subsequently replaced by IEEE/EIA
12207).

Mike

Phlip

2005-10-11, 3:57 am

Mike Bandor wrote:

[color=darkred]
> Try this link:
> http://www.tecnet.jcte.jcs.mil/htdo...t/ds2167a.html.
> Just out of curiosity, why this one? It's been obsolete for years
> (replaced by Mil-Std-498, which was subsequently replaced by IEEE/EIA
> 12207).

And if you take the A off, it's Waterfall, and directly correlated with huge
project failures...

--
Phlip
[url]http://www.greencheese.org/Z

Land[/url] <-- NOT a blog!!!

2005-10-12, 3:58 am

"Phlip" <phlipcpp@yahoo.com> wrote in message
news:oUF2f.1216$ny2.1169@newssvr19.news.prodigy.com...
>
> And if you take the A off, it's Waterfall, and directly correlated with huge
> project failures...
>
And also correlated with huge project successes. Lots of weapon systems
now in place and operational were developed under 2167 and 2167A.

Failures can be found among projects under nearly any method that has
been used, and probably any method that will be used in the future. I
am sure we will find examples of eXtreme programming failures, agile
modeling failures, and RUP failures if we look hard enough. And, in
the future, people will be complaining about the shortcomings of Test
Driven Design and other current fads in software practice. Some new
fad will come along and its proponents will be pooh-poohing the
sacred doctrines so dear to those devotees of our time who have
consecrated themselves to promoting their favorite software method.

At the same time, 2167A is now a bit old-fashioned and represents a
document-driven approach to development. While it has been
successful for a great many projects, most software development does
not require this heavyweight approach. Incremental methods, in many
cases, will serve much better. There may still be a few circumstances
where 2157A is appropriate but those circumstances are becoming more
the exception than the rule. Even so, a modified form of waterfall, used
with good judgement and under the guidance of a skilled project manager
can be, and often has been, successful in creating large-scale, well
architected software systems.

Richard Riehle

Andrew Gabb

2005-10-16, 7:56 am

SKA wrote:
> Does anyone know if DoD 2167A is available in www or pdf format
> anywhere. Appreciate any help.

I can dig this out if you still need it, or 498. Not sure about 1679
though ... <g>

From memory I think it's in txt and/or Word or WP. We're talking
1990 or so.

Andrew
--
Andrew Gabb
email: agabb@tpgi.com.au Adelaide, South Australia
phone: +61 8 8342-1021, fax: +61 8 8269-3280
-----

Sponsored Links