Requirements analysis in LLD - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the primary stakeholder in requirements analysis.

LLD

primary_stakeholder = '[1]'

Drag options to blanks, or click blank then click option'

Aserver

Bdatabase

Cend_user

Dnetwork

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing technical components like server or database as stakeholders.

The primary stakeholder in requirements analysis is the end user who will use the system.

2fill in blank

medium

Complete the code to define the first step in requirements analysis.

LLD

first_step = '[1]'

Drag options to blanks, or click blank then click option'

Atest_system

Bdesign_architecture

Cwrite_code

Dgather_requirements

Attempts:

3 left

💡 Hint

Common Mistakes

Starting with design or coding before understanding requirements.

The first step in requirements analysis is to gather requirements from stakeholders.

3fill in blank

hard

Fix the error in the code to correctly represent a requirement type.

LLD

requirement_type = '[1]'

Drag options to blanks, or click blank then click option'

Afunctional

Bhardware

Cnetwork

Ddatabase

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing functional requirements with technical components.

Functional requirements describe what the system should do.

4fill in blank

hard

Fill both blanks to complete the requirement gathering process.

LLD

requirements = [1](stakeholders) and [2](requirements)

Drag options to blanks, or click blank then click option'

Ainterview

Bcompile

Cdeploy

Dtest

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing deployment or testing steps with gathering requirements.

Requirements are gathered by interviewing stakeholders and then compiling the collected data.

5fill in blank

hard

Fill all three blanks to define the key outputs of requirements analysis.

LLD

outputs = { 'requirements_document': '[1]', 'use_cases': '[2]', 'validation_plan': '[3]' }

Drag options to blanks, or click blank then click option'

Acomplete

Bdetailed

Capproved

Ddraft

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'draft' instead of 'approved' for validation plan.

The requirements document should be complete, use cases detailed, and the validation plan approved for a successful analysis.

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