Master Manual Testing: Free Course Part 2 - Learn Essential Techniques

3. Explain Spiral model.

• It is a combination of the waterfall model and the and iterative model. Spiral Model helps us to adopt software development elements of multiple process models for the software project based on unique risk patterns ensuring efficient development process.
• The development process in the Spiral model, starts with a small set of requirements and goes through each development phase for those sets of requirements. The software engineering team adds functionalities for the additional requirements increasing spirals until the application is ready for the production phase.

Advantages

• Additional functionality or changes can be done at a later stage
• Continuous or repetition development helps in risk management
• Development is fast and features are added systematically in Spiral development
• There is always a space for customer input and feedback

Disadvantages

• Risk of not meeting the schedule or budget within deadlines
• Spiral development works best only for large projects and also demands risk assessment expertise
• Spiral software development is not advisable for a small project, it might cost them a lot

4.Explain Prototype model.

        The prototyping model is a software development model in which a prototype is built, tested, and reworked until an acceptable prototype is achieved. It also creates a base to produce the final system or software. It works best in scenarios where the project's requirements are not known in detail. It is an iterative, trial-and-error method that takes place between the developer and the client.

Requirements gathering and analysis

• A prototyping model starts with requirement analysis. In this phase, the requirements of the software are defined in detail. During this process, the users of the system are interviewed to know what is their expectation from the system.

Quick design

• The second phase is a preliminary design or a quick design. In this phase, a simple design of the system is created. However, it is not a complete design. It gives a briefidea of the software to the user. The quick design helps in developing the prototype.

Build a Prototype

• In this stage, an actual prototype is designed on the basis of the information collected from quick design. It is a small working model of the required system.

Initial user evaluation

• In this stage, the proposed system is presented to the client for an initial evaluation.It helps to find out the strength and weaknesses of the working model comments and feedback are collected from the customer and updated to the developer.

Refining prototype

• If the user is not happy with the current prototype, you need to refine the prototype according to the user's feedback and suggestions.
• This phase will not end until all the requirements specified by the customer are met.Once the customer is satisfied with the developed prototype, a final system is developed based on the approved final prototype.

Implement Product and Maintain

• Once the final system is developed based on the final prototype, it is thoroughly tested and deployed to production. The system undergoes routine maintenance for minimizing downtime and preventing large-scale failures

Advantages

• Customers are actively involved in development. Therefore, errors can be detected in the initial stage of the development.
• Missing functionality can be identified, which helps to reduce the risk of failure as
• Prototyping is also considered a risk reduction activity.
• Helps team members to communicate effectively.
• Customer satisfaction is higher because the customer can feel the right product ata very early stage.

Disadvantages

• Prototyping is a slow and time taking process.
• The cost for developing a prototype would cost more and it is inefficient as the prototype is ultimately thrown away.
• Prototyping may encourage excessive change requests.
• Sometimes customers may not be willing to participate in the iteration cycle for longer time duration.
• There may be too many variations in software requirements when each time the prototype is evaluated by the customer.
• It is very difficult for software developers to accommodate all the changes demanded by the customer.
• The client may lose interest in the final product when he or she is not happy with the initial prototype.
• Developers who want to build prototypes quickly may end up with building substandard development solutions.

5.Explain V and V model (VERIFICATION AND VALIDATION MODEL)

• Verification : It involves a static analysis technique performed without executing code. It is the process of evaluation of the product= development phase to find whether specified requirements meet.
• Validation : It involves dynamic analysis technique testing done by executing code.Validation is the process to evaluate the software after the completion of the development phase to determine whether the software meets customer’s expectations and requirements.

Advantages

• Easy to Understand.
• Testing Methods like planning, and test design goes well before coding.
• Saves a lot of time. Hence the chance of success over the waterfall model.
• Works well for small projects where requirements are easily understood.

Disadvantages

• Very rigid and least flexible.
• Not good for a large project.
• Software is developed during the implementation stage, so no early prototypes of the software are produced.
• If any changes happen in the process, then the test documents along with the required documents has to be updated.

-: THANK YOU :-