<christian.huvelle@siemens.com> wrote:I don't identify exactly a particular project/product, my question is moregeneric.The purpose is to take in charge the whole maintenance activity on anapplication previously developped by another company.Of course we will have full access to sources, etc....I'm loking for some "receipt" or good practice to make the best evaluationof the application and to determine a budget for the maintenance activity.Thanks for your reaction.
Well, here are a few random thoughts:
* Is it written in a standard language?
* Do you already have staff familiar with the language/platform?
* Do you already have staff familiar with the product?
* Do you already have staff familiar with the application?
* What is the approximate size of the app in lines of code?
* Does it come with design documents?
* Does it come with a maintenance history?
* Can you even complete a build of it from available materials?
* Do you have a list of outstanding bugs?
* Do you have a list of outstanding enhancement requests?
* Will you be asked to port it to a new platform on day 2?
* How many people have been maintaining it up to now?
* Is it a mission-critical system?
I know that this is probably the question you are trying to answer,
but I will ask anyway -- what is the approximate size of the effort,
one person part-time, or two people full-time, or larger?
Joshua Stern