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

Question about experience with this requirements engineering tool as modelled

master
cslotty 2012-03-13 15:08:50 -04:00 committed by admin
parent 90c07225f4
commit a0e0717394
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/tips/ikiwiki_as_a_requirements_management_tool/discussion.mdwn
View File

@ -16,3 +16,6 @@ This could be as simple as adding a link, fo e.g. :
+ \[[attributes/non-functional]]
You just have to create pages for each attribute you want and then pagespec could be used to filter requirements by attributes. I think something similar is used to trac bug with ikiwiki (linking to a \[[done]] page, etc.).
---
Generally speaking, I think it's always a good idea to get back to the "basics" for something, that huge and expensive tools were made for. But I'm doubtful if such a text oriented tool would really fit all needs of a requirements engineering tool... so what is your real world experience with your requirements engineering tool as described?