Home arrow Practices arrow Page 8 - Writing A Functional Specification

Hitting The High Notes - Practices

Writers hate coding, and developers hate writing. And never thetwain shall meet...except, perhaps, in a functional specification. More,inside.

TABLE OF CONTENTS:
  1. Writing A Functional Specification
  2. Getting Formal
  3. Of Time And Talent
  4. Laying The Foundations
  5. I, User
  6. The Screening Process
  7. The Color Purple
  8. Hitting The High Notes
  9. Sealed With A Kiss
By: Deepa L, (c) Melonfire
Rating: starstarstarstarstar / 73
April 25, 2003

print this article
SEARCH DEV SHED

TOOLS YOU CAN USE

advertisement
At this point, you have all the information needed to begin writing thefunctional specification. Here's a list of the high notes - make sure youhit them all!

* A very, very important rule of creating specifications is to be consistentand extremely precise in your use of words. For example, if you're using theword "function" to indicate the, well, functions of your software, youshouldn't at any point switch to "features", "commands", "menu items" or"actions". To this end, make yourself a glossary of the terms that you'regoing to use right at the start, and stick to them consistently. Add thisglossary to the end of your specification so that your readers have a readyreference, and to ensure that developers can communicate with each otherusing the right words.

* Conventions in the document lead to patterns that the users can grasp.They then start expecting information in a particular format, thusincreasing their level of comfort with the document. Using consistent stylesalso speeds up assimilation of the information, and helps spot particularinformation easily on re-reads.

* Headings are a powerful tool in making a huge mass of text lookmanageable. A common model is that as you go deeper in a particular topic,you indicate that by descending prominence of headings. So, all top levelheadings will be, say, in a large font size and bold typeface, with the nextlevel taking a smaller font size, and so on. You might also want to numberthe headings to help users understand the grouping of information.

* Use bullets and numbering to break up complex concepts into simpler,smaller information nuggets. The convention here is to use numbering forsequential information only and bullets for information that is bestpresented in points instead of a paragraph. Bullets also allow you to grouptogether points related to a concept and ascribe them levels of importance.

* Use screen grabs, schematics or flow diagrams to increase the efficacy ofyour document. Since a functional specification also includes information onwhat the user will see in the application, it will include schematics,screen flow diagrams and sample screens. These screen grabs will be used bythe developers to ensure that the final product conforms to what has beendecided in the specification. Ensure that you are consistent in your usageand labeling of screenshots.

* Ensure that nothing is left open to interpretation. Since this documentwill be used as a guideline for the actual implementation of theapplication, it's important that it be clear, concise and accurate at alltimes. Ambiguity and a failure to resolve troublesome points are sure signsof trouble in the future.

 
 
>>> More Practices Articles          >>> More By Deepa L, (c) Melonfire
 

blog comments powered by Disqus
escort Bursa Bursa escort Antalya eskort
   

PRACTICES ARTICLES

- Calculating Development Project Costs
- More Techniques for Finding Things
- Finding Things
- Finishing the System`s Outlines
- The System in So Many Words
- Basic Data Types and Calculations
- What`s the Address? Pointers
- Design with ArgoUML
- Pragmatic Guidelines: Diagrams That Work
- Five-Step UML: OOAD for Short Attention Span...
- Five-Step UML: OOAD for Short Attention Span...
- Introducing UML: Object-Oriented Analysis an...
- Class and Object Diagrams
- Class Relationships
- Classes

Developer Shed Affiliates

 


Dev Shed Tutorial Topics: