What can you evaluate



draft task list to help you estimate your project one-time costs

The headings in bold are phase names. The tasks are not necessarily in the right order, and some tasks are missing, but this can be used to do a rough estimate of project costs. Add any tasks you think necessary and cross out any tasks you don’t need.

DO NOT include this full task list in assignment A. Just use the totals for the phases.

use abbreviations in the second column...

PM project manager U users (not management)

P programmer UM user management

A analyst QA quality assurance personnel

W technical writer DB database administrator

T technical staff (network, etc.) etc.

in the third column, put the total number of hours for all personnel then...

add all the hours together and multiply by ($100,000 cost per year)/(1760 hours per year) = $57

(average $50K salary for the personnel mix translates to $100K cost to employer,

220 working days of 8 hours each = 1760 hours per year)

for purchases of equipment, add together the estimated dollar amounts

|task/phase |personnel and materials |time estimate in hours |labour + material |

|project selection | | | |

|initial meetings with client |PM, U, UM, A |20 |$1,140.00 |

|initial proposal to client | | | |

|project initiation | | | |

|kickoff meeting | | | |

|project planning | | | |

|establish management procedures | | | |

|establish project workbook | | | |

|research enterprise packages | | | |

|prepare initial information requirements | | | |

|prepare research report | | | |

|prepare statement of project scope | | | |

|analysis | | | |

|read client’s current documentation | | | |

|interview client personnel | | | |

|analyze client database | | | |

|prepare needs/functional requirements | | | |

|determine recovery requirements | | | |

|gather info needed for user manual | | | |

|produce hierarchy chart | | | |

|produce DFD’s | | | |

|create data dictionary | | | |

|review documentation with users | | | |

|revise according to user recommendations | | | |

|draft maintenance instructions | | | |

|determine network requirements | | | |

|assess current hardware | | | |

|complete analysis | | | |

|logical design | | | |

|design output screens, reports | | | |

|design input screens | | | |

|get user approval for user interfaces | | | |

|design interfaces to other systems | | | |

|design database | | | |

|physical design | | | |

|design files | | | |

|design controls, security | | | |

|design application programs | | | |

|review application design | | | |

|design data conversion programs | | | |

|design data loading programs | | | |

|draft the user manual | | | |

|draft maintenance instructions | | | |

|draft instructions for operations support | | | |

|draft recovery instructions | | | |

|determine workstation requirements | | | |

|research hardware options | | | |

|plan hardware placement | | | |

|design network | | | |

|design hardware configuration | | | |

|select vendor(s) | | | |

|finalize hardware requirements | | | |

|review completed technical specifications | | | |

|implementation | | | |

|order hardware | | | |

|test hardware | | | |

|prepare site for hardware | | | |

|receive and install hardware | | | |

|write application programs | | | |

|write recovery programs | | | |

|write data loading programs | | | |

|plan testing | | | |

|load data for testing | | | |

|conduct unit tests | | | |

|conduct integration tests | | | |

|conduct performance tests | | | |

|conduct user acceptance tests | | | |

|get approval for user manual | | | |

|train users | | | |

|load data for “go live” | | | |

|maintenance | | | |

|draft maintenance agreement | | | |

|followup support and training | | | |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download