What are the contents of High Level Design Document and Low Level Design Document ? How to start the Design Document? I would like to know for .Net with MS SQL Server and IIS. Please explain in detail .
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi,
Here are some links to other discussions you may have seen:
http://www.coderanch.com/t
http://www.linkedin.com/an
Template:
http://www.cmcrossroads.co
Just type 'high level design template' into Google and you will get plenty of hits, same for low level.
Cheers,
Darren
Business Accounts
Answer for Membership
by: DarrenDPosted on 2009-10-23 at 05:06:24ID: 25643534
Hi,
At this point you should have your requirements or most of them in a state that you know what you are going to build even though some of them might change during the development stage (if you are using an Agile methodology).
In UML you might use Use Case and Activity diagrams to show requirements.
In my opinion the High Level Design should show the system at a higher level of abstraction.
Basically what you are trying to show is HOW the system will be built, seperation of business tier, data tier and presentation tier.
You would show the classes (objects) that are needed to build each tier of the system and high level Entity Relationship Diagrams (ERD) or simply a listing of table names.
In UML you might use Class diagrams and Activity diagrams, Deployment diagrams, Package diagrams and Component diagrams to show HLD
The Low Level Deisgn should take the HLD to a lower level of abstraction where by the details of the classes and entitys are "Filled in". This shows in greater detail HOW the system will be built and will include all classes, fields, methods and signatures, interactions etc...
In UML you might use Interaction Diagrams (Sequence Diagrams) to show communication between objects in the LLD.
I know that I have used UML examples but you could simply create a document with class names for HLD and then with fields and methods for LLD.
Hope this helps,
Darren