A question for those experienced in project managmement . . .

  • Thread starter Thread starter ChrisB
  • Start date Start date
C

ChrisB

Hello:

I am in involved in the creation of a .NET application and was wondering if
there are any "rules of thumb" in terms of the percentage of time typically
required for each step in the development process? Are there any good
websites that discuss these types of issues?

We have logically divided our software lifecycle into the following stages:
1. Requirements Gathering (% time?)
2. Analysis/Design
a. Business Logic/Data Components (% time?)
b. Interface (% time?)
3. Coding
a. Business/DataComponents - including creation of unit tests (%
time?)
b. Interface - no unit tests created (% time?)
4. System Testing/Debugging (% time?)

Of particular interest is the typical ratio of back-end developers (middle
tier/database responsibilities) to front-end developers (interface
responsibilities). I realize these values can vary by project, but again,
just looking for estimates based upon the average project.

Thanks very much for any insight!
Chris
 
One more point I should have made. In addition to business/data access
component creation, back-end developers are also responsible for the
creation of database tables, stored procedures, etc.

Thanks again!
Chris
 
Chris,

There is no straight forward answer to your questions.
Time spent depends heavily on the complexity and quality of the application
you wand to develop.

Moreover it depends on your budget and schedule!!!

In my opinion you should spent more time in the first two steps.

Michael
 
Back
Top