Chapter 3 of the document focuses on requirements determination in system analysis and design, emphasizing the transformation of high-level business needs into detailed system requirements. It outlines various types of requirements, such as business, user, functional, and nonfunctional requirements, and discusses techniques for requirements gathering. Key concepts include the necessity of creating use cases, process models, and a data model to ensure that the new system delivers value to the business.

1. System Analysis
and Design
Chapter 3: Requirements
Determination

3. At the end of this chapter:
●Apply requirements analysis techniques
(business process automation, business process
improvement, or business process
reengineering).
●Use requirements gathering techniques
(interview, questionnaire, document analysis, or
observation).
●Develop requirements definition.

4. Requirements Determination
- transform high-level business needs into a detailed
list of system requirements
- ensure the new system provides value to the
business
- Supporting Activities:
- Creating use cases
- Building process models
- Building a data model

5. What Is a Requirement?
- A statement of what the system must do or its
necessary characteristics.
- Written from the business perspective, focusing on
what users need to accomplish with the system.
Types of Requirements:
- Business Requirements
- User Requirements
- Functional Requirements
- Nonfunctional Requirements
- System Requirements

6. Functional Requirement
VS
Non-functional
Requirement

8. Functional Requirement
- What the software should do
Functional
Requirement
Description Examples
Process-oriented A process the system must
perform; a process the system
must do
The system should allow
students to view a course
schedule while
registering for classes.
Information-oriented Information the system must
contain
The system must include
real-time inventory levels at
all warehouses.

9. Nonfunctional Requirement
- characteristics the system should have
Nonfunctional
Requirement
Description Examples
Operational The physical and technical
environments in which the system
will operate
The system should be able to
work on any Web browser.
Performance The speed, capacity, and reliability of
the system
The system should be available
for use 24 hours per day, 365
days per year.
Security Who has authorized access to the
system under what circumstances
Customers can see their order
history only during business
hours.
Cultural and Political Cultural and political factors and legal
requirements that affect the system
Personal information is
protected in compliance with the
Data Protection Act.

10. Pretend that you received the following list of
requirements for a sales system:
1. restrict access to profitability information.
2. provide management reports.
3. include sales information that is updated at least
daily.
4. print subsidiary reports in the primary language of
the subsidiary.

11. FUNCTIONAL NONFUNCTIONAL

12. Requirements Elicitation
Techniques
- Interviews
- Questionnaires,
- Document Analysis
- Observations

13. Requirements
Elicitation Techniques
Interviews

14. Requirements
Elicitation Techniques
Interviews

15. Requirements Elicitation
Techniques
Questionnaires

16. Requirements Elicitation
Techniques
Document Analysis

17. Requirements Definition