SOFTWARE REQUIREMENT ENGINEERING
LAB 2
Introduction To Requirement Engineering
OBJECTIVES:
✔ Learn about Functional and Non Functional Requirements?
Functional Requirements:
Functional requirements
– Statements of services the system should provide, how the system should react to
particular inputs and how the system should behave in particular situations.
Statements describing what the system does
– Functionality of the system
Statements of services the system should provide
– Reaction to particular inputs
– Behavior in particular situations
Example of Functional Requirements:
The LIBSYS System
• The users can search for, download and print articles for personal study.
• The user shall be able to search either all of the initial set of databases or select a subset
from it.
• The system shall provide appropriate viewers for the user to read documents in the
document store.
• The users order shall be allocated a unique identifier (ORDER_ID) which the user shall be
able to copy to the account’s permanent storage area.
Non Functional Requirement:
A non-functional requirement is a statement of how a system must behave, it is a constraint upon
the systems behavior.
• Most non-functional requirements relate to the system as a whole.
– They include constraints on timing, performance, reliability, security, maintainability,
accuracy, the development process, standards, etc.
Example of Non Functional Requirements:
● "Display of the patient's vital signs must respond to a change in the patient's status within
2 seconds."
TASK 1:
Write down Functional and Non Functional Requirements of ATM (Automated teller Machine)?