Caliber 11.0 for Visual Studio Team Systems

Transcription

1 Caliber 11.0 for Visual Studio Team Systems

2 Getting Started Getting Started Caliber - Visual Studio 2010 Integration... 7 About Caliber... 8 Tour of Caliber

3 Concepts Concepts Projects Baselines Requirement Attributes Requirement Validation Requirement References Requirement Discussions Requirement History Requirement Traceability Requirement Change Notifications Requirement Grid

4 Procedures Procedures Projects Enabling the Integration with Visual Studio 2010 Work Items and Tests Logging Off from Caliber Logging on and Selecting a Caliber Project Removing a Project Browsing Creating a Requirement Deleting a Requirement Displaying Groups of Using the Requirement Grid Participating in Requirement Discussions Refreshing Viewing and Editing Requirement Description Viewing and Editing Requirement References Viewing Requirement Attributes Viewing Requirement Change Notifications Viewing Requirement History Viewing Requirement System Attributes Viewing Requirement Validation Procedures Requirement Traceability Creating a Trace between a Requirement and a Test Creating a Trace between a Requirement and a Work Item Creating a Trace between Modifying Requirement Traces

5 Getting Started 5

6 Getting Started The topics in this section are designed to help you understand and begin using Caliber 11.0 with Visual Studio. In This Section Caliber - Visual Studio 2010 Integration This section provides information about the integration between Caliber and Visual Studio About Caliber This section describes Borland Caliber. Tour of Caliber This section provides information about the Caliber user interface in Visual Studio. 6

7 Caliber - Visual Studio 2010 Integration Caliber 11.0 integrates with Visual Studio 2010 to provide Visual Studio users with the following capabilities and features: 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 directly from within Visual Studio. Allows Visual Studio users to participate in requirement discussions, attach or modify references to requirements and create traceability from requirements to Visual Studio and Team System artifacts including work items and tests. Additionally, Visual Studio users can open the full Caliber Author from within Visual Studio to edit requirements. About Caliber Projects Logging on and Selecting a Caliber Project 7

8 About Caliber Caliber 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 large or small, in local or global offices effectively manage expectations across the lifecycle so that projects are delivered on time, within scope, and according to specification. Designed for ease of use, the intuitive interface of the new client for Microsoft Visual Studio provides developers the real-time access they need to requirements right in their own IDE. Caliber also helps applications meet end-user needs by allowing all project stakeholders marketing teams, analysts, developers, testers, and managers to collaborate and communicate the voice of the customer throughout the lifecycle. Caliber provides the following capabilities and features: Visibility: Dynamic business demands makes visibility a must. Customers are faced with constantly evolving software requirements and less time, money or resources to deliver software. Communication & Collaboration: Business demands drive requirements which drives application development. All members of a project team need to have a common understanding of the requirements. need to be simple, complete, concise, testable and accurate. Software development teams are able to respond rapidly to ever-changing requirements. Control: Traceability and metrics reporting are key to proactively controlling a software project. To ensure they are being fulfilled, requirements should be traced to other artifacts in the lifecycle such as design, tests, change requests and source code files. Traceability allows enterprises to enable automated change notifications and impact analysis. also have many important metrics concerning scope creep and volatility which are key to understanding the status of projects. Caliber - Visual Studio 2010 Integration Projects Logging on and Selecting a Caliber Project 8

9 Tour of Caliber After you have opened a Caliber 11.0 project in Visual Studio, the Caliber Explorer displays the Caliber 11.0 project requirements. Expanding the project displays requirement types, and expanding requirement types displays requirements. Projects You can right-click on the project name to open the Requirement Grid. Requirement Types You can right-click on a requirement type to add a new requirement. You 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 Details Displays the requirement name, version, owner, status, priority and description. Responsibilities Displays a list of users and groups. References Displays reference information for a requirement. You can reference a file of any of the following format: prototype screens, 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. URLs are added through web references. Traceability Allows you to view and modify the relationships between requirements and other related development and testing information. 9

10 Validation Allows you to view validation procedures for the selected requirement. Discussion Displays all discussions for a requirement. Allows you to participate in existing discussions or start new discussions. History Details 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 changes occurred. Attributes Displays 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. Caliber - Visual Studio 2010 Integration Requirement Attributes Logging on and Selecting a Caliber Project Logging Off from Caliber 10

11 Concepts 11

12 Concepts This section provides overview information about requirements and related functionality available in Caliber In This Section Projects This section provides information about Caliber projects. Baselines This section provides information about project baselines. This section provides information about requirements. Requirement Attributes This section provides information about system and user-defined attributes of a requirement. Requirement Validation This section provides information about requirement validation procedures. Requirement References This section provides information about requirement references. Requirement Discussions This section provides information about requirement discussions. Requirement History This section provides information about requirement revision history. Requirement Traceability This section provides information about requirement traceability. Requirement Change Notifications This section provides information about requirement change notifications. Requirement Grid This section provides information about requirement groups and the requirement grid. 12

