HLD & LLD

The HLD stands for High-Level Design, where the designer will
only focus on the various models, like:

 Decision Tables
 Decision Trees
 Flow Diagrams
 Flow Charts
 Data Dictionary
o The solution architect develops the High-level design, which is
used to specifies the complete description or architecture of the
application.

o The HLD involves system architecture, database design, a brief

description of systems, services, platforms, and relationships
among modules.
 Introduction
• The Software Development Life Cycle (SDLC) goes
through various phases like planning, requirements
assessment, analysis, design, execution,
documentation, testing, etc. Each phase is further
divided into tasks with properly defined objectives
and results.

• Analysis and Design are phases where the actual

architecture, working model, and execution process
of building a software product is laid down.
 HLD
•  The high level design is a general system of
design.
• In simpler words, it refers to the overall design
of a system and describes the overall
architecture/ description of any application.
• It is also called system/ macro-level design.
 High-Level Design (HLD) provides a comprehensive overview of
the software development process along with the system
architecture, applications, database management, and complete
flowchart of the system and navigation.
 It’s a blueprint that consolidates the various steps and modules,
their objectives, variable components, results, architecture, and
timeline to develop the software.
 HLD translates a business plan into a software product or service.

o Examples of HLD in software development include system

architecture documents, app development flowcharts, etc.
 Purpose of HLD
• The high-level design defines the project level
architecture of the system.
• This architecture defines the sub-systems to be
built, internal and external interfaces to be
developed, and interface standards identified.
• The high level design is where the sub-system
requirements are developed.
LLD
• Low-Level Design (LLD) deals with the
planning, coding, and execution of the various
components, modules, and steps in the HLD,
at an individual level. Each module in an HLD
has a unique LLD document that provides
comprehensive details about how the module
will be coded, executed, tested for quality, and
integrated into the larger program. LLD
provides actionable plans by deconstructing
HLD components into working solutions.
S.NO Comparison Basis HLD LLD
.
1. Stands for It stands for High-Level Design. It stands for Low-Level Design.
2. Definition It is the general system design, which means it It is like describing high-level design, which
signifies the overall system design. means it signifies the procedure of the
component-level design.
3. Purpose The HLD states the concise functionality of LLD states the particular efficient logic of the
each component. component.
4. Also, known as HLD is also called a System or macro-level LLD is also called details or micro-level design.
design.
5. Developed by Solution Architect prepares the High-Level Designer and developer prepare the Low-Level
Design. Design.
6. Sequential order in It is developed first in sequential order, which It is developed after High-level design.
the design phase implies that the HLD is created before the
LLD.
7. Target Audience It is used by management, program, and It is used by designers, operation teams, and
solution teams. implementers.
8. Conversion The HLD changes the client or business The LLD changes the high-level solution to a
requirement into a high-level solution. comprehensive solution.

9. Probable output The high-level design is necessary to A low-level design is required for creating the
understand the flow across several system configurations and troubleshooting inputs.
objects.
10. Input Criteria The input measure in high-level design is SRS The input measure in low-level design is the
(Software Requirement Specification). reviewed HLD (High- Level Design).

11. Output Criteria The output measures in the HLD are The output bases in the low-level design are the
functional design, database design, and review unit test plan and program specification.
record.