Caliber™ 11.0 for VisualStudio Team Systems

Getting StartedGetting Started

Caliber - Visual Studio 2010 Integration ...................................................................................................... 7About Caliber .............................................................................................................................................. 8Tour of Caliber ............................................................................................................................................. 9

2

ConceptsConcepts

Projects ...................................................................................................................................................... 13Baselines ................................................................................................................................................... 14Requirements ............................................................................................................................................. 15Requirement Attributes .............................................................................................................................. 16Requirement Validation .............................................................................................................................. 17Requirement References ........................................................................................................................... 18Requirement Discussions .......................................................................................................................... 19Requirement History .................................................................................................................................. 20Requirement Traceability ........................................................................................................................... 21Requirement Change Notifications ............................................................................................................ 22Requirement Grid ....................................................................................................................................... 23

3

ProceduresProcedures

Projects ...................................................................................................................................................... 27Enabling the Integration with Visual Studio 2010 Work Items and Tests ........................................... 28Logging Off from Caliber ..................................................................................................................... 29Logging on and Selecting a Caliber Project ........................................................................................ 30Removing a Project ............................................................................................................................ 31

Requirements ............................................................................................................................................. 32Browsing Requirements ...................................................................................................................... 33Creating a Requirement ...................................................................................................................... 34Deleting a Requirement ...................................................................................................................... 35Displaying Groups of Requirements Using the Requirement Grid ..................................................... 36Participating in Requirement Discussions .......................................................................................... 37Refreshing Requirements ................................................................................................................... 38Viewing and Editing Requirement Description .................................................................................... 39Viewing and Editing Requirement References ................................................................................... 40Viewing Requirement Attributes ......................................................................................................... 42Viewing Requirement Change Notifications ....................................................................................... 43Viewing Requirement History ............................................................................................................. 44Viewing Requirement System Attributes ............................................................................................ 45Viewing Requirement Validation Procedures ..................................................................................... 46

Requirement Traceability ........................................................................................................................... 47Creating a Trace between a Requirement and a Test ........................................................................ 48Creating a Trace between a Requirement and a Work Item .............................................................. 49Creating a Trace between Requirements ........................................................................................... 50Modifying Requirement Traces ........................................................................................................... 51

4

Getting Started

5

Getting StartedThe topics in this section are designed to help you understand and begin using Caliber 11.0 with Visual Studio.

In This SectionCaliber - Visual Studio 2010 IntegrationThis section provides information about the integration between Caliber and Visual Studio 2010.

About CaliberThis section describes Borland Caliber.

Tour of CaliberThis section provides information about the Caliber user interface in Visual Studio.

6

Caliber - Visual Studio 2010 IntegrationCaliber 11.0 integrates with Visual Studio 2010 to provide Visual Studio users with the following capabilities andfeatures:

♦ Simple integration plug-in installation as a Visual Studio extension.

♦ Visibility into Caliber projects and requirements directly from within Visual Studio.

♦ Open and view requirements and inspect requirement details, attributes, versions and change history directlyfrom within Visual Studio.

♦ Allows Visual Studio users to participate in requirement discussions, attach or modify references torequirements and create traceability from requirements to Visual Studio and Team System artifacts includingwork items and tests. Additionally, Visual Studio users can open the full Caliber Author from within Visual Studioto edit requirements.

Related Concepts

About CaliberProjectsRequirements

Related Procedures

Logging on and Selecting a Caliber Project

7

About CaliberCaliber™ is an enterprise requirements management system designed to facilitate collaboration, impact analysis,and communication in the definition and management of changing requirements. Caliber helps organizations—largeor small, in local or global offices—effectively manage expectations across the lifecycle so that projects are deliveredon time, within scope, and according to specification. Designed for ease of use, the intuitive interface of the newclient for Microsoft Visual Studio provides developers the real-time access they need to requirements right in theirown IDE. Caliber also helps applications meet end-user needs by allowing all project stakeholders—marketingteams, analysts, developers, testers, and managers—to collaborate and communicate the voice of the customerthroughout the lifecycle.

Caliber provides the following capabilities and features:

♦ Visibility: Dynamic business demands makes visibility a must. Customers are faced with constantly evolvingsoftware requirements and less time, money or resources to deliver software.

♦ Communication & Collaboration: Business demands drive requirements which drives applicationdevelopment. All members of a project team need to have a common understanding of the requirements.Requirements need to be simple, complete, concise, testable and accurate. Software development teams areable to respond rapidly to ever-changing requirements.

