This document discusses requirements engineering and its key processes. It describes how requirements engineering involves eliciting requirements through activities like interviews and prototyping. It also involves analyzing requirements by documenting them, resolving conflicts between stakeholder needs, and validating requirements. The document stresses the importance of requirements engineering in defining a system's functionality and ensuring project success.

2.  Introduction
 Requirement engineering process
 Requirement elicitation
 Requirement analysis
 Problems of requirement analysis
 Conclusion

3.  Requirements engineering (RE) refers to the
process of defining, documenting and
maintaining requirements and to the subfields of
systems engineering and software engineering
concerned with this process.
 The first use of the term 'requirements engineering' was
probably in 1979 in a TRW technical report but
did not come into general use until the 1990s with
the publication of an IEEE Computer Society tutorial
and the establishment of a conference series on
requirements engineering.
 In the waterfall model requirements engineering is
presented as the first phase of the development process

4.  The processes used for RE vary widely
depending on the application domain, the
people involved and the organisation
developing the requirements.
 However, there are a number of generic
activities common to all processes
 Requirements elicitation;
 Requirements analysis;
 Requirements validation;
 Requirements management.

5.  Process of identifying needs
 Front end system development
 Involves social ,communicative issues and Technical
issues
 It helps to express the requirements systematically

6.  Is the practice of collecting the requirements of
a system from users, customers and other
stakeholders.
 Also referred as ‘requirement gathering’
 The practices include
 Interviews
 Questionnaires
 Used observation
 Workshops
 Brainstorming
 Prototyping,etc..

7.  System developers and engineers work in close
relationship with customer and end user to:
 Find out more about the problem to be solved
 To describe the functionality of the system
 Performance of the system
 Hardware constraints and so forth,..
 Not just a simple process of fishing for requirement
, but a highly complex process :
 Customer rarely have a clear idea about the
requirements
 Different people have conflicting requirements

8.  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 product or
project, taking account of the possibly
conflicting requirements of the
various stakeholders, analyzing, documenting,
validating and managing software or system
requirements.
 Requirements analysis is critical to the success of a
systems or software project. The requirements should
be documented, actionable, measurable, testable,
traceable, related to identified business needs or
opportunities, and defined to a level of detail sufficient
for system design.

9.  Stakeholders don’t know what they really
want
 Stakeholders express requirements in their
own terms
 Organisational and political factors may
influence the system requirements
 The requirements change during the analysis
process.New stakeholders may emerge and
the business environment change.

10.  Requirement elicitation and analysis is
included among the requirement engineering
process
 It involves technical staff working with
customers to find out about the application
domain. The services that should provide and
the system’s operational constraints.
 Encompasses all activities involved in
discovering the requirements of a system.