Creating a good and simple specification is a difficult task. Here are some tips to help you in creating good specifications.
# Keep your target audience in mind
# Don’t describe everything by yourself. You can borrow explanations from other specifications using appropriate hypertext.
# Avoid jargons and obscure language.
# Avoid excessive use of flow charts or diagrams. Sometimes, a good paragraph is better than a diagram.
# Keep old specifications which are good. Those may help you in describing a complicated concept or diagram.
# Use simple language to describe (complex) algorithms.
# Seek advices from others. Ask for better ways of understanding things.
When authoring specifications, information that is useful to both project manager and team must be separated. Hence, divide details of functionalities and issues or questions.
Now, who prepares the specifications? It is business analysts, clients, or project managers who create specifications often. The responsibility is given based on the nature of the project team as well as the responsible authority.
In large projects, project manager or designer is the person responsible for feature specifications and programmers for technical specifications. Usually, technical specifications are shorter as its audience is small in number. However, it should map to the supporting design in feature specifications. In small projects, generally the project manager or the lead programmer generates a single document containing all the four specifications.
Specifications communicate a set of intentions so that people know what they need to do exactly for the project. It helps the project manager in gathering useful information about project to accomplish its goals.
