Verifying and validating software requirements and design specifications

The concept of The CMMi easy button is to be able to jump start SQA software professionals in establishing an effective Software process Improvement (SPI) framework that is based on CMMi theories and best practices.Product Integration (PI) is one of the core Engineering Process Areas within CMMi, this process is concerned with assembly of product components to build the finished software product.In a more traditional Waterfall process, with Specifications and Requirements defined at the start, Validation is often performed at the end of the testing cycle.You spend tons of time defining a product, build it, make sure your software was bug-free, and then do user acceptance testing, or submit it to a client / users, perhaps even a Beta release.This may happen because when a product or application is build as per the specification but these specifications are not up to the mark hence they fail to address the user requirements.Validation is basically done by the testers during the testing. Incidents can also be of type ‘Question’ where the functionality is not clear to the tester.

verifying and validating software requirements and design specifications-76verifying and validating software requirements and design specifications-60verifying and validating software requirements and design specifications-14verifying and validating software requirements and design specifications-24

Part of the problem is that the document General Principles of Software Validation; Final Guidance for Industry and FDA Staff (2002) does not do a good job of differentiating actual verification and validation activities. The recent article Building Quality into Medical Device Software provides a pretty good overview of the these regulatory requirements, but is a another case in point.The article talks about “software validation” at every step just like the FDA document. (my highlight): No, testing specific requirements is a verification activity! These definitions, Difference between Verification and Validation, are better as they highlight the sequencing of activities: Verification takes place before validation, and not vice versa.Another similar article on this subject is Software Validation: Turning Concepts into Business Benefits. Verification evaluates documents, plans, code, requirements, and specifications.While validating the product if some deviation is found in the actual result from the expected result then a bug is reported or an incident is raised. Hence, validation helps in unfolding the exact functionality of the features and helps the testers to understand the product in much better way. Also Read: What is Verification in Software Testing?Verification and validation techniques applied throughout the development process enable you to find errors before they can derail your project.