First of all im sorry that i am posting a little dissimilar issue. But i dont have any other forums to post to. Please let me know if you know any related forum for my issue.
My issue is related to Software Development Process. I am working for a firm where we are capturing requirements from client in following manner: 1) Firstly we prepare a BRS (Business Requiremet Specification) document by the functional and other docs given by the client. Note - BRS captures only the Business Requirements. 2) Then we prepare SRS (Software Requirement Specification) document in which we just expand BRS requirement points into detailed Use cases. SRS captures technical requirements at use case level, not at Class level. 3) In end we prepare IDD (Integrated Design Document) in which we further expand SRS requirement points into detailed coding level defining the class diagrams and sequence diagrams.
Now the issue is that we need to maintain a connection chain from BRS -to- SRS -to- IDD. This connection/mapping we need for handling Change Requests and doing Impact Analysis. We are maintaining an excel sheet for that named as RTM (Requirements Tracibility Matrix).
This PROCESS of maintaining RTM is so cumbersome. Its an overhead and consumes lots of time. Please any of you guys who is or was a part of Process, please give some suggestions or guidelines by which we can do some betterment in this workflow.
Thanks for Reading... do suggest something
Joined: Sep 16, 2007
I think, you should go for CodeBeamer 5.x, It has a free variant as well as paid variants , but i think, Free variant will be enough for your needs (based on your question).
And which SCM you use?? You will be able to integrate with your code commits also. It is great software for software requirement, task, bug, change request management. I love it, but our department does not accepted it, they like excel files.
Before software can be reusable, it first has to be usable. - Ralph Johnson
Originally posted by Inderpal Dhami: ... We are maintaining an excel sheet for that named as RTM (Requirements Tracibility Matrix).
This PROCESS of maintaining RTM is so cumbersome. Its an overhead and consumes lots of time. ....
Ooops so many documents !!!
One thing I can assure from your description is that you will not able to able to deliver quality software on time. Sooner or later, this RTM document will become so outdated that even anybody wanting to update this will have nightmares.
Two things you can do: 1. Convince your supervisor to switch to Agile 2. Change the job
You can't wake a person who is <b><i>pretending</i></b> to be asleep.<br />Like what <b>"it"</b> does not like - <i> Gurdjieff </i>
Joined: Apr 16, 2008
If an organization has adopted a mature software documentation process, then it should also invest in technologies that support these processes.
Software tools such a Rational Asset Manager help organizations create, modify, govern, find and reuse any type of development asset, i.e. Use-case narratives, class diagrams, etc.