Practices
  Home arrow Practices arrow Page 2 - Writing a Software Technical Reference...
Dev Shed Forums 
Administration  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Forums Sitemap 
IBM® developerWorks 
Dedicated Servers 
E-Commerce Hosting 
Linux Web Hosting 
Managed Hosting 
Small Business Hosting 
Download TestComplete 
VPS Hosting 
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
PRACTICES

Writing a Software Technical Reference Manual (part 1)
By: Deepa L, (c) Melonfire
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 10
    2003-02-05

    Table of Contents:
  • Writing a Software Technical Reference Manual (part 1)
  • Under The Microscope
  • A Little Knowledge...
  • Hard Decisions
  • Doing It In Style

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
     
    ADVERTISEMENT

    PCmover - $15 Off with Coupon Code CJPH7Q

    Writing a Software Technical Reference Manual (part 1) - Under The Microscope
    (Page 2 of 5 )

    As the name suggests, the Software Technical Reference Manual (STRM) isconcerned solely with the technical aspects of a software application -how the application is structured, how each component works and how toinstall and configure it. The idea is to give the customer independencein installation, maintenance, administration and further development ofthe application.

    From the developer's point of view, the STRM is a blueprint of theapplication that allows him/her to continue development from the lastrelease. The STRM provides developers with the knowledge needed to hitthe ground running when extending or adding on to an application,providing them with the level of detail needed to quickly and rapidlymake leveraged changes to an application's code tree.

    The audience, therefore, is technically knowledgeable in both cases -either the customer's MIS department or developers who want to enhance,improve or modify the application.

    Given the content and the audience, this document is usually adevelopment team deliverable...unless you have a technical writer in theteam with a very sound technical background. A very big advantage ofthis, especially as compared to support documentation like user manualsand help files, is that the time spent on information collection isnegligible; almost all of it is already captured in the planning stagesof the software, in the software requirements document and the softwaredesign document (read more about these at ).

    With these two documents in hand and, given the fact that the personwriting the STRM would have been an integral part of the developmentprocess already, actually producing this document becomes a matter of:
    1. Defining the scope of the manual
    2. Setting the conventions
    3. Developing the table of contents
    4. Production
    5. Review
    In this article, I'll be focusing on the first two steps, with a list ofthings you should keep in mind when formulating the structure and styleof your manual.

    More Practices Articles
    More By Deepa L, (c) Melonfire


     

       

    PRACTICES ARTICLES

    - The System in So Many Words
    - Basic Data Types and Calculations
    - What`s the Address? Pointers
    - Design with ArgoUML
    - Pragmatic Guidelines: Diagrams That Work
    - Five-Step UML: OOAD for Short Attention Span...
    - Five-Step UML: OOAD for Short Attention Span...
    - Introducing UML: Object-Oriented Analysis an...
    - Class and Object Diagrams
    - Class Relationships
    - Classes
    - Basic Ideas
    - Choosing the Right Team
    - Trees
    - Basic Array Searching in C++

     
    Accelerating Trading Partner Performance
     
    Competing on Analytics
     
    Cost Effective Scaling with Virtualization and Coyote Point Systems
     
    Five Checkpoints to Implementing IP Telephony
     
    Hosted Email Security: Staying Ahead of New Threats
     




    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 5 hosted by Hostway