🚀 go-pugleaf

----------------------------Original message----------------------------
                      Summary of SW Stds

Please send any responses to me.  Do not reply to the
sender.

Hello,

In April I sent out a request looking for software development standards to
possibly replace our company software management standard.  At long last
here is a summary of the responses with the original message.  Thanks
again to all who responded, quickly too.  The delay was mine.  Apologies
in advance to those on two or three email lists.

Karen Owens
kowens@isd.jpl.nasa.gov

========================
Original Message:

Subject: Request for SW Devel Stds

Our company wants to know about other software development
standards either international, national or company
standards.

DOD-STD-2167A, soon to be replaced by MIL-STD-498 is
primarily an acquisition standard.

ISO 9000 and NASA SMAP standards are aimed at assuring
quality, but not necessarily on the software process
itself.

The Software Engineering Institute (SEI) is working hard
to ensure that the Capability Maturity Model (CMM) and the
in-work SPICE standard activities will be consistent with
one another.  The CMM addresses many software development
aspects, but is not a process standard.

Our current standard states activities and products and
gives review criteria for the products.  It also gives
content outlines for the products, but the focus is on the
process without specifying a method.  It states what you
must do, but not how to do it.

If a company had such a standard, how willing would they
be to sell it to another company and provide updates?

Please send any responses to me.  Do not reply to the
sender.

Thank you,
Karen Owens
kowens@acm.org

=================================
Summary

Have you looked at
o       ADARTS from Software Productivity Consortium

o       Software Development Capability Evaluation (SDCE) AF pamphlet 800-
61
o       Sam Redwine's article surveying many software standards

o       Rockwell's Process Assets Library (PAL) containing a set of
procedures, standards, methods, tools, metrics, and role specifications.
Each is controlled as a product.

o       DO - 178B Software Considerations in Airborne Systems and
Equipment Certifications (FAA)

o       IEEE-1074  Software Engineering Standard for Developing Software
Life Cycle Processes

o       General Electric published its Software Engineering Handbook.  It's
available from a commercial publisher,

o       FDA published software guidelines for its Good Manufacturing
Practices (GMP) program

o       Contact SEI's Software Process Definition project which has some
examples in this area (Jim Over's e-mail address is jwo@sei.cmu.edu)

o       ISO 9000-3

o       Look at these companies:  IBM Federal Systems Company, now Loral
FSC in Bethesda, Maryland and Hughes Aircraft Company, Fullerton,
California

o       Perhaps the most useful article is by Samuel Redwine, surveying all
information standards.
        Sarah H. Nash and Samuel T. Redwine, "A Map of the World of
Software-Related Standards, Guidelines, and Recommended
Practices," Proceedings of the Computer Standards Conference, San
Francisco, CA, 13-15 May 1986.

There are lots of corporate standards info; perhaps the best
work is by TI.

There is or will be
o       An in-work standard ISO 12207, which might replace MIL-STD-498

o       SPICE

Other comments:

o       What company are you?  [JPL, part of NASA]

o       We would like a copy of the responses.

o       What makes you think that your company could use some other
company's stds?

o       We have standards, but they are proprietary.
        We would not want to update them for someone else.
        If we did sell them, it would not be cheap --
        they took several million dollars to produce.

o       We are interested in exploring this consulting opportunity
        with a non-competitor.
        We would be reluctant to modify our process for a client.

I'm willing to send a long version of the responses to those who request it.

However, I did not think that the whole mailing list (especially those who
are not software folks) would want it.  If you want the summary send me
your email address with the request for the long responses and I will
forward the long version to you.  There may be a delay because of
vacation.

Thanks again,
kowens@isd.jpl.nasa.gov

Please send any responses to me.  Do not reply to the
sender.