V-model (software development): Difference between revisions

Revision as of 13:34, 31 May 2007

Revision as of 09:12, 1 June 2007

Line 45:

==Coding==

''Refer [[software programming|Coding]]''

== Validation Phases ==

Line 52:

''Main article [[Unit Testing]]''

In the V-model of software development, unit testing implies the first stage of [[dynamic testing]] process. According to software development expert [[Barry Boehm]], a fault discovered and corrected in the unit testing phase is more than a hundred times cheaper than if it is done after delivery to the customer.

It involves analysis of the written code with the intention of eliminating errors. It also verifies that the codes are efficient and adheres to the adopted [[Programming style|coding standards]]. Testing is usually [[White box testing|white box]]. It is done using the Unit test design prepared during the module design phase. This may be carried out by software testers of software developers or both.

===Integration Testing===

''Main article [[Integration testing]]''

In integration testing the separate modules will be tested together expose faults in the [[Interface (computer science)|interfaces]] and in the interaction between integrated components. Testing is usually [[Black box testing| black box]] as the code is not directly checked for errors. It is done using the integration test design prepared during the architecture design phase. Integration testing is generally conducted by software testers.

===System Testing===

''Main article [[System testing]]''

System testing will compare the system specifications against the actual system. The system test design derived from the system design documents and is used in this phase. Sometimes system testing is [[Test automation|automated]] using testing tools.

===User Acceptance Testing===

''Main article [[Acceptance testing]]''

Acceptance Testing checks the system against the requirements of the user. It uses [[Black box testing|black box testing]] using real data, real people and real documents to ensure ease of use and functionality of systems. Users who understand the business functions run the tests as given in the acceptance [[Test plan

|test plans]], including [[Installation|installation]] and [[Online help]]. Hardcopies of user documentation is also be reviewed for usability and accuracy. The testers formally document the results of each test, and provide error reports, correction requests to the developers.

==Benefits==

The V-model deploys a well-structured method in which each phase can be implemented by the detailed documentation of the previous phase. Testing activities like test designing start at the beginning of the project well before coding and therefore saves a huge amount of the project time.

==References==

* Roger S. Pressman:''Software Engineering: A Practitioner's Approach'', The McGraw-Hill Companies, ISBN: 007301933X

* Mark Hoffman & Ted Beaumont: ''Application Development: Managing the Project Life Cycle'', Mc Press, ISBN-10: 1883884454

* Boris Beizer: ''Software Testing Techniques.'' Second Edition, International Thomson Computer Press, 1990, ISBN 1-85032-880-3

==External Links==

*[http://www.bucanac.com/documents/The_V-Model.pdf, A paper by Christian Bucanac]

*[http://www.iacis.org/iis/2004_iis/PDFfiles/Boggs.pdf,The SDLC and SixSigma]

*[http://www.elucidata.com/refs/sdlc.pdf, SDLC for small and medium DB applications]