Requirements analysis in LLD - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Identify the primary goal of requirements analysis

What is the main purpose of performing requirements analysis in system design?

A To gather and understand what users need from the system

B To write the final code for the system

C To deploy the system to production

D To test the system for bugs

💡 Hint

Think about what happens before coding starts.

Requirements analysis is about understanding user needs and system goals before building anything.

❓ Architecture

intermediate

Choosing the right stakeholders for requirements gathering

Which group is most important to involve during requirements analysis to ensure the system meets user needs?

A Only the software developers

B System administrators only

C End users who will use the system daily

D Marketing team only

💡 Hint

Who uses the system the most?

End users provide the most relevant information about what the system should do.

❓ scaling

advanced

Handling changing requirements in a large system

In a large system project, requirements often change. What is the best approach to handle this during requirements analysis?

A Only update requirements once a year

B Freeze all requirements at the start and do not allow changes

C Ignore changes until after deployment

D Use an iterative process that revisits requirements regularly

💡 Hint

Think about flexibility and adapting to new information.

An iterative approach allows the team to adapt to changes and improve the system continuously.

❓ tradeoff

advanced

Balancing detail and speed in requirements analysis

What is a common tradeoff when deciding how detailed the requirements analysis should be?

A Less detail always leads to better system design

B More detail takes more time but reduces misunderstandings later

C Skipping requirements saves time without risks

D Detailed requirements slow down development with no benefits

💡 Hint

Think about the cost of fixing mistakes later.

Detailed requirements take time but help avoid costly errors during development.

❓ estimation

expert

Estimating time for requirements analysis phase

If a project has 10 major features and each feature requires about 3 days of requirements analysis, plus 5 days for integration and review, what is the total estimated time for the requirements analysis phase?

A 35 days

B 30 days

C 25 days

D 40 days

💡 Hint

Multiply features by days per feature, then add review days.

10 features × 3 days = 30 days + 5 days review = 35 days total.

Practice

1. What is the main purpose of requirements analysis in system design?

easy

A. To deploy the system to users

B. To write the system code

C. To test the system performance

D. To define what the system must do

Solution

1. Step 1: Understand the role of requirements analysis

   Requirements analysis focuses on understanding and defining the system's needs and functions.

2. Step 2: Differentiate from other phases

   Writing code, testing, and deployment happen after requirements are clear.

3. Final Answer:

   To define what the system must do -> Option D

4. Quick Check:

   Requirements analysis = Define system needs [OK]

Hint: Requirements analysis = What system must do [OK]

Common Mistakes:

• Confusing requirements analysis with coding
• Thinking testing is part of requirements
• Mixing deployment with requirements gathering

2. Which of the following is a correct step in requirements analysis?

easy

A. Writing deployment scripts

B. Compiling source code

C. Gathering user needs

D. Running system tests

Solution

1. Step 1: Identify key activities in requirements analysis

   Gathering user needs is essential to understand what the system should do.

2. Step 2: Exclude unrelated activities

   Deployment scripts, compiling code, and testing happen after requirements are set.

3. Final Answer:

   Gathering user needs -> Option C

4. Quick Check:

   Requirements analysis = Gather needs [OK]

Hint: Gather user needs first in requirements analysis [OK]

Common Mistakes:

• Mixing coding or deployment with requirements
• Ignoring user input during analysis
• Confusing testing with requirements gathering

3. Given these requirements:
- System must handle 1000 users simultaneously
- Data must be encrypted
- Users can reset passwords
Which requirement type is "Data must be encrypted"?

medium

A. Non-functional requirement

B. Functional requirement

C. Business requirement

D. User interface requirement

Solution

1. Step 1: Classify the requirement "Data must be encrypted"

   This describes a quality or constraint on the system, not a specific function.

2. Step 2: Understand requirement types

   Functional requirements describe actions; non-functional describe qualities like security.

3. Final Answer:

   Non-functional requirement -> Option A

4. Quick Check:

   Encryption = Non-functional requirement [OK]

Hint: Security needs are non-functional requirements [OK]

Common Mistakes:

• Confusing security with functional features
• Mixing business goals with technical details
• Assuming all requirements are functional

4. A requirements document states: "Users must login with username and password." Later, it says: "Users can login using email and password." What is the main issue here?

medium

A. Performance bottleneck

B. Ambiguous requirements

C. Security vulnerability

D. Scalability problem

Solution

1. Step 1: Identify conflicting statements

   The document gives two different login methods without clarifying which is correct.

2. Step 2: Understand impact of ambiguity

   Ambiguous requirements confuse developers and cause design errors.

3. Final Answer:

   Ambiguous requirements -> Option B

4. Quick Check:

   Conflicting login info = Ambiguity [OK]

Hint: Conflicting info means ambiguous requirements [OK]

Common Mistakes:

• Assuming security or performance issues without evidence
• Ignoring requirement conflicts
• Thinking scalability relates to login methods

5. You are designing a messaging app. Which of these is the best way to gather requirements to ensure scalability and user satisfaction?

hard

A. Interview users, analyze competitors, and document clear functional and non-functional needs

B. Start coding immediately based on your assumptions

C. Only focus on UI design without backend planning

D. Ignore user feedback and add features later

Solution

1. Step 1: Identify best practices in requirements gathering

   Interviewing users and analyzing competitors helps understand real needs and market standards.

2. Step 2: Emphasize clear documentation of all requirements

   Clear functional and non-functional requirements guide scalable and user-friendly design.

3. Final Answer:

   Interview users, analyze competitors, and document clear functional and non-functional needs -> Option A

4. Quick Check:

   User research + clear docs = good requirements [OK]

Hint: Gather user input and document clearly before coding [OK]

Common Mistakes:

• Skipping user research
• Starting development without clear requirements
• Ignoring backend needs for scalability