13 Projects Caliber Projects in Visual Studio A Caliber project contains a collection of requirements that you need to manage as a whole, such as an application or system under development. Caliber projects consist of several types of information, including users and groups, requirement types and requirements. Project Administration Caliber project administration is maintained in the Caliber Administrator component of the standalone Caliber client. Logging Off from Caliber Logging on and Selecting a Caliber Project 13

14 Baselines A 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 current baseline. For other baselines all requirements are read only. Project Baseline Administration Creation of project baselines, and comparison of baseline content is performed in the standalone Caliber client. Projects 14

15 are specifications that the application or system you are building must meet. can originate 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/ID field on the Details tab in the document window. The serial number does not change, regardless of the requirement position, 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.). Requirement Attributes Requirement Traceability 15

16 Requirement Attributes Attributes are characteristics that help define a requirement. Both system and user-defined attributes are supported in Caliber You can view and assign values to all requirement attributes. Requirement attributes are shown on the Details and User Attributes tabs of a requirement document window. System Attributes (Details) System attributes are those that Caliber automatically maintains for each requirement. The system attributes that are 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 the requirement is static and automatically generated; each ID number is unique in the system; if a requirement is deleted, that ID number will not be reused Version (see also requirement history) the revision number of the requirement; when a change is made to the requirement, the version number is automatically updated; the change may cause a major or minor revision number change; a Caliber administrator determines this when attributes types are defined in the standalone Caliber client Status the requirement status Priority the requirement priority Owner the default Owner is the user who created the requirement; requirement ownership varies through the project life-cycle; typically, the beginning Owner is an analyst, after implementation, the Owner is a developer, and once the requirement is in testing, the Owner is a QA engineer Description the requirement description User-Defined Attributes User-defined attributes help further define requirements and are optional. They can be one of several different types of data, including text, long integer, date, boolean and users. A system administrator can set up the list of userdefined 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 defined in the standalone Caliber client by the Caliber administrator), but you cannot create new attributes or remove the existing attributes from your project. Requirement History Viewing Requirement System Attributes Viewing Requirement Attributes 16

17 Requirement Validation In the Caliber client, you can write a validation procedure for each requirement, which you can then view in the Caliber 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. The validation 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. Viewing Requirement Validation Procedures 17

18 Requirement References You 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 else that 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 the References tab of a requirement document window. There are two differences between references and requirement traceability. You use references to link requirements with external objects that help define a requirement. References are single-direction links, so you can traverse them only from a source requirement. There are three types of references: File reference Text reference Reference on the Web File References You use this type to reference an existing file on the network. Reference files are best placed on a shared drive for all 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 a referenced file. Warning: If the referenced file is no longer available or renamed, the reference becomes invalid. Text References You use this type to add a piece of text to a requirement. This text is stored in the Caliber project. Web References You use this type to link an external Internet resource. You need to specify a URL of a resource to reference. This URL is stored in the Caliber project. Warning: If the referenced link is no longer available or renamed, the reference becomes invalid. Requirement Traceability Viewing and Editing Requirement References 18

19 Requirement Discussions Project teams can provide feedback on requirements through discussions. This collaborative feature enables team members 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 the Discussion tab of a requirement document window. Caliber discussions are independent from Visual Studio discussions and are stored in the Caliber project. You can receive notification that a new message has been posted for a requirement. The Caliber administrator must first enable notifications in the Caliber Administrator, then you must be assigned as a responsible user to receive change notifications. See the related information link below. Participating in Requirement Discussions Viewing Requirement Change Notifications 19

20 Requirement History Caliber 11.0 maintains a history record for each requirement. The history record assigns revision numbers and keeps a list of changes for each revision. All changes made to a requirement, including changes to specific attributes (the requirement description, status, priority, and so on) are recorded in the requirement history. The current requirement version is displayed on the requirement Details tab. Viewing Requirement History 20

21 Requirement Traceability The traceability feature allows you to create and track relationships between requirements and other related development and testing information in your Visual Studio project. Such relationships are called "traces" and shown on 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 require changes in other elements of the project. Tracing related objects helps to ensure that changes are implemented correctly 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. For example, if there are direct traces between a software requirement and an interface requirement, and between the interface requirement and a coding requirement, there is also an implied trace between the software requirement and the coding requirement. When you change a requirement, traces to other objects become suspect. Suspect traces are an indicator that other objects can be affected by the changed requirement and you should review them. Requirement References Requirement Traceability 21

22 Requirement Change Notifications Caliber 11.0 can notify one or more users by about requirement changes. Notified users are shown on the Responsibilities 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 changes made to the requirement. The Caliber administrator manages user accounts and groups and enables notifications in the Caliber Administrator component of the standalone Caliber client. For information on enabling notifications, please see the Caliber User Guide. Viewing Requirement Change Notifications 22

23 Requirement Grid You can view requirements in a spreadsheet format to sort requirements and export requirements to XML. The grid view 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. Displaying Groups of Using the Requirement Grid 23

24 24

25 Procedures 25

26 Procedures This section provides "how to" information. In This Section Projects This section provides information about tasks related to projects. This section provides information about tasks related to requirements. Requirement Traceability This section provides information about tasks related to requirement traceability. 26

27 Projects Caliber project administration is performed in the Caliber Administrator component of the standalone Caliber client. In This Section Enabling the Integration with Visual Studio 2010 Work Items and Tests This section describes how to enable the integration with Visual Studio 2010 work items and tests. Logging Off from Caliber This section describes how to log and off Caliber. Logging on and Selecting a Caliber Project This section describes how to log on to Caliber and select a Caliber project from within Visual Studio. Removing a Project This section describes how to remove a Caliber project from the Borland Caliber Explorer in Visual Studio. 27

28 Enabling the Integration with Visual Studio 2010 Work Items and Tests To enable the integration with Visual Studio 2010 work items and tests 1 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. Projects 28

29 Logging Off from Caliber To release the Caliber license you consume when logged on, you can log off Caliber from within Visual Studio. To log off from Caliber 1 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. Logging on and Selecting a Caliber Project 29

30 Logging on and Selecting a Caliber Project To log on and select a project 1 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 in your standalone Caliber client. This initializes the Caliber project and makes it available for selection 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 with requirements in Visual Studio, consider logging off to free a license for other Caliber 11.0 users. The connection gets automatically broken by default. Projects Baselines 30

31 Removing a Project To remove a Caliber project from a Visual Studio project 1 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. Projects 31

32 This section describes the tasks involved in working with requirements. In This Section Browsing Describes how to browse requirements in a Caliber project opened from within Visual Studio. Creating a Requirement Describes how to create a requirement. Deleting a Requirement Describes how to delete a requirement. Displaying Groups of Using the Requirement Grid Describes how to view a group of requirements using the requirement grid. Participating in Requirement Discussions Describes how to view and participate in a requirement discussion. Refreshing Describes how to refresh requirements in a Caliber project opened in Visual Studio. Viewing and Editing Requirement Description Describes how to view and edit description of a requirement. Viewing and Editing Requirement References Describes how to view and edit the list of references of a requirement. Viewing Requirement Attributes Describes how to work with requirement attributes. Viewing Requirement Change Notifications Describes how to view requirement change notification settings. Viewing Requirement History Describes how to view revision history of a requirement. Viewing Requirement System Attributes Describes how to view system attributes (details) of a requirement. Viewing Requirement Validation Procedures Describes how to view requirement validation procedures. 32

33 Browsing To browse requirements in a Caliber project 1 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. 33

34 Creating a Requirement The Caliber integration with Visual Studio provides you with the basic ability to create requirements from within Visual Studio. However, you will find that creating requirements is easier in the Caliber standalone Windows client that allows for relocation of requirements in the requirement tree, as well as inclusions of images, tables and hyperlinks in the requirement text. To create a requirement 1 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 document window. Note: Alternately, to create a requirement as a child requirement of another, right-click a requirement in the requirement tree and select Add Requirement. Requirement Attributes Deleting a Requirement 34

35 Deleting a Requirement You can only delete a requirement if you have delete permissions as defined by the Caliber administrator in the Caliber Administrator component of the standalone Caliber client. To delete a Caliber requirement 1 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. Creating a Requirement 35

36 Displaying Groups of Using the Requirement Grid The 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 Grid 1 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 the toolbar 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 and choose View Go to requirement from the toolbar menu. To print the Requirement Grid 1 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 XML 1 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. Requirement Grid 36

37 Participating in Requirement Discussions To participate in a requirement discussion 1 Select a Caliber project in Visual Studio. See 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 message appears in the message text area at the bottom of the tab. To post a message 1 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 message 1 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 notification that a new message has been posted for a requirement. The Caliber administrator must first enable notifications in the standalone Caliber client, then you must be assigned as a responsible user to receive change notifications. See the related information link below. Requirement Change Notifications Viewing Requirement System Attributes Logging on and Selecting a Caliber Project 37

38 Refreshing To refresh requirements in a Caliber project 1 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 Visual Studio. Projects Logging Off from Caliber 38

39 Viewing and Editing Requirement Description To view the description of a requirement 1 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 requirement 1 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 as Visual 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 in Visual Studio. Requirement Attributes Viewing Requirement System Attributes Viewing Requirement Attributes 39

40 Viewing and Editing Requirement References To view references of a requirement 1 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 reference 1 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 reference 1 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 Web 1 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: Click OK. To edit a text or Web reference 1 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

41 To remove a requirement reference 1 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 or Web references, the text or URL you entered is lost. Requirement References 41

42 Viewing Requirement Attributes You can view user-defined attributes available in your project by using the Caliber Administrator or standalone Caliber client. For more information, please consult the Caliber User Guide. To view and edit user-defined attributes of a requirement 1 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. Requirement Attributes Viewing Requirement System Attributes 42

43 Viewing Requirement Change Notifications This 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 Group Assignment tab in Caliber Administrator. See the Caliber User Guide for more information. To view user notification settings of a requirement 1 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. This check box indicates whether this user or a group is selected, not selected, or partially selected for notification about changes of the current requirement. Requirement Change Notifications 43

44 Viewing Requirement History To view history of a requirement 1 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 (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 initial revision is displayed at the top. The list of attributes changed at the selected revision is displayed at the lower part of the window. To view all details of a change 1 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 user who made this change, and the user comments about the change. Requirement Attributes Requirement History 44

45 Viewing Requirement System Attributes To view system attributes of a requirement 1 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 of the requirement in the lower part. You can select a version of the requirement in the Requirement Version drop-down list for viewing. To edit a requirement, click the Edit in Caliber button to open the Caliber client from which you can edit the requirement. Requirement Attributes Viewing and Editing Requirement Description Viewing Requirement Attributes 45

46 Viewing Requirement Validation Procedures To view a validation procedure for a requirement 1 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. Requirement Validation 46

47 Requirement Traceability You can create traceability relationships between requirements, requirements and Visual Studio tests, and requirements and Visual Studio work items. In This Section Creating a Trace between a Requirement and a Test Describes how to create between a requirement and a test. Creating a Trace between a Requirement and a Work Item Describes how to create a trace between a requirement and work item. Creating a Trace between Describes how to create a trace between requirements. Modifying Requirement Traces Describes how to modify requirement traces. 47

48 Creating a Trace between a Requirement and a Test To create a trace between a test and a requirement 1 Select a Caliber project in Visual Studio. See 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.0 integration in the Caliber Administrator. Refer to the Enabling the Integration with Visual Studio 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 trace indicator appears in the test list. 8 Click the Save all changes button. Your trace between a test and a requirement is now created. Requirement Traceability Logging on and Selecting a Caliber Project Enabling the Integration with Visual Studio 2010 Work Items and Tests 48

49 Creating a Trace between a Requirement and a Work Item To create a trace between requirement and a work item 1 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.0 integration in the Caliber Administrator. Refer to the Enabling the Integration with Visual Studio 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. The trace 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. Requirement Traceability Logging on and Selecting a Caliber Project Modifying Requirement Traces Enabling the Integration with Visual Studio 2010 Work Items and Tests 49

50 Creating a Trace between To create a trace between requirements 1 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. Requirement Traceability Logging on and Selecting a Caliber Project Modifying Requirement Traces 50

51 Modifying Requirement Traces To modify a requirement trace with a work item or test 1 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. Requirement Traceability Requirement Traceability Logging on and Selecting a Caliber Project 51

52 Index about CaliberRM CaliberRM, 8 Borland CaliberRM, 7 browsing requirements, 33 Caliber Administrator, 13 CaliberRM interface user interface, 9 creating trace between test and requirement, 48 trace between work item and requirement, Description, 16 description editing, 39 detail history, 44 Details, 39 displaying requirement grid, 36 file references, 18 creating, 40 groups, 22 history viewing, 44 HTML format, 39 logon, log off, 29 modifying requirement traces, 51 Name, 16 notification viewing, 43 Owner, 16 participating requirement discussions, 37 Priority, 16 project baseline, 14 projects project administration, 13 references viewing, 40 editing, 40 removing, 41 references on the Web, 18 creating, 40 refreshing requirements, 38 removing project, requirement change notifications viewing and editing, 43 requirement description viewing and editing, 39 requirement details viewing and editing, 45 requirement grid requirement groups, 23 Requirement Grid, 36 requirement references viewing and editing, 40 Requirement Type, 34 requirement type, 48 requirement validation viewing and editing, 46 requirements requirement types, 15 attributes, 16 change notifications, 22 discussion, 19 history, 20 references, 18 traceability, 21 validation, 17 revision history, 44 selecting project, 30 Status, 16 system attributes, 16 Tag/ID, 16 test, 21 text references, 18 creating, 40 traces, 21 URL, 18 user accounts, 22 user-defined attributes, 16 viewing and editing, 42 validation procedures viewing, 46 vendor add-in modules, 21 Version, 16 version, 20 work item, 21 52