Scribd
Upload
6 views15 pages

02 Requirment Engineering

The document discusses functional requirements and non-functional requirements. Functional requirements describe what a system should do, including reactions to inputs and behaviors in situations. Non-functional requirements relate to system constraints like timing, performance, reliability and security.

Uploaded by

Talha Irfan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views15 pages

02 Requirment Engineering

The document discusses functional requirements and non-functional requirements. Functional requirements describe what a system should do, including reactions to inputs and behaviors in situations. Non-functional requirements relate to system constraints like timing, performance, reliability and security.

Uploaded by

Talha Irfan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

Software Requirement Engineering

Lecture 02
Subscribe Us
Youtube.com/SoftwareEngineering

/SoftwareEngineeringYT

@iMrHammad
Functional Requirement
• Statements describing what the system should do.
• Functionality of the system.
• Statements of services the system should provide.
• Reaction to particular inputs
• Behavior in particular situations
• Abnormal behavior is also documented as functional requirements
in the form of exception handling.
• Customers and developers usually focus all their attention on
functional requirements.
Functional Requirement
• Examples of Functional Requirements
• The user shall be able to search either the entire database of patients or
select a subset.

• Every order shall be allocated a unique identifier (ORDER_ID) which the user
shall use to access that order.

• The system shall allow customers to return non-perishable items within


fifteen days of the purchase. A customer must present the original sale
receipt to return an item.
Functional Requirement
•Comments on Functional Requirement:
• Incomplete and ambiguous requirements are open to multiple
interpretations and assumptions.

• This can lead to the development of poor quality, or faulty,


software products.

• The level of details are different in all the requirements


Non-Functional Requirement
• Most non-functional requirements relate to the system. They include
constraints on timing, performance, reliability, security, maintainability,
accuracy, the development process, standards, etc.

• They are often more critical than individual functional requirements.

• Must be built into the framework of the software product.

• Failure to meet a non-functional system requirement may make the


whole system unusable.
Non-Functional Requirement
• Example on Non-Functional Requirements
• if an aircraft system does not meet reliability requirements, it will not be certified as
„safe‟.

• If a real-time control system fails to meet its performance requirements, the control
functions will not operate correctly.
• Observations of Non-Functional Requirements
• Non-functional requirements can be written to reflect general goals for the system.
• Examples include:
• – Ease of use
• – Recovery from failure
• – Rapid user response
Non-Functional Requirement
Observations of Non-Functional Requirements
• Non-functional requirements are sometimes written as general goals.

Verifiable and Unverifiable NFR


• Unverifiable
The system should be easy to use by experienced controllers and should be organized
in such a way that user errors are minimized.

• Verifiable:
Experienced controllers shall be able to use all the system functions after a total
of two hours‟ training. After this training, the average number of errors made by
experienced users shall not exceed two per day
Non-Functional Requirement
Non-Functional Requirement
Non-Functional Requirement
Non-Functional Requirement
Some Definitions:
• Interoperability is a characteristic of a product or system, whose
interfaces are completely understood, to work with other products
or systems.

• A legislature is a deliberative assembly with the authority to make


laws for a political entity such as a country or city.
Facebook Page:
https://www.facebook.com/SoftwareEngineeringYT
Thank You
Please Subscribe the channel

You might also like