|
== Validation phases ==
In the V-model, each stage of the verificationdesign phase has a corresponding stage in the validation phase.<ref>{{cite web |url=http://www.pharmpro.com/Articles/2008/03/GAMP-Standards-For-Validation-Of-Automated-Systems/ |title=GAMP Standards For Validation of Automated Systems |author1=DeSpautz, Joseph |author2=Kenneth S. Kovacs |author3=Gerhard Werling |publisher=Pharmaceutical Processing |date=11 March 2008 |access-date=28 February 2012 |archive-url=https://web.archive.org/web/20120508022817/http://www.pharmpro.com/Articles/2008/03/GAMP-Standards-For-Validation-Of-Automated-Systems/ |archive-date=8 May 2012 |url-status=dead |df=dmy-all }}</ref> The following are the typical phases of validation in the V-Model, though they may be known by other names.
=== Unit testing ===
=== System testing ===
System Tests Plans are developed during the System Design Phase. Unlike Unit and Integration Test Plans, System Test Plans are composed by the client's business team. System Test ensures that expectations from the application developed are met. The whole application is tested for its functionality, interdependency, and communication. System Testing verifies that functional and non-functional requirements have been met. Load and performance testing, stress testing, [[regression testing]], etc., are subsets of system testing.
=== User acceptance testing ===
User Acceptance Test (UAT) Plans are developed during the Requirements Analysis phase. Test Plans are composed by business users. UAT is performed in a user environment that resembles the production environment, using realistic data. UAT verifies that the delivered system meets the user's requirement and the system is ready for use in real -time.
== Criticism ==
The V-Model has been criticized by [[Agile software development|Agile]] advocates and others as an inadequate model of software development for numerous reasons.<ref>[httphttps://harmonicsswww.cobdtask.ukcom/projectblog/thev-deathmodel-ofin-thesoftware-v-modeldevelopment "TheV DeathModel ofIn theSoftware V-ModelDevelopment"], accessed JanuaryOctober 614, 20132024 (updated)</ref><ref>[https://web.archive.org/web/20190915230955/http://www.clarotesting.com/page11.htm "The Dangerous & Seductive V Model"], archived version from September 15, 2019</ref><ref>[http://www.exampler.com/testing-com/writings/new-models.pdf "New Models for Test Development"], accessed January 6, 2013</ref> Criticisms include:
# It is too simple to accurately reflect the software development process, and can lead managers into a false sense of security. The V-Model reflects a project management view of software development and fits the needs of project managers, accountants and lawyers rather than software developers or users.
== Current state ==
Supporters of the V-Model argue that it has evolved over time and supports flexibility and agility throughout the development process.<ref>[https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.640.3024&rep=rep1&type=pdf "Toward Agile Systems Engineering Processes"], accessed August 9, 2022</ref> They argue that in addition to being a highly disciplined approach, it promotes meticulous design, development, and documentation necessary to build stable software products. Lately, it is being adopted by the medical device industry.<ref>[{{cite book | chapter-url=https://link.springer.com/chapter/10.1007%2F978-3-642-30439-2_13?LI=true "| doi=10.1007/978-3-642-30439-2_13 | chapter=Barriers to Adopting Agile Practices Whenwhen Developing Medical Device Software"] | title=Software Process Improvement and Capability Determination | series=Communications in Computer and Information Science | date=2012 | last1=McHugh | first1=Martin | last2=McCaffery | first2=Fergal | last3=Casey | first3=Valentine | volume=290 | pages=141–147 | isbn=978-3-642-30438-5 }}</ref><ref>[http://eprints.dkit.ie/144/ "A Software Process Development, Assessment and Improvement Framework, for the Medical Device Industry "]</ref>
== See also ==
| 