Bird
0
0
LLDsystem_design~12 mins

Requirements analysis in LLD - Architecture Diagram

Choose your learning style9 modes available
LearnWhyDeepArchPracticeChallengeDesignRecallScale
System Overview - Requirements analysis

Requirements analysis is the process of understanding what a system must do. It involves gathering, organizing, and defining the needs and constraints of users and stakeholders. This step ensures the system built will meet expectations and work well in real life.

Architecture Diagram
  +------------+      +----------------+      +----------------+
  |  Stakeholder| ---> | Requirements   | ---> | Requirements   |
  |  (User,    |      | Gathering Team |      | Analysis Team  |
  +------------+      +----------------+      +----------------+
                             |                        |
                             v                        v
                      +----------------+      +----------------+
                      | Requirements   | ---> | Requirements   |
                      | Documentation  |      | Validation &   |
                      | Repository     |      | Prioritization |
                      +----------------+      +----------------+
Components
Stakeholder
user
Provides needs and expectations for the system
Requirements Gathering Team
service
Collects raw requirements from stakeholders
Requirements Analysis Team
service
Organizes and clarifies gathered requirements
Requirements Documentation Repository
database
Stores all collected and analyzed requirements
Requirements Validation & Prioritization
service
Checks requirements for correctness and ranks them by importance
Request Flow - 5 Hops
Stakeholder → Requirements Gathering Team
Requirements Gathering Team → Requirements Analysis Team
Requirements Analysis Team → Requirements Documentation Repository
Requirements Validation & Prioritization → Requirements Documentation Repository
Requirements Validation & Prioritization → Requirements Documentation Repository
Failure Scenario
Component Fails:Requirements Documentation Repository
Impact:Loss or inaccessibility of requirements data, causing delays and confusion in development
Mitigation:Use backups and version control to restore data; implement access redundancy
Architecture Quiz - 3 Questions
Test your understanding
Who provides the initial needs and expectations in requirements analysis?
AStakeholder
BRequirements Analysis Team
CRequirements Documentation Repository
DValidation & Prioritization Service
Design Principle
This architecture shows the importance of clear roles and data flow in requirements analysis. Storing requirements centrally allows validation and prioritization, ensuring the system meets real user needs.