There may be other well-established ways of doing this but one approach
is as follows:
Wrap each requirement in a { SET } field as follows:
{ SET requirementID "the requirement text" }
(You have to avoid double-quotes within the text to do that)
Follow that by a { TC } field, e.g.
{ TC { REF requirementID } }
or even
{ TC { requirementID } }
Follow that with a { REF } field, e.g.
{ REF requirementID }
Create a { TOC } field as follows to insert the list of TC texts:
{ TOC \f }
A TOC will always insert the TCs in the same sequence in which they
occur in the document, so if you need a different sequence, you would
probably have to jump through some more hoops.
If you want to generate requirementIDs (which may not be a good idea if
you are ever going to publish version 2 with new requirements within the
original sequence) you can use e.g.
{ SET "requirement{ SEQ ID }" "the requirement text" }
{ TC { REF "requirement{ SEQ ID \c }" }
{ REF "requirement{ SEQ ID \c }" }
If you want to include the requirement ID in the TOC, include it in the
TC fields, e.g. something like
{ TC "requirement{ SEQ ID \c }: { REF "requirement{ SEQ ID \c }" }" }
A lot of these things can be set up as autotexts/document building
blocks for relatively easy insertion.
NB, all the {} need to be the special field code braces you can insert
with ctrl-F9, not the ordinary {} on the keyboard.
Another approach is to do the complete reverse, i.e. something like
- Create your list of requirements at the point you need it in the
document.
- Bookmark each requirement with a unique name.
- Insert the requirement text where you need it using a REF field.
Peter Jamieson
http://tips.pjmsn.me.uk