I'm evaluating requirements tools for possible purchase, and Confluence is one I'm looking into.
Confluence is one I'm considering. Here are our needs. How does Confluence fit with them?
Each requirement must have a unique identifier.
Multiple (all?) requirements kept in a single database.
Relationships Between Requirements
Many-to-many relationships between requirements
Requirements Traceability Matrix
Able to generate an RTM, both top-down and bottom-up
Types of Requirements
Supports defining varying classes of requirement (i.e. Enterprise, System, Operational, Interface) with varying fields for each class (i.e. ID, Name, Description, Notes)
There should be a capability to establish a workflow for generation and approval of requirements.
There should be the capability to baseline requirements – for instance, tag a set of requirements as being for a specific release.
There should be a capability to roll back requirements.
- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events