Jump to content

Low-level design

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Saurabhdverma (talk | contribs) at 12:51, 22 June 2015 (Created page with '<!--- Don't mess with this line! --->{{New unreviewed article|date={{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}}} <!--- Write your article below this line --...'). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

Template:New unreviewed article

Low Level Design (LLD) is a component level design process that follows a process of step wise refinement may be used for the design of data. That is, overall data organization may be a defined during requirement analysis, refined during data design work, and then each component is specified in detail.[1]

Low Level Design (LLD) is like detailing the High-Level Design(HLD). The low-level design (LLD) phase is where the actual software components are designed. During the detailed phase the logical and Functional design is done of application structural design that is developed during the high level design phase.

Design phase

A Design is structure of system good design is important to achieve high reliability, Low cost and good maintainability.[2] We can distinguish two type of program design phase. • Architectural or high-Level design • Detailed or Low-level design


Purpose

The goal of Low Level Design (LLD)|Low Level Design Document(LLDD) is to give the internal Logic design of the actual program code which is designed based on the High Level Design. LLD describes the Class diagrams with all the methods, relation between classes and Programs specs, It describes each and every module in an elaborate manner so that the programmer can directly code the program based on it.

A good Low Level Design Document developed will make the program very easy to be developed by developers, because if proper analysis is made and the Low Level Design Document is prepared then the code can be developed by developers directly from Low Level Design Document with minimal effort of debugging and testing.

Sample

An example is provided of HLD:Sample HLD, after iterations which is developed as LLD:Sample LLD

References

  1. ^ Software Engineering: A Practitioner’s Approach Roger S. Pressman
  2. ^ The Essence of Program Design: By Bell Stephen P., Douglas Bell, Ian Morrey, John Pugh
  • The Software Life Cycle: edited by Darrel Ince, Derek Andrews
  • The Essence of Program Design By Bell Stephen P., Douglas Bell, Ian Morrey, John Pugh