1

563 - The Mandvi Education Society

Institute of Computer Studies – MCA

Subject Code : 3640003

Subject Name : Software Engineering
Unit 2 – Requirement Engineering
Prepared By: Dr. Vikas S. Chomal
 2

Software requirement
IEEE defines requirements as:
(a) a condition or capability needed by a user to solve a problem
or achieve an objective.
(b) a condition or capability that must be met or possessed by a
system or system component to satisfy a contract, standard,
specification, or other formally imposed documents. and
(c) a documented representation of a condition or capability as in
(a) or (b).

Prepared By: Dr. Vikas S. Chomal

 3

Requirement Engineering (RE)

 Requirement Engineering (RE) is also known as Requirement
Analysis (RA). It is the procedure of shaping user expectations for a
new or modified product.
 RE can be defined as a subset of Software Engineering that mainly
focuses on the use of various tools and techniques for the
development and management of software requirements.

Prepared By: Dr. Vikas S. Chomal

 4

 RE is concerned with the identification of the goals to be achieved

by the envisioned system, the operationalization of such goals into
services and constraints, and the assignment of responsibilities for
the resulting requirements to agents such as humans, devices, and
software.
The requirements are fundamentally classified into three
categories explicitly, functional requirements, non-functional
requirements and domain requirements.

Prepared By: Dr. Vikas S. Chomal

 5

 Functional Requirements:
They also known as behavioral requirements illustrates the
functionality or services that software should provide.
The functional requirements part discusses the functionalities
required from the system. The system is considered to perform a set
of high-level functions {fi}. The functional view of the system is shown
in figure below.
Each function fi of the system can be considered as a transformation
of a set of input data (ii) to the corresponding set of output data
(oi). The user can get some meaningful piece of work done using a
high-level function.

Prepared By: Dr. Vikas S. Chomal

 Figure : View of a system performing a set of functions

6 Prepared By: Dr. Vikas S. Chomal

 7
Here we list all functions {fi} that the system performs. Each
function fi as shown in figure below is considered as a
transformation of a set of input data to some corresponding
output data.

Figure: Function fi

Prepared By: Dr. Vikas S. Chomal

 8
Example:-
Consider the case of the library system,
where - F1: Search Book function (figure Below)
Input: an author’s name
Output: details of the author’s books and the location of these
books in the library

Figure: Book Function

Prepared By: Dr. Vikas S. Chomal

 9

 Non - Functional Requirements:

Non-functional requirements deal with the characteristics of the

system which can not be expressed as functions - such as the
maintainability of the system, portability of the system,
usability of the system, etc.

Non-functional requirements may include:

# reliability issues,
# accuracy of results,
# human - computer interface issues,
# constraints on the system implementation, etc.

Prepared By: Dr. Vikas S. Chomal

 Figure: Metrics for non-functional requirements

10 Prepared By: Dr. Vikas S. Chomal

 11
 Domain requirements
Finally, requirements which are derived from the application domain
for a system instead from the needs of the users are known as
domain requirements. If domain requirements are not satisfied, the
system may be unworkable
 Example: Library system

Prepared By: Dr. Vikas S. Chomal

 12
Software requirement analysis perhaps is separated into
five areas of efforts:

1) Problem recognition
2) Evaluation and synthesis
3) Modelling
4) Specification
5) Review

Prepared By: Dr. Vikas S. Chomal

Requirement Analysis Process

Requirements
definition and
specification
Requirements
validation

Domain
understanding
Prioritization

Requirements Conflict
collection resolution

Classification

Figure: Requirement Analysis Process

13 Prepared By: Vikas S. Chomal