Re: Questions to ask
- From: Roedy Green <see_website@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 25 Oct 2007 19:19:25 GMT
On Thu, 25 Oct 2007 18:29:59 -0000, Robert Hicks <sigzero@xxxxxxxxx>
wrote, quoted or indirectly quoted someone who said :
I am being thrown into a team to go scope out a project that is being
pulled in house. It is Java (of course). What would try to do or ask
when meeting with the other team? I will be talking with the
programmers.
To estimate how difficult this will be you need primarily to know:
1. what os where they running on. What will it run on in house?
2. How much JNI is there?
3. What 3rd party packages does it rely on. Do these run on your
in-house machine.
4. Are you going to change databases?
5. What documentation is there on how to run the system, and over all
docs on what it does. Detail is rarely a problem. What you want to
check out is the docs at the head of each class and overall project
docs, and docs about what you have to run in what order for the daily
schedule.
6. What are the big problems with the code that will have to be fixed.
7. What improvements would they suggest (which is different from what
your users may be requesting).
--
Roedy Green Canadian Mind Products
The Java Glossary
http://mindprod.com
.
- Follow-Ups:
- Re: Questions to ask
- From: Robert Hicks
- Re: Questions to ask
- References:
- Questions to ask
- From: Robert Hicks
- Questions to ask
- Prev by Date: Re: Remote Log Off In Java
- Next by Date: Re: Questions to ask
- Previous by thread: Questions to ask
- Next by thread: Re: Questions to ask
- Index(es):
Relevant Pages
|
|