[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency-msg] Meeting Minutes 1-17-06
HI Renato, I appreciate your intent, but I am not quite sure I adequately explained the current documents from which we are working. I will get to that momentarily. First, I want to explain that the document you found is an adaptation by another TC of the standard OASIS "Specification" Template. While that template is helpful for writing specifications, it was not developed to serve the needs of a Requirements Document, per se even if it can be adapted in some circumstances. That is why I said OASIS does not have its own Requirements Template. The underlying template for the document you found is available at http://docs.oasis-open.org/templates/ I, like many other TC chairs and co chairs, had a hand in the development over time of this set of templates, and I will eventually suggest developing a Requirements Template as well since my thinking is that this is itself a requirement for a well-dcoumented specification effort. That is why we developed our own template. Unfortunately, it is not a one-size-fits-all situation for us. A Requirements Document needs to set forth both the specific point by point requirements such as the document you found, but, for the purpose of keeping the specification-writing effort on track, it needs to include documented use-cases from which specific requirements are drawn. That provides accountability back to the original intent of writing the specification--a problem when one is up to one's armpits in alligators and trying to remember one's intent was to drain the swamp. Bad analogy considering our misunderstanding of the ecological functionality of wetlands, however, apt for the specific situation. The Requirements Supplement Document I have attached is the Requirements Document of Record for this work. It came into being as a result of a TC decision to provide a template of our own to the practitioner group from the EIC/DHS/DOJ community (Emergency Interoperability Consortium, Dept of Homeland Security, Dept of Justice) which originally submitted a draft specification. We spent an entire day going through it point by point Oct. 19, 2005 at our last face to face meeting in Washington, D.C. Now you know. That doesn't mean it should not be amended to fit any requirements we uncover as we start in on the specification itself. Regards, Rex At 4:21 PM +1000 1/24/06, Renato Iannella wrote: >On 24 Jan 2006, at 10:32, Rex Brooks wrote: > >>While OASIS has specification templates, I have >>not seen, or found a Requirements Template. >>Michelle and I worked together to develop one >>for the TC for that very reason, so I don't >>think we need to do more than review the >>requirements, and ask if anyone has further >>requirements, and discuss it if we turn up more >>than what we have. > >I have found one from OASIS (see attached) > >I think we should "own" the requirements in the sense that they become >an OASIS document. > >I am happy to have a go at converting them across!! > >Cheers... Renato Iannella >National ICT Australia (NICTA) > > > >-------------------------------------------------------------------------- >This email and any attachments may be confidential. They may contain legally >privileged information or copyright material. You should not read, copy, >use or disclose them without authorisation. If you are not an intended >recipient, please contact us at once by return email and then delete both >messages. We do not accept liability in connection with computer virus, >data corruption, delay, interruption, unauthorised access or unauthorised >amendment. This notice should not be removed. > >Attachment converted: Macintosh >HD:oasis-sdd-requirements-v04.doc (WDBN/«IC») >(000DE4DB) -- Rex Brooks President, CEO Starbourne Communications Design GeoAddress: 1361-A Addison Berkeley, CA 94702 Tel: 510-849-2309
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]