|
|
This article is sample content outsourced to DocuMaker Communication Solutions. You can get similar content for your own website by outsourcing it here. |
 |
NOTE: As a demonstrative piece of writing, this content may or may not be relevant to the Just Outsourcing website. |
Personal Schedule Programming Estimate
The spreadsheet below describes how long it takes me to produce a publication using the iGui Cut and Paste Interface with the iCode Commander Expander. It does not, however, include the other factors described in the professional Schedule Estimate (time spent on planning, interacting with end-users, reviewing and updating plans, changing things, testing, and fixing errors).
Now, I’m able to code about 286KB a day and each of those pages is about 13KB. So that means I’m also able to develop about 22 pages a day. I’ve discovered that a typical help file is about 10% of its parent program’s size, and that the installation program is about 35%. Using these figures, I came up with the chart below that helps me determine how many days I’ll spend constructing the publication, it’s help file, and installation program:
The significance of the focus on “pages” is its relationship with features. Because each page contains a single feature, and when I determine what features a publication will have, I’ll have a rough idea of how many pages the publication will have. Cool!
Find This Page On The Internet Using:
Recommended Approach to Publishing, NASA’s Recommended Approach to Developing Software, meet software hardware requirements, print worksheets, determine features, writing development plan, master interface, DOS batch files, feature pages, writing end-user documentation, debugging, creating executable, installation routine, release
