Requirement Specification- Add chapters for descriptions
Posted: Fri Jun 19, 2009 10:16 pm
Hi,
i would like to write a "complete" requirement specification in test link.
The current problem with testlink is that it just has one scope chapter and that then every subchapter has to be a requirement.
However if you write full requirement specifications, you often have text that describes the topic and explains scenarios based on pictures, tables These chapters are not necessarily requirements and you don't want to count these.
Is it possible to use the same concepts that you have for Test cases (i.e. TestSuites, that contain test suites that may contain test cases) for
Requirements?
I.e. you have a RequirementSuite, that can contain RequirementSuites, which can or may not contain requirements.
This way you can generate a document that can resembles a real specification.
Any comments?
i would like to write a "complete" requirement specification in test link.
The current problem with testlink is that it just has one scope chapter and that then every subchapter has to be a requirement.
However if you write full requirement specifications, you often have text that describes the topic and explains scenarios based on pictures, tables These chapters are not necessarily requirements and you don't want to count these.
Is it possible to use the same concepts that you have for Test cases (i.e. TestSuites, that contain test suites that may contain test cases) for
Requirements?
I.e. you have a RequirementSuite, that can contain RequirementSuites, which can or may not contain requirements.
This way you can generate a document that can resembles a real specification.
Any comments?