Benson and Matthew,
I cannot agree with this line of thinking.  Of course there is benefit in 
having the requirements documented regardless if there are ever any solutions 
delivered.  And how can solutions be successfully developed, tested and 
verified without a published requirements document ??

There are many processes available for modifying the document after publication.
Many people have put in effort.  Finish this phase, get something successful 
out of the process and then move on to phase 2.

Carter

                
Carter Bullard • CTO
150 E 57th Street Suite 12D
New York, New York 10022-2795
Phone +1.212.588.9133 • Mobile +1.917.497.9494

> On Jan 31, 2015, at 10:13 PM, Benson Schliesser <[email protected]> wrote:
> 
> Dear NVO3 Contributors -
> 
> As mentioned during the virtual interim meeting last week, Matthew and I have 
> been discussing when to publish the various NVO3 requirements documents. Our 
> view is that there is no real value in publishing requirements if we fail to 
> also deliver solutions. Further, we expect that the process of developing 
> solutions will enhance our collective understanding, and therefore put NVO3 
> in a better position to evaluate whether the requirements documents are 
> complete.
> 
> Finally, in some cases it may not make sense to have requirements documents 
> that are separate from the solution. In other words, it is possible that the 
> requirements may simply be a section of a solution document. This would need 
> to be evaluated after we have a more firm idea of what the solution 
> documentation might look like.
> 
> Thus, it is our proposal that we should update the milestones to reflect that 
> the requirements will be published at the same time as the solutions. We 
> welcome any feedback on this proposal within the next two weeks.
> 
> Cheers,
> -Benson & Matthew
> 
> _______________________________________________
> nvo3 mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/nvo3
> 
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3

Reply via email to