Re: DOD-STD-1679A(Navy)

[sws@mercury.nswses.navy.mil (Scott . Smart CDR)]

In article <3jncg0$7vu@butch.lmsc.lockheed.com>,
Garlington KE <l107353@cliffy.lfwc.lockheed.com> wrote:
>Doc Elliott (helliott@losat.redstone.army.mil) wrote:
>: ?!?!?!?!  The Navy actually will accept a CSCI that has KNOWN problems?
>: And yet they still get more of the DoD budget than we do.....
>
>To be fair, I think all U.S. military services have a waiver and deviation
>process that permits accepting CSCIs with known problems.
>
>--------------------------------------------------------------------
>Ken Garlington                  GarlingtonKE@lfwc.lockheed.com
>F-22 Computer Resources         Lockheed Fort Worth Co.
>
>If LFWC or the F-22 program has any opinions, they aren't telling me.

Ummm...  Show me the software with no known problems, and I'll show
you the software that hasn't been tested.

1679A defines problems in terms of severity.  Pri 1 -- Pri 5.

The old NAVELEX TADSTANDS provided test and acceptance criteria
for Navy software in Mission Critical Computer Resources.  The
TADSTANDS were cancelled by SECNAVINST 5200.32A  which considers
software as part of the system.  The acceptance criteria was no
Pri 1s or 2s.

But the real acceptance criteria is whether the independent T&E
agent finds the system operationally effective and suitable.

scott smart


--
|Naval Surface Warface Center|  sws@suned1.nswses.navy.mil
| Port Hueneme Division      |  Any statements / opinions are mine and not
| Cruise Weapons Dept        |  DoD or DoN