What do I need to show to an auditor?

In a nutshell, an auditor wants to assess if you said what you did and if you did what you said.

Well, it might be a bit more complex in certain situations, but it mostly boils down to this for the majority of times. Of course, each audit situation requires analysis and preparation, and far from us the intent of taking this subject lightly.

So, since Integrator is a requirement driven testing framework, we suggest you put the audit section of your certification right into your project, highlighting each audit requirement as if it was like any other requirement of your project (because it is exactly the case, after all!). You can use tags to label these requirements with something like "Certification", "AuditReq" or the like.

From that point, you have a clear checklist of things to perform to get certified which is impossible to miss and you have a great section to print or show to an auditor. Moreover, you can record your intent for each of these audit requirements.

On top of that, by using Integrator for the project, you will have collected:

• A definition of the project (using the description fields: what does it apply to, how long is it expected to take, who works on this, what is the desired outcome, who are the end customers).
• A list of all the reference documents you have used (the specifications with their provenance and versions used).
• A list of all the requirements you anotated directly in the spec with the reference text.
• A list of all the reference text that you explicitely will not test (ie: table of content, annex).
• A list of all the test cases you developed to prove all the requirements.
• A list of any derogation you might have put in place.
• A complete set of test results, with the configurations used (serial numbers, versions of everything).
• A list of test equipment used for the project with their pedigree.

We are not aware of any certification entity that would not consider these as important items to collect!