W-Model - Software Engineering Last Updated : 09 Jan, 2024 Comments Improve Suggest changes Like Article Like Report Paul Herzlich introduced the W-Model in 1993. W-model is the most recent software development model where we start real testing activity simultaneously software development process. Where software development process is a method in which a software or product is made through various stages of planning, development, and testing before the final software or product is delivered. testing is such a stage that is extremely crucial to ensure the delivery of an optimum quality product. V-model and W-model are two of the most important models that are used in software testing.W-Model covers those activities that are skipped by V-Model and also, it deals with problems that couldn’t be caught by V-Model.W-Model approach attempts to address and tackle the shortcomings W-Model approach attempts to address and tackle the shortcomings of V-Model.W-model can be done only once the development of the product is complete with no modifications required to be done in between. This type of testing is most suitable for short projects.With the help of W-Model, we ensure that the testing of the product starts from the very first day of the inception of the product, and each phase of the product development is verified and validated.W-ModelPhases of W-ModelEach phase is verified/validated. Dotted line shows that every phase in green is validated/tested through every phase in sky blue. Now, in the above figure, Point 1 refers to – Build Test Plan & Test Strategy. Point 2 refers to – Scenario Identification. Point 3 refers to –Test case preparation from Specification document and design documents. Point 4 refers to – Test case preparation from Specification document and design documents. Point 5 refers to – review of test cases and update as per the review comments. Point 6 refers to – Various testing methodologies such as Unit/integration testing, path testing, equivalence partition, boundary value, specification based testing, security testing, usability testing, performance testing. After this, there are regression test cycles and then User acceptance testing. Testing Techniques Used in W-Model:Regression TestingStatic Testing:Static Testing is further divided into two parts:(a) Review (b) Static Analysis (c) Dynamic Testing Advantages of W-Model:In W-Model there is no strict division between constructive tasks on the left-hand side and the more destructive tasks on the right-hand side. During the test phase, the developer is responsible for the removal of defects and the correction of the implementation. Emphasis the fact that testing is more than just construction, execution and evaluation of test cases. The importance of the tests and the ordering of the individual activities for testing are clear. Disadvantages Of W-Model:The real facts are simplified in this model. There is a need for a simple model if all people involved in a project are to accept it. For highly critical applications the test activities certainly have higher weighting or at least equal weighting with other activities. Comment More infoAdvertise with us Next Article W-Model - Software Engineering M mks075 Follow Improve Article Tags : Software Engineering Similar Reads SDLC V-Model - Software Engineering The SDLC V-Model is a Types of Software Development Life Cycle (SDLC), which is used in Software Development process. In V-Model is the extension of the Traditional Software Development Model.It is creating a Structure like the "V" which includes the different phases which we are discussing here in 10 min read Waterfall Model - Software Engineering The Waterfall Model is a Traditional Software Development Methodology. It was first introduced by Winston W. Royce in 1970. It is a linear and sequential approach to software development that consists of several phases. This classical waterfall model is simple and idealistic. It is important because 13 min read COCOMO Model-Software Engineering COCOMO-II is the revised version of the original Cocomo (Constructive Cost Model) and was developed at the University of Southern California. It is the model that allows one to estimate the cost, effort, and schedule when planning a new software development activity. Sub-Models of COCOMO ModelCOCOMO 2 min read COCOMO Model - Software Engineering The Constructive Cost Model (COCOMO) It was proposed by Barry Boehm in 1981 and is based on the study of 63 projects, which makes it one of the best-documented models. It is a Software Cost Estimation Model that helps predict the effort, cost, and schedule required for a software development project 15+ min read Domain Modeling - Software Engineering Domain modeling is an important step in software engineering. It means making a simple picture or description of the real world and things that the system will work with. This helps everyone understand and plan how the system should work before actually building . It is understood as abstract modeli 5 min read Like