Zusammenfassung der Ressource
Software Development Lifecycle Models
- It covers all stages
of the software.
- Since its inception with requirements
and definition, to the field and
maintenance.
- Categories according to use
- Category 1
- Category 2
- Category 3
- Front-end.
Application that
is a graphical
user interface
(GUI).
- End user
(software that
encapsulates
logic, being more
understandable
to the end user)
- Back-end
(provides a
service to other
applications)
- They can be
classified into three
broad groups:
- Linear
- Iterative
- ombination of
linear and
iterative models
- Recognize that
the development
process may
stop at a certain
stage.
- Ensures that all
stages of the
model are
reviewed in the
future.
- The stage, once
completed, leads
to the start of the
next stage.
- Types of models
- Waterfall Model
- B-Model
- Incremental Model
- V-Model
- The model is a
variation of the
waterfall.
- Spiral Model
- Several iterations
that spiral out from
small beginnings.
- Wheel-and-spoke Model
- The wheel-and-spoke model is
based on the spiral model and is
designed to work with smaller
teams initially, which then scale
up to build value faster
- Represent the number of
iterations that would be
made in order to improve
the functionality of the end
product incrementally.
- denoted as the
maintenance
cycle
- Recommended for
software that is
developed in stages
- Rapid Application Development
- Development (RAD) is a
methodology that uses
prototypes as a
mechanism, for iterative
development.
- Agile
- Joint Application Development (JAD)
- Lean Development (LD)
- Scrum
- Development takes
place over a series of
short iterations, or
sprints, and progress is
measured daily
- Lean Development
attempts to deliver a
project early with a
minimal functionality.
- Collaborative
development with the
end user or client
involved
- Development occurs in short
intervals and software releases
are made to capture small
incremental changes.
- Extreme Programming (XP)
- Development takes place incrementally and on the fly with a business
champion acting as a conduit for user-driven requirements and functionality;
there is not an initial design stage.
- Advantage
- Provides ease and speed.
- Highly organized programming
- The error rate is very minimal
- Promotes programmer satisfaction.
- Saves a lot of time and money
- Communication between clients and developers.
- It can be applied to any programming language.
- Disadvantages
- It is advisable to use it only in short-term projects.
- Requires version control.
- Requires self-discipline in application
- It requires a greater work effort.
- Presentado por: Miguel Oswaldo Hernández Sáenz