HTTP/2 302 server: nginx date: Tue, 15 Jul 2025 19:33:49 GMT content-type: text/plain; charset=utf-8 content-length: 0 x-archive-redirect-reason: found capture at 20080615163111 location: https://web.archive.org/web/20080615163111/https://www.mojofat.com/tutorial/ server-timing: captures_list;dur=0.829653, exclusion.robots;dur=0.039588, exclusion.robots.policy;dur=0.022951, esindex;dur=0.020838, cdx.remote;dur=158.760397, LoadShardBlock;dur=505.982070, PetaboxLoader3.datanode;dur=218.960923, PetaboxLoader3.resolve;dur=208.436633 x-app-server: wwwb-app202 x-ts: 302 x-tr: 728 server-timing: TR;dur=0,Tw;dur=0,Tc;dur=1 set-cookie: SERVER=wwwb-app202; path=/ x-location: All x-rl: 0 x-na: 0 x-page-cache: MISS server-timing: MISS x-nid: DigitalOcean referrer-policy: no-referrer-when-downgrade permissions-policy: interest-cohort=() HTTP/2 200 server: nginx date: Tue, 15 Jul 2025 19:33:50 GMT content-type: text/html x-archive-orig-date: Sun, 15 Jun 2008 16:31:11 GMT x-archive-orig-server: Apache/1.3.41 (Unix) mod_log_bytes/1.2 mod_bwlimited/1.4 mod_auth_passthrough/1.8 FrontPage/5.0.2.2635 mod_ssl/2.8.31 OpenSSL/0.9.7a x-archive-orig-last-modified: Sun, 12 Nov 2006 22:30:19 GMT x-archive-orig-etag: "f4d28c-198c-4557a07b" x-archive-orig-accept-ranges: bytes x-archive-orig-content-length: 6540 x-archive-orig-connection: close x-archive-guessed-content-type: text/html x-archive-guessed-charset: utf-8 memento-datetime: Sun, 15 Jun 2008 16:31:11 GMT link: ; rel="original", ; rel="timemap"; type="application/link-format", ; rel="timegate", ; rel="first memento"; datetime="Thu, 12 Apr 2001 01:19:22 GMT", ; rel="prev memento"; datetime="Tue, 13 May 2008 12:41:34 GMT", ; rel="memento"; datetime="Sun, 15 Jun 2008 16:31:11 GMT", ; rel="next memento"; datetime="Fri, 27 Jun 2008 15:53:24 GMT", ; rel="last memento"; datetime="Tue, 18 Jun 2024 22:20:59 GMT" content-security-policy: default-src 'self' 'unsafe-eval' 'unsafe-inline' data: blob: archive.org web.archive.org web-static.archive.org wayback-api.archive.org athena.archive.org analytics.archive.org pragma.archivelab.org wwwb-events.archive.org x-archive-src: 51_4_20080615155350_crawl109-c/51_4_20080615162717_crawl100.arc.gz server-timing: captures_list;dur=0.721007, exclusion.robots;dur=0.034069, exclusion.robots.policy;dur=0.020489, esindex;dur=0.014023, cdx.remote;dur=53.986590, LoadShardBlock;dur=350.203876, PetaboxLoader3.datanode;dur=411.836731, load_resource;dur=607.178932, PetaboxLoader3.resolve;dur=445.275063 x-app-server: wwwb-app202 x-ts: 200 x-tr: 1082 server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0 x-location: All x-rl: 0 x-na: 0 x-page-cache: MISS server-timing: MISS x-nid: DigitalOcean referrer-policy: no-referrer-when-downgrade permissions-policy: interest-cohort=() content-encoding: gzip

Introduction Define The Application Develop Models Define Information Flow Create Wireframes Draft Design Document Write Functional Spec Edit & Rewrite Conclusion & Resources Print Friendly Version

What Is A Functional Specification? Functional specifications (functional specs), in the end, are the blueprint for how you want a particular web project or application to look and work. It details what the finished product will do, how a user will interact with it, and what it will look like. By creating a blueprint of the product first, time and productivity are saved during the development stage because the programmers can program instead of also working out the logic of the user-experience. It will also enable you to manage the expectations of your clients or management, as they will know exactly what to expect. Why write a Functional Spec? A key benefit of writing up a Functional Spec is in streamlining the development process. The developer working from the spec has, ideally, all of their questions answered about the application and can start building it. And since this is a spec that was approved by the client, they are building nothing less than what the client is expecting. There should be nothing left to guess or interpret when the spec is completed...and this, in a nut, explains my love affair with the Functional Spec. Joel on Software has a very good analysis of why Functional Specs should be written. Who writes a Functional Spec? The functional spec should be written by someone who is not involved in any other aspect of the project. You will want somebody who is very familiar with user-interface issues and web design, familiar enough with technology to know its limitations and capabilities, and someone who is a very skilled and detailed writer. While writing a spec, you will spend much of your time imagining how a user might use a certain feature and how they may navigate their way through the information. Not only do you need to map this world out visually, but you also have to write out in great detail what this world does; all the while, balancing everything within the current technological limitations and business demands. The functional spec writer's sole concern is marrying the user-experience with the various departmental, business, and technical requirements of the project. Next