Scribd
Upload
1K views2 pages

Requirements Gathering Phase (HLD & LLD) in Data Warehouse Project Life Cycle

The requirements gathering phase in a data warehouse project life cycle involves business analysts interacting with clients to understand business needs and pain points in order to create requirements documents. Developers then use these documents to create high level designs (HLDs) and low level designs (LLDs). HLDs divide requirements into modules and provide overall system architecture and database design. LLDs provide detailed descriptions and logic for each module based on the HLD. Proof of concept models are also created for client approval.

Uploaded by

Syed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
1K views2 pages

Requirements Gathering Phase (HLD & LLD) in Data Warehouse Project Life Cycle

The requirements gathering phase in a data warehouse project life cycle involves business analysts interacting with clients to understand business needs and pain points in order to create requirements documents. Developers then use these documents to create high level designs (HLDs) and low level designs (LLDs). HLDs divide requirements into modules and provide overall system architecture and database design. LLDs provide detailed descriptions and logic for each module based on the HLD. Proof of concept models are also created for client approval.

Uploaded by

Syed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Requirements Gathering Phase(HLD & LLD) in Data Warehouse Project Life

Cycle
Business Analyst(BA): He is the person or a mediator between the client and
the organization.

First Business Analyst is going to interact with the client to know about
the client business and pain-areas, from that business analysis BA will
prepare the document called as Business requirement document
or BRD or FSD(Functional Specification document) or SPEC.

From the BRD,the development team will prepare the HLD and LLD.
HLD(High-level-design-document): Divide the BRD into different modules
for requirement analysis, prepared by developers. An HLD document is
prepared based on Business Requirement.
LLD(Low-level-design-document): Gives the detailed information about
each entity in the BRD or HLD, prepared by developers. It gives the details
descriptions of the each module in details which is completely based on HLD.

GAP Analysis: This is the comparison between client requirement and


reporting tool features like is the tool fulfill all the requirements of the
client or not.

POC(Proof of Concept): This is the dummy or a duplicate model


where the development team will cook the data manually and prepares
a sample model which is going to send for the client's approval.
Note: The end product should be same with the POC.
what are the major differences between HLD,DLD,LLD?
HLD -- High Level Design (HLD) is the overall system design - covering the system architecture
and database design. It describes the relation between various modules and functions of the
system. data flow, flow charts and data structures are covered under HLD.

High Level Design gives the overall System Design in terms of Functional Architecture details
and Database design. This is very important for the ETL developers to understand the flow of the
system with function and database design wise. In this phase the design team, testers and
customers are plays a major role. Also it should have projects standards, the functional design
documents and the database design document also.

LLD -- Low Level Design (LLD) is like detailing the HLD. It defines the actual logic for each
and every component of the system. Class diagrams with all the methods and relation between
classes comes under LLD. Programs specs are covered under LLD.

Low - Level Design (LLD) - This document is need to do during the detailed phase, the view of
the application developed during the high level design is broken down into separate modules and
programs for every program and then documented by program specifications.

DLD -- Detailed Level Design (DLD) -- DLDs are referring to a process known as top-down
design. In short, when you think about the problem you are trying to solve, you start at the
highest level and then work yourself into the details. This approach works very well when you
have an overall structure you want your application to live within. At the macro level you are
considering how many machines will be needed to host your application, which existing services
you will need to use, etc. As you dive deeper, you are looking at use cases (or user stories if you
prefer that terminology), and error handling (use cases have both normal and error condition
paths to worry about). As you go even further into the details, you are looking at your algorithm,
state transitions, logical sequence, and how internal parts of the code work together

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy