Name: Agie Ignacio Subject: INSY 55 – System Analysis and

Design
Year & Section: BSIT-3C

Assignment # 2

List down the Advantages and Disadvantages of the following:

Advantages Disadvantages
1. Waterfall Model • Before the next • Error can be fixed
phase of only during the
development, each phase
phase must be • It is not desirable for
completed complex project
where requirement
• Suited for smaller changes frequently
projects where • Testing period
requirements are comes quite late in
well defined the developmental
• They should process
perform quality • Documentation
assurance test occupies a lot of
(Verification and time of developers
Validation) before and testers
completing each • Clients valuable
stage feedback cannot be
• Elaborate included with
documentation is ongoing
done at every phase development phase
of the software’s
development cycle
• Project is
completely
dependent on
project team with
minimum client
intervention
2. Prototype Model • It is easy to detect • It has poor
errors. documentation
because of
 • We can find missing continuously
functionality easily. changing customer
• There is scope of requirements.
refinement, it means • There may be too
new requirements much variation in
can be easily requirements.
accommodated. • Customers
• It can be reused by sometimes demand
the developer for the actual product to
more complicated be delivered soon
projects in the after seeing an early
future. prototype.
• It ensures a greater • There may be sub-
level of customer optimal solutions
satisfaction and because of
comfort. developers in a
hurry to build
prototypes.
• Customers may not
be satisfied or
interested in the
product after seeing
the initial prototype.

3. Spiral Model • Risk handling is one • It is not suitable for

of important small projects as it
advantages of the is expensive.
Spiral model, it is • It is much more
best development complex than other
model to follow due SDLC models.
to the risk analysis Process is complex.
and risk handling at • Too much
every phase. dependable on Risk
• Flexibility in Analysis and
requirements. In this requires highly
model, we can specific expertise.
easily change • Difficulty in time
requirements at management. As
later phases and the number of
can be incorporated phases is unknown
accurately. Also, at the start of the
additional project, so time
Functionality can be estimation is very
added at a later difficult.
date. • Spiral may go on
indefinitely.
 • It is good for large
and complex
projects.
• It is good for
customer
satisfaction. We can
involve customers in
the development of
products at early
phase of the
software
development. Also,
software is
produced early in
the software life
cycle.
• Strong approval and
documentation
control.

4. Extreme • Close contact with • Additional work

Programming the customer • Customer must
• No unnecessary participate in the
programming works process
• Stable software • Relatively large time
through continuous investment
testing • Relatively high
• Error avoidance costs
through pair • Requires version
programming management
• No overtime, teams •
work at their own Requires self-
pace discipline to practice

5. Unified Process • It allows us to deal • It is a complex

with changing model to implement
requirements within as it has multiple
the project’s workflow stages.
development life • It is challenging for
cycle as per the organizations to
client or customer implement which
needs, i.e., it has small team
welcomes change. sizes or projects.
 • It supports • Individuals or teams
incremental build of should prioritize
the software achieving highly
product. tangible results.
• The software • It emphasizes the
product provides integration of
proper modules throughout
documentation. the software
• It helps to use the development
resources efficiently. process, creating
• It helps to identify trouble during the
issues early in the testing phase.
process life cycle.
• Process control and
risk management
are improved.
• It enhances team
productivity.
• It helps reduces
unexpected
development costs.

6. Agile Modeling • Customer • In case of some

satisfaction by software
rapid, continuous deliverables,
delivery of useful especially the large
software. ones, it is difficult to
• People and assess the effort
interactions are required at the
emphasized rather beginning of the
than process and software
tools. Customers, development life
developers and cycle.
testers constantly
• There is lack of
interact with each
emphasis on
other.
necessary
• Working software is designing and
delivered frequently documentation.
(weeks rather than
• The project can
months).
easily get taken off
• Face-to-face track if the customer
conversation is the representative is not
best form of clear what final
communication. outcome that they
want.
 • Close, daily • Only senior
cooperation programmers are
between business capable of taking
people and the kind of decisions
developers. required during the
development
process. Hence it
has no place for
newbie
programmers,
unless combined
with experienced
resources.

7. Rapid Application • It offers improved • It requires huge

Development flexibility as collaboration and
developers can joint effort from
adapt to required many people and
changes and departments. This
incorporate new can become
functionalities and confusing if it isn’t
features during the organized or
build process. conducted
• You can create adequately.
quick iterations that • It can lead to
cut down time problems such as
frames to make code documentation
your delivery issues if you have a
process a lot more large team that is
streamlined. mostly filled with
• It is dependent on new or
customer inexperienced
collaboration developers.
satisfying every • It needs slightly
stakeholder such as more talented
users, developers, developers to carry
and clients. out iterations and
• It offers enhanced update code during
risk management the development
solutions because process as they’d
code vulnerabilities be quick to
are fixed before the understand each
final release. aspect of the
• You can carry out project.
integrations at the
 initial stages and • The RAD model is
reuse code at any typically suitable
point, which results just for projects that
in a shorter testing must be developed
time. and delivered
• Fast reviews can be quickly.
carried out, and • Rapid Application
hence you achieve Development
more productivity requires customer
with fewer people. input at numerous
stages, making the
process a lot more
complex than other
methodologies.
• It can be very hard
to manage if every
stakeholder is not
on the same page.

8. Joint Application • JAD allows you to • Different opinions

Development resolve difficulties within the team
more simply and make it difficult to
produce better, align goals and
error-free software maintain focus
• The joint • Depending on the
collaboration size of the project,
between the JAD may require a
company and the significant time
clients lowers all commitment
risks
• JAD reduces costs
and time needed for
project development
• Well-defined
requirements
improve system
quality
• Due to the close
communication,
progress is faster
• JAD encourages the
team to push each
other to work faster
and deliver on time