The document discusses requirements analysis for software development projects based on the IEEE standard. It defines functional requirements as describing system behaviors that support user goals and non-functional requirements as including system constraints and qualities. Examples are given of both functional and non-functional requirements. The process of requirements analysis involves collecting both types of requirements and distinguishing between them.

1. Requirements
Analysis

2. IEEE-Standard 610.12 (1990)

3. Learning Objective
To analyze the requirements of the solution you are working on
To collect both the functional requirements (FR) and non-functional
requirements (NFR)

6. Process

7. Approach

8. Levels of software
requirements

10. Origin of

12. Skill

13. another RD Process

14. Define Requirement
Functional Requirement
Functional requirements describe the behaviors (functions or services) of the
system that support user goals, tasks or activities
Non-Functional Requirement
Non-functional requirements include constraints and qualities
[System] qualities are properties or characteristics of the system that its
stakeholders care about and hence will affect their degree of satisfaction
with the system.

16. Examples of Requirements
The product will support multiple human languages
The persistence will be handled by a relational database
The database will be Oracle 8i
The system will run 7 days a week, 24 hours a day
An online help system is required
All presentation logic will be written in Visual Basic

27. FR vs NFR

28. Deriving NFR