♦ Control: Traceability and metrics reporting are key to proactively controlling a software project. To ensure theyare being fulfilled, requirements should be traced to other artifacts in the lifecycle such as design, tests, changerequests and source code files. Traceability allows enterprises to enable automated change notifications andimpact analysis. Requirements also have many important metrics concerning scope creep and volatility whichare key to understanding the status of projects.

Related Concepts

Caliber - Visual Studio 2010 IntegrationProjects

Related Procedures

Logging on and Selecting a Caliber Project

8

Tour of CaliberAfter you have opened a Caliber 11.0 project in Visual Studio, the Caliber Explorer displays the Caliber 11.0 projectrequirements. Expanding the project displays requirement types, and expanding requirement types displaysrequirements.

ProjectsYou can right-click on the project name to open the Requirement Grid.

Requirement TypesYou can right-click on a requirement type to add a new requirement.

RequirementsYou can click a requirement to view the following requirement information on a series of tabs:

♦ Details

♦ Responsibilities

♦ References

♦ Traceability

♦ Validation

♦ Discussion

♦ History

♦ Custom Attributes tabs

DetailsDisplays the requirement name, version, owner, status, priority and description.

ResponsibilitiesDisplays a list of users and groups.

ReferencesDisplays reference information for a requirement. You can reference a file of any of the following format: prototypescreens, document files such as Microsoft Word and Microsoft Excel, graphic files, HTML files, audio and video files,etc. You can also enter a text reference, so you can reference a book, periodical, or anything that is not online. URLsare added through web references.

TraceabilityAllows you to view and modify the relationships between requirements and other related development and testinginformation.

9

ValidationAllows you to view validation procedures for the selected requirement.

DiscussionDisplays all discussions for a requirement. Allows you to participate in existing discussions or start new discussions.

HistoryDetails all revisions made to a requirement, including changes to specific attributes, requirement descriptions, status,priority, etc. Displays the change history for a requirement. Change history includes who created the requirement,when the requirement was created and any revisions or changes to the requirement and the dates those changesoccurred.

AttributesDisplays all user-defined attributes for the selected requirement. Each requirement type can have multiple,customizable tabs. These are created and administered in the standalone Caliber client.

Related Concepts

Caliber - Visual Studio 2010 IntegrationRequirementsRequirement Attributes

Related Procedures

Logging on and Selecting a Caliber ProjectLogging Off from Caliber

10

Concepts

11

ConceptsThis section provides overview information about requirements and related functionality available in Caliber 11.0.

In This SectionProjectsThis section provides information about Caliber projects.

BaselinesThis section provides information about project baselines.

RequirementsThis section provides information about requirements.

Requirement AttributesThis section provides information about system and user-defined attributes of a requirement.

Requirement ValidationThis section provides information about requirement validation procedures.

Requirement ReferencesThis section provides information about requirement references.

Requirement DiscussionsThis section provides information about requirement discussions.

Requirement HistoryThis section provides information about requirement revision history.

Requirement TraceabilityThis section provides information about requirement traceability.

Requirement Change NotificationsThis section provides information about requirement change notifications.

Requirement GridThis section provides information about requirement groups and the requirement grid.

12

Projects

Caliber Projects in Visual StudioA Caliber project contains a collection of requirements that you need to manage as a whole, such as an applicationor system under development. Caliber projects consist of several types of information, including users and groups,requirement types and requirements.

Project AdministrationCaliber project administration is maintained in the Caliber Administrator component of the standalone Caliberclient.

Related Concepts

Requirements

Related Procedures

Logging Off from CaliberLogging on and Selecting a Caliber Project

13

BaselinesA Caliber project can contain multiple baselines that allow you to view sets of requirements at specific versions,using a single label to refer to the requirements.

The currently selected baseline appears in line with the name of the Caliber project.

The default baseline for a Caliber project is called Current Baseline. You can only edit requirements in the currentbaseline. For other baselines all requirements are read only.

Project Baseline AdministrationCreation of project baselines, and comparison of baseline content is performed in the standalone Caliber client.

Related Concepts

ProjectsRequirements

14

RequirementsRequirements are specifications that the application or system you are building must meet. Requirements canoriginate from many sources such as business rules, business process models, product marketing, prototypes,development meetings, and more.

Each requirement within a project has the unique ID (or serial) number that displays in the Requirement Tag/IDfield on the Details tab in the document window. The serial number does not change, regardless of the requirementposition, and it is not reused if the requirement is deleted.

