Added by Geoff Sauer on May 11, 2006.
Average rating: 3.84/5.00 (n=25, std dev: 1.55)
 


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.
 
  View all 11 works by Le Vie, Donald S., Jr.  
  View all 132 works published by TECHWR-L  

Please share your rating/opinion of "Writing Software Requirements Specifications".
 PoorExcellent 
The link to this work seems to be broken.

Copyright © 2001-09 by the EServer. All rights reserved.Add a Work | Update this Work | Discussion Forum | Habitués