File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes OO, Patterns, UML and Refactoring and the fly likes Diffrence between High Level Desgin and Low Level Design Document Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Make it so: Java DB Connections & Transactions this week in the JDBC forum!
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "Diffrence between High Level Desgin and Low Level Design Document" Watch "Diffrence between High Level Desgin and Low Level Design Document" New topic

Diffrence between High Level Desgin and Low Level Design Document

Neha Dhaka

Joined: Aug 30, 2005
Posts: 29
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

Hussain Fakhruddin
Ranch Hand

Joined: Aug 13, 2004
Posts: 96
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.

Hussain Fakruddin<br /> <br /><b>IBM 486-OOAD with UML</b>
Scott Ambler
Ranch Hand

Joined: Dec 12, 2003
Posts: 608
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

<a href="" target="_blank" rel="nofollow">Scott W. Ambler</a><br />Practice Leader Agile Development, IBM Rational<br /> <br />Now available: <a href="" target="_blank" rel="nofollow">Refactoring Databases: Evolutionary Database Design</a>
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
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 good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
I agree. Here's the link:
subject: Diffrence between High Level Desgin and Low Level Design Document
It's not a secret anymore!