Practices
  Home arrow Practices arrow Page 2 - Writing A Functional Specification
Dev Shed Forums 
Administration  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Forums Sitemap 
IBM® developerWorks 
Dedicated Servers 
E-Commerce Hosting 
Linux Web Hosting 
Managed Hosting 
Small Business Hosting 
Download TestComplete 
VPS Hosting 
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
PRACTICES

Writing A Functional Specification
By: Deepa L, (c) Melonfire
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 47
    2003-04-25

    Table of Contents:
  • Writing A Functional Specification
  • Getting Formal
  • Of Time And Talent
  • Laying The Foundations
  • I, User
  • The Screening Process
  • The Color Purple
  • Hitting The High Notes
  • Sealed With A Kiss

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
     
    ADVERTISEMENT

    Route your faxes to your email inbox. Private, secure fax numbers available from CallWave. Choose your fax number.

    Writing A Functional Specification - Getting Formal
    (Page 2 of 9 )

    According to http://www.whatis.com/, a functional specification is "...aformal document used to describe in detail for software developers aproduct's intended capabilities, appearance, and interactions withusers...". Webopedia at http://www.webopedia.com/has a similar definition- it calls a functional specification "...a formal description of a softwaresystem that is used as a blueprint for implementing the program...".

    A functional specification is written primarily for the development team,with the objective of providing the members of that team with all theinformation they need to begin designing an application. It aims atoutlining the entire experience of the application, without really gettinginto the details of implementation, thereby providing the developers with acomprehensive knowledge base and reference for any and all questionsconcerning the project. The idea here is for the kinks in the design to beworked out at a conceptual level, and (more importantly) for the customer toget a clear idea of what the deliverable is and how it will work.

    Once finalized and approved by the customer, the functional specificationcan be used by a software developer to create a detailed software designdocument, which contains high-level architectural diagrams of the system,together with descriptions of the components used and their relationshipsvia a modeling language. Application development then becomes a matter ofimplementing what has been frozen in the specification.

    The level of detail in this document varies from project to project andcompany to company, and depends on the level of complexity inherent in theproject, and the amount of time and staff available to compile the dataobtained into a structured report. If you're an independent developer or aproject manager with a small team, you might prefer a smaller, simplerdocument; if, on the other hand, you have a full-fledged team behind you,work in a large, process-driven organization and/or have a complex projectto tackle, you might prefer a document that drills down to the very lastlevel of detail.

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


     

       

    PRACTICES ARTICLES

    - 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
    - Basic Ideas
    - Choosing the Right Team
    - Trees
    - Basic Array Searching in C++

     
    Accelerating Trading Partner Performance
     
    Competing on Analytics
     
    Cost Effective Scaling with Virtualization and Coyote Point Systems
     
    Five Checkpoints to Implementing IP Telephony
     
    Hosted Email Security: Staying Ahead of New Threats
     




    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 4 hosted by Hostway