hello... i'm in the crisis stage of a class project, and am wondering if anyone can help me... :)

it's not much information, but i just kinda want foofy numbers...

we're doing a consulting project for our university, and although we have our recommendations, we want to get a few numbers on the ideal recommendation (which will never get implemented, but oh well...)

if anyone has experience as an oracle developer (and has dealt with PeopleSoft, ideally...)

what price range would you charge for the developement of an interface system between two PeopleSoft modules? i know that is extremely little information to go on, but maybe a per hour cost or something?

ALSO

are there any MS Access programmers out there? can i get you guys to quote me what it would cost (again, per hour...) to set up a fairly complex database?

again, i know it's not too much detail, but any help would be appreciated... :)

thanks!

Send me a email, I think I can help.

This is probably slim help because I can't find the fool link myself, now; however, somewhere over on cnet.com I believe I saw a "typical rates" sheet reflecting much of the information you wanted. Happy hunting!

To give you a feel, I used to work for a consultancy working with Oracle financials, their chargeouts where:

Junior Consultant (i.e. Graduate) £600per day
Consultant with experience £800per day
Senior Consultant £1000per day
Guru/Project Manager £1250per day

They also did a lot of MS Access work, same rates. The type of work you are looking at is normally quoted in days, or half days, not hours.

In your quote, you have to make sure you allocate time for, with rough percentage of total time involved (based on previous experience):

1) Converting functional spec to a good quality tech spec (25% - 35%)
2) The actual coding (25 - 30%)
3) Unit Testing of your coding (10% - 20%)
4) Time to fix code in light of unit test (10% - 20%)
5) Integration testing with rest of application (10% - 20%)
6) Time to fix code in light of integration test (10% - 20%)

The test spec is derived from the functional spec. You have to ensure your customer signs off the functional spec before writing the tech spec, and they sign off the tech spec before coding. These two docos are what you measure your deliverable against.

And lest this crucial point be omitted, may make a reminder of it.

Multiply any reasonable cost figure by two -- because everything always takes twice as long as quoted.