locked
How to use VS 2012 / TFS for requirement engineering RRS feed

  • Question

  • Hi,

    we are moving from waterfall to agil. We have already a lot of requirements with associations between them. For requirements analysis  with the business people we need still the old styled requirements / actors etc.

    The question is, what is the most suitable mapping, how to put and how to visualize requirements, actors and use cases in  VS 2012 / TFS 2012 ?

    Mapping

    1. Requirement = ?
    2. UseCase = StoryBoard (?)
    3. Actor = ?

    Thanks a lot in advance,

    Michel


    Saturday, June 22, 2013 10:27 AM

Answers

  • Hi!

    If you want to support traditional requirements - you may use cmmi process template. Mapping

    1. Requirement = Requirement with type Functional, Operational ...

    2. Use Case = Requirement with type Scenario + StoryBoard

    3. Actor = You may add your own type Actor for Requirement

    • Marked as answer by Michel777 Sunday, October 27, 2013 10:06 PM
    Sunday, October 27, 2013 11:23 AM

All replies

  • Hi Michel,

    I am moving your thread into the Team Foundation Server - General Forum for dedicated support. Thanks for your understanding.

    Best Regards,


    Jack Zhai [MSFT]
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Monday, June 24, 2013 7:41 AM
  • Hi,

    Thanks for your post!

    First, you need to install TFS 2012 as the server for application lifecycle management, and VS 2012 as your client. For more information, please refer to TFS installation guide: http://www.microsoft.com/en-us/download/details.aspx?id=29035 , which includes the System Requirements, Prerequisites for TFS, Accounts and Ports Required for TFS Installation, and how to install TFS step by step.

    Second, you need to know the some theory for Agile, please refer to Application Lifecycle Management with Visual Studio and Team Foundation Server in this link: http://msdn.microsoft.com/en-us/library/fda2bad5.aspx. there are three types of process template which you can choose for your team project. For more information, please refer to http://msdn.microsoft.com/en-us/library/vstudio/ms400752.aspx 

    Third, please refer to a tutorial that follows members of a fictitious team as it incrementally adopts Visual Studio as its solution for application lifecycle management (ALM), which will give you an example how to use TFS in your work.

    http://msdn.microsoft.com/en-us/library/vstudio/dd286491.aspx

    Hope it helps!

    Best Regards,


    Cathy Kong
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Monday, June 24, 2013 8:00 AM
    Moderator
  • Hi Cathy,

    thanks a lot for your effort !  I have already done all of the mentioned tasks. There is only my qustions open:

    Mapping

    1. Requirement = ?
    2. UseCase = StoryBoard (?)
    3. Actor = ?

    Have you perhaps ideas ?

    Thanks a lot in andvance,

    Michel


    • Edited by Michel777 Monday, June 24, 2013 8:20 AM correct
    Monday, June 24, 2013 8:20 AM
  • Hi Michel777,

    Thanks for your feedback!

    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
     
    Thank you for your understanding and support.

    Best Regards,


    Cathy Kong
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Tuesday, June 25, 2013 3:15 AM
    Moderator
  • Hi Cathy,

    any news ?

    Warm regards,

    Michel

    Sunday, October 27, 2013 8:35 AM
  • Hi!

    If you want to support traditional requirements - you may use cmmi process template. Mapping

    1. Requirement = Requirement with type Functional, Operational ...

    2. Use Case = Requirement with type Scenario + StoryBoard

    3. Actor = You may add your own type Actor for Requirement

    • Marked as answer by Michel777 Sunday, October 27, 2013 10:06 PM
    Sunday, October 27, 2013 11:23 AM