Comments on: Traceability must be planned http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/ Connecting Business Requirements to Technology Mon, 30 Jan 2012 21:31:56 +0000 hourly 1 By: oCraig http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/comment-page-1/#comment-1079 oCraig Thu, 11 Oct 2007 12:54:26 +0000 http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/#comment-1079 Kerber Extend the columns out to the testing phases and then to implementation. Plan your requirements' journey right through to the end. When things get dropped off you are alerted. Also it helps you get your test plan and test cases organized early. Kerber Extend the columns out to the testing phases and then to implementation. Plan your requirements’ journey right through to the end. When things get dropped off you are alerted. Also it helps you get your test plan and test cases organized early.

]]> By: Kerber http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/comment-page-1/#comment-1078 Kerber Wed, 10 Oct 2007 20:29:39 +0000 http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/#comment-1078 I'm with Jakub, requirements traceability is not clear for me too. Each new project seems to show me the need for more traceability. One tool I'm using now is a simple table, as suggested by you, that contains the scope items (user requirements), the use case it affects and a description of how the requirement affects the use case. It is particular useful when you are modeling changes in a system that already exists because the system analyst does not have search for modifications in the use cases or compare the current documentation with the previous one. Kerber ITBA - Digitro Technology www.digitro.com www.kerber.com.br I’m with Jakub, requirements traceability is not clear for me too. Each new project seems to show me the need for more traceability. One tool I’m using now is a simple table, as suggested by you, that contains the scope items (user requirements), the use case it affects and a description of how the requirement affects the use case. It is particular useful when you are modeling changes in a system that already exists because the system analyst does not have search for modifications in the use cases or compare the current documentation with the previous one. Kerber ITBA – Digitro Technology http://www.digitro.com http://www.kerber.com.br

]]> By: Jakub Strzemżalski http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/comment-page-1/#comment-1077 Jakub Strzemżalski Wed, 10 Oct 2007 06:35:11 +0000 http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/#comment-1077 Barbara, Craig, Thanks very much for your suggestions, will definately give them a try. Actually the first technique will be perfect for me right now as I'm thrown into an already ongoing project and I'm not quite clear about where all the ideas originate from :) Barbara, Craig,

Thanks very much for your suggestions, will definately give them a try.

Actually the first technique will be perfect for me right now as I’m thrown into an already ongoing project and I’m not quite clear about where all the ideas originate from :)

]]> By: Craig Brown http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/comment-page-1/#comment-1076 Craig Brown Wed, 10 Oct 2007 03:00:40 +0000 http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/#comment-1076 Thanks Barbara! i love a good RTM. One of the most useful management and comms tools a BA can have. Jakub - How about excel as a starter. You know the tool and requirements themselves can vary by project. put in a column for each phase of the project and tick or comment as you pass through it. <a href="http://betterprojects.blogspot.com/search?q=v-model" rel="nofollow">Here is an example</a> software dev process with milestones for a reference point. Thanks Barbara! i love a good RTM. One of the most useful management and comms tools a BA can have.

Jakub – How about excel as a starter. You know the tool and requirements themselves can vary by project. put in a column for each phase of the project and tick or comment as you pass through it.

Here is an example software dev process with milestones for a reference point.

]]> By: Barbara Carkenord http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/comment-page-1/#comment-1075 Barbara Carkenord Wed, 10 Oct 2007 02:58:23 +0000 http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/#comment-1075 Jakub, You are not the only one learning about traceability. The easiest tool is a matrix (you can use an Excel spreadsheet or Word table). Any of your requirements components can be traced. For example, if you have high level project objectives you can matrix them against detailed requirements. You are showing which requirements will support each objective. If you find an objective without any requirements than you missed a requirement. If you find a requirement that doesn't support an objective, you have an unnecessary requirement or missing objective. Try it out and see how you like it! Let us know how you do. Jakub,
You are not the only one learning about traceability. The easiest tool is a matrix (you can use an Excel spreadsheet or Word table). Any of your requirements components can be traced. For example, if you have high level project objectives you can matrix them against detailed requirements. You are showing which requirements will support each objective. If you find an objective without any requirements than you missed a requirement. If you find a requirement that doesn’t support an objective, you have an unnecessary requirement or missing objective. Try it out and see how you like it! Let us know how you do.

]]> By: Jakub Strzem&#380;alski http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/comment-page-1/#comment-1074 Jakub Strzem&#380;alski Tue, 09 Oct 2007 16:47:03 +0000 http://www.b2ttraining.com/2007/10/09/traceability-must-be-planned/#comment-1074 I must admit that requirements traceability is still a dubious subject for me, could you suggest some sample techniques or tools which could be helpful in the process? I must admit that requirements traceability is still a dubious subject for me, could you suggest some sample techniques or tools which could be helpful in the process?

]]>