Development Support Services
  • Home
  • About DSS
  • About Kim
  • DSS Services
    • Lessons Learned
    • Services for CLIENTS >
      • Client Svcs: Definition of Requirements
      • Client Svcs: Changes
      • Client Svcs: Product Reviews
      • Client Svcs: Editing & Proofreading
      • Client Svcs: Documentation
    • Services for DEVELOPERS >
      • Developer Svcs: Requirements
      • Developer Svcs: Changes
      • Developer Svcs: Quality Assurance
      • Developer Svcs: Documentation
  • The Cost
  • Contact Me
  • Testimonials

DSS Services​​ for Developers


Documentation of Products, including Related Processes, System Overviews & Maintenance Procedures


Despite the challenges associated with producing it, wise developers find a way to create essential documentation before, during, and after a project.

Flowcharts and Other Developer Documentation
​Many developers fail to prioritize the time to document the products they have developed.

Many do so because they are not fully aware of the long-term value of documenting the products they've developed.  Others simply don't have the available staff and/or expertise to do the documentation job justice. ​

​The wise ones, however, understand the value of system documentation to both the client and themselves.  And despite the challenges associated with producing it, they find a way to create essential documentation before, during and after the development project.
​

Why Don't Developers Document?

​
​Let's face it — just about everyone hates to document.
It is generally painstaking, time-consuming, bloody-boring work!
​
Fortunately, there are a few of us on the planet who find it rewarding to do, and I happen to be one of those unusual people. I do the stuff my clients hate to do, and I do it to the very best of my ability.


​Let's face it — just about everyone hates to document. It is generally painstaking, time-consuming, bloody-boring work!

​
Besides hating even the thought of it, what are the other reasons developers fail to do their due diligence when it comes to documentation?
  • To keep project prices down so they're competitive
  • To minimize project costs that can't be passed on to the client
  • To keep the product delivery date on schedule
  • To avoid pulling overextended personnel off of other projects
  • To compensate for budget overages in other aspects of the project.

All of these reasons are understandable. But the fact remains that supporting documentation is critical to ensuring the development of a top-quality product — and to cost-effectively supporting and/or enhancing that product in the future. And both of those results translate into happy, long-term clients.

​As a developer, you know these facts. So it's important to remind yourself of what the payback is on investing in documentation, no matter what...
​
​

The Payback on Investing in Documentation

Costs & Benefits of Developer Documentation
​
​What's the payback to the developer on investing in documentation?
  • Clearer requirements communication among staff
  • A higher-quality product
  • Less expensive cross-training of development and support personnel
  • Faster, less-expensive debugging
  • Higher-quality client support
  • Easier, faster product enhancements in the future
  • A demonstration of your professionalism to your client.
​​
It's important to keep these benefits in mind in order to put the cost of documentation into perspective.


​Let Me Help!


Take the documentation burden off your team, and assign it to DSS.  I have decades of experience in creating technical documentation and am highly-skilled at producing it time-efficiently and cost-effectively.

If your development company is experiencing backlogs in the documentation of products you're developing, DSS is available to help you catch up and/or stay ahead of this essential effort in the future.  


​I communicate this critical information in a straight-forward manner that developers quickly grasp — even those whose native language is not English.

​
For maximum efficiency in communicating the most information in the least amount of time, my documentation methods rely heavily on flowcharts, diagrams, and other technical and process-focused documentation.

I communicate this critical information in a straight-forward manner that developers quickly grasp — even those whose native language is not English.


So don't let unfinished documentation tasks snowball out of control. Contact me today to explain how I can assist you in staying on top of documentation that's essential to quality products and excellent long-term support.

​See examples below of documentation I have created for other clients.

Clarification of Requirements                               Monitoring of Changes                        Quality Assurance Services


​A Sample Flowchart Documenting
the User Registration Process
on a Complex, Database-Driven Website

Flowchart of a Registration Process on a Database-Driven Site



​A Sample Flowchart Documenting
a Client's Internal Process
​ Relative to its Custom-Developed Database

Flowchart of a Client's Internal Process

A Sample Flowchart Documenting
​User Navigation on a Database-Driven Website

Flowchart of User Navigation on a Complex Site

DevelopmentSupportSvcs.com                                Kim@DevelopmentSupportSvcs.com 
Copyright © 2016 Development Support Services.  All rights reserved.
Photo used under Creative Commons from quinn.anya
  • Home
  • About DSS
  • About Kim
  • DSS Services
    • Lessons Learned
    • Services for CLIENTS >
      • Client Svcs: Definition of Requirements
      • Client Svcs: Changes
      • Client Svcs: Product Reviews
      • Client Svcs: Editing & Proofreading
      • Client Svcs: Documentation
    • Services for DEVELOPERS >
      • Developer Svcs: Requirements
      • Developer Svcs: Changes
      • Developer Svcs: Quality Assurance
      • Developer Svcs: Documentation
  • The Cost
  • Contact Me
  • Testimonials