[news.eclipse.technology] Re: Project Idea: Automated Software Productiv

["jK.MkIII" <Jari.Kujansuu@xxxxxx>]

Carl Stottlemyer wrote:
> I have investigated using a few tools that assist in the automation of 
> the Personal Software Process (PSP) and every tool I have used has too 
> much overhead to make it useful.
>
> I think that integrating many aspects of the PSP into an IDE would 
> eliminate most of the overhead of using the PSP and would give software 
> developers very useful information they can use to improve their 
> productivity.
>
> For example: Some of the aspects of PSP that are time consuming that 
> could be automated by the IDE are:
>
> 1.  Logging of time spent on project:  The IDE could record the time 
> spent developing each class of a project.
> 2.  Error/Defect tracking: The IDE automatically enters compile time 
> errors, failed unit test errors and also has a way of letting the user 
> indicate the time spent fixing an error.
> 3.  Software measurements:  The IDE automatically keeps track of 
> software measurements for entire project and daily development.
> 4.  Planning:  The user can make estimations of size and the IDE will 
> let the user know how close they are to the actual measurement.
> 5.  Reports on LOC/hour, amount of time fixing defects vs total project 
> time.
> 6.  Multiple project statistics let user know how much their 
> productivity and estimation has improved.
>
> I am wondering what everyone thinks about this as a project idea.

I think it is good idea.

Of course I think it has couple problems, but propably some kind of rule
could be made for them.

How you actually calculate time spent on each class? How long it has
been open? But if you have 5 classes open and leave program running
while you go for lunch :) Could you just count time user is actually
modifying file, or at least viewing file without computer beeing idle
longer than certain time?

Of course you have to remember than coding is only part of developing
time. You would need ability to add things manually too.

How should error/defect tracking work? Because Eclipse compiles files
automatically at least I have zillions of errors that I am going to fix
when get there, they are not there because I made something wrong but
because there is work in progress. Should it be checked in the end of
day, when commit to CVS or when run your tests?

But I think it would be great plugin. We in our project haven't used any
such tools but I have always tried to ask people to manually keep track
of time spent on specific things ...of course with not very good success
:( Having somethings done automatically and rest beeing easily done
would propably make everyone in our project finally do it.


--
  jari k

  remove unnecessary parts of address to make it work