A directory of resources inthe field of technical communication (and technical writing).


11 found.

About this Site | Advanced Search | Localization | Site Maps



Common Mistakes: Functional Specification for Web Development

What are pitfalls that companies should avoid when specifying Web applications for internal or external development?

Buerki, Nicolas. E-Consultancy (2004). Articles>Writing>Specifications>Functional Specifications


Functional Spec Tutorial: What and Why

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.

Mojofat. Articles>Writing>Specifications>Technical Writing


Functional Specification Standard   (Word)

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.

Software Reality. Articles>Writing>Specifications>Functional Specifications


Getting Real, Step 1: No Functional Spec

Don't write a functional specifications document. Why? Well, there's nothing functional about a functional specifications document.

Fried, Jason. Signal vs. Noise (2005). Articles>Writing>Specifications>Functional Specifications


On Writing

Whatever your role in a project, insist on getting the spec right before the code is written. The spec'ing process may take several iterations, so plan accordingly.

Shetty, Ashish. Blogspot. Articles>Writing>Specifications


Painless Functional Specifications - Part 1: Why Bother?

Why won't people write specs? People claim that it's because they're saving time by skipping the spec-writing phase. They act as if spec-writing was a luxury reserved for NASA space shuttle engineers, or people who work for giant, established insurance companies. Balderdash.

Spolsky, Joel. Joel on Software (2000). Articles>Writing>Specifications>Software


Painless Functional Specifications - Part 2: What's a Spec?

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.

Spolsky, Joel. Joel on Software (2000). Articles>Writing>Specifications>Functional Specifications


Seeing the World Through Different Specs: Or, How I Came to Love Writing Software Specifications   (PDF)

Much has been said and written about Object-Oriented Programming in the past few years, some of it even worthwhile. While not the panacea on which we've all waited, OOP is, however, changing not only our concept of software design and development, but is subtly re-shaping the way in which we see and know the world. For technical communicators, this epistemological change will radically affect not only the way we craft software specifications, but will permanently re-shape our worldview.

Weathington, Thomas L., Jr. STC Proceedings (1998). Articles>Writing>Specifications>Technical Writing


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


Writing Software Requirements Specifications

For technical writers who haven't had the experience of designing software requirements specifications (SRSs, also known as software functional specifications or system specifications) templates or even writing SRSs, they might assume that being given the opportunity to do so is either a reward or punishment for something they did (or failed to do) on a previous project. Actually, SRSs are ideal projects for technical writers to be involved with because they lay out the foundation for the development of a new product and for the types of user documentation and media that will be required later in the project development life cycle. It also doesn't hurt that you'd be playing a visible role in contributing to the success of the project.

Le Vie, Donald S., Jr. TECHWR-L (2000). Articles>Writing>Specifications>Technical Writing


Writing Technical Specifications in the Present

Technical specifications are improved in several ways with one easy procedure - writing them in the present tense. That is, rather than trying to specify constraints on a product that does not yet exist, describe the product as though it already existed.

Kendall, Matthew. Ionocom (2005). Articles>Writing>Specifications>Grammar

Follow us on: TwitterFacebookRSSPost about us on: TwitterFacebookDeliciousRSSStumbleUpon