What Should A Technical Design Document Contain For A Software Project?
Posted by benny in FreeWare on December 1st, 2009 | 2 responses
I was looking for a comprehensive template for a Technical Design Document, would you happen to know what should a document contain and what should it not. Should a remote Programmer be able to develop the software just by using information from this document? Should it contain Activity Diagrams, or Flowcharts or algorithms? Thanks for your answer.
Popularity: 1% [?]
Related posts:
- How Do You Write A Technical Specification Document For A To Be Developed Software Application? I have never written a technical Specification document for...
- What Is The Best Software To Design Technical Catalog? i want to design a technical catalog for an industrial...
- What Do We Need To Document For A “new” Agile Software Project That Assumes A 5 Person Team,6 Month To Deliver What do we need to document and measure for a...
- What Software Should I Use For A Document To Send To A Mac User? I have a document in MS Word, and my friend...
- How Do I Write A Technical Paper For A New Software Algo? A friend of mine and I have been writing a...
Related posts brought to you by Yet Another Related Posts Plugin.
2 Responses to “What Should A Technical Design Document Contain For A Software Project?”
Leave a Reply
Basically, the main purpose of your technical design document is to make sure that the developers have each and every thing that they need to develop the application. This said, the technical design document should be written in a language which your developer can understand. And believe this differs from company to company… If your developer does not understand the UML, activity diagrams etc, there is no point in writing a technical design document with help of UML. But if your company follows this format and your developers are well versed with it, then you should go with it.
Most of the times technical design document is created in 2 parts. 1. High Level Design Document (HLDD), 2. Low Level Design Document (LLDD).
The HLDD contains the general overview of the architecture, components to be used in the program, details about the interaction with other applications, protocols to be used, security measure, reusable compon etc.
The LLDD contains every minute detail about the program that needs to be written like the database dictionary, method names, details of components, reusable components, how to reuse. Most importantly, it also contains the psuedo code as well.
Your basic objective is to lower the dependency of your developers on the technical architect/designer.
HTH, Regards.
Nachiket.
It should be designed using UML (unified modelling language)….. Rational rose, microsoft visio are some UML tools……..