Requirements gathering (functional and non-functional) in HLD - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are functional requirements in system design?

Functional requirements describe what the system should do. They specify the features, behaviors, and functions the system must have to meet user needs.

beginner

Define non-functional requirements with an example.

Non-functional requirements describe how the system performs its functions. Examples include performance, security, usability, and reliability.

intermediate

Why is it important to gather both functional and non-functional requirements?

Gathering both ensures the system not only works correctly but also meets quality standards like speed, security, and user experience.

beginner

List three common methods used to gather requirements.

1. Interviews with stakeholders 2. Surveys and questionnaires 3. Observation of current system or processes

intermediate

What is the difference between a use case and a user story in requirements gathering?

A use case describes detailed interactions between users and the system, while a user story is a short, simple description of a feature from the user's perspective.

Which of the following is a functional requirement?

A The system must allow users to reset their password.

B The system should load pages within 2 seconds.

C The system must be available 99.9% of the time.

D The system should encrypt user data.

Functional requirements describe what the system does, such as allowing password resets.

Non-functional requirements usually focus on:

A Features and functions

B User interface design only

C System performance and quality attributes

D Database schema

Non-functional requirements focus on qualities like performance, security, and reliability.

Which method is NOT typically used for requirements gathering?

A Stakeholder interviews

B Code refactoring

C Surveys

D Observation

Code refactoring is a development activity, not a requirements gathering method.

A user story usually includes:

A Detailed technical specifications

B System deployment plan

C Database design diagrams

D A short description of a feature from the user's perspective

User stories are brief descriptions of features from the user's point of view.

Why should non-functional requirements be gathered early?

A They affect system architecture and design decisions

B They are less important and can be added later

C They only impact user interface colors

D They are only needed for testing

Non-functional requirements influence key design choices and system architecture.

Explain the difference between functional and non-functional requirements with examples.

Think about what the system does versus how well it does it.

Describe three methods to gather requirements and why they are useful.

Consider how you would learn what users need.