Each requirement is assigned to a Requirement Type. Requirement Types are high-level groups of requirements,typically classified by their function (i.e., Business, Marketing, GUI, Hardware, Software, Testing, etc.).

Related Concepts

Requirement AttributesRequirement Traceability

Related Procedures

Requirements

15

Requirement AttributesAttributes are characteristics that help define a requirement. Both system and user-defined attributes are supportedin Caliber 11.0.

You can view and assign values to all requirement attributes. Requirement attributes are shown on the Details andUser Attributes tabs of a requirement document window.

System Attributes (Details)System attributes are those that Caliber automatically maintains for each requirement. The system attributes thatare maintained for each requirement are:

♦ Name—the name of the requirement

♦ Tag/ID—the tag of the requirement comes from the requirement type name; the serial number of therequirement is static and automatically generated; each ID number is unique in the system; if a requirementis deleted, that ID number will not be reused

♦ Version (see also requirement history)—the revision number of the requirement; when a change is made tothe requirement, the version number is automatically updated; the change may cause a major or minor revisionnumber change; a Caliber administrator determines this when attributes types are defined in the standaloneCaliber client

♦ Status—the requirement status

♦ Priority—the requirement priority

♦ Owner—the default Owner is the user who created the requirement; requirement ownership varies throughthe project life-cycle; typically, the beginning Owner is an analyst, after implementation, the Owner is adeveloper, and once the requirement is in testing, the Owner is a QA engineer

♦ Description—the requirement description

User-Defined AttributesUser-defined attributes help further define requirements and are optional. They can be one of several different typesof data, including text, long integer, date, boolean and users. A system administrator can set up the list of user-defined attributes in the standalone Caliber client.

For more information, please consult the Caliber User Guide.

You can view values for user-defined attributes in Caliber 11.0 if you have the appropriate permissions (as definedin the standalone Caliber client by the Caliber administrator), but you cannot create new attributes or remove theexisting attributes from your project.

Related Concepts

RequirementsRequirement History

Related Procedures

Viewing Requirement System AttributesViewing Requirement Attributes

16

Requirement ValidationIn the Caliber client, you can write a validation procedure for each requirement, which you can then view in theCaliber project as it appears in Visual Studio. Validation procedures are expressed as plain text for testers to read,not instructions for the system to process.

The validation procedure describes in “free form” how to verify that the requirement is implemented properly. Thevalidation procedure might also be a test case.

Usually, analysts write validation procedures for quality assurance engineers.

Validation procedures are shown on the Validation tab of a requirement document window.

Related Concepts

Requirements

Related Procedures

Viewing Requirement Validation Procedures

17

Requirement ReferencesYou can include additional information or resources for a requirement using requirement references. For example,you can reference a specification document, meeting notes, a link to a Web page, a screen shot or anything elsethat might be of use in defining or understanding a requirement.

You can have an unlimited number of references for each requirement. Requirement references are shown on theReferences tab of a requirement document window.

There are two differences between references and requirement traceability. You use references to link requirementswith external objects that help define a requirement. References are single-direction links, so you can traverse themonly from a source requirement.

There are three types of references:

♦ File reference

♦ Text reference

♦ Reference on the Web

File ReferencesYou use this type to reference an existing file on the network. Reference files are best placed on a shared drive forall users to access.

You can reference file of any type, such as Microsoft Word, Excel, Power Point, images, or HTML files.

The content of the file is not stored in the Caliber project. Caliber 11.0 keeps only the filename and path to areferenced file.

Warning: If the referenced file is no longer available or renamed, the reference becomes invalid.

Text ReferencesYou use this type to add a piece of text to a requirement. This text is stored in the Caliber project.

Web ReferencesYou use this type to link an external Internet resource. You need to specify a URL of a resource to reference. ThisURL is stored in the Caliber project.

Warning: If the referenced link is no longer available or renamed, the reference becomes invalid.

Related Concepts

RequirementsRequirement Traceability

Related Procedures

Viewing and Editing Requirement References

18

Requirement DiscussionsProject teams can provide feedback on requirements through discussions. This collaborative feature enables teammembers to enter and reply to comments to help define, refine, and prioritize requirements.

Each discussion is dedicated to a particular requirement. Discussion messages and replies are shown on theDiscussion tab of a requirement document window.

Caliber discussions are independent from Visual Studio discussions and are stored in the Caliber project.

