A functional specification is the set of documentation that describes the requested behavior of an engineering system. The documentation typically describes what is needed by the system user as well as requested properties of inputs and outputs.
#33667
The Art of the Functional Spec
'The Art of the Functional Spec' is a forum for those of us responsible for writing functional specs. We'll discuss the basics of functional spec writing, offer tips, provide examples and respond to your feedback and questions.
Functional Spec (2009). Resources>Writing>Technical Writing>Specifications
#33952
Stage Directions Meet Functional Specifications: They Have a Lot in Common
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.
Lepore, Traci. UXmatters (2009). Articles>Writing>Technical Writing>Functional Specifications
#34276
This article describes several characteristics of high quality software requirement statements and specifications. We will examine some less-than-perfect requirements from these perspectives and take a stab at rewriting them. I’ve also included some general tips on how to write good requirements. You might want to evaluate your own project’s requirements against these quality criteria.
Wiegers, Karl E. Process Impact (2007). Articles>Project Management>Business Communication>Specifications
#34277
Introduction to Requirements: The Critical Details That Make or Break a Project 
Every project has requirements. It doesn't matter if it's building hardware solutions, developing software solutions, installing networks, protecting data, or training users. For the project to be a success, knowing what the requirements are is an absolute must. Requirements exist for virtually any components of a project or task. For example, a project may require specific methods, expertise levels of personnel, or the format of deliverables. This whitepaper will discuss the various kinds of information technology requirements, their importance, the different requirement types, the concept of requirements engineering, and the process for gathering requirements.
Frederick, Richard. Global Knowledge (2007). Articles>Project Management>Business Communication>Specifications
#34467
So What IS User Requirements Gathering?
Requirements gathering is all about aiming at the right target. It doesn't matter how accurate you are, if you aim at the wrong target, you miss.
Frontend Infocentre (2009). Articles>Usability>Research>Functional Specifications
#34496
Using Customer Tests to Drive Development
Test-driven development or TDD is a widely accepted practice used by agile software development teams of many flavors – not only Extreme Programming teams. For each small bit of functionality they code, programmers first write unit tests, then they write the code that makes those unit tests pass. TDD is seen as a design tool, since it forces the programmer to think about many aspects of each feature before coding.
Agile Journal (2009). Articles>User Centered Design>Agile>Functional Specifications
#35167
If you’re working with the latest technology, there may not be any user reference material at all; the only documentation available is the specification. In such a case, learning to read the spec is a necessity, not a luxury.
Eisenberg, J. David. List Apart, A (2009). Articles>Web Design>Standards>Specifications
#35178
Using Wikis to Document UI Specifications
The role of the interaction designer is to specify the interface’s behaviors and elements, so that engineers know what to build and how the product should operate. This documentation is commonly known as a UI specification or UI spec. There are several applications for authoring a UI spec, with wikis being a relatively new tool. However, designers should be aware of a wiki’s benefits and drawbacks for documentation, since UI specs uniquely reflect a project and its context. The documentation needs are often based on the size of the project, launch date, team dynamics, audience, technology, and the product development process. The development process usually plays a major role in how teams interact and how work is completed or delivered, thus, there is a direct relationship between the UI spec and the process the team is using.
Gremett, Peter. Boxes and Arrows (2009). Articles>User Experience>Interaction Design>Functional Specifications
#35179
User Interface Pattern Documentation Review
User interface (UI) patterns have the potential to make software development more efficient. The prospect of such efficiency gains has led to interest in user interface (UI) patterns by individuals and organizations looking for ways to increase quality while at the same time reducing the costs associated with software development.
Stapleton, Patrick. Boxes and Arrows (2009). Articles>User Interface>Documentation>Functional Specifications
