Ans1) Waterfall approach was first Process Model to be introduced and followed widely in

Software Engineering to ensure success of the project. In "The Waterfall" approach, the whole
process of software development is divided into separate process phases. The phases in Waterfall
model are: Requirement Specifications phase, Software Design, Implementation and Testing &
Maintenance. All these phases are cascaded to each other so that second phase is started as and
when defined set of goals are achieved for first phase and it is signed off, so the name "Waterfall
Model". All the methods and processes undertaken in Waterfall Model are more visible.

ADVANTAGE:
1) Progress of system is measurable.
2) Strict sign-off requirements.

DISADVANTAGE:
1) Little room for iteration
2) Difficulty responding to changes

SPIRAL MODEL: Spiral model is an evolutionary version of incremental prototyping,

developed by Boehm in 1988. Each iteration of the prototype represented as a cycle in the
spiral. The Spiral software development model is a risk-oriented.
Spiral software development model may be applicable to projects where:

 The projects requirements are very difficult

 Where new technologies are used

ADVANTAGE:
Estimates (i.e. budget, schedule, etc.) become more realistic as work progresses, because
important issues are discovered earlier.

   2. It is more able to cope with the (nearly inevitable) changes that software development
generally entails.

   3. Software engineers (who can get restless with protracted design processes) can get their
hands in and start working on a project earlier.

DISADVANTAGE:
   1. Highly customized limiting re-usability

   2. Applied differently for each application

   3. Risk of not meeting budget or schedule

   4. Risk of not meeting budget or schedule

ITERATIVE MODEL: Iterative and Incremental development is at the heart of a cyclic

software development process developed in response to the weaknesses of the waterfall
model. It starts with an initial planning and ends with deployment with the cyclic interactions
in between.

ADVANTAGE:
1) Iterative model is more flexible, as it presents more opportunities to introduce change

2) Iterative model is that the complexity of implementing the system is never overwhelming.
Because elements are designed, developed and integrated in iterations, the "analysis
paralysis" that is common on enterprise scope projects is alleviated.

DISADVANTAGE:
1. Each phase of an iteration is rigid with no overlaps
2.Costly system architecture or design issues may arise because not all requirements are
gathered up front for the entire lifecycle

PROTOTYPE MODEL:

Prototype Model slowly builds from a simple concept of what a program is. Little by little the
software is updated and tested in a real time environment. Users will be able to test and
improve the software as they are created. This goes in a different pattern if you compare it to
the regular SDLC pattern, and the feedback is only in the later stage. If there are any changes,
it has to go back to the drawing board, wasting more time.

There are different types of a prototype model of SDLC. Each of them has their own
advantage and disadvantage but ultimately, the prototype model is geared to be changed
constantly until it reaches its intended audience and function.
ADVANTAGE:

1) Prototype modelled software has is the time frame of development. Instead of

concentrating on documentation, more effort is placed in creating the actual software. This
way, the actual software could be released in advance.

2) Prototype modelled software is that the software is created using lots of user feedbacks. In
every prototype created, users could give their honest opinion about the software. If
something is unfavourable, it can be changed. Slowly the program is created with the
customer in mind.

DISADVANTAGE:

1) it’s being built out of concept, most of the models presented in the early stage are not
complete.

2) Prototypes are not yet complete software programs, there is always a possibility of a
designer flaw. When flawed software is implemented, it could mean losses of important
resources.

ANS2) the study understanding of several needs of the client and the users so
that the software can be built in a way that all the needs shall be known as
analysis. The analyst, who is responsible for the specifications of the software,
must be totally aware of the business processes of the organisation.

This is important factor because if the analyst has the knowledge about the
business processes only then he can change them into the specified
requirements or we can say the required features of the software and the
designers can get the same in the software

The analyst is supposed to have knowledge about the questions the clients has
and users to know about how the business processes are going in the
organization.

Ans 5) Requirements analysis in systems engineering and software engineering,

Encompasses those tasks that go into determining the needs or conditions to
meet for a new or altered Requirements analysis is critical to the success of a
development project. Requirement Its must be actionable, measurable,
testable, related to identified business needs or opportunities, and
defined to a level of detail sufficient for system design. Requirements can
be functional and non-functional. Conceptually, requirements analysis includes
three types of activity:
1) Eliciting requirements: the task of communicating with customers and users
to determine what their requirements are. This is sometimes also called
requirements gathering.

2) Analysing requirements: determining whether the stated requirements are

unclear, incomplete, ambiguous, or contradictory, and then resolving these
issues.
3) Recording requirements: Requirements might be documented in various
forms, such as natural-language documents, use cases, user stories, or process
specifications.
Requirements analysis can be a long and arduous process during which many
delicate psychological skills are involved. New systems change the environment
and relationships between people, so it is important to identify all the
stakeholders, take into account all their needs and ensure they understand the
implications of the new systems. Analysts can employ several techniques to
elicit the requirements from the customer. Historically, this has included
such things as holding interview s, or holding focus groups (more aptly named
in this context as requirements workshops) and creating requirements lists.
More modern techniques include prototyping, and use cases. Where necessary,
the analyst will employ a combination of these methods to establish the exact
requirements of the stakeholders, so that a system that meets the business needs
is produced.
Systematic requirements analysis is also known as requirements engineering. It
is sometimes referred to loosely by names such as requirements gathering,
requirements capture, requirements specification. The term requirements
analysis can also be applied specifically
to the analysis proper, as opposed to elicitation or documentation of the
requirements, for instance.