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
We currently use Jira to manage our detailed design documents.
But I'm still not sure if this is the correct form.
Reusability seems to be poor, and the link with SRS takes too much work.
I purchased another app to manage the detailed design, but this only improved the management of the detailed design, but did not help with efficient writing.
Although it is very difficult for developers to write, it is very easy for administrators to manage SRS-based traceability.
The detailed design was reviewed based on Confluence, but in this case, the detailed design is expected to be managed in several documents.
It will increase usability for developers, but I'm not sure it will manage traceability well with a Jira-based SRS.
Our development code (features) is very large and complex.
I'm not sure Confluence-based detailed design can handle this.
Please give your opinion on a good way to ensure both developer usability and administrator SRS traceability.