You can receive email notification that a new message has been posted for a requirement. The Caliber administratormust first enable notifications in the Caliber Administrator, then you must be assigned as a responsible user toreceive change notifications. See the related information link below.

Related Concepts

Requirements

Related Procedures

Participating in Requirement DiscussionsViewing Requirement Change Notifications

19

Requirement HistoryCaliber 11.0 maintains a history record for each requirement. The history record assigns revision numbers and keepsa list of changes for each revision. All changes made to a requirement, including changes to specific attributes (therequirement description, status, priority, and so on) are recorded in the requirement history.

The current requirement version is displayed on the requirement Details tab.

Related Concepts

Requirements

Related Procedures

Viewing Requirement History

20

Requirement TraceabilityThe traceability feature allows you to create and track relationships between requirements and other relateddevelopment and testing information in your Visual Studio project. Such relationships are called "traces" and shownon the Traceability tab of a requirement document window.

Changing an object, whether it is a requirement, a test step, or a section of source code, can potentially requirechanges in other elements of the project. Tracing related objects helps to ensure that changes are implementedcorrectly at all levels.

Traces link requirements with internal objects of your team project. Traces between requirements are bidirectional,so you can traverse a trace from a source or destination requirement.

A requirement can trace to

♦ Another requirement in the same Caliber project or in another project located in the same Caliber server

♦ A work item in the same Visual Studio Team project or across projects

♦ A test in the same Visual Studio Team project or across projects

♦ Another object supported by custom vendor add-in modules

When you create a trace, Caliber 11.0 automatically implies traces to other requirements that can be affected. Forexample, if there are direct traces between a software requirement and an interface requirement, and between theinterface requirement and a coding requirement, there is also an implied trace between the software requirementand the coding requirement.

When you change a requirement, traces to other objects become suspect. Suspect traces are an indicator that otherobjects can be affected by the changed requirement and you should review them.

Related Concepts

RequirementsRequirement References

Related Procedures

Requirement Traceability

21

Requirement Change NotificationsCaliber 11.0 can notify one or more users by email about requirement changes. Notified users are shown on theResponsibilities tab of a requirement document window.

All team members have user accounts in the Caliber Server. Each user belongs to one or more groups.

Usually the Owner of a requirement assigns responsibility to the user or users who could be affected by changesmade to the requirement.

The Caliber administrator manages user accounts and groups and enables notifications in the CaliberAdministrator component of the standalone Caliber client.

For information on enabling notifications, please see the Caliber User Guide.

Related Concepts

Requirements

Related Procedures

Viewing Requirement Change Notifications

22

Requirement GridYou can view requirements in a spreadsheet format to sort requirements and export requirements to XML. The gridview displays the requirement type, tag, name, status, priority, responsible users, owner and user defined attributes.Selecting a requirement displays its description in the lower pane of the Requirement Grid.

Related Concepts

Requirements

Related Procedures

Displaying Groups of Requirements Using the Requirement Grid

23

24

Procedures

25

ProceduresThis section provides "how to" information.

In This SectionProjectsThis section provides information about tasks related to projects.

RequirementsThis section provides information about tasks related to requirements.

Requirement TraceabilityThis section provides information about tasks related to requirement traceability.

26

ProjectsCaliber project administration is performed in the Caliber Administrator component of the standalone Caliber client.

In This SectionEnabling the Integration with Visual Studio 2010 Work Items and TestsThis section describes how to enable the integration with Visual Studio 2010 work items and tests.

Logging Off from CaliberThis section describes how to log and off Caliber.

Logging on and Selecting a Caliber ProjectThis section describes how to log on to Caliber and select a Caliber project from within Visual Studio.

Removing a ProjectThis section describes how to remove a Caliber project from the Borland Caliber Explorer in Visual Studio.

27

Enabling the Integration with Visual Studio 2010 Work Items andTests

To enable the integration with Visual Studio 2010 work items and tests1 In Caliber Administrator, choose View Projects.2 Select the project in which to enable the integration.3 Right-click the External Traceability tab.4 In the Disabled column, select VSTS WorkItems and/or VSTS Tests.5 Click the arrow button to move the selected objects to the Enabled column.

Related Concepts

Projects

28

Logging Off from CaliberTo release the Caliber license you consume when logged on, you can log off Caliber from within Visual Studio.

To log off from Caliber1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Right-click the Caliber project node.3 Select Logout Caliber project. The project closes and you are logged off.

Related Concepts

Requirements

