Would you use a bugtracker to track the development of initial requirements?

Question

Imagine putting each requirement as a function in my bugtracker. It would be nice? Are there any better tools?

Answer 1

I would say that this is definitely a good idea, because you can easily track how requirements and ideas arose. You can also easily track your progress, time estimates, time spent, etc.

Answer 2

This is what I and many people do. Put the specifications in the form of errors, and then eliminate the errors when they are full functions.

. , , !

Answer 3

Bugtracking - . / - .

BTW - , .

Answer 4

: (WBS), (MRD) . / . , , , , .

, , / .

Answer 5

, . . , .

Answer 6

, .

, - , / , . , , .

Answer 7

, . , . , .

, , . , .

I apologize for the inital soapbox, but many people forget that documents may have flaws, not just software.