Re: Requirements process suggestions

[Michael Richardson <mcr@sandelman.ottawa.on.ca>]

>>>>> "Melinda" == Melinda Shore <mshore@cisco.com> writes:
    Melinda> The requirements process doesn't seem to be going very well,
    Melinda> which isn't that surprising - requirements documents are hard 
    Melinda> to do.  I think it might be possible to have the son-of-IKE 
    Melinda> requirements through WG last call before Yokohama
    Melinda> by applying some discipline, if that's what the working group
    Melinda> wants.

    Melinda> In particular, it's impossible to develop a good requirements
    Melinda> document by evaluating it in terms of whether or not it presents
    Melinda> a harmonious, pleasing whole.  It's got to be taken apart and
    Melinda> put back together again.  What I've found to be effective (but
    Melinda> a lot of work) is:

    Melinda> 1) take the requirements document, turn it into a numbered
    Melinda>    list of crisp, declarative sentences
    Melinda> 2) make a quick first pass through the list and identify items
    Melinda>    on which there's already consensus either to keep or to
    Melinda>    drop.  If there's any - *any* - disagreement about anything, 
    Melinda>    it goes on the "unresolved" list.  

  Yes, I agree with this process. Make three lists:
  a) requirement is in scope	       (no debate)
  b) requirement is out of scope       (it may never be discussed again)
  c) requirement is eligble for debate.

    Melinda> I've found that the only thing that requires face-to-face interaction
    Melinda> is item 2 - doing it on the mailing list is too slow.  However, given
    Melinda> the 30-day-notice requirement for interim meetings waiting for an
    Melinda> interim meeting may take too long, too, and perhaps instead everything
    Melinda> could go on the unresolved list.  It's a lot of work for the chairs

  We should start on the mailing list anyway.

  I am willing to keep track of the list.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another NetBSD/notebook using, kernel hacking, security guy");  [