Related Procedures

Logging on and Selecting a Caliber Project

29

Logging on and Selecting a Caliber Project

To log on and select a project1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Click the link titled Click Here to Add a New Caliber project. The Caliber dialog box opens.3 Type your Caliber server name, User ID, and Password and click the Logon button.4 After a successful logon, select a project and baseline in the enabled Project and Baseline drop-down lists

respectively.

Note: To select a recently created Caliber project from Visual Studio, you must first open it inyour standalone Caliber client. This initializes the Caliber project and makes it available forselection in the Project drop-down list of the Caliber dialog box in Visual Studio.

5 Click the Add button to add the selected project of the selected baseline to the Borland Caliber Explorer.

Note: Every connection to Caliber consumes a Caliber license. Once you have finished viewing and working withrequirements in Visual Studio, consider logging off to free a license for other Caliber 11.0 users. Theconnection gets automatically broken by default.

Related Concepts

ProjectsBaselines

30

Removing a Project

To remove a Caliber project from a Visual Studio project1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Right-click the Caliber project node.3 Choose Remove Caliber project from the menu. Your Caliber project is removed from the Borland Caliber

Explorer.

Related Concepts

Projects

31

RequirementsThis section describes the tasks involved in working with requirements.

In This SectionBrowsing RequirementsDescribes how to browse requirements in a Caliber project opened from within Visual Studio.

Creating a RequirementDescribes how to create a requirement.

Deleting a RequirementDescribes how to delete a requirement.

Displaying Groups of Requirements Using the Requirement GridDescribes how to view a group of requirements using the requirement grid.

Participating in Requirement DiscussionsDescribes how to view and participate in a requirement discussion.

Refreshing RequirementsDescribes how to refresh requirements in a Caliber project opened in Visual Studio.

Viewing and Editing Requirement DescriptionDescribes how to view and edit description of a requirement.

Viewing and Editing Requirement ReferencesDescribes how to view and edit the list of references of a requirement.

Viewing Requirement AttributesDescribes how to work with requirement attributes.

Viewing Requirement Change NotificationsDescribes how to view requirement change notification settings.

Viewing Requirement HistoryDescribes how to view revision history of a requirement.

Viewing Requirement System AttributesDescribes how to view system attributes (details) of a requirement.

Viewing Requirement Validation ProceduresDescribes how to view requirement validation procedures.

32

Browsing Requirements

To browse requirements in a Caliber project1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Click the plus sign (+) to the left of the Caliber project node. The Caliber logon dialog box opens.3 Browse the requirements displayed.

Related Concepts

Requirements

Related Procedures

Requirements

33

Creating a RequirementThe Caliber integration with Visual Studio provides you with the basic ability to create requirements from within VisualStudio. However, you will find that creating requirements is easier in the Caliber standalone Windows client thatallows for relocation of requirements in the requirement tree, as well as inclusions of images, tables and hyperlinksin the requirement text.

To create a requirement1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Click the plus sign (+) to the left of the Caliber project node to expand the node.3 Right-click the desired requirement or Requirement Type and select Add Requirement from the context menu

to create a new requirement of that type. The new requirement's Details tab is displayed in the documentwindow.

Note: Alternately, to create a requirement as a child requirement of another, right-click arequirement in the requirement tree and select Add Requirement.

Related Concepts

RequirementsRequirement Attributes

Related Procedures

Deleting a Requirement

34

Deleting a RequirementYou can only delete a requirement if you have delete permissions as defined by the Caliber administrator in theCaliber Administrator component of the standalone Caliber client.

To delete a Caliber requirement1 Right-click the requirement to delete.2 Select Delete Requirement. A message box appears, verifying the deletion.

Warning: Once you delete a requirement, you cannot recover it.

3 Click Yes to delete the requirement. The requirement is deleted.

Related Concepts

Requirements

Related Procedures

Creating a Requirement

35

Displaying Groups of Requirements Using the Requirement GridThe Requirement Grid is used to display a set of requirements. The grid view includes the requirement type, tag,name, status, priority, users, owner and many other attributes.

To view the Requirement Grid1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Right-click the Caliber project that contains the requirements to view.3 Choose Requirement Grid from the context menu. The Requirement Grid dialog box opens.

Tip: To force the Requirement Grid to stay on top, choose View Always on top from thetoolbar menu.

Tip: To sort requirements, click on the column header to sort by that column.

Tip: To view requirement details, select the requirement in the Requirement Grid dialog box andchoose View Go to requirement from the toolbar menu.

