SDLC Methodologies:
--------------------
1.WaterFall Model
2.V-Model Of Testing
3.Iterative Model
4.Agile Model
1.Waterfall Model:
-------------------------
-->Simple and easy to understand and use.
-->Each phase has specific deliverables and review processes.
-->Not suitable for projects where requirements are at a risk of changing.
-->Not a good model for complex and long projects.
-->Developers and testers will not work together.
2.V-Model:
--------------
The V-model is an SDLC model where execution of processes happens in a sequential
manner in a V-shape.
It is also known as Verification and Validation model.
3.Iterative Model:
-----------------------
We are going to iterate each functionality in to each part and design,develop and
test and deploy.
4.Agile Model:
-------------------
-->Agile methodology is a practice that promotes continuous iteration of
development and testing.
-->Here both development and testing activities are concurrent unlike the Waterfall
model.
Why we go for Agile?
---------------------------
-->More Control
-->Better Productivity
-->Better Quality
-->Higher Customer Satisfaction
-->Higher return on investment
Agile Manifesto(Principles):
------------------------------------
-->Individual and team interactions over processes and tools
-->Working software over comprehensive documentation
-->Customer collaboration over contract negotiation
-->Responding to change over following a plan
[Note: Framework - Scrum and Kanban]
Agile:
--------
-->Roles
-->Artifacts
-->Cermonies
Roles:
------
Product Owner --> Product Owner defines requirements of the product and decides
release date,
prioritize according to the market value and profitability.
Scrum Master --> Scrum Master manages the team, responsible for setting up the
team, scrum meeting invite.
Scrum Team --> Developers and Testers.
Artifacts:
----------
Userstory --> Short explanation of Requirements.
Acceptance Criteria --> Detailed explanation of Requirements.
Product Backlog --> Collection of Userstories captured for an agile project
manage by Product Owner.
Sprint Backlog --> No of userstories taken for a patricular sprint.
Sprint --> Set period of time to complete the user stories, decided by
product usually 2-3 weeks of time.
BurnUp and Burndown Chart --> Burn-up chart illustrates the amount of completed
work in a project and
the burn-down chart illustrates the amount of work remained to complete a project.