Bookmark and Share
Blog powered by Typepad
Member since 03/2007

Become a Fan

« Requirements Traceability | Main | Why is Tool Qualification an Additional Consideration? »

September 14, 2010

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Ammiraju

Agree:
Major objective of SW-SW Integration testing is to uncover the integration issues. If HW-SW integration and Module tests are 100% each, no need of SW-SW Integration at all.

But to do DC/CC Analysis we should need SW-SW Integration Tests. If we can justify that DC/CC approach with an alternative method then the complete SW-SW Integration can be skipped.

How to be an alpha male

The good thing about your information is that it is explicit enough for students to grasp. Thanks for your efforts in spreading academic knowledge.

Eric Bresie

If the requirements are clearly defined, implemented, and unit tested on both SW components, then integration testing is less necessary, but I have yet to find a situation where this has always been done successfully so I believe ditching SW-SW integration testing is not a good idea.

The comments to this entry are closed.

My Photo

Life sometimes turns on a dime. Especially when you are actively looking out for a change. I now work at HCL Technologies. And all I am looking for is to make a difference. By the way, the blog contents remain my own. It does not reflect the official position of HCL.

Your email address:


Powered by FeedBlitz