Content deleted Content added
Line 29:
[[User:Achilles852|Achilles852]] ([[User talk:Achilles852|talk]]) 02:09, 5 February 2009 (UTC)
While I agree with the two views above. I was just wondering if I'm misinterpreting it in thinking that there should be a line from "Architectural Design" Phase in the Image leading into "Integration Testing" - which would mean that Integration tests are designed during "Architectural Design"? because that is exactly what "Architectural Design" states i.e. "The integration testing design is carried out in this phase."
== Verification (or Validation) on the descending left side of the V makes no sense at all ==
As mentioned above, having Verification or Validation on the V's "left side" doesn't make any sense at all and the heading structure of the article is thus wrong. Verification (and Validation) are tasks performed on the "right side" only. You **verify** that the software and system works and you **validate** it against the (user) requirements. In the real world, "validation" may be ongoing on the left side too insofar as you may validate the requirement list against what the user says during meetings, but the left side is really just the design and top-down decomposition phase.
For example, the Galileo Software Standard (Galileo Industries document "GAL-SPE-GLI-SYST-A/0092" issue 7) has the following definitions:
- VALIDATION: Confirmation, by examination and provision of objective evidence, that the particular requirements for a specific intended use are fulfilled, i.e. to ensure that specification requirements of the product are met.
- VERIFICATION: Confirmation, by examination and provision of objective evidence, that specified requirements have been fulfilled, i.e. check to ensure that the requirements process for a dedicated phase is properly applied.
And "Validation" is done during "Requirement Baseline Validation" and "Technical Specification Validation", at which point the Software System must actually exist so that there is something to validate!
- RB-VALIDATION: Confirmation, through the validation process, that the Requirements Baseline (RB) functions and performances are correctly and completely implemented in the SOFTWARE PRODUCT and its components.
- TS-VALIDATION: Confirmation, through the validation process, that the Technical Specification (TS) functions and performances are correctly and completely implemented in the SOFTWARE PRODUCT and its components.
The software lifecycle phases being listed as in order:
- SW Planning Phase
- SW Specification Phase
- SW Design Phase
- SW Implementation Phase
- SW Integration and TS-Validation Phase
- SW RB-Validation Phase
- SW Acceptance Phase
- SW Maintenance Phase
[[Special:Contributions/2001:7E8:C047:1B01:223:54FF:FE15:1831|2001:7E8:C047:1B01:223:54FF:FE15:1831]] ([[User talk:2001:7E8:C047:1B01:223:54FF:FE15:1831|talk]]) 23:39, 24 February 2013 (UTC)
== Criticisms of the system ==
| |||