Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Junilu Lacar
  • Martin Vashko
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Scott Selikoff
  • salvin francis
  • Piet Souris

Diffrence between High Level Desgin and Low Level Design Document

 
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What is the diffrence between low level design and high level design document.
whether high level desgin (hld ) consist only class and sequence diagram.
And a low level document(lld) consist each class thorough description which includes
method and property name and every possible details.
Also can anbody explain me diffrence between fine grained object and coarse grained objects ?


Thanks in Advance

Raja
 
Ranch Hand
Posts: 96
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
High level design means abstract view of the system ..... details are not shown... yes high level design does contain class diagram at conceptual level no operations are defined ...... while low level design uses class diagram at implementation level with most of the required detail.

I thing coarse grained refers too ... high level design
and fine grained refers too ... low level design.
 
author
Posts: 608
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, that's one way to look at it. At High-Level Domain Model and Detailed PDM I show examples of high-level and low-level data models. The issue is the amount of detail that you show. In the essay containing the two examples, I show how you start with high-level requirements and domain models and then evolve your design through six iterations.

- Scott
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A smart-aleck (or maybe practical) answer is that each artifact is whatever the reader asked for or needs. Who's reading it? What do they want to know? Why? Producing a document to some template so it can be filed forever is not much fun no matter how beautiful the doc.
 
A wop bop a lu bop a womp bam boom! Tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!