Re: [Corelinux-public] Oops

[<t.r...@at...>]

I agree with your sense of heaviness.  In an ideal world 
the requirement originator would be the one to determine 
if a design/implementation fufills the requirements, 
however once the requirement is fully analyzed and 
specified any developer should be capable of designing 
and implementing to meet the specifications.

Tom
--
----------
			
> I was re-reading the documentation and I noticed that I wrote something
> along the lines of "A requirement is owned through to implementation."
> 
> Is this to heavy? I mean, I have received e-mails from people with a
> range of interest and experience but not necessarily across the board.
> Should I change this to be a more modular effort?
> 
> I know there are times when I feel up to Analysis and/or Design, and
> other times I want to follow the recipe and just put out some code.
> 
> ---
> Frank V. Castellucci
> http://corelinux.sourceforge.net
> OOA/OOD/C++ Standards and Guidelines for Linux
> 
> 
> 
> _______________________________________________
> Corelinux-public mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-public