SOFTWARE SAFETY AND QUALITY
I finally got some time to edit this page. Next task is to add more to the
library and a table of contents. I hope to have that next week. Enjoy.
TABLE OF CONTENTS
Basic software Engineering Library
Software Engineering Links
Testing Links
Computer Language Links
Software Engineering Documentation
BASIC SOFTWARE ENGINEERING LIBRARY
These are the references I use on an almost daily basis. I've chosen to list
them title first to make the subject matter more obvious
IEEE STANDARDS - SOFTWARE ENGINEERING 1999 Edition
Vol. One - Customer and Terminology Standards
Vol. Two - Process Standards
Vol. Three - Product Standards
Vol. Four - Resource and Technique Standards
ISO-9000.
ISO 9000 is a collection of standards by ISO and published by ANSI
in the United States. Taken together, they specify a system for documenting
an organizations quality control system. They do not specify a particular
system. The standards most applicable to software development are
ISO-9000-1, ISO-9000-3, and ISO 9001. If you simply document your process
according to ISO-9000, you will
probably have a high SEI level 2 or level 3 rating. If starting a software
QC system from scratch, I recommend first documenting your existing process
per ISO-9000. Then start collecting metrics per SEI recommendations.
ISO-9000-1 Quality Management and Quality Assurance Standards - Part 1:
Guidelines for Selection and Use.
ISO-9000-3 Quality Management and Quality Assurance Standards -
Guidelines for the Application of ANSI/ISO/ASQC Q9001 to the Development,
Supply, and Maintenance of Software.
ISO-9001 - Quality Systems - Model for Quality Assurance in Design,
Development, Production, Installation, and Servicing.
ISO 9000-3 A Tool for Software Product and Process Improvement, Kehoe,
Raymond and Alka Jarvis, Springer, New York, 1995 ISBN 0-387-94568-7
A guide to applying ISO 9000-3.
A Discipline for Software Engineering, Watts S. Humphrey, Addison-Wesley,
Reading, MA, 1995, ISBN 0-201-54610-8
The guide for the Personal Software Process. It is a lot of work, but
worthwhile on an individual level.
The Capability Maturity Model : Guidelines for Improving the Software
Process, Carnegie Mellon University Software Engineering Institute,
Addison-Wesley, Reading, MA, 1997, ISBN 0-201-54664-7
Basic reference on the CMM.
Handbook of Software Quality Assurance, G. Gordon Schulmeyer, and McManus,
James I., Prentice Hall, Upper Saddle River, NJ, 1999, ISBN 0-13-010470-1
Covers just about every thing you need to know for SQA.
Software Engineering, A Practitioner's Approach, Roger Pressman, McGraw-Hill,
New York, ISBN 0-07-050814-3.
The ISBN is for the third edition. I think there is a fifth edition out
now. This is a standard in any edition.
Software Engineering Guides, C. Mazza, et al., ISBN 0-12-449281-1
This is a guide to European Standards which are similar to, but not the
same as, the IEEE standards.
Software Inspection, Tom Gilb, and Graham, Dorothy. Addison-Wesley, Reading,
MA, 1993, ISBN 0-201-63181-4
In this case "Inspection" does not refer to final product testing. It
means a type of in-process review and analysis to prevent defects. It
also covers process analysis and improvement.
BACK TO TABLE OF CONTENTS
SOME USEFUL SOFTWARE ENGINEERING LINKS:
BACK TO TABLE OF CONTENTS
SOME USEFUL TESTING LINKS:
BACK TO TABLE OF CONTENTS
LINKS TO COMPUTER LANGUAGES:
BACK TO TABLE OF CONTENTS
The above link is to outline documentation for software development process. This outline
is not the only possible breakdown for ISO-9000. You should evaluate it in
light of your existing process. Your process is fully defined when every
"shall" in ISO-9001 has been documented, and every "should" in ISO9000-3 has
been considered.
This is very much a work in progress. My priorities are to complete the cross
reference matrix first, then the plan outlines, and then outlines for each
standard as I can. Comments and suggestions are welcomed. If they are used
they will be acknowledged. Others that I consider important alternatives may
be posted here. But nothing submitted may be considered proprietary.
I have started the sequence with the Business Plan. After much trying, I came
to the conclusion that it isn't possible to do a proper software
development process without starting with the very highest level documents in
the company.
Many of the links are broken right now. I will be moving document outlines over as
fast as I can get them converted to net format.
BACK TO TOP
BACK TO TABLE OF CONTENTS
Back to Charles Lyttle home page