To print the Requirement Grid1 Choose File Print from the Requirement Grid dialog box main menu. The Report Setup dialog box opens.2 Click the Print Preview button. This displays the Requirement Grid in a browser, from which you can follow

standard Windows printing procedures.

To export the Requirement Grid content to XML1 Choose File Print from the Requirement Grid dialog box main menu. The Report Setup dialog box opens.2 Click the Export button. The Save As dialog box opens.3 Enter the File name and specify where to save the file.

Note: The default file name is RequirementGridReport.xml.

4 Click the Save button. The Requirement Grid content is exported.

Related Concepts

RequirementsRequirement Grid

36

Participating in Requirement Discussions

To participate in a requirement discussion1 Select a Caliber project in Visual Studio. See Related Procedures below for details.2 Select a Requirement Type and click the plus sign (+) to expand the list of requirements.3 Select the requirement whose discussion you want to take part in.4 Select the Discussion tab. All messages posted for the selected requirement appear.5 Read, post, or reply to a message.

Note: To read a message, select the message you want to view from the list displayed. The text of the messageappears in the message text area at the bottom of the tab.

To post a message1 Click the Post New button. The New Message dialog box opens.2 Type a subject in a Subject field.3 Type a message in a message box.4 Choose File Post Message from the New Message dialog box menu. To exit without posting a message,

choose File Close from the New Message dialog box menu.

To reply to a message1 Select the message you want to reply to.2 Click the Reply button. The New Reply Message dialog box opens with the subject field filled out automatically.3 Type your message in your message box.4 Choose File Post Message from the New Message dialog box menu. To exit without posting a message,

choose File Close from the New Message dialog box menu.

Note: To update the message list, click the Refresh button on the Discussion tab.

You can receive email notification that a new message has been posted for a requirement.The Caliber administrator must first enable notifications in the standalone Caliber client, thenyou must be assigned as a responsible user to receive change notifications. See the relatedinformation link below.

Related Concepts

RequirementsRequirement Change Notifications

Related Procedures

Viewing Requirement System AttributesLogging on and Selecting a Caliber Project

37

Refreshing Requirements

To refresh requirements in a Caliber project1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Click the Refresh button on the the Borland Caliber Explorer toolbar.

The Login dialog box appears.

3 Type your login credentials, and then press Logon.The latest changes made to the Caliber project are refreshed and reflected in the project appearing in VisualStudio.

Related Concepts

RequirementsProjects

Related Procedures

Logging Off from Caliber

38

Viewing and Editing Requirement Description

To view the description of a requirement1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Select a requirement under the Caliber project node.3 Click the Details tab in the document window. The description of the requirement shows in the lower part of the

tab.

To edit the description of a requirement1 On the Details tab of the requirement window, click the Edit in Caliber button.

Note: This button is only enabled when the Caliber client is installed on the same computer asVisual Studio.

2 Make your changes to the description text. The description is stored in HTML format. You can insert images,tables, text formatting tags, and use other HTML features.

Note: After making changes, close the Caliber client to refresh the Caliber project appearing inVisual Studio.

Related Concepts

RequirementsRequirement Attributes

Related Procedures

Viewing Requirement System AttributesViewing Requirement Attributes

39

Viewing and Editing Requirement References

To view references of a requirement1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Click the References tab. This displays the list of items referenced from the current requirement.

Note: Requirement can reference a file on the network, a piece of plain text, or an Internet resource.

To create a file reference1 On the References tab, click the New File button. The Open dialog box opens.2 In this dialog box, choose the type of the file you need to reference.3 Browse for the target file on the network.

Tip: Reference files are best placed on a shared drive for all users to access.

4 Click Open.

Note: If the referenced file has been moved or renamed, you need to remove the reference and create a new one.If the content of the referenced file has been updated, you do not need to recreate the reference.

To create a text reference1 On the References tab, click the New Text button to create a new piece of plain text. The Text Reference

dialog box opens.2 In this dialog box, type in your text.3 Click OK.

To create a reference on the Web1 On the References tab, click the New Web button to reference a Web page or another Internet resource. The

Web Reference dialog box opens.2 In this dialog box, enter the URL of an Internet resource to reference, for example: http://

www.borland.com/.3 Click OK.

To edit a text or Web reference1 On the References tab, select a reference you need to edit.2 Right-click the reference and choose Edit Reference from the context menu. The Text (Web) Reference dialog

