How to Write an Effective Design Document » “Hello World” - T...
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
Bookmark History
Saved by 9 people (-1 private), first by anonymouse user on 2007-05-20
- Buckwoo on 2007-09-25 - Tags design , programming , development , documentation , software , delicous-export
- Eapen7 on 2007-06-20 - Tags designdoc , design , Programming , development , documentation , software , architecture , Reference , documents , webdev
- Colcord on 2007-06-18 - Tags Ruby
- Dashun on 2007-06-17 - Tags programming
- Quacrobat on 2007-06-14 - Tags design , dev , programming , documentation , software , reference , advice
Public Sticky notes
The process of designing before coding is becoming outdated. Documenting designs is becoming even rarer. Many developers have never written a design document and cringe at the idea of doing so. Many who are required to, typically generate a lot of interaction diagrams and class diagrams, which don’t often express the developer’s thought process during the design phase. This article will discuss how to do write an effective design document concisely with no special tools, and without needing to know UML. It will also discuss why a well written design document is one of the most valuable tools a developer can have when entering a new project.
Highlighted by joel
Public Comment