Re: [ros-dev] Flow chart

[art yerkes]

On Tue, 31 Jan 2006 22:29:55 +0000
James Tabor <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> wrote:

>   Ged Murphy wrote:
> >   Hi all.
> >  
> >  Would someone be willing to put a flow chart together on moving code 
> >  from the main branch to the audited branch.
> >  I think if something like this is put in place, it would ensure everyone 
> >  was operating in the same manner.
> >   
>  I hope someone would have a plan! I want to get started ASAP! But everyone
>  are stuck on stupid, IP crap!
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>   
Not sure how much sense it makes, but this is my plan:

1) Take the next easiest part to audit
2) Identify components in common with other object files of the same type
3) Document tasks which must be undertaken by these components (if those
   documents don't already exist)
4) Analyze the code for the component, first grouping functions under 
   categories identified by the building block documents and justifying
   their code according to the language in the building block documents.
   This should dentify file names and line numbers and be very specific.
5) Identifying code that was not named in the above and showing it to be
   either obvious or necessary in context.
6) Code that is neither obvious nor obviously necessary should be shown to
   be necessary through a test case.

This isn't 100% objective yet, but I think most of it is close.  

That's the best I can come up with... Thoughts?
-- 
Here's a simple experiment. Stand on a train track between two
locomotives which are pushing on you with equal force in opposite
directions. You will exhibit no net motion. None the less, you may
soon begin to notice that something important is happening.
-- Robert Stirniman