HLD Full Form

What is the full form of HLD?

HLD stands for High-Level Design. HLD is a general system design used to explain the architecture to help us build a system. It is also known as macro-level Design or macro-system design. A solution architect develops it and converts the Business and client requirement into a High-Level Solution. It also describes the overall description and architecture of the application. The architecture diagram helps us provide a prototype of an entire system and identify the main components that need to be developed for the product and its interfaces. HLD includes a description of system architecture, database design, and a brief description of systems, services, platforms, and module relationships. HLD uses almost a low amount of technical terms or no technical terms that should be understandable to the system's administration. HLD applies to both software as well as hardware.

This Story also Contains

1. What is the full form of HLD?
2. 1. Purpose of High-Level Design (HLD)
3. 2. Characteristics of High-Level Design (HLD)
4. 3. High-Level Design (HLD) Overview
5. 4. High-Level Design (HLD) Requirements
6. 5. During Which Phase of The Project is High-Level Design (HLD) Created
7. 6. High-Level Design (HLD) Making Responsibilities

1. Purpose of High-Level Design (HLD)

The purpose of the High-Level Design (HLD) Document is to append the details description which is necessary to represent a model. The Design of the HLD document helps with operational requirements. It can be used as a reference manual of how modules interact.

During the initial stages of development of a project, we need to identify those parts of the project which are risky and very time-consuming. Therefore, HLD briefly describes how the sub-systems and system components work together.

2. Characteristics of High-Level Design (HLD)

• HLD presents all design aspects and explains them in diagrammatic form.

• It expresses the brief functionality of each module.

• It describes the hardware and software interface and also gives information about the user interface implemented.

• The input criteria in HLD is Software Requirement Specification (SRS).

• The output criteria in HLD are database design, functional Design, and review record.

• HLD includes the architecture and design features of the project.

• It describes the user's daily work performance requirements and flow process.

3. High-Level Design (HLD) Overview

• A high-level design overviews the product, service, and process.

• This overview helps in supporting components to become compatible with others.

• High-Level Design describes all platforms, systems, services, products, and processes on which it depends. It also includes the changes that are required to make to them.

• HLD includes the architecture and design features of the project.

• It also describes the performance requirements and daily flow of a process for the user.

• Nowadays, High-Level Design requires contributions from many experts who represent their respective professional disciplines.

• Ultimately, every type of end-user should be identified in High-Level Design, and each contributing Design should be considered for the customer experience.

4. High-Level Design (HLD) Requirements

• Since HLD describes various things such as platforms, services, and processes, the flow of traffic on which it depends and includes significant changes that need to be made to them.

• HLD is the input for creating Low-Level Design (LLD) because the essential communication items are displayed in HLD that are further converted to elaborated communication in LLD to show connectivity and physical level.

• Thus, HLD requires contributions from several experts who represent many distinct professional disciplines, such as Design Architecture and Subject Matter Expertise (SME).

• HLD is required during the Preliminary Design and Design overview.

5. During Which Phase of The Project is High-Level Design (HLD) Created

After knowing the project's requirements, and when an overview of the overall solution and system components communication needs to be emptied, this is where High-Level Design (HLD) is created.

High-Level Design is the input for Low-Level Design creation.

The available information in HLD is the guiding principle for the LLD, which it needs to demonstrate in detail.

6. High-Level Design (HLD) Making Responsibilities

The responsibilities for making the HLD are in the hands of Solution architects. Solution Architects build HLD, and then Subject Matter experts (SMEs) or some designers work to create Low-Level designs (LLD) according to the guidelines of HLD. LLD will enclose the information related to understanding the traffic flow, creating network topology, IP(Internet Protocol) addresses, VLANs(virtual local area network ), and naming conventions of devices in an organization for smooth troubleshooting and running operations.