software engineering requirements analysis

Requirements analysis

Requirements analysis is the process of determining user expectations for a new or
modified product. These features, called requirements, must be quantifiable, relevant
and detailed.
• In software engineering, there are two types of requirements 1) functional
requirement 2) non- functional Requirement. Requirements analysis is an important
aspect of project management.
• Requirements analysis involves frequently communicate with system users(developer)
and client(group of user).
• Requirements analysis is a team effort that demands a combination of hardware,
software and human factors engineering expertise as well as skills in dealing with
people.
• The software requirements are description of features and functionalities of the target
system. Requirements convey the expectations of users from the software product.
• The hardware requirements are description of which operating system is used and
which types of software are installed.

Requirement Engineering

• The process to gather the software requirements from client, analyze and document

them is known as requirement engineering.

• The goal of requirement engineering is to develop and maintain sophisticated and

descriptive ‘System Requirements Specification’ document.(SRS)

Requirement Engineering Process

• It is a four step process,

1 Feasibility Study

2 Requirement Gathering

3 Software Requirement Specification (SRS)

4 Software Requirement Validation

Requirement Elicitation Process

• Requirement elicitation is the practice of collecting the requirement of a system from

user, customer, and other stakeholders. The practice is also sometimes referred to as a

requirement gathering. process can be depicted using the following diagram:

• Requirements gathering - The developers discuss with the client and end users and know

their expectations from the software.

• Organizing Requirements - The developers prioritize and arrange the requirements in order

of importance, urgency and convenience.

• Negotiation & discussion –

If requirements are ambiguous or there are some conflicts in requirements of

various stakeholders, if they are, it is then negotiated and discussed with

stakeholders.

 The requirements come from various stakeholders. To remove the ambiguity

and conflicts, they are discussed for clarity and correctness. Unrealistic

requirements are compromised reasonably.

• Documentation - All formal & informal, functional and non-functional requirements are

documented and made available for next phase processing.