box opens.3 Make your changes.4 Click OK.

40

To remove a requirement reference1 On the References tab, select a reference you need to remove.2 Click the Remove button.

Alternatively, right-click the reference and choose Remove from the context menu.

The confirmation dialog box opens.

3 Click Yes.

The selected reference is removed from the list. For file references, the corresponding file is not deleted. For text orWeb references, the text or URL you entered is lost.

Related Concepts

RequirementsRequirement References

Related Procedures

Requirements

41

Viewing Requirement AttributesYou can view user-defined attributes available in your project by using the Caliber Administrator or standaloneCaliber client. For more information, please consult the Caliber User Guide.

To view and edit user-defined attributes of a requirement1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Select a requirement under the Caliber project node. A document window opens, displaying attributes of this

requirement.3 In the document window, click the User Attributes tab (this tab name will vary depending on your organization).

This shows optional user-defined attributes of the requirement. A user-defined attribute appears as a check box,a text field, a list box, a calendar chooser, or another window control.

Related Concepts

RequirementsRequirement Attributes

Related Procedures

Viewing Requirement System AttributesRequirements

42

Viewing Requirement Change NotificationsThis section describes how to view requirement change notification settings for a particular requirement.

Tip: You also need to enable automatic notification globally for your Caliber project. You can do it on the GroupAssignment tab in Caliber Administrator. See the Caliber User Guide for more information.

To view user notification settings of a requirement1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Select a requirement under the Caliber project node. The requirement document window displays the

requirement attributes.3 In the window, click the Responsibilities tab.

The Responsibilities tab shows the structure of user groups and accounts. Each of them has a check box. Thischeck box indicates whether this user or a group is selected, not selected, or partially selected for notification aboutchanges of the current requirement.

Related Concepts

RequirementsRequirement Change Notifications

Related Procedures

Requirements

43

Viewing Requirement History

To view history of a requirement1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Click the plus sign (+) to the left of the Caliber project node.3 Select a requirement under the Requirements (Borland Caliber) node. A tab appears and displays the

requirement attributes.4 In the document window, click the History tab.

The History tab shows the list of revisions for the selected requirement in the upper part of the window. The initialrevision is displayed at the top. The list of attributes changed at the selected revision is displayed at the lower partof the window.

To view all details of a change1 On the History tab, select a revision.2 In the attribute changes list, select a change.3 Click the Detail... button at the bottom of the window.

A dialog box opens displaying old and new values of the attribute, date and time of the change, name of the userwho made this change, and the user comments about the change.

Related Concepts

RequirementsRequirement AttributesRequirement History

Related Procedures

Requirements

44

Viewing Requirement System Attributes

To view system attributes of a requirement1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Select a requirement under the Caliber project node.3 Click the Details tab in the document window.

The Details tab shows system attributes of the requirement in the upper part of the window, and the description ofthe requirement in the lower part.

You can select a version of the requirement in the Requirement Version drop-down list for viewing. To edit arequirement, click the Edit in Caliber button to open the Caliber client from which you can edit the requirement.

Related Concepts

RequirementsRequirement Attributes

Related Procedures

Viewing and Editing Requirement DescriptionViewing Requirement AttributesRequirements

45

Viewing Requirement Validation Procedures

To view a validation procedure for a requirement1 Choose View Other Windows Borland Caliber Explorer from the menu.2 Select a requirement under the Caliber project node. The requirement document window displays the

requirement attributes.3 In the window, click the Validation tab. This displays the text of a validation procedure for the selected

requirement.

Related Concepts

RequirementsRequirement Validation

Related Procedures

Requirements

46

Requirement TraceabilityYou can create traceability relationships between requirements, requirements and Visual Studio tests, andrequirements and Visual Studio work items.

In This SectionCreating a Trace between a Requirement and a TestDescribes how to create between a requirement and a test.

Creating a Trace between a Requirement and a Work ItemDescribes how to create a trace between a requirement and work item.

Creating a Trace between RequirementsDescribes how to create a trace between requirements.

Modifying Requirement TracesDescribes how to modify requirement traces.

47

Creating a Trace between a Requirement and a Test

To create a trace between a test and a requirement1 Select a Caliber project in Visual Studio. See Related Procedures below for details.2 Select a requirement type and click the plus sign (+) to expand the list of requirements.3 Select the requirement you want to trace to a test.4 Select the Traceability tab.5 Click the Modify button. The Traceability Modification dialog box opens.6 Click the VSTS Tests tab. The list of available tests appears.

Note: The VSTS Work Items tab displays in Visual Studio only after you enable the Caliber 11.0integration in the Caliber Administrator. Refer to the “Enabling the Integration with VisualStudio 2010 Work Items and Tests” topic for details.

7 Select the test in the list and choose Trace Trace To or Trace Trace From from the menu. The traceindicator appears in the test list.

8 Click the Save all changes button. Your trace between a test and a requirement is now created.

Related Concepts

Requirement Traceability

Related Procedures

Logging on and Selecting a Caliber ProjectEnabling the Integration with Visual Studio 2010 Work Items and Tests

48

Creating a Trace between a Requirement and a Work Item

To create a trace between requirement and a work item1 Select a Caliber project in Visual Studio.2 Select a requirement type and click the plus sign (+) to expand the list of requirements.3 Select the requirement you want to trace to a work item.4 Select the Traceability tab.5 Click the Modify button. The Traceability Modification dialog box opens.6 Click the VSTS Work Items tab. The list of available work items appears.

Note: The VSTS Work Items tab displays in Visual Studio only after you enable the Caliber 11.0integration in the Caliber Administrator. Refer to the “Enabling the Integration with VisualStudio 2010 Work Items and Tests” topic for details.

7 Select the work item in the list and choose Trace Trace To or Trace Trace From from the toolbar. Thetrace indicator appears in the work item list.

8 Click the Save all changes button. Your trace between the requirement and work item is now created.

Related Concepts

RequirementsRequirement Traceability

Related Procedures

Logging on and Selecting a Caliber ProjectModifying Requirement TracesEnabling the Integration with Visual Studio 2010 Work Items and Tests

49

Creating a Trace between Requirements

To create a trace between requirements1 Select a Caliber project in Visual Studio.2 Select a requirement type and click the plus sign (+) to expand the list of requirements.3 Select the requirement you want to trace to a work item.4 Select the Traceability tab.5 Click the Modify button. The Traceability Modification dialog box opens.6 Select the requirement and choose Trace Trace To or Trace Trace From from the toolbar. The trace

indicator appears next to the requirement.7 Click the Save all changes button. Your trace between the requirements is now created.

Related Concepts

RequirementsRequirement Traceability

Related Procedures

Logging on and Selecting a Caliber ProjectModifying Requirement Traces

50

Modifying Requirement Traces

To modify a requirement trace with a work item or test1 Select a Caliber project in Visual Studio.2 Select a Requirement Type and click the plus sign (+) to expand the list of requirements.3 Select the requirement with the trace to modify.4 Select the Traceability tab.5 Select the Filter to display traces between requirements, VSTS Work Items, and VSTS Tests.6 Click the Modify button. The Traceability Modification dialog box opens.7 Modify the trace between the selected requirement and another requirement, work item or test.

Related Concepts

Requirement Traceability

Related Procedures

Requirement TraceabilityLogging on and Selecting a Caliber Project

51

Indexabout CaliberRM

CaliberRM, 8Borland CaliberRM, 7browsing

requirements, 33Caliber Administrator, 13CaliberRM interface

user interface, 9creating

trace between test and requirement, 48trace between work item and requirement, 49 50

Description, 16description

editing, 39detail

history, 44Details, 39displaying

requirement grid, 36file references, 18

creating, 40groups, 22history

viewing, 44HTML format, 39logon, log off, 29modifying

requirement traces, 51Name, 16notification

viewing, 43Owner, 16participating

requirement discussions, 37Priority, 16project

baseline, 14projects

project administration, 13references

viewing, 40editing, 40removing, 41

references on the Web, 18creating, 40

refreshingrequirements, 38

removingproject, 28 31

requirement change notificationsviewing and editing, 43

requirement descriptionviewing and editing, 39

requirement detailsviewing and editing, 45

requirement gridrequirement groups, 23

Requirement Grid, 36requirement references

viewing and editing, 40Requirement Type, 34requirement type, 48requirement validation

viewing and editing, 46requirements

requirement types, 15attributes, 16change notifications, 22discussion, 19history, 20references, 18traceability, 21validation, 17

revision history, 44selecting

project, 30Status, 16system attributes, 16Tag/ID, 16test, 21text references, 18

creating, 40traces, 21URL, 18user accounts, 22user-defined attributes, 16

viewing and editing, 42validation procedures

viewing, 46vendor add-in modules, 21Version, 16version, 20work item, 21

52