How do you measure a small, large, very large project?

Question

I am reading Code Complete, as well as a couple of other programming books at the moment. Project size affects many other parameters that must be considered when planning, coding, test automation, etc. I was wondering what do people on SO usually use in the real world to categorize a project in its correct “weight” class?

Are these lines of code? The number of external interfaces? Required Documentation Pages?

Answer 1

I would say that a development effort is required. Accepting a team of six developers:

• Small project - up to 6 months.
• - 6-18
• - 18+ .

.

Edit

, 1 . , :

• - 1
• - 1-3
• - 3+

, -, , :

• - 1
• - 1-3
• - 3+

, 6 , , . , , .

Answer 2

.

Answer 3

, , .

Answer 4

:

• . -
• -
• (-, , , - - ).
• - - , 20 -, .

-

Answer 5

, , . ... ;) .

, , /, . , .

Answer 6

Learning curve - the amount of time it takes a new developer to familiarize themselves with the code before he can do something useful to help him.

Answer 7

This is kind of a left-wing idea, but when I work on a project, I assume that

1) House = small project

2) Project supermarkert = medium size

3) Airport = big project

You know the people around you, what you and they are doing, and your chances of success, of which you are three.