You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
Identifier
Each requirement must have a unique identifier.
Single Database
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)
Reporting Capability
Workflow
There should be a capability to establish a workflow for generation and approval of requirements.
Baselining
There should be the capability to baseline requirements – for instance, tag a set of requirements as being for a specific release.
Rollback
There should be a capability to roll back requirements.
Yes, as @Davin Studer said, this is definitely a description of Jira. Most of your requirements can be fulfilled with Jira.
Thanks to you both.
Looks like our customer will be providing us with a Jira installation next week (for certain values of "next week") so I'll be able to explore it.