Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I am in need of an estimation technique to verify if the source code delivered is appropriate.

for example, if the vendor has developed an application and is surrendering the source code, me as a consultant to the client, need to verify if the source code delivered is genuine and appropriate. Question is how to verify and how much to charge for this service?

share|improve this question
    
You may want to also post this on the project management (pm.stackexchange.com) site. –  blueberryfields Mar 11 '11 at 12:47
    
It should be easy enough to Verify the application meets all the requirements. –  Ramhound Mar 14 '12 at 15:09
add comment

migrated from stackoverflow.com Mar 11 '11 at 8:33

This question came from our site for professional and enthusiast programmers.

1 Answer

You must first have a Requirement Specification document (spec). Without a spec there is no way for you to know if the delivered software is even remotely close to the client's request or expectation.

Review the spec looking for inconsistencies, conflicts, and individual features and behaviors that you can verify through testing. Inconsistencies and conflicts should raise an immediate red flag indicating that the delivered code is either incomplete or incorrect.

For each of the individual features and behaviors that you found, write a procedure that you can use to test each one. Once you have this list you can run your tests on the code to verify the accuracy of the results.

Now, how to charge for this: If you assume that a developer makes $80000 per year, then your hourly rate should be around $40/hr. You should be able to critically evaluate about 25 pages per hour. You should be able to write the testing procedure for one feature in about 30 minutes. Testing the feature by following your procedure is highly variable--some features may require you to wait while a timer counts down, etc. You won't know all the details for this until you have reviewed the spec, but you might want to estimate 1-2 hours per feature. A state-machine diagram is very useful in helping you determine how you can get to each feature. This will also help verify that you have performed a full coverage test of the software.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.