As an application engineer, we invest great deal of the time reading and writing design papers. After having been through a huge selection of these docs, I’ve seen very first hand a powerful correlation between good design docs and also the ultimate success of the task.
This informative article is my effort at describing why is a design document great.
This article is split up into 4 parts:
- Why compose a design document
- What things to use in a design document
- Just how to compose it
- The method around it
Why compose a design document?
A design doc — also referred to as a technical spec — is just a description of the manner in which you want to re solve a challenge.
There are several writings currently on why it is essential to create a design doc before diving into coding. Therefore all I’ll say let me reveal:
A design doc is one of tool that is useful making certain the proper work gets done.
The definitive goal of the design doc will be cause you to more efficient by forcing you to definitely consider the style and gather feedback from other people. Individuals frequently think the purpose of a design doc would be to to instruct other people about some system or act as paperwork later on. While those could be useful negative effects, they’re not the objective in and of by themselves.
In most cases of thumb, you should write a design doc if you are working on a project that might take 1 engineer-month or more. Read more