IJSER Home >> Journal >> IJSER
International Journal of Scientific and Engineering Research
ISSN Online 2229-5518
ISSN Print: 2229-5518 2    
Website: http://www.ijser.org
scirp IJSER >> Volume 3,Issue 2,February 2012
Improvement in the V-Model
Full Text(PDF, )  PP.366-373  
Ravi Shanker Yadav
Acceptance, accuracy, compiling, debugging, model checking, performance, program validation, reliability, security, testing
The V-model represents a software development process (also applicable to hardware development) which may be considered an extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical V shape. The V-Model demonstrates the relationship between each phase of the development life cycle and its associated phase of testing. The horizontal and vertical axes represents time or project completeness (left-to-right) and level of abstraction (coarsest-grain abstraction uppermost), respectively. This model depends on verification and validation phase Software Testing is the most important phase of the Software Development Life Cycle. On most software projects testing activities consume at least 30 percent of the project effort. On safety critical applications, software testing can consume between 50 to 80percent of project effort. Software testing is essential to ensure software quality. Schedule is always running tight during the software system development, thereafter reducing efforts of performing software testing management. In such a situation, improving software quality becomes an impossible mission It is our belief that software industry needs new approaches to promote software testing management. The article discussed the model that already existed, further excavates the parallelism between test stages and maintenance test stages and tries to propose a improved V model. This model makes the software testing pass through the each stage of software development cycle
Marshall Anthony, Student Software Architect, Fairleigh Dickinson University

Semyon Axelrod and Mike Regan, GMAC/RFC

Dewayne E. Perry and Alexander L. Wolf."Foundations for the Study of Software Architecture'.ACM SIGSOFT Software Engineering Notes, 17:4, October 1992:

[1] Bass, Len; Paul Clements, Rick Kazman (2003). Software Architecture In Practice, Second Edition. Boston: AddisonWesley. pp. 21–24. ISBN 0-321-15495-9.

[2] [Myers79] Myers, Glenford J., The art of software testing, Publication info: New York: Wiley, c1979. ISBN: 0471043281 Physical description: xi, 177 p. .

[3] [Hetzel88] Hetzel, William C., The Complete Guide to Software Testing, 2nd ed. Publication info: Wellesley, Mass. : QED Information Sciences, 1988. ISBN: 0894352423.Physical description: ix, 280 p..

[4] Sommerville, Ian, Software Engineering, 6th ed., Addison Wesley, 2000

[5] IEEE Standard for Software Verification and Validation Plans (Reaff.1992). IEEE Std 1012-1986.

[6] IEEE Standard for Software Unit Testing. IEEE Std 1008- 1987.

[7] IEEE Standard Glossary of Software Engineering Terminology. IEEE Std 610.12-1990.

[8] IEEE Standard for Software Test Documentation. IEEE Std 829-1998.

[9] IEEE. 1993. IEEE Standard for Software Maintenance. IEEE Std 1219-1993. Institute of Electrical and Electronics Engineers, inc., New York, NY.

[10] Gopalswamy Ramesh; Ramesh Bhattiprolu (2006). Software maintenance : effective practices for geographically distributed environments. New Delhi: Tata McGraw-Hill. ISBN 9780070483453.

[11] Rook, Paul, E. Rook, ―Controlling software projects‖, IEEE Software Engineering Journal, 1(1), 1986, pp. 7-16.

[12] [Han93] Hannus, Jouko, Prosessijohtaminen. Gummerus Kirjapaino, Jyväskylä, 1993. http://members.tripod.com/bazman/index.html

^a bc dClarus Concept of Operations. Publication No. FHWA-JPO- 05-072, Federal Highway Administration (FHWA), 2005

^ "Systems Engineering for Intelligent Transportation Systems". US Dept. of Transportation. p. 10. Retrieved 2007-06-09.

^a bc de f g h Forsberg, K., Mooz, H., Cotterman, H. Visualizing Project Management, 3rd edition, John Wiley and Sons, New York, NY, 2005. Pages 108-116, 242-248, 341-360.

^a bc de 3.3 to International Council On Systems Engineering (INCOSE), Systems Engineering Handbook Version 3.1, August 2007, pages 3.8^ Forsberg, K., Mooz, H. (1998). System Engineering for Faster, Cheaper, Better. Center of Systems Management. Archived fromthe original on 2003-0420.^"The SE VEE". SEOR, George Mason University. Retrieved 2007-05-26.^a b cd eForsberg, K. and Mooz, H., "The Relationship of SystemsEngineering to the Project Cycle," National Council On Systems Engineering (NCOSE), October 1991

Garlan and Perry, guest editorial to the IEEE Transactions on Software Engineering, April 1995

Dewayne E. Perry and Alexander L. Wolf. "Foundations for the Study of Software Architecture'.ACM SIGSOFT Software Engineering Notes, 17:4, October 1992:

Bass, Clements, and Kazman. Software Architecture in Practice, Addison-Wesley 1997:

Bass, Clements, and Kazman. Software Architecture in Practice2nd ed, Addison-Wesley 2003:

Bass, Clements, and Kazman. Software Architecture in Practice, Addison-Wesley 1997:

Wikipedia and Encyclopedia

Untitled Page