A directory of resources inthe field of technical communication.


3 found.

About this Site | Advanced Search | Localization | Site Maps



Bridging the Gap with Requirements Definition

Developing a new product or service is tricky. When everything goes well, the product can redefine a market or even create an entirely new one, to the benefit of its manufacturer and its consumers. When the product doesn't click with its audience, though, the costs—development, employee, manufacturing—can be staggering. How do you ensure that your new product doesn't flop? One effective method is to conduct a requirements definition phase before developing a new product.

Olshavsky, Ryan. Cooper Interaction Design (2002). Articles>Usability>Specifications


Identifying Web Site Requirements   (PDF)

The authors emphasize the importance of conducting thorough research on business goals, branding goals, user needs, and technical resources before Web designers undertake a redesign. The article also offers suggestions about how to define, develop, and communicate a client's brand.

Summers, Kathryn and Michael Summers. Intercom (2001). Articles>Usability>Specifications


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

Follow us on: TwitterFacebookRSSPost about us on: TwitterFacebookDeliciousRSSStumbleUpon