What is System Design?

System design more about architecture. is the process of designing any software application . 
 It's called "design" but actually is We're building a new project's flow.

HLD (high-level design)

High-Level design is done by a solution architect to specify the general design 
 of a system or application. Purpose? 
 To transform the requirements of a client to a high-level solution. It's a no-code stage which is rather about technical documentation and diagrams.

It includes decision tables, decision trees, flow diagrams, flow charts, and a data dictionary.

LLD (low-level design)

Low-Level design is more about diving into details. You take the parts of high-level design and start going into specifying how they would be composed and coded.

It includes:

description of schemes for placement and connection of equipment ;

description of methods for installing software modules ; detailing the operating modes of individual components of the system.

High-Level design is the overall system design. It shows us the general design.

High-Level means macro-rank. HLD overall description/architecture of the application.

HLD is architect’s work.

High-Level design collects the design team, review team, and client team.

Low-Level design is a detail-level process

Low-Level means micro-rank. It is a detailed description of each and every module.

LLD is done by designers and developers.

Low-Level design participants bring together the design team, operation team, and coders.

The first thing created is high-level design. Low-Level design is done only after HLD step.

Why Not Go Straight to an LLD?

(thanks, cap) I

t necess ary to dedic ate so much effort before the general plan is not approved? We think you know the answer.

The HLD describes the big pictureLLD focuses on details , while the in the technic al and implementation sphere.