Requirements Authoring Starter Kit

Are you looking for a way to easily (and cheaply) integrate requirements authoring into Visual Studio Team System? If so, you’ll want to take a look at the Requirements Authoring Starter Kit. This is the solution I blogged about back in February (Requirements Authoring Solution).

The kit integrates and uses a number of Microsoft products:

  • Microsoft Office Word 2003
  • Microsoft SQL Server 2005
  • Microsoft Windows SharePoint Services
  • Microsoft Visual Studio 2005 Tools for Office
  • Microsoft Visual Studio 2005 Team Suite
  • Microsoft Visual Studio 2005 Team Foundation Server

Learn how the Requirements Authoring Starter Kit (RASK) can help software development teams collect, interpret, distribute, and synchronize project requirements in a structured Word document using Microsoft Visual Studio 2005 Tools for the Microsoft Office System and the Microsoft Visual Studio 2005 Team Foundation Server.

From: Microsoft Downloads – Requirements Authoring Starter Kit

You can learn more from this two-part article:


Comments (9)

  1. Add item to SharePoint list but returning to another

    location [Via: Serge van den Oever [Macaw]


  2. Rob says:

    The installer dumps all the files into a single directory, instead of one per project that the solutions are expecting, so nothing will compile, and the assemblyinfo.cs of each project overwrites the last one etc.  Does anybody test this stuff?

  3. Peter Bauwens says:

    Too bad the installer doesn’t create the original directory structure, which is why the included cmd files and projects are unusable without manual intervention…

  4. RobCaron says:

    We’re working on a new installer to address the issue with the directory structure.

  5. Neil Davis says:

    Do you know when it will be available?

  6. Rob Caron posts:

    Requirements Authoring Starter Kit

    Hands on with Microsoft Team System

    DSL Tools:…

  7. Rod says:

    Hi Rob,

    Is there a way to improve the performance in rendering of nodes in the document besides setting screenupdating to false? Or is there a way we can render nodes in memory before dumping it in document?

    Currenlty we can not do this:

    Word.XmlNode node = new Word.XmlNode();

    Currently the only way to instanciate a node si to do this:

    Word.XmlNode node = Globals.ThisDocument.Nodes[1];



  8. yuhang sun says:

    RASK is using structured word files. There is another interesting way to do TFS and word integration.  This approach doesn’t impose any special formatting on word documents. Its key feature is to allow users add Hyper Link (Smart Tag) referring to Work Items. Users can create/track/edit work items via the links inside Word Documents. Please go to to give it a try.

Skip to main content