SDLC - Software development lifecycle models
Waterfall Model -
The waterfall Model is a linear sequential flow.
In which progress is seen as flowing steadily downwards (like a waterfall) through the phases of software implementation.
This means that any phase in the development process begins only if the previous phase is complete.
The waterfall approach does not define the process to go back to the previous phase to handle changes in requirement.
Used for Projects which not focus on changing the requirements.
e.g.
Requirement, Design, Execution, Testing, Release.
V-Shaped Model -
It is an extension of the waterfall model.
Instead of moving down in a linear way, the process steps are bent upwards after the implementation and coding phase, to form the typical V shape.
early test planning in the V-shaped model.
e.g.
Planning -> Requirements -> Architecture -> Detailed Design -turnup to v-> unit testing -> integration test -> system & acceptance test -> mintenance
Prototyping Model -
the initial phase is contineous analysis & suggestion improvement and then after that furhter steps will follow in lenear.
It used to visualize some component of the software to limit the gap of misunderstanding the customer requirements by the development team.
final prototype is developed, the requirement is considered to be frozen.
Spiral Model (SDM) -
Manages risks and develops the system into phases.
Early involvement of developers.
It is combining elements of both design and prototyping-in-stages.
combines the features of the prototyping model and the waterfall model.
effort to combine advantages of top-down and bottom-up concepts.
This model uses many of the same phases as the waterfall model, in essentially the same order, separated by planning, risk assessment, and the building of prototypes and simulations.
Iterative and Incremental Model -
It is developed to overcome the weaknesses of the waterfall model.
It is combination of mini waterfall/v-shaped models with Final waterfall/vshaped.
It starts with an initial planning and ends with deployment with the cyclic interactions in between.
Agile Model -
Requirements -> Plan -> Design -> Develop -> Release -> Track & Monitor -> Requirements
Each Team has a designated Scrum Master, Product Owner, and set of Team members.
The usual “Scrum ceremonies” of Backlog Grooming, Sprint Planning, Daily Stand-Up, Review, and Retrospective are held.
It is based on iterative and incremental development, where requirements and solutions evolve through collaboration between cross-functional teams.
Decrease the time required to avail some system features.
Face to face communication and continuous inputs from customer representative leaves no space for guesswork.
The end result is the high-quality software in the least possible time duration and satisfied customer.
e.g.
Product Backlog - <- Grooming - - Planning-> Sprint Backlog -> Sprint - <-Daily scrum-> Valueable product.
Backlog grooming is when the product owner and some, or all, of the rest of the team review items on the backlog to ensure the backlog contains the appropriate items, that they are prioritized, and that the items at the top of the backlog are ready for delivery.
Sprint Review -
Preparation for an agile sprint review meeting should not take more than a few minutes at most.
The sprint review focuses on demonstrating what the development team has done.
Preparing for the sprint review meeting involves the product owner and the development team.
The product owner needs to know which user stories the development team completed during the sprint.
The development team needs to be ready to demonstrate completed, shippable functionality.
product in the sprint review, it must be complete according to the definition of done (Developed, Tested, Integrated, Documented).
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
- Waterfall Model.
- V-Shaped Model.
- Evolutionary Prototyping Model.
- Spiral Method (SDM)
- Iterative and Incremental Method.
- Agile development.
Requirement analysis, Design, Implementation, Testing, Evolution.
Waterfall Model -
The waterfall Model is a linear sequential flow.
In which progress is seen as flowing steadily downwards (like a waterfall) through the phases of software implementation.
This means that any phase in the development process begins only if the previous phase is complete.
The waterfall approach does not define the process to go back to the previous phase to handle changes in requirement.
Used for Projects which not focus on changing the requirements.
e.g.
Requirement, Design, Execution, Testing, Release.
V-Shaped Model -
It is an extension of the waterfall model.
Instead of moving down in a linear way, the process steps are bent upwards after the implementation and coding phase, to form the typical V shape.
early test planning in the V-shaped model.
e.g.
Planning -> Requirements -> Architecture -> Detailed Design -turnup to v-> unit testing -> integration test -> system & acceptance test -> mintenance
Prototyping Model -
the initial phase is contineous analysis & suggestion improvement and then after that furhter steps will follow in lenear.
It used to visualize some component of the software to limit the gap of misunderstanding the customer requirements by the development team.
final prototype is developed, the requirement is considered to be frozen.
Spiral Model (SDM) -
Manages risks and develops the system into phases.
Early involvement of developers.
It is combining elements of both design and prototyping-in-stages.
combines the features of the prototyping model and the waterfall model.
effort to combine advantages of top-down and bottom-up concepts.
This model uses many of the same phases as the waterfall model, in essentially the same order, separated by planning, risk assessment, and the building of prototypes and simulations.
Iterative and Incremental Model -
It is developed to overcome the weaknesses of the waterfall model.
It is combination of mini waterfall/v-shaped models with Final waterfall/vshaped.
It starts with an initial planning and ends with deployment with the cyclic interactions in between.
Agile Model -
Requirements -> Plan -> Design -> Develop -> Release -> Track & Monitor -> Requirements
Each Team has a designated Scrum Master, Product Owner, and set of Team members.
The usual “Scrum ceremonies” of Backlog Grooming, Sprint Planning, Daily Stand-Up, Review, and Retrospective are held.
It is based on iterative and incremental development, where requirements and solutions evolve through collaboration between cross-functional teams.
Decrease the time required to avail some system features.
Face to face communication and continuous inputs from customer representative leaves no space for guesswork.
The end result is the high-quality software in the least possible time duration and satisfied customer.
e.g.
Product Backlog - <- Grooming - - Planning-> Sprint Backlog -> Sprint - <-Daily scrum-> Valueable product.
Backlog grooming is when the product owner and some, or all, of the rest of the team review items on the backlog to ensure the backlog contains the appropriate items, that they are prioritized, and that the items at the top of the backlog are ready for delivery.
Sprint Review -
Preparation for an agile sprint review meeting should not take more than a few minutes at most.
The sprint review focuses on demonstrating what the development team has done.
Preparing for the sprint review meeting involves the product owner and the development team.
The product owner needs to know which user stories the development team completed during the sprint.
The development team needs to be ready to demonstrate completed, shippable functionality.
product in the sprint review, it must be complete according to the definition of done (Developed, Tested, Integrated, Documented).
Comments
Post a Comment