יום רביעי 13 יוני 2012 14:39I am beginning a project in which we have 2500 requirements to manage and trace. I am using CMMI templates and have all the requirements loaded as workitems. I need to establish traceability from requirements to certain components of the system. Right now, my struggle is where/what template to use for the Design phase of the project. Design is where we analyze requirements and then design a piece of the system (software) to realize the requirements. So, where best to create this artifact? I was envisioning using Word/Visio for doing the actual design but then I want to link it to the numerous requirements it implements. Should I create a work item (and if so should it be a task, change request, or other work item type). If not, should I create the Design as a document within the TFS Project and then just link requirements to it? I would prefer to have these design documents contain additional attributes which if I use the latter method, it won't support. Any help would be appreciated on the best practices here. I have searched the internet for a couple days and am coming up dry.
- הועבר על-ידי Esther FanMicrosoft Employee, Moderator יום חמישי 14 יוני 2012 18:00 (From:Visual Studio Visualization & Modeling Tools)
יום שישי 15 יוני 2012 00:16
You can use the power tool of TFS to modify the process of your team project.
In your case I can see that you want to have a new work item type to capture the Designs, and then create from a Design work item the Requirement work items (which have a parent/child relationship). You can then either link the docs by using a hyperlink to sharepoint or attaching it to the work item.
Please remember to mark the replies as answers if they help.