aboutsummaryrefslogtreecommitdiff
path: root/doc/tips
diff options
context:
space:
mode:
authorcslotty <cslotty@web>2012-03-13 15:08:50 -0400
committeradmin <admin@branchable.com>2012-03-13 15:08:50 -0400
commita0e071739405787cb1c0c7151c62567178cd2e8c (patch)
treed6a7a8c4a378f97d28c62dab082cbabe6b0735ae /doc/tips
parent90c07225f436c5dfb043c13eadd7962a95621f27 (diff)
downloadikiwiki-a0e071739405787cb1c0c7151c62567178cd2e8c.tar
ikiwiki-a0e071739405787cb1c0c7151c62567178cd2e8c.tar.gz
Question about experience with this requirements engineering tool as modelled
Diffstat (limited to 'doc/tips')
-rw-r--r--doc/tips/ikiwiki_as_a_requirements_management_tool/discussion.mdwn3
1 files changed, 3 insertions, 0 deletions
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 94f0f8b4b..26eae28a5 100644
--- 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.).
+
+---
+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?