diff options
Diffstat (limited to 'doc/tips/ikiwiki_as_a_requirements_management_tool.mdwn')
| -rw-r--r-- | doc/tips/ikiwiki_as_a_requirements_management_tool.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/tips/ikiwiki_as_a_requirements_management_tool.mdwn b/doc/tips/ikiwiki_as_a_requirements_management_tool.mdwn index 083878aef..17be5b9b2 100644 --- a/doc/tips/ikiwiki_as_a_requirements_management_tool.mdwn +++ b/doc/tips/ikiwiki_as_a_requirements_management_tool.mdwn @@ -50,7 +50,7 @@ This is the most important feature of a requirements engineering tool. How to do * One simple solution: Links. Just link from one requirement to another one to create a traceable directional connection * One harder: file attributes (see section about requirements just above) -For coverage analysis , using [/ikiwiki/directive/pagecount] is the perfect solution to summarize and show covered and uncovered requirements. We could add several pages per module - probably using template pages- with ready made coverage analysis reports... Wow!!! [/ikiwiki/directive/linkmap] directive can show traceability information graphically. +For coverage analysis , using [ikiwiki/directive/pagecount] is the perfect solution to summarize and show covered and uncovered requirements. We could add several pages per module - probably using template pages- with ready made coverage analysis reports... Wow!!! [ikiwiki/directive/linkmap] directive can show traceability information graphically. Navigating among requirements needs... Nothing!!! Just follow the links of referring pages that ikiwiki adds by default. |