From a0e071739405787cb1c0c7151c62567178cd2e8c Mon Sep 17 00:00:00 2001 From: cslotty Date: Tue, 13 Mar 2012 15:08:50 -0400 Subject: [PATCH 1/1] Question about experience with this requirements engineering tool as modelled --- .../ikiwiki_as_a_requirements_management_tool/discussion.mdwn | 3 +++ 1 file changed, 3 insertions(+) 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? -- 2.45.2