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
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
Hi, I've just started on a project where we will be working with an implementation partner to deliver a large set of HR solutions (HCM, Payroll, Rostering etc) - a COTS solution as a managed service.
I'm trying to implement some traceability between our functional and non-functional requirements, the design documents held in Confluence (including design discussions and decisions, and configuration workbooks), and test cases. I want to make sure that all design and configuration decisions are made with the original requirements taken into account, and that testing can also occur against these requirements. In other words, I want to be able to link requirements into existing pages in Confluence and track where each requirement is being referenced, as well as allow the requirements to be linked to test cases.
The complicating factor is that we have the cloud version of Confluence & Jira.
Testing will be managed with the TM4J add-in, but I've found out that the corresponding R4J add-in for requirements is not available for cloud.
I've used Requirements Yogi elsewhere before and really like it, but it's also not available for cloud.
Does anyone have any recommendations for what I could use? The main thing I've come across so far is rmcloud - is that likely to be able to do what I want?
Do you just want Traceability or do you want features related to requirements management too?
If you need features related to requirements management also, can you please elaborate on this?
Thanks for your reply, particularly at this time of year!
The high level requirements (our business requirements) were set at ITO stage, so these will be our baseline requirements at the top of the tree.
We'll be looking at adding system or configuration requirements that trace back to these business requirements as we progress through the design phase in collaboration with our implementation partner, so we'll need to keep an eye on the coverage of those requirements as well as any changes along the way. These will also be the 'testable' requirements level, so will need to be traced to the test cases in TM4J.
Still working our way through structure, but this is my plan at the moment.
Hi, @Melissa Field. It sounds like you already found Structure Cloud and that you found a suitable implementation partner. But, if it helps, we know Atlassian Solution partners who have expertise in this area and who know Structure quite well. You may want to speak with them as well, even if informally.
And, of course, we can answer questions for you, too. firstname.lastname@example.org
-dave [ALM Works]
For the Traceability needs, you can try out the addon Links Explorer Traceability and Hierarchy. This is available for Jira Cloud.
Unfortunately when it comes to requirements management, the only option available right now is rmcloud which has some limited set of features.