MODEL/ YEAR AND STAGES CHARACTERISTICS ADVANTAGES DISADVANTAGES APPLICATION

CREATED METHODOLOGY
R
Winston Definition of It must be verified the Make a good A rare project It is the approach
W. Royce requirements. Software after operation in once follows a methodological that organizes
1970 System design merge it and before weak teams and linear sequence rigorously the stages
my software operate it. mature products this creates a bad one of the process for the
Implementation and It is the most used. as far as I know implementation of software development,
test of They must be developed requires less model, which in such a way that the beginning
units all the phases capital y make him take it to the from each stage must
Integration and The phases continue tools for failure. wait for completion
test of until the make it work The process of from the previous stage.
system objectives have been optimally. creation
Operation and fulfilled It is an easy model the software takes time At the end of each stage, the
Waterfall Maintenance. to implement and a long time already the model is designed
to understand. that until to carry out a
It is oriented towards the software is not final review, that is
documents. I don’t know complete is responsible for determining whether

It is a model opera. This is the the project is ready for

known and used basis for what advance to the next
frequently. function well. phase.
Any error of
design detected in
the testing phase
drives
necessarily to the
redesign and
programming of
affected code,
increasing the
costs of
development.
 Barry For each cycle: Contains a new It does not require one Exists Use an approach
Boehm stage that is the definition complication evolutionary for the
1986 Determine risk analysis, no complete of the when it software engineering
objectives included requirements evaluate the allowing to the
Analysis of previously. from the software to risks. developer and the client
risk This model is the develop for The required understand and react to
Develop and indicated for start your participation the risks at each level
to try develop software functionality. continues with of the spiral model.
Planning with different In the part of
versions termination of client. Use the creation of
updated as a product It gets lost prototypes like a
do with the since the end of time to return reduction mechanism
modern programs the first produce of risk, but, the most
of PCs. iteration is initially important allows to
Spiral Engineering can very feasible a who develops it apply
develop through approve the specification the approach to creation of
of the life cycle requirements. complete of the prototypes in any
classic or the one of Suffer delays requirements stage of the evolution of
construction of runs a risk when is prototypes.
prototypes. smaller, because modify or
This is the approach are verified improve it
more realistic the conflicts software.
currently. presented
early
and there is a way
to be able
correct them to
time.
 Friday Planning This design leads to This model is useful Administration It basically consists of
1984 Modeling the construction of a when the client Difficult: Said that based on the
Construction of prototype, which is know the the difficulty lies in requirements and
Prototype evaluated by the client general objectives drive the needs that it has the
Development for a for the software,
prototype as a client, is carried out by
Delivery and feedback but does not identify
thanks to this, they are refined the requirements project within the quick form a
feedback Development Cycle prototype, this one will not come
the requirements of detailed of
Communication of System without not much complete
software that is entry
with client
will develop. The processing or lose sight of which less finished, but yes
Delivery of the
interaction occurs exit. it was his purpose. will allow to have the
final development when the prototype is It also offers a Adopt it as the necessary bases for
adjust to meet the better approach final system: The any programmer
customer needs. when the users and I can continue working
This allows that when responsible for
Prototypes professionals of in the until reaching the
same time the development of
developer understand systems can final code.
software is
better what should be unsure of the consider the
make and let the client see effectiveness of a prototype like the
short-term results. algorithm, of the final system
adaptability of when it is still
a system incomplete and
operational or of the inadequate.
form that it should The developer and the
take the clients have little
interaction
communication to
human-machine
start of the process.
It can be reused
the code. Changes arise
unexpected issues that
they delay progress
of the prototype.
 SAGE Operational Plan It is a model in which Requires little to be subjected to The development model
1956 Software specification is shown to the sophistication for a planning the software by stages is
of requirements customer in stages the executives and predefined. similar toModel of
Successively refined specifications. developers. Works with little prototypessince it
functional In this way Allows compression on the sample to the client
Design develops the capabilities modifications to architecture. software in different
Most important implementation, halfway. Works with little successive states of
on reducing your time of Requires little identification of the developments, it differs
Integration construction of the management time. requirements of in which the
Validation and product Generate a system design. specifications are not
verification highly reliable and Must be delivered known in detail to the
Maintenance with wide a stage for project start and for
o development. continue with the so many are leaving
Allows a next. developing
Development by useful functionality in This model is not simultaneously with the
stages client's hands viable without one different versions of the
without having the planning code.
application adequate.
completed.
Provide signs
tangibles of
progress.
 Mills Requirements The model Through this Each phase of a This model focuses on
1980 Definition of the incremental combination model is generated iteration is rigid and the delivery of a product
tasks and the elements of operating software they do not overlap operational with each
iterations waterfall model quickly and with others. increase. The first
Design of the with philosophy in stages They can arise increments are
increases interactive of early in the cycle problems related to incomplete versions of the
Development of construction of of life of the to the architecture of the final product, but
increase prototypes. software. system because no provide the user
Validation of It is based on philosophy It is another model all the requirements the functionality that
increments: to build flexible, therefore they have gathered already it needs and also one
Integration of increasing the the cost is reduced What is supposed to platform for the
increases functionalities of the in the change of all of them have evaluation.
Delivery of program. scope and requirements. defined at the beginning
product This model applies It is easier to try and
linear sequences of debug in a
Incremental stepped shape more iteration
as it progresses the small.
time in the It is easier
calendar. Each manage risks.
linear sequence Each iteration is a
produce a managed person
increase of easily
software
 James Modeling of The method Buying can Buying can be This methodology
Martin Management understands the save money on more expensive than proposes a process of
1980- Modeling of interactive development, comparison with build. software development
1990 Data the construction of build. Cost of that allows for the creation of
Modeling of prototypes and the use of The deliverables tools systems of
Process CASE utilities they can be integrated and equipment usable computers
Generation of (Computer Aided easily necessary. over a period of time
applications Software transferred to another More difficult progress between 60 to 90 days. RAD is
Tests of Engineering. platform. to measure. a development cycle
delivery Traditionally, the The development is Less efficient. designed to create
rapid development of carry out at a level of Lower accuracy applications of
applications tends to greater abstraction. scientific. high computers
also encompass the Visibility Risk of reversing the quality of those
usability, utility and early. to the practices without they happen in
the speed of Greater flexibility. control of yesteryear. large corporations.
RAD execution. Minor coding More failures (due to
manual. syndrome of The development of
Mayor "encode to" applications face a
involvement of beast) transformation
the users. Prototypes can fundamental. Five ago
Possibly no scaling, a years a project for
fewer failures. problem develop an application
Possibly uppercase. took a period of
lower cost. Reduced functions between 18 to 24 months;
Development cycles (for "timeboxing"). currently, with the
smaller. Dependency on RAD model practice
components of it takes between 1 to 3 months.
third parties
functionality of
more or less,
legal problems.
 Davis Organization Provide a meta- Excellent for If they are not given the The development model
Sitaram Communications description of the projects in the conditions concurrent is used to
decade Specification software process. that are formed pointed out is not chitterlings like the
from 1990 Development of The model work groups applicable. development paradigm
product concurrent has the independents. If there are no application groups
capacity of Provide a I don't know about work client/server.
describe the multiples exact image of can work in A system
activities of the current state of a this method client/server
software occurring project consists of a set
simultaneously. of components
Most of the functional.
process models When applied to
of development of client/server, the
software are directed process model
for the time; how much concurrent defines
Concurrent the later it is, the more activities in two
you will find behind dimensions: a division
in the process of of systems and a division
development. A of components.
process model
concurrent is
directed by the
needs of the
user, the
decisions of the
management and the
results of the
reviews.
 IBM Start The authors of RUP d The advantages of this As disadvantages, In RUP they have been grouped
Corporation Preparation they establish that the process model are the we can point out group activities
on, of Construction or software reduction of what requires a logicals defining 9
property Transition proposed by RUP you risks in the great forecast on workflows
d of three characteristics project, the what is going to happen mainly, the 6
Rational s quality guarantee (in order to first are known
Software essentials: it is directed and integration to control it) and that as engineering flows
in 2003. or by the Us Cases between what is abundant genera and the last three like
it is centered on the properly additional work (and support flows.
architecture, and it is development with associated costs) of orBusiness Model
iterative and incremental maintenance of documentation and oRequirement
al. software (a base de communication, with o Analysis and Design
1. Directed process by it is iterating through each what is not usual or Implementation
Use Cases phase, combining practical result Test
RUP 2. Process activities of one and for projects Installation or deployment
focused on the arch another type). small. or Administration of
reading project
3. or Administration of
Iterative process and in configuration and changes
incremental the Environment
4. Dynamic Structure
of the process. Phases and
iterations
 Ikujiro Planning of Regular management of the Deliverables in Some members Currently, the
Nonaka y sprint expectations of the time and manner of your team projects are developed
Takeuchi 2. Stage of cliente, resultados you can start sending they can skip steps in very contexts
1986 development anticipated, deliverables to important in the versatile. They are more
3. Review of flexibility and client while you go fast track to more complex than before,
sprint adaptación, retorno attacking the reach the 'sprint' in the face of some demands
4.Feedback of investment, more objectives final. of the customer and of the market
on risk mitigation simple, that will you The customer is always much more variables, and
productivity and saves time is going to wait for the with uncertainty
calidad, alineamiento to attack the reports with the elevated. That's why the
between client and more objectives exact date, and application of the method
SCRUM team, finally, complex Many times Scrum has been extended
motivated team. the ScrumMaster to ask beforehand, like gunpowder in
Is used for has the when able no numerous sectors,
car equipment- knowledge were you able to make progress inout of the world of

directed and self- necessary for nothing. software development

organized. achieve the goal Too many
It is done daily. primary and Meetings for
Scrum meeting secondary for the little progress, to
what is a meeting which one can go sometimes it is very

of daily progress that controlling the tiring and

it lasts no more than 15 project and stressful to meet
minutes with him delegating roles. too many times
objective of obtaining Each person knows for the same issue,
feedback on what does it have some go
the tasks of the team. what to do and what not to do losing interest
necessary to be in the project.
reorganizing one and
again the Tracks
of each person.
 Kent Planning Lightweight methodology Gives rise to a It is advisable Design, implement
Beck Design of development programming use it only in to programthe fastest
1999 Coding software extremely short-term projects possible, hastake a case
Test Set of practices organized. deadline. recommend to skip the
and rules used It causes efficiencies In case of failure, the documentation and the
to develop in the process of commissions are very procedures
software planning and high. traditional. It
Based on different tests. Requires a foundations in the
ideas about how It has a rate rigid adjustment to the team capacity
confront environments of very errors principles of XP. to communicate with each other
very changeable small. It may not always and the desire to learn
Originated in the Fosters the be easier than the of one's own mistakes
C3 project for communication between development inherent in a
Chrysler customers and the traditional. programmer.
Instead of planning, developers. The great advantage of XP is
analyze and design Facilitates changes. your incredible ability to
XP for the future Allows to save response to
distant, do everything a long time and unforeseen events, although for
this a little each money. design is a
time, through everything It can be applied to methodology that does not
the process of any language build for the long
development of programming. deadline and for which it is
The client has the difficult to document.
control over the XP is a method
priorities. great for teams
Tests are being conducted extremely
you continue during small ones that focus
the project. in a single client.
The XP is better
used in the
implementation of
new technologies.
 Jim Speculation Iterative It serves to learn.The errors or ASD highlights that the
Highsmit Collaboration Oriented towards the of the mistakes and changes that are not approximations
in 1998 Learning Software components restart the detected in cascading sequences
Tolerant to the development cycle meetings they only work in
changes Use information previous to time, well-known environments.
Guided by the available about affects the quality of But like the changes
risks changes for product and to its happen frequently
The review of the improve the total cost in software development,
components serve behavior Given that it is a it is important to use a
to learn from the from SW agile methodology tolerant method
errors and go back Promulgates implies not to carry out changes. The first cycle
start the cycle of collaboration processes that are of an ASD project usually
THE development interaction of required in the be brief, ensuring
people methodologies that the client is
traditional involved and
confirming the feasibility
of the project.
Each cycle ends with
a group review
customer-focused.
During the meetings of
review, the study of the
application running. The
result of the
meetings are requests
of change
documented.