Requirements Management

Thursday, October 6, 2016


I have some question concerning the requirements management tools of SpiraTeam.

My main question is the ability to link requirements to different features, such as customer specifications, mechanical parts and assemblies, mechanical and electronic BOMs etc. What kind of links does the software support?

For example, I have a requirement and I use a certain COTS product or a specially designed mechanism to satisfy it. Can I link them? I suppose I can, the question is to what extent? In other words, can I link different documents, such as vendor specs, pictures, CAD models etc.?

Thank you,


3 Replies
Thursday, October 6, 2016
re: Guy Thursday, October 6, 2016

More questions concerning the requirements:

1. Are there any structured types of requirements already built in the software, such as functional, non-functional, performance, design etc. requirements? Is it possible to define new types of requirements?

2. Is it possible to define a requirement as a sub-requirement, such as derived or refining requirements of a main requirement? The same question is about the original customer requirements, can I trace back to them?

3. Are there any special fields for quantitative requirements where I assign a number and its unit to a certain requirement? For example “the mass should be no more than 1 kg”. Are there two different columns available, one for the number (1) and the other for its unit (kg)?

4. Does the software allow defining constraints as opposed to requirements?

Monday, October 10, 2016
re: Guy Thursday, October 6, 2016
Also, is any risk management tool available?
Tuesday, October 11, 2016
re: Guy Monday, October 10, 2016
Hi Guy

To answer the questions:

1) You can link a requirement to other "requirements" of different types (features, design elements, use cases, etc.) using the Association tab. You can link requirements to defects and Source Code revisions also using this tab. To link the requirement to images, drawings and other 'attachments' you would just use the Attachments tab instead.

2) We have various requirement types built in - feature, use case, design element, user story, quality (the -ilities), you can see them in the requirements type field for the requirement.

3) For the quantitative side of requirements you can do that using custom fields to capture such values. We are also planning adding support for quantitative values as part of the requirement definition itself in the future.

4) Constraints are typically defined as one of the Incident Types and then they are linked to the requirement using the Associations tab

5) We provide Risk as a type of incident already, which then appears in the Project "Top Open Risks" section. These Risks can then be associated with the Requirement using the Associations tab.

Please let me know if you have any questions.



Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885


  • Started: Thursday, October 6, 2016
  • Last Reply: Tuesday, October 11, 2016
  • Replies: 3
  • Views: 1897