Talk:V-model (software development): Difference between revisions

Content deleted Content added
new comments go at the bottom.
Line 80:
 
In the longer term the former article should be broken out into its three constituent parts. Otherwise explanations can get hopelessly confused when one is dealing with things that look superficially similar but are really fundamentally different with quite distinct uses. [[User:Freddie Threepwood|Freddie Threepwood]] ([[User talk:Freddie Threepwood|talk]]) 13:29, 12 January 2013 (UTC)
 
--[[User:Lisaneo|Lisaneo]] ([[User talk:Lisaneo|talk]]) 04:38, 20 October 2014 (UTC)
Hi, my concern is regarding the 4 validation phases of the V model:
1. Unit testing
2. Integration testing
3. System testing
4. User acceptance testing
 
First, I find the definition of "Integration" testing to be somewhat confusing if used in isolation without qualifying whether if it is referring to function, component, or system level. If "Integration" testing here refers to Function or Component Integration testing, I guess the sequence of test will still make sense. However, for System Integration Testing, SIT, I think this is performed after System Test, in cases where there are multiple systems integrating together to form the whole solution.
 
== Verification (or Validation) on the descending left side of the V makes no sense at all ==