1

As per IEEE 12207, who has to perform Software integration testing (SOIPL): SW Testing team or SW Development team?

Andrew
  • 2,018
Mahendar
  • 19
  • could you quote how exactly the standard defines SOIPL? if definition of integration testing is similar to one in Wikipedia then the answer is testing team; if defined differently though, the answer may be opposite – gnat Nov 01 '12 at 11:19
  • Mil specs have pros and cons, but have probably helped us in many areas. We may have learned a few things about software lifecycle models and testing since the specification was created, although its prescriptions should not be ignored without the substitution of good alternatives. – DeveloperDon Nov 01 '12 at 14:06

1 Answers1

1

The TL;DR; answer is "It depends..."

ISO/IEEE 12207 doesn't specify teams as such, simply the processes to be followed. Depending on the nature of the activity (and other requirements, eg DO-178, IEC61508) which introduce requirements for independence at the higher levels, then a single person can be responsible for the whole life-cycle.

In simple terms, the Software Integration Process (of which integration testing is a part) builds all the (unit tested) modules into a single executable. The stages of the process will be as follows:

  • Build manager (or automated process, eg Jenkins) fetches files from Configuration Control tool, and builds the build
  • Integration tester(s) then test that build

In a small project, the integration tester(s) may well be the same software engineer(s) who wrote the code... if you have separate teams, I suggest that start of the Software Integration Process is probably a good handover point, because thereafter you are testing a full build, probably on target hardware. But that is a local decision to be made.

Andrew
  • 2,018