Requirements ManagementRequirements Management

IntroductionsRecap: Team Foundation ServerRequirements Management in TFS

Document-based ApproachItem-based Approach

Comparison: Borland CaliberRMQ&AClose & Next Steps

Business Business AnalystAnalyst

Operations, QA Operations, QA and Help Deskand Help Desk Third-PartyThird-Party

IDEsIDEs

Web Clients Web Clients and XML Web and XML Web ServicesServices

Two ApproachesDocument-basedItem-based Approach

Many variations to both approaches

Leverage Team Portal site (SharePoint) for document control & approvalDocuments accessible via portal, Team System, TFS Web Access

Benefits Drawbacks

• Analysts remain in comfort application (Word, etc.)

• SharePoint is a "natural" extension in Word/Office applications

• Requirement specs more easily consumed by other roles in lifecycle.

• Provides basic mechanism to enable traceability and better "cross-artifact" reporting.

• Lack of item-level granularity.

• Document-level linking only (can't link to an individual requirement inside specification document)

• Document Workflow managed by SharePoint, whereas Workflow for other lifecycle artifacts are managed by TFS.

Leverage Work Item Tracking in TFSIncreased granularity Complete control over form, fields, permissions, workflow, etc.Full link-support

Work Items (other req’s, bugs, tasks, etc.)SourceTest Results

Accessible (Team System, TFS Web Access, Excel, etc.)Detailed reporting

Benefits Drawbacks

• All changes will be recorded and audited

• Consistency• Links can be created between

individual requirements and other work items (any type), source code, test results, and hyperlinks)

• Workflow is enforced and controlled in the same manner as all other work item types

• Supporting information (screenshots, documents, UML diagrams, etc.) can be attached

• Reporting can be much more granular (showing requirement implementation rates, impact analysis, scope creep).

• Change of interface may meet resistance (i.e. no more Word!)

• Customization involved• Work item types, fields, &

workflow• Reports

Document-Based Item-Based

Interface Any Any TFS client

Repository SharePoint TFS Work Item Tracking

Granularity Document Requirement

Workflow SharePoint TFS Work Item Tracking

Customization Some on the SharePoint Site

Work Item types, fields, workflow & reports

Consistency Rely on Word (or other) templates. Difficult to enforce

Consistent UI, data capture via Work Item Tracking

Whitepaper: Requirements Management and Visual Studio Team System: http://www.microsoft.com/downloads/details.aspx?FamilyId=EEF7BB41-C686-4C9F-990B-F78ACE01C191

Blog Series: Requirements and TFS: http://tinyurl.com/4vevpc

Questions?

© 2006 Microsoft Corporation. All rights reserved.© 2006 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.