Question

What are the similarities and differences between the conventional waterfall model and the Unified Process model? Identify and explain three advantages and three disadvantages of each of these two models.

combines below questions together too

Explain in an essay why the waterfall process is a process for solving tame problems. also Explain in an essay how agile development tackles application software development as a wicked problem.

Answer 1

similarities and differences between waterfall Model and unified process model:

waterfall Model:

The traditional code development method, is usually spoken as “Waterfall”, may be a extremely structured and serial method that depends heavily on up-front designing and prescribed tasks that be due one to a different sort of a water. every section typically needs its own set of material specialists (SME) to blame for making the deliverables (requirements documents, style document, test plans, elaborated styles, etc…) to fulfill rigorously written milestones. In water, succeeding section generally can not be started till the previous one has been completed. The goal is to assemble and analyze all the elaborated needs early within the method so a whole resolution may be architect-ed and build with extremely foreseeable results.
Waterfall software development methodology will work good for advanced mission-critical systems or for organizations that need the best levels of fault tolerance (such because the military or aerospace). However, comes victimization water processes take too long, in several cases months or years, to supply results which will be verified by the user and sometimes and lacks the pliability for today’s setting. additionally, as a result of water comes need that each one the necessities be outlined direct (often spoken as massive Up Front needs – BUFR), these comes typically don't give business price in today’s fast code market as in several cases needs modifications lead to expenses change requests or buggy systems.

Rational Unified method

The Rational Unified method may be a code Engineering method. It provides a disciplined approach to assignment tasks and responsibilities inside a development organization. Its goal is to make sure the assembly of high-quality code that meets the wants of its end-users, inside a foreseeable schedule and budget.

Rational unified process method additionally defines the roles and activities of team members in-depth and depends at every stage on the assembly of visual models, that area unit made graphical representations of package systems, and specific use cases instead of the big amounts of documentation needed for every stage of falls. All team members have access to a similar massive mental object of pointers, templates, tools, and different things to make sure that they share a similar language and perspective on the project.