ISO9000/ASA9100 spec writing advice

[bruce phipps]

My company in the UK is going for ISO9000 quality certification for our software
development department (8 developers). I think this is called ASA9100 in the USA.

I have been given the task of writing procedures and other ISO9000
docs, such as:

Project Plan
Functional Requirements Specification
Technical Requirements Specification


Initially, I'm looking for web resources and document templates which
show what sort of things I should put in each document.
Better still, are there any downloadable examples of QA docs for systems
which have passed ISO9000?

Also, I gather docs should be arranged in project folders on a
SourceSafe system or similar. Is this correct?

And what about docs about how to write the docs??!

Thanks
Bruce

 

[Oscar kind]

My company in the UK is going for ISO9000 quality certification for our software
development department (8 developers). I think this is called ASA9100 in the USA.

I have been given the task of writing procedures and other ISO9000
docs, such as:

Project Plan
Functional Requirements Specification
Technical Requirements Specification

These three examples are not part of ISO9000, but are referred to. There
is no fixed requirement however, other than what you set forth in the
ISO procedures as written for your company.

Initially, I'm looking for web resources and document templates which
show what sort of things I should put in each document.
Better still, are there any downloadable examples of QA docs for systems
which have passed ISO9000?

The ISO9000 and ISO9000-2000 (the newest version) manuals specify a generic
set of procedures. You just need to adapt them to your organization. In
many cases this simply means putting in your company's name, but some
procedures have to be rewritten (the part about calibration for example,
is important in the production industry, but not in software development).

Also, I gather docs should be arranged in project folders on a
SourceSafe system or similar. Is this correct?

Not in the sense that you're required to do so. But I would still advise
you to do so.

And what about docs about how to write the docs??!

That's also an ISO9000 procedure. There are separate procedures on writing
quality documentation and documents about writing software (in your
case). There is even a procedure about controlling your test environment
(assuming you adapt the procedure in calibration to fit that description).