Practices
  Home arrow Practices arrow Writing A Software Technical Reference Manual (part 2)
Dev Shed Forums  
Administration  
AJAX  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Smartphone Development  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Mobile Linux  
App Generation ROI  
IBM® developerWorks  
Forums Sitemap  
E-Commerce Hosting  
Linux Web Hosting  
Managed Hosting  
Small Business Hosting  
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 2)
By: Deepa L, (c) Melonfire
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: starstarstarstarstar / 2
    2003-02-13


    Table of Contents:
  • Writing A Software Technical Reference Manual (part 2)
  • Starting Off Easy
  • System Shock
  • Remote Control
  • Improving Yourself
  • Sealed With A Kiss

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      error-file:tidyout.log Del.ici.ous error-file:tidyout.log Digg
      error-file:tidyout.log Blink error-file:tidyout.log Simpy
      error-file:tidyout.log Google error-file:tidyout.log Spurl
      error-file:tidyout.log Y! MyWeb error-file:tidyout.log 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


    Writing A Software Technical Reference Manual (part 2)
    ( Page 1 of 6 )

    With the groundwork out of the way, this concluding part examines the standard components of a technical reference manual, explaining what goes into each section and why. It also discusses the process by which such a manual should be reviewed and vetted prior to delivery to a customer.In the first part of this article, I discussed the purpose and goals of a software technical reference manual, explaining who the target audience usually is and how to cater to its needs. I also talked a little bit about how to go about deciding the scope of things to be covered in your manual, and discussed the standard components of a stylesheet for such a manual.

    In this second article, I'll build on what you've learned thus far by putting together a sample table of contents for this type of manual, and discussing how to break the technical material up into a format that is both structured and easily understandable. Keep reading!

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

       

    PRACTICES ARTICLES

    - More Techniques for Finding Things
    - Finding Things
    - Finishing the System`s Outlines
    - 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





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 2 hosted by Hostway
    Stay green...Green IT