I have received comments from the supervisor reviewing my thesis. He asked two questions I cannot answer right now:

  1. If ISO 12207 says under "Integration verification" that it "checks that components are correctly and completely integrated into a system", how this can be verified without testing, if all testing is validation? How without testing can I know that system is integrated correctly and fully?
  2. If unit testing is validation, how does it match the ISO definiton of validation "that requirements for intended use were fulfilled" if its so low level?

1 Answer 1

  1. There's a reason ISO standards have the reputation of being impractical beaurocratic nonsense. Theoretically, it's possible to check that the artifacts that represent the components are all present, complete and configured the way they should be, by inspecting directories, file contents, perhaps comparing checksums, all without actually running the system. In practice, that's a lot of work and does very little to prove that the system actually works. The closest thing that is done in practice is to check that the automated build script has not produced an error. Perhaps the solution to the puzzle is that ISO 12207 was written to cover integration processes that are not automated (in which case you better have a reason why it cannot be automated, otherwise automate that damn build already instead of wasting time on ISO standards).
  2. Requirements can be very low level, e.g. business rules.
  • I agree in general. In an application with dependency injection or plug-in architecture, tests like this become less trivial and more useful.
    – neontapir
    Commented Nov 13, 2012 at 20:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.