From: Cameron S. <ca...@sh...> - 2003-09-27 11:19:52
|
On Saturday 27 Sep 2003 7:00 pm, Sean Wheller wrote: > > 2. I suggest your template references or includes > > http://www.faqs.org/rfcs/rfc2119.html . It > > explains the meaning of > SHALL, > > > SHOULD etc. > > Sure, do you want to add it or shall I? I don't want to update anything until the original has first been put in CVS. Then we can keep a track of who updated what. So, probably better if you do it for the moment. > > > 3. You mention that requirements should tracable. > > I think it would be > good if > > > you could explain how. Ie, what naming/numbering > > convension should be > used. > > > Requirements are usually associated with a SHALL > > statement. Should the > SHALL > > > be included inside a <emphasis > > id="shall_number">shall</emphasis> tag? > > Your example is valid. Yet I was thinking <xref > linkend="req_var_ver"> > Where: > req is abbreviation for requirement. > var is variable unique neumonic or alphanumeric string > ver is the version of the of the req_var > > Traceability ensures that generguide can produce a > high-level SRS that can > be applied to sub and eddy projects, yet the SRS of > those projects can be > traced back to generguide. Authors can therefore use > generguide SRS as the > basis for IP and understanding. They will be able to > assume and reference > instead of include and duplicate. Yes, this sounds like a good idea. Once we get an example together I will probably have more comments. > I also have documents and check lists for User > Profiling:-) from ISO-18109 > interested?:-) etc. I'm not familiar with this standard. Will have to check up on it later. I sure it will be useful in the generguide master collection of documentation. -- Cameron Shorter http://cameron.shorter.net Open Source Developer http://generguide.sourceforge.net http://mapbuilder.sourceforge.net http://geotools.org Senior Software Engineer http://www.adi-limited.com |