urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Minor changes

master
http://oscarjacho.myopenid.com/ 2009-09-02 17:24:47 -04:00 committed by Joey Hess
parent 086b90c313
commit dd96853fe3
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/tips/ikiwiki_as_a_requirements_management_tool.mdwn
View File

@ -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.