(no commit message)

[git.ikiwiki.info.git] / doc / tips / ikiwiki_as_a_requirements_management_tool / discussion.mdwn

diff --git a/doc/tips/ikiwiki_as_a_requirements_management_tool/discussion.mdwn b/doc/tips/ikiwiki_as_a_requirements_management_tool/discussion.mdwn
index 94f0f8b4ba652e5e51afe0a9cde756ec09b02ac3..26eae28a5e6c554083d51bb8be895ee7850ec8b7 100644 (file)
--- a/doc/tips/ikiwiki_as_a_requirements_management_tool/discussion.mdwn
+++ b/doc/tips/ikiwiki_as_a_requirements_management_tool/discussion.mdwn
@@ -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.).
     + \[[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?