http://tc.eserver.org/dir/Articles/Writing/Specifications/Functional-Specifications A listing of the most recently indexed works about Articles and Writing and Specifications and Functional Specifications in the field of technical communication (and technical writing). en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Articles/Writing/Specifications/Functional-Specifications http://tc.eserver.org/33952.html http://tc.eserver.org/33952.html When it comes to modern theater, stage directions—the descriptive text that appears within brackets in a script—are an important piece of the puzzle. They speak for the playwright when he is not there. They provide details about how the playwright has imagined the environment and atmosphere. They describe critical physical aspects of the characters and settings. Stage directions can also be critical in dictating the intended tempo and rhythm of the piece. Whether they establish a production’s overall tone or elucidate particular actions of characters, stage directions help tell the complete story that is in the playwright’s mind. Stage directions accomplish all of this, using a simple convention that structurally separates them from the actual story. http://tc.eserver.org/27764.html http://tc.eserver.org/27764.html What are pitfalls that companies should avoid when specifying Web applications for internal or external development? http://tc.eserver.org/27761.html http://tc.eserver.org/27761.html In general terms, the functional specification states what the proposed system is to do, whereas design is how the system is to be constructed to meet the functional specification. However in writing it, some consideration of design issues must take place, to ensure a realistic system is specified. http://tc.eserver.org/27762.html http://tc.eserver.org/27762.html A functional specification can substantially simplify and streamline the process of application development. Intended to describe how a piece of software works, it provides a ready reference for software developers andaligns large and disparate development teams to a single goal. In the process, it provides technical clarity on how the different components of aparticular applications are to be designed, implemented and integrated witheach other, and (if used correctly) significantly reduces the time and costcomponent of any development exercise. http://tc.eserver.org/27757.html http://tc.eserver.org/27757.html A functional specification (or sometimes functional specifications) is a formal document used to describe in detail for software developers a product's intended capabilities, appearance, and interactions with users. The functional specification is a kind of guideline and continuing reference point as the developers write the programming code. (At least one major product development group used a "Write the manual first" approach. Before the product existed, they wrote the user's guide for a word processing system, then declared that the user's guide was the functional specification. The developers were challenged to create a product that matched what the user's guide described.) Typically, the functional specification for an application program with a series of interactive windows and dialogs with a user would show the visual appearance of the user interface and describe each of the possible user input actions and the program response actions. A functional specification may also contain formal descriptions of user tasks, dependencies on other products, and usability criteria. Many companies have a guide for developers that describes what topics any product's functional specification should contain. http://tc.eserver.org/27760.html http://tc.eserver.org/27760.html The Functional Specification is created after the Software Requirements Document. It provides more detail on selected items originally described in the Software Requirements Document. Some software development organizations combine these two documents into a single document. http://tc.eserver.org/27759.html http://tc.eserver.org/27759.html Don't write a functional specifications document. Why? Well, there's nothing functional about a functional specifications document. http://tc.eserver.org/27756.html http://tc.eserver.org/27756.html When you design a product, inside and out, the most important thing is to nail down the user experience. What are the screens, how do they work, what do they do. Later, you worry about how to get from here to there. There's no use arguing about what programming language to use before you've decided what your product is going to do. In this series, I'm only talking about functional specifications.