Task 4
Published: 2023-12-23 18:23:06

**Manual Testing**
     Testing is a critical part of development process that involves evaluating software application

**Different types of models of SDLC process**

1. Waterfall Model
2. Prototyping Model
3. Incremental or Iterative Model
4. Spiral Model
5. V Model
6. Agile Model

**Waterfall Model**
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/p82jpt5tmjjni0311o8k.png)

- It is the oldest SDLC Model.
- It will be like how water fall flows from up side to down side.
- It will proceed Phase by Phase i.e all the requirements should be ready to proceed to next phases.
- Testing is not involved from the beginning phase, so that the defect fixing becomes time consuming and costly.
- Any changes in the requirements, design or issues to be fixed, we have move back to respective phases and again come down.
- It takes more time to see the working product. So that it is suitable for smaller projects

**For example**: A client called RAMU and he wants to built one car washing software. He goes to the IT services company and ask to create one car washing software and give his requirements.

Now the Business Analyst will create a document i.e requirement team then Design team will work i.e front end development team then the implementation team i.e developers will work then Testing team will test the Ramu's car washing software if the testing is success without any error then go for Deployment then if any Maintenance is required.

Here client will connect only in the requirement phare and in the deployment phase.

**Prototyping Model**
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/dlevum8uvz3nrjn9mss8.png)

- Instead of giving the final product, we first show a dummy prototype to the customers to take their feedback.
- We develop the full and final product after the customer feedback, so that the right product is developed.
- Unlike waterfall model, the risk is low her as the customer knows the product is going to developed in advance.

**Incremental or Iterative movel**
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3qqqylmsdblgymfwti4c.png)
- In this model product is designed, implemented and tested incrementally.
- It is created in different iteration, in each iteration new requirements are added untill the product is completed developed.
- Requirements are not freezed and new requirements can be added at any point of time
- Again testing team is not involved in the beginning phases.
-  Unlike waterfall model we can see some working product in less time.

**For example**: In between the car washing software development Ramu want to add some other requirments.

**Spiral Model**
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/pinxkmsxzfil7q23c69v.png)

- It is the combination of waterfall and iterative model.
- Instead of taking all requirements at one, the one iteration will be conducted with basic requirements and its starts with concept creation.
- Then the next version of product can be achieved in next spiral and so on.
- Spiral model is generally followed by Product based complanies for delivering the product.
**For example**: Ms office create a software in 1995 then create a another version in 1997 like that created new versions in 2000,2003,2013....

**V-Model**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2t0if5scx85okwaftm8r.png)


- It is also known as Verification & Validation Model.
- Testing is incorporated with every phase of life cycle
- Verification phase(requirement analysis, system design, architecture design, module design)
- Validation phase(unit testing, integration testing, acceptance testing)
- It is time saving and every phase is testable
- Risk analysis is not done

**Agile Model**
- Agile means Quick
- In these days, everything is changing very dynamically in the market.
- To accommodate such dynamic changes in the requirements, Agile model is came into the picture.
- No importance to Documentation( very less documentation required)
- More importance to communication(more meetings will be conducted)
- Requirements will be small stories and added as backlogs
- Prioritize the stories and adde to one sprint of duration 2 weeks to 4 weeks.
- In this sprint, all product owners, BA Developers, testers and other will communicate and complete their tasks on a story by story basis in quicker way.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/02z56u60sv57w4w1av5d.png)

## Terminologies of Agile methodology

**Product owner**: In most companies it is the customer/client
**Epic**: It is a collection of user stories i.e complete requiremnts is called Epic.
**User story**: A feature or a module in a software
**Product backlog**: It is a list of stories which is prepared by product owner.
**_example:_** : Backlog 1: Ramu's car wasing software login page creating, after login options of vehicles buttons creating.
Backlog 2: In the vehicles option what type of wash text is available.
**Sprint**: Period of time to complete a user story that is to code and test a user story.

**_for example_**: project has 100 user stories, then QA and DEV with commited to give 5 to 8 user stories in one sprint.

**Sprint Planning meeting**: It is done within the team to discuss which stories to be delivered in a sprint to complete a userstory within the duration. Team decide what stories to be developed, tested and released in a particular sprint.

**Sprint backlog**: commited stories by DEV and QA in specific sprint

**Scrum Master**:Enables close cooperation among the team 

**Scrum meeting/standup meeting **: To conduct daily call about the sprint like what I did yesterday?, what issues I faced?
What will I do today?

**Burnt Down Chart**: Based on the scrum meeting , the scrum master will create a chart to chek the completed and pending tasks.

**Sprint Retrospective Meeting**: It is conducted after every sprint gets over. They discuss what went well, what went wrong in this sprint and how to overcome this issues in next sprint. The entire team along with scrum master and product owner will participate.