Define and Manage Requirements with IBM Rational Requirements Composer. Lab Exercises for Workshop 2266

Transcription

1 Define and Manage Requirements with IBM Rational Requirements Composer Lab Exercises for Workshop 2266

2 An IBM Proof of Technology Catalog Number Copyright IBM Corporation, 2012 US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents OVERVIEW...5 LAB 1 LAB 2 LAB 3 LAB 4 LAB 5 LAB 6 Contents TOUR OF IBM RATIONAL REQUIREMENTS COMPOSER & JKE BANKING SAMPLE START THE REQUIREMENTS MANAGEMENT APPLICATION EXAMINE THE PROJECT DASHBOARD OPEN THE REQUIREMENT ARTIFACT EDITOR ARTIFACT CHANGE HISTORY EXAMINE THE PROJECT PAGE LOGOUT SUMMARY RESPOND TO CHANGE REQUEST START THE REQUIREMENTS MANAGEMENT APPLICATION CREATE NEW REQUIREMENTS EDIT THE NEWLY CREATED REQUIREMENTS AND DEFINE SOME ATTRIBUTES NOW LET S ADD SOME TAGS CREATE NEW REQUIREMENTS VIA IMPORT DEFINE RELATIONSHIPS OPTIONAL MODEL WORD IMPORT SUMMARY UPDATING THE BUSINESS PROCESS NAVIGATE TO THE BUSINESS PROCESS DIAGRAM EXAMINE THE CAPABILITIES AVAILABLE IN THE BUSINESS PROCESS DIAGRAM EXAMINE WHAT WORK HAS ALREADY BEEN DONE ENHANCE THE EXISTING PROCESS COLLABORATING REGARDING CHANGES TAG YOUR DIAGRAM SUMMARY REFINE THE USE CASE DIAGRAM START THE REQUIREMENTS MANAGEMENT APPLICATION STUDY AND NAVIGATE THE USE CASE DIAGRAM UPDATE THE USE CASE DIAGRAM MODIFY A USE CASE ELABORATION NOTIFY TEAM OF CHANGES BROWSE A MODULE USED FOR A USE CASE SPECIFICATION CREATING A MODULE SUMMARY CHANGE THE USER INTERFACE START THE REQUIREMENTS MANAGEMENT APPLICATION OPEN THE STORYBOARD EDIT THE STORYBOARD EDIT THE PART CONTINUE EDITING THE STORYBOARD APPLY A TAG SUMMARY CONDUCT A REVIEW Page 3

4 6.1 LAB 7 LAB 8 CREATE A REVIEW PARTICIPATE IN REVIEW FINALIZE REVIEW (OPTIONAL) SUMMARY LEVERAGING THE REQUIREMENTS ACROSS THE LIFECYCLE FILTER USING A TAG TO VIEW REQUIREMENT ARTIFACTS CHANGE STATUS OF THE REQUIREMENTS ADD APPROVED REQUIREMENTS TO A COLLECTION CREATE LIFECYCLE LINKS OPEN THE QUALITY MANAGEMENT APPLICATION START THE REQUIREMENTS MANAGEMENT APPLICATION (OPTIONAL) UPDATE THE PRODUCT BACKLOG VIEWING THE LIFECYCLE RELATIONSHIPS SUMMARY STATUS OF PROJECT START THE REQUIREMENTS MANAGEMENT APPLICATION REVIEW JKE BANKING (REQUIREMENTS) PROJECT'S DASHBOARD CUSTOMIZE THE PROJECT DASHBOARD WORK WITH VIEWS GENERATE A REPORT FROM A VIEW SUMMARY APPENDIX A TROUBLESHOOTING APPENDIX B NOTICES APPENDIX C TRADEMARKS AND COPYRIGHTS Page 4 Define and Manage Requirements with IBM Rational Requirements Composer

5 Overview This workshop dives into the Analyst role of the Rational Collaborative Lifecycle Management (CLM) solution powered by Jazz. We join a project that has finished Iteration 1 (Sprint) and is about to begin Iteration 2 (Sprint) and we will understand how IBM Rational Requirements Composer extends the next iteration user stories with additional graphical artifacts and storyboards, business process diagrams, use cases, vision documents, review and approval, commenting and management for impact and coverage analysis. The workshop also examines the use of the User Stories and additional detail through the development lifecycle of an application Introduction General This Hands-On Workshop leverages the jazz.net Money that Matters Lifecycle Scenario ( The Money that Matters Program In the wake of a recent financial crisis, a large financial institution (JKE) has decided it needs to reinvigorate its brand value in order to survive. It has developed a new company initiative and tag line Money that Matters - to reflect the core values of its customer base, not only to make money but to invest in programs that matter to the communities it serves. By combining traditional financial services with creative community investment opportunities, the Money that Matters program will reinvigorate its image and improve customer loyalty in a turbulent market. The Money that Matters initiative will market a host of potential offerings that extend JKE s core business with community investment initiatives. Key initiatives include: Business Recovery Matters. This program seeks to accelerate the economic recovery of disaster-stricken areas by linking investors/donors with impacted business owners. Business Recovery Matters provides both low-touch and focused investment options. The low-touch, Dividend Deposit option automatically deposits a portion of a customer s dividends into a pooled assistance fund. The high-touch, MicroLoan option establishes a direct link between an investor and an affected business owner and provides the infrastructure needed to set up Microloans and track business performance. Collaborative Team Roles and Scenario Bob is the primary analyst working on some changes to the project, and he will be doing most of the additions and modifications to the requirements. Bob wants to monitor the artifacts he is working on and changing, so he creates a shared tag named "bob" for easy access to the artifacts. Overview Page 5

6 In an effort to collaborate with his team, Bob will ask Al, a software architect, to look at some of his work. Al makes some necessary changes to the Use Case. Bob will then request that Curtis review and approve the work. Curtis is the customer on this project. All artifacts with the tag bob are then used to create a collection of artifacts. Bob will tie the impacted items to the development and test teams' activities. Finally, Ursula will review the project activities from her dashboard. Ursula is the project Executive. Icons The following symbols appear in this document at places where additional guidance is available. Icon Page 6 Purpose Explanation Important! This symbol calls attention to a particular step or command. For example, it might alert you to type a command carefully because it is case sensitive. Information This symbol indicates information that might not be necessary to complete a step, but is helpful or good to know. Troubleshooting This symbol indicates that you can fix a specific problem by completing the associated troubleshooting information. Define and Manage Requirements with IBM Rational Requirements Composer

7 Lab 1 Tour of IBM Rational Requirements Composer & JKE Banking sample This is an instructor-led module and provides an overview of both IBM Rational Requirements Composer (RRC) and the JKE Banking sample, documented on jazz.net at MTM Lifecycle Scenario 2012 Important! Students may optionally follow along with the instructor, but you might not see exactly the same thing on your computer. At the end of this module you will have an understanding of the following: 1. Awareness of what s going on via the web client 2. Quick access to artifacts hover options to provide more detail 3. Collaboration with teams commenting, dashboards, reviews by examining: The Analysts Dashboard and the viewlet's used in the General and Development tabs. The Recent Changes viewlet, which shows which artifacts have recently changed The change history of an artifact. How to published an artifact to a document, including any comments and attributes. The traceability tree, which shows the requirements and their various life cycle relationships. Lab 1 Page 7

8 Page 8 Define and Manage Requirements with IBM Rational Requirements Composer

9 1.1 Start the Requirements Management application Team Role You are now playing the role of Bob, an Analyst (Product Owner), in the JKE Banking (Requirements) project. Bob has Author role privileges 1. Open your Firefox web browser and go to Alternatively click RM in the browser bookmarks toolbar. Lab 1 Page 9

10 Troubleshooting If you see certificate error click Add Exception and Confirm Security Exception Page 10 Define and Manage Requirements with IBM Rational Requirements Composer

11 2. Log into IBM Rational Requirements Composer. Type bob for both the User ID and Password and then click Log In. Troubleshooting User ID and Password are case sensitive. Ensure you use lower case bob All labs use lower case user id and password. Lab 1 Page 11

12 3. From the All Projects page, click Explore Dashboard, for the JKE Banking (Requirements) project 1.2 Examine the Project Dashboard Page 12 Define and Manage Requirements with IBM Rational Requirements Composer

13 Dashboards Provide a better whole-team collaboration on requirements, with improved on-boarding (time-toproductivity) of new team members, with better team and project transparency Dashboards provide information about the project status at a glance. It provides the option to drill down to get more complete information. It also represents the integration point for the data provided by all Jazz components. There are project and user dashboards. User dashboards can be tailored, by the user, to contain only those viewlets of interest. Web Client Allows the involvement of customers and stakeholders in the requirements process 1. Lab 1 From the project dashboard select each of the tabs, General and Development Page 13

14 2. Examining various viewlets, especially a. Done Stories (Development Tab) i. Page 14 Rich hover, Allocate Dividends by Percentage Define and Manage Requirements with IBM Rational Requirements Composer

15 Rich Hover Supports the end-to-end requirements information lifecycle by providing visibility of the development work across departmental and organizational boundaries. Lab 1 Page 15

16 b. Requirements Tracing, (General Tab) Requirements Tracing Shows requirements in a single requirements project that are implemented by work items in change and configuration management projects or validated by test cases in quality management projects. The work items and test cases are displayed as child items of the requirement to which they correspond. You can limit the results to a single collection or status. This shows alignment of development and test activities with requirements, and allows reporting across project team domains (e.g. requirements satisfied in current project deliverables as proven in test case completion) Page 16 Define and Manage Requirements with IBM Rational Requirements Composer

17 c. Reviews, Reviews Lists recently created or modified reviews in all your projects. You can limit this viewlet to just your active reviews, all active reviews. Also you can filter or group the results by Status, Role, or Review Name. d. Recent Changes, Recent Changes Lists recently modified artifacts in this project. Clicking any of the listed artifacts will open the artifact. The default limit for recent changes is 14 days but this can be configured in the server. e. Lab 1 My Requirements Project, Page 17

18 My Requirements Project Lists all requirements projects for which you are a team member. From this viewlet it is possible to navigate to either the project Dashboard or All Artifacts view. f. finishing with the Comments viewlet Comments Lists recent comments that are related to your projects. Provides information visibility for the whole team. You can filter the comments for those that are addressed to you or those that were made by you. The default limit for recent comments is 14 days but this can be configured in the server. Page 18 Define and Manage Requirements with IBM Rational Requirements Composer

19 Artifact Comments A comment is a textual discussion item that is associated with an artifact or an element within an artifact. You can use comments to provide team feedback during the development of an artifact. Comments are displayed in the Comments section of an artifact sidebar, in the Recent Comments section of the Project Artifacts page sidebar, and in the Comments viewlet on the User Dashboard. You can comment on an artifact as a whole (by using artifact-level comments) and on specific elements within the artifact. In rich-text artifacts, you can comment on the whole document (by using document-level comments), a paragraph or an item in a bulleted list within the document. Comments are visible to all team members who have access to the artifact. When creating a comment, you can direct it to one or more users, in which case it will be displayed in their dashboards. If your server has notifications set up, you will get when comments are directed to you. 1.3 Open the requirement artifact editor 1. From the Artifacts menu, click the Browse Artifacts option. Lab 1 Page 19

20 2. This opens the Artifacts page. From the Views section, Click Elaborated User Stories (Lifecycle Coverage). Filters! Filters are located in the left hand side of the screen and they determine which artifacts are shown in this view. When creating a new view, ensure that any unnecessary filters are cleared! Project Page The Project artifacts page is used to view, open and modify artifacts. You can create saved filtered views by selecting various attribute values, tags, folders, status of life cycle links, artifact types, etc. A saved view is a way to configure both (1) the look of the project page (which information is displayed in the columns of the UI, the column order, column widths); and (2) the filters that select the rows (which artifacts show up in the rows). Saved Filters can be public (shared with the team) or private (visible only to you). Page 20 Define and Manage Requirements with IBM Rational Requirements Composer

21 3. This displays all the User Story Elaboration artifact types in the project, together with CLM lifecycle links Tracked By, Implemented By and Validated By. 4. From the displayed artifacts, select the user story elaboration Donor Chooses Multiple Organizations Tip To open the requirement artifact in a new tab or window, right-click the link, and choose new tab or window from the menu. Lab 1 Page 21

22 5. This opens the artifact in a rich text view. Requirement A requirement describes a condition or capability to which a system must conform; it is either derived directly from user needs or stated in a contract, standard, specification, or other formally imposed document. A requirement is expressed as an artifact of one ore more requirement types. Other artifact types are used to define related requirements information; however, the requirement is definitively expressed as an instance of a requirement type. A requirement can contain links to related artifacts that enhance its definition. Requirements are created using a rich-text editor that has extensive formatting capabilities and a browser spell checker. Misspelled words are marked with a red wavy underline. Ctrl-right-click a misspelled word to select from suggested spellings or to add it to the browser dictionary. Page 22 Define and Manage Requirements with IBM Rational Requirements Composer

23 6. Examine the artifact editor's various sections Information When you create a new artifact or click on an existing artifact in the Project artifact page, the artifact is displayed in the artifact editor. You add new content or modify existing content by clicking on the Edit button. The editing tools that are displayed in the content creation part of the editor is determined by the artifact type; however, there are common tasks that you can perform on all artifacts. a. Lab 1 main content creation part of the editor, Page 23

24 b. breadcrumb, c. tags, d. controls, with appropriate privileges, you can perform the following tasks on all artifacts: Create and Print Save the contents of the artifact to either Microsoft Word format or to Adobe PDF file format. Create Review Add the artifact to a review. Add to Collection Add the artifact to a collection. Create Artifact Template Create an artifact template using the artifact as a model for the template. (Needs project Administrator role privilege) Page 24 Open History View the revision history of the artifact. Move to Folder Move the artifact to another folder. Copy Artifact Copy the artifact and save it in a designated folder. Delete Delete the artifact. Refresh Refresh the current view of the artifact. Select tags Create a new or apply an existing shared or personal tag to the artifact. Tags are used to filter artifacts on the artifact page. Define and Manage Requirements with IBM Rational Requirements Composer

25 i. For off-site meetings, it is often necessary to export an artifact to a PDF or a Microsoft Word document. To do this, click the Create/Print button, click the button Create and Print PDF Document ii. From the dialogue, select Include Attributes and Show Embedded Titles, and press OK Document Creation The time to create a document can vary between a few 10's seconds to a few minutes depending the performance of the host machine. Lab 1 Page 25

26 Page 26 iii. Once the publishing is complete, the following pop-up will be displayed, click OK. iv. The following PDF is displayed Define and Manage Requirements with IBM Rational Requirements Composer

27 7. Now, click the Edit button, to modify the artifact. 8. Examine the various rich-text editing capabilities Paragraph Format Fonts (Colour, Size, Style) Bold, Italic, Underline, Strikethrough Alignment (Left, Center, Right, Justified) Indent (Increase, Decrease) Lists (Numbered, Bullet) Insert (Table, Image, Artifact) Save Selection As ( New Artifact and Link. New Artifact and Insert ) Lookup Term Lab 1 Page 27

28 Links (Create/Delete); including trace links which appear in the sidebar. Information During editing, rich hover and highlighting comments is not available. 9. Page 28 Examine the sidebar attributes, which can be changed in Edit mode. Define and Manage Requirements with IBM Rational Requirements Composer

29 Information You can assign attribute values to requirements and other artifacts to manage properties such as status, priority, and owner. You can create (saved) filtered views of artifacts, by selecting attribute values, together with tags, folders, status of life cycle links, artifact types, etc. Administrator role privileges are needed to create, delete or modify the attributes defined for an artifact. 10. Lets now close the Editor, by pressing CANCEL 11. And examine the other sidebar sections, Comments, Links and Where Used Lab 1 Page 29

30 a. Page 30 Sidebar Comments section i. This section indicates any comments relating to this artifact, and allows comments to be created for either the entire artifact or selected content. ii. It is also possible to Sort, Group, Filter or Highlight comments Define and Manage Requirements with IBM Rational Requirements Composer

31 b. Sidebar Links section i. Examine the content of the various artifact links with rich hover by holding the cursor over a link. Rich Hover The information shown changes based upon the link. For example References Term links show the term definition, where as the Validated By link shows the test case summary ii. Lab 1 Also it is possible to see these links graphically, by selecting the Links Explorer button. Page 31

32 iii. From the pop-up, select for the default Walker style, the following appearance Landscape, Curvy Wires, and Compact View. Page 32 Define and Manage Requirements with IBM Rational Requirements Composer

33 iv. And press the + to expand some of the requirements to provide a similar view as below: v. When ready, press X to close the pop-up. vi. It is also possible to Add, Sort, Filter and Highlight links Lab 1 Page 33

34 c. Sidebar Where Used section i. This section indicates any Collections or Reviews where this artifact is used, and the links can be sorted by selecting Group by Relationship, Group by Project or Filter Links Information A review is a set of artifacts that you create to be reviewed by specific team members. The status of the reviews changes as participants complete the review. You can create a review for individual artifacts that you select or you can create a review of a collection. You can send notifications to participants when a review is started and whenever certain events occur in the review. Page 34 Define and Manage Requirements with IBM Rational Requirements Composer

35 1.4 Artifact change history 1. Click the Open History button to see all changes for this artifact in detail. Information You can use the artifact history viewer to view the history of most artifacts. A revision is created each time you save an artifact. Read-only revisions are organized by time period (today, yesterday, past week, past month, earlier). You can restore a previous revision to the latest revision. 2. Lab 1 A history view of the artifact opens, with each revision represented by a revision icon. Page 35

36 3. Examine the modifications for the artifact by holding the cursor over the icon to see a change summary. Select Show More to expand the modifications rich hover. The most recent version is on the left and the oldest on the right. Information On a particular revision date, you can view the complete content change, as well as values of attributes, links and comments. Page 36 Define and Manage Requirements with IBM Rational Requirements Composer

37 4. Click Open Current Version button to return to the latest version of the artifact. 1.5 Examine the project page 1. From the artifact editor, choose the JKE Banking (Requirements) breadcrumb. Lab 1 Page 37

38 2. And return to the previously selected view (or return to this tab or window if the user story was opened in a separate tab or window) 3. Close the sidebar Page 38 Define and Manage Requirements with IBM Rational Requirements Composer

39 4. And select Satisfy High Priority Goals (Tree View) a. Lab 1 This shows a trace tree, where a Business Goal is Satisfied by a Feature which is Satisfied by a User Story Elaboration which is in turn Illustrated by Graphical Artifacts and Storyboards. Page 39

40 Information A storyboard is frame-by-frame depiction of a user scenario that consists of sequentially numbered frames on a timeline. You can create the frames in your storyboard using existing artifacts, such as sketches, parts and images, or by using drawing elements from the editor toolbar. b. Page 40 The view will show the selected link types, configured as follows: Define and Manage Requirements with IBM Rational Requirements Composer

41 Lab 1 c. Which is configured with this advanced rule: d. Press Cancel to close the dialogue. Page 41

42 1.6 Logout 1. This concludes the demo, from the user menu, click Log Out 2. And if necessary close the browser Page 42 Define and Manage Requirements with IBM Rational Requirements Composer

43 1.7 Summary We have demonstrated that IBM Rational Requirements Composer provides: 1. Awareness of what s going on via the web client 2. Quick access to artifacts hover options to provide more detail 3. Collaboration with teams dashboards, commenting reviews Business Value Lab 1 Dashboards and Widgets- Provide an individual and/or team quick overviews of what is happening in a project or multiple projects. Widgets provide a detailed piece of the puzzle. Hover Gesture to provide just enough pertinent detail for the artifact in question Team Collaboration- Conduct both informal communication techniques using comments as well as formalized validation and concurrence through reviews. Both techniques are critical in driving a team-based approach. Collections Group artifacts in a meaningful way for your organization to help identify which requirements are related to a release and/or a functional component area. Artifact Change History and Recent Changes Understand who has changed an artifact over time and what those changes are from the artifact change history. Quickly pinpoint specific changes between versions and, if there is a necessity, roll back changes. Traceability Tree - Obtain a preview of lifecycle traceability in a transparent manner. Quickly ascertain development and test coverage as well as gaps. Page 43

44 Lab 2 Respond to Change Request In this module, we will respond to a request to add new functionality to meet customers needs. Requirements Composer is flexible and provides many options to create new requirements. This task can be accomplished by choosing the option to create a new requirement. There are also quick create ways that allow an analyst to create simple content from the in-line view editing mode, and you can import existing artifacts (e.g. CSV files and Word documents). You will only see a few options highlighted in this module. Lab Scenario As described in the Instructor Demo, JKE project is amidst a sprint and there are requests to add new functionality to meet stakeholders' needs. The new functionality provides the ability for a donor to choose more than one organization to allocate dividends. We will also take this opportunity to add some additional high priority, late breaking requirements. These requirements will be tagged with Extended Functionality along with some other tags. Team Role You are now playing the role of Bob, an Analyst (Product Owner), in the JKE Banking (Requirements) project. Bob has Author role privileges. Page 44 Define and Manage Requirements with IBM Rational Requirements Composer

45 2.1 Start the Requirements Management application 1. Open your web browser and go to 2. Log into IBM Rational Requirements Composer. Type bob for both the User ID and Password and then click Log In. Troubleshooting User name and password are case sensitive. Ensure you use lowercase bob Lab 2 Page 45

46 3. You will then see All Projects. Open the JKE Banking (Requirements Management) project. Since he has only one project you can click on Explore Dashboard. 4. You will then see the JKE Banking (Requirements) Dashboard: Page 46 Define and Manage Requirements with IBM Rational Requirements Composer

47 5. Open the JKE Banking (Requirements) project from My Requirements Projects widget by selecting Show artifacts 2.2 Create new requirements You will create some new requirements from the Project Home Page leveraging the quick create function with in-line editing. The requirements you want to create are Features. 1. Lab 2 Under Filter by Folder, expand the JKE Business Recovery Matters folder and then select the Features folder. Page 47

48 2. Enable Quick Create by expanding the arrow on the Create button (blue button at the top). Select Use One-click Create below More 3. Once again, expand the Create button (blue button at the top) and change the artifact type creation to Feature, by clicking Feature. A dialog box will display and indicate Creating Artifact(s)... Page 48 Define and Manage Requirements with IBM Rational Requirements Composer

49 4. The name of the Feature will list New Feature. Edit the name of the Feature to reflect: Support Windows 7 operating system 5. To save the newly created artifact, click outside the Name box 6. Click Create Feature again and name the Feature: Support Windows 2008 Server and save. Lab 2 Page 49

50 2.3 Edit the newly created requirements and define some attributes. 1. Select the option check box next to both new requirements 2. Click the pencil icon and choose the option Edit the attributes for 2 Artifacts Page 50 Define and Manage Requirements with IBM Rational Requirements Composer

51 3. Lab 2 Select the option check box next to Business Priority and choose the option Must and click Save to complete the attribute changes Page 51

52 2.4 Now let s add some tags 1. Ensure the 2 created Features are still selected, click the pencil icon and choose the option Apply Tags to 2 Artifacts Tags provide the ability to group artifacts in a manner pertinent to a requirement's management team. Tags may be used to represent release concepts or functional components. Business Value: Tags provide the ability to quickly filter on a set of artifacts across artifact types. They can be used as input to help create saved filters. Page 52 Define and Manage Requirements with IBM Rational Requirements Composer

53 2. Choose the two existing tags: Release 1 and Extended Functionality 3. Add a new tag by clicking New Tag. Name the new tag bob, make it a Shared tag, and click OK twice. Lab 2 Page 53

54 4. The three shared tags will be added to the artifacts Shared tags allow team members to group and filter artifacts. They are viewable to all members of the project. Personal tags allow an individual to group and filter artifacts. They are only viewable to the author. 2.5 Create new requirements via import You are importing some new features via a CSV file. You will identify new mobile devices that will be supported. These have been previously captured in an Excel spreadsheet, as shown below: Page 54 Define and Manage Requirements with IBM Rational Requirements Composer

55 CSV files Note that each CSV file must have a header row, and the value in each header cell must match the name of an attribute. Each row corresponds to a new artifact that will be created. To ensure that you get the correct labels, it is recommended that you first create a Requirements Composer view that contains the same artifact types and attributes you plan on importing, export that view, and then use the exported file as a basis for your CSV file for importing. There are 4 required fields: Type, description, primary text and title. 1. Lab 2 Expand the Create button (blue button) and Click Import. Page 55

56 2. An Import Requirements dialog will display. a. Page 56 Select option Import requirements from a CSV file. Then, select Next. Define and Manage Requirements with IBM Rational Requirements Composer

57 Lab 2 b. Click Browse c. Navigate to C:\Workshops\RRC_HOW and select the file new_mobile_devices.csv and click Open. d. Select option Import requirements into a folder then click Pick folder Page 57

58 e. Page 58 Expand the folders JKE Banking (Requirements Management)>JKE Business Recovery Matters Project, select the Features folder and click OK. Define and Manage Requirements with IBM Rational Requirements Composer

59 f. Click Finish. 3. The requirements will be uploaded and created under the Features folder, a refresh may be needed before the new artifacts are displayed 4. Three new features will be created: Mobile Device Support Android Lab 2 Page 59

60 Mobile Device Support Blackberry Mobile Device Support Iphone Click refresh icon, and then click the ID column header (twice) to sort it from most recent to earliest, to ensure that the created features appear on the first page. Troubleshooting If the imported artifacts are not listed on the first page, they may be located on page 2 or a refresh is needed. Page 60 Define and Manage Requirements with IBM Rational Requirements Composer

61 5. To ensure that the value Should (for the Business Priority attribute) was correctly imported for each requirement, select the option check box next to only the three (imported) Mobile Device Support artifacts and choose the pencil menu option Edit the attributes for 3 Artifacts. 6. Click Cancel because the attribute value for the Business Priority is (already) set to Should Lab 2 Page 61

62 7. Now from the pencil menu choose the option Apply Tags to 3 Artifacts 8. Select existing Shared Tags: Release 1, Extended Functionality, bob and click New Tag Page 62 Define and Manage Requirements with IBM Rational Requirements Composer

63 9. Lab 2 Create a new Shared tag named Mobile Devices and click OK twice. Page 63

64 10. Page 64 Rich hover over one of the artifacts to confirm the tags have been created Define and Manage Requirements with IBM Rational Requirements Composer

65 2.6 Define Relationships. Requirements Composer supports the concept of traceability. The new requirements should be represented as satisfying an existing requirement. 1. Make sure the three newly imported requirements are still selected and from the pencil menu choose the option Add a link to 3 artifacts and select Satisfies for the link type. 2. In the Create Link dialog, type mobile devices in the box Search for artifacts by id or for words contained in the name: Lab 2 Page 65

66 3. Select the Feature requirement Support dividend processing via mobile devices 4. If necessary, scroll the dialog box to find the requirement and click OK to create the 3 trace links Page 66 Define and Manage Requirements with IBM Rational Requirements Composer

67 5. Hover over one of the requirements to see the Links 2.7 Optional Model Word Import This module is optional and it is to be completed only if time permits. This module will provide a brief example of a Word import. Importing Microsoft Word documents Due to Microsoft licensing constraints we do not include Microsoft Word in the installs of the VMware images, but IBM Rational Requirements Composer will still import a created Microsoft Word document. Lab 2 Page 67

68 1. Expand the Create button (blue button) and Click Import 2. In the dialog, select option to Import a text document and convert to a rich text artifact. Then, select Next. Page 68 Define and Manage Requirements with IBM Rational Requirements Composer

69 3. Click Browse to navigate to C:\Workshops\RRC_HOW and select the file JKE Browser Support.doc and click Open. 4. Ensure the artifact type is Feature. Lab 2 Page 69

70 5. Page 70 Click Pick folder and from the dialogue expand the folders JKE Banking (Requirements Management)>JKE Business Recovery Matters Project, select the Features folder and click OK. Define and Manage Requirements with IBM Rational Requirements Composer

71 6. Select Import for Editing and viewing and click Finish 7. After the conversion has finished, click the ID column header (twice) to sort it from most recent to earliest, to ensure that the created feature appears on the first page. Lab 2 Page 71

72 8. Page 72 Click JKE Browser Support.doc to open and you will see the document Define and Manage Requirements with IBM Rational Requirements Composer

73 9. Click Edit to further refine this artifact. 10. Select all the text below the text Features, starting with 1.Browser Support should include through Chrome 10.0 or higher. Lab 2 Page 73

74 11. In the editor tool bar, click Save Selection as New Artifact and Insert. This will create a new artifact using the selected text, and then insert that new artifact into the current artifact. Requirements Parsing When importing a document, you can use text delimiters to identify requirements in a document to make separate artifacts. Users can mark up a document with text delimiters and then define those delimiters by using the Requirements Parsing wizard. Requirements are created from the text found in the delimiters. Individual artifact types can be defined for each unique keyword or set of text delimiters. Any requirement artifacts that are identified based on those keywords or delimiters will be of that defined artifact type. When you parse Rational Requirements Composer text artifacts, you can also create a link from the source artifact to any requirements that are parsed from that artifact. Page 74 Define and Manage Requirements with IBM Rational Requirements Composer

75 12. In the subsequent dialog, shorten the name to just Browser Support, ensure the artifact type is Feature, the link type is Extracted and click Finish. Extracted Link Type By creating an Extracted link, this will create a link between the new content and the place in the original document that it was extracted from. This allows us to identify the context from which a new requirement was created. Lab 2 Page 75

76 13. The new artifact is inserted into the original artifact, as an embed. 14. Click Done to finish editing and save. 15. To minimize the inserted artifact to show only the link, hover over the artifact and select Minimize artifact Page 76 Define and Manage Requirements with IBM Rational Requirements Composer

77 16. To maximize the inserted artifact to show both the link and content, hover over the artifact and select Maximize artifact Lab 2 Page 77

78 17. Return to the previous feature folder, by clicking the Features breadcrumb shown in green, to see that the folder view has a new artifact Browser Support. 2.8 Summary In this module, you were able to respond to a request to add new functionality to meet stakeholders needs using IBM Rational Requirements Composer. 1. This task was accomplished quickly by choosing the option to one-click create a new requirement. 2. You then added tags and attributes to the requirement with the use of the grid view editing, which provides the ability to quickly filter on a set of artifacts across artifact types. 3. You also created new requirements through importing CSV and Microsoft Word documents, allowing teams to import content outside of Requirements Composer into Requirements Composer. This provides an automated fashion to import multiple requirements at once. Page 78 Define and Manage Requirements with IBM Rational Requirements Composer

79 Realized Business Value Lab 2 One Click Create Expedites the creation of requirements with fewer key strokes. Grid View Editing Quickly access elements of a requirement such as Name, Primary Text, Attributes and Links and refine as needed. Multi-Select and Edit Attributes- Quickly change the status and other pertinent attributes of multiple artifacts at once. This function allows teams to refine and track status across artifacts during key phases in a project. Expedite Creation of Requirements with CSV Comma separated value files provide an easy medium for teams to leverage existing artifacts and import them into IBM Rational Requirements Composer. There is also flexibility to create new content while in an off site meeting and import the CSV at a later time. Web 2.0 Tags Identify and group artifacts with Web 2.0 tags. Once the tags are applied to artifacts, quickly filter to isolate artifacts with those tags, place the artifacts in collections and review. Next, create saved filters to quickly query against specified tags. Requirement Reuse - Save time in creating requirements by using existing Word documents to seed your IBM Rational Requirements Composer projects. Simply import the Word documents and create requirements from the content. Page 79

80 Lab 3 Updating the Business Process In this lab, you will learn how to modify business process diagrams to support the new business requirements. It is often said that a picture is worth a thousand words. In many cases, visual requirements specifications are much easier for business users to digest than textual requirements. The techniques practiced in this module may not be new to you but in this lab section you will employ these techniques within the highly collaborative and intuitive Rational Requirements Composer environment. In Rational Requirements Composer, we utilize an easy-to-use, easy-to-understand business process notation called BPMN ( Here is a quick summary of the main elements of BPMN. Page 80 Define and Manage Requirements with IBM Rational Requirements Composer

81 You will perform the following tasks in this lab: Navigate to a business process diagram in the project. Examine the Requirements Composer capabilities for working with business process diagrams Examine what work has already been done on a diagram Modify existing business process to add new functionality. Put in comments so others can review your work and provide early feedback Add a shared tag so anyone can easily find the work you have done At the end of the lab, we will have developed the new tasks to support the allocation of dividends to different good causes. In the real world, you would have to do this discovery and analysis yourself! Lab Scenario As we continue to gather more information, some faceto-face meetings with stakeholders should occur to gather and validate requirements. A workshop is conducted to describe some information about Allocating Dividends to Causes, and from this workshop we will identify the business process elements to be modified. Note that this does not represent all of the Allocating Dividends to Causes requirements, but this is the change we will be working with in this lab. The beauty of the collaborative approach is that we can start with what we know, and add to the requirements as the rest of the requirements become clearer. Team Role You are now playing the role of Bob, an Analyst (Product Owner) in the JKE Banking (Requirements) project. Bob has Author role privileges. Lab 3 Page 81

82 3.1 Navigate to the Business process diagram 1. Your browser should still be open from the previous lab and you are positioned on the Feature folder (under JKE Business Recovery Matters). Page 82 Define and Manage Requirements with IBM Rational Requirements Composer

83 2. Select the Processes folder (under JKE Business Recovery Matters) to see the business process diagrams (NOTE: The order and ID of these diagrams might be different on your screen ) 3. Select the Business Process diagram Allocating Dividends to a Cause. This will open up the business process diagram. Lab 3 Page 83

84 4. Examine the process diagram. Note: You are currently in read-only mode and cannot edit the diagram. Business Value When you hover over the elements, you can review the links associated with that element. 3.2 Examine the capabilities available in the Business Process diagram You start by examining an existing business process diagram, Allocating Dividends to a Cause in order to understand what capabilities exist in for this diagram. These include pools, swimlanes, tasks, connectors, decision points, events and data and message objects. (NOTE: The ID of the diagram could vary from what you see on your screen but the values within will be the same) 1. Page 84 Examine the diagram and look at the horizontal areas in the diagram. There are two outer areas which are called pools in BPM. Pools typically represent the organizations or entities. Within the pools you can have lanes which represent the resource, person or department that performs the tasks or takes the decisions within the lane. Define and Manage Requirements with IBM Rational Requirements Composer

85 You have two pools in this diagram, the Donor pool representing the donor and the JKE pool representing the bank. Lab 3 Page 85

86 If you select any blank area in the diagram and then hover over the pool area, a popup will appear indicating the name of the pool. Hint If the popup does not display the element you are hovering over, try clicking on the element to select it, then move away from the element and back again. This should bring up the correct popup. 2. Select any clear space in the area called Securities and a popup entitled Lane:Securities will appear. This indicates what part of the JKE organisation performs certain tasks or decisions. 3. Select the Task Display Detailed List of Accounts. The task is a function that is performed by the JKE organisation in the Securities division. Page 86 Define and Manage Requirements with IBM Rational Requirements Composer

87 4. The Connector identifies the sequence in which the elements are performed, such as the message flow connector from Provide Secure Profile Info to Access Account (task) to the Display Account Details (task). 5. Decisions points are when a choice has to be made. The exclusive (OR) decision point is shown on the diagram. Lab 3 Page 87

88 6. Events trigger the business process. There are two special events on the diagram. The Start event and the End event. The Start event occurs to start the business process and occurs when the Donor Accesses the JKE web site. The End event is when the business process has completed,in this case after the task Display of Finalized Transaction (scroll the diagram to the right, if necessary). Page 88 Define and Manage Requirements with IBM Rational Requirements Composer

89 7. Data and Messages can be generated or consumed by tasks. In this process, the History data object is passed between tasks on the Securities and Private Banking swimlanes (scroll the diagram to the right and down, if necessary). 3.3 Examine what work has already been done In this part of the exercise, you look at the tags and links to see the context of the diagram. 1. Start on the the right-hand side of the screen where the Overview sidebar is displayed. Note your Overview sidebar will have different values compared to the example displayed below. Lab 3 Page 89

90 This Overview section indicates the name of the business process diagram, a description and other attributes of the diagram such as status. 2. Look above the Edit button and you will see the tags for this diagram. The tag Release 1 indicates this business process will form part of the first release of the system. Tags allow you to quickly select and manage artifacts in the project. They allow you to introduce structures beyond the traditional requirements hierarchy. Page 90 Define and Manage Requirements with IBM Rational Requirements Composer

91 3. Lab 3 Select the Links section in the sidebar to display all the links related to this business process diagram. Page 91

92 4. Select the icon Highlight all Links in the Links area. This displays the link icons on the business process diagram in the places where the elements are linked to other elements in the project. The top part of your business process diagram should now look similar to this, with the linked elements highlighted in green and the link number on the top-left corner of each linked element 5. Page 92 De-select the icon Highlight all Links in the Links sidebar and the highlighting will be removed from the business process diagram. Define and Manage Requirements with IBM Rational Requirements Composer

93 6. Lab 3 Now look at the content of the Links sidebar. Examine the different types of Links: Link To, Link From, Illustrated By and Satisfied By. These all refer to other elements in the project that relate to elements of this business process diagram. Page 93

94 7. Hover over the item in the Link To section entitled Donor must be registered user to access account details. You will see a pop-up with the details of that element in this case a Business Rule. Business Value When you hover over the elements in the Links sidebar, you see a summary of the linked element. This gives you quick access to the linked information without taking away your focus on the process diagram. If you want more information, you can immediately drill-down into the actual element. 3.4 Enhance the existing process You will now modify the business process diagram to reflect the modified or missing requirements. Saving your edits At any time during the editing, you can use the Save button to save your work and then continue editing. Page 94 Define and Manage Requirements with IBM Rational Requirements Composer

95 1. Select the Edit button on the top right of the screen so you can start modifying the business process diagram. 2. Now your diagram will be reloaded for editing and have additional buttons, menus and editable areas. 3. For more room in editing the diagram, collapse the side bar Lab 3 Page 95

96 Sidebar To edit the artifact description and attributes the sidebar will need to be open In the Donor lane move the Acknowledge Contribution Dialog, Display Finalized Transaction and the End event to the right leaving sufficient space to add a decision point and a note. a. Use the ctrl key or lasso to multi-select these elements or individually click and drag elements. Make sure only the three elements are moved. You may need to click on a blank area outside any pool or swimlane to clear your selection. b. Drag the elements, right, to a new position Add a decision point a. Page 96 Select the Exclusive Decisions element, from the toolbar Define and Manage Requirements with IBM Rational Requirements Composer

97 b. Click in the space between Provide % and Organization Details and the Display Finalized Transaction tasks to add the Decision to the diagram. c. Enter the name of Decision Choose More Than 1 Org and press the Return key. Your diagram should look similar to this: Lab 3 Page 97

98 6. Page 98 Add connectors to the decision point. a. Switch your cursor to a Connectors cursor by going to the Pointer pulldown menu b. Click on the Task Provide % and Organisation Details and the click on the Decision Choose More Than 1 Org. Define and Manage Requirements with IBM Rational Requirements Composer

99 Lab 3 c. Repeat the previous steps to add a connector between the Decision Choose More Than 1 Org and the Task Acknowledge Contribution Dialog. d. Repeat the previous steps to add a connector between the Task Acknowledge Contribution Dialog and Display of Finalized Transaction. Page 99

100 7. Add a Note to explain the change 8. Select the Note element from the Annotation toolbar pulldown menu a. 9. Click on the drawing area to place the Note and enter the text Display to include multiple orgs. Select Save to save your changes. Page 100 Define and Manage Requirements with IBM Rational Requirements Composer

101 At the end of these steps, the diagram should look similar to this: 3.5 Collaborating regarding changes You will now add comments to the diagram to inform the tester and developer of the changes you have made. Business Value Focussed commenting - at an element level like a task or other diagram element saves time for you and your teammates by directing their attention to the item you want they to look at. Lab 3 Page 101

102 1. Select the Acknowledge Contribution Dialog task and a menu will appear above the task. Select the balloon icon Add Comment. 2. A Comment dialog box will appear. a. Enter the following into the Subject section of the comment: Please note that changes will need to occur in the acknowledge dialog. Enter the following into the Comment section: The acknowledge dialog will need to be refined to reflect UI changes in order to support processing for multiple organizations in a single transaction. Page 102 Define and Manage Requirements with IBM Rational Requirements Composer

103 3. Specify the users you want to see the Comment 4. Select the button next to the Directed To: section of the comment. a. Lab 3 In the Select Users dialog, click Show All. Page 103

104 5. b. Select the users Al, Deb and Tanuj (use the Ctrl key and click to select multiple users) c. Click the Add & Close button. Select OK to complete the comment and close the comment dialog. Page 104 Define and Manage Requirements with IBM Rational Requirements Composer

105 This will generate a comment 6. If the sidebar is closed, open it and expand the Comments section 7. Select the Done button to save and complete your edit. Lab 3 Page 105

106 If your organisation has configured the provider in Requirements Composer, you will be notified by if any comments directed at you, or if comments has been changed. Business Value We provide the ability at the element and artifact level to generate in-context information such as comments directed to teammates as well as links to related artifacts such as business rules and user story elaborations. 3.6 Tag your diagram Now you will add the tag Bob to this business process diagram. You will use this tag later in this workshop. Page 106 Define and Manage Requirements with IBM Rational Requirements Composer

107 1. Select the tag icon in the top right-hand corner of the browser to add a new tag to this business process diagram. A dialog box will appear. 2. Lab 3 Select the tag bob to add this tag to this business process diagram and select OK Page 107

108 3. Confirm that bob is added as a tag 4. Select the user menu Bob and log out. For the next lab you will take on the role of another user Al 3.7 Summary You have now finished all your changes to the business process diagram. You have modified the business process diagram and added a comment directed to specific members of your team. You also added a personal tag to this diagram for later use. You have now learned the basics of business process sketching in Rational Requirements Composer. This allows you to document changes that affect your organization's business processes as part of any business process improvement programme. Page 108 Define and Manage Requirements with IBM Rational Requirements Composer

109 Realized Business Value Lab 3 IBM Rational Requirements Composer Business Process Capabilities Easy to use and manage business process capabilities help teams quickly visualize elements of a business process. Visualizing the business process is a great communication vehicle to identify the process. Elements that can be captured include: business events, tasks, connectors, business decisions, data and message objects, lanes and pools. Refining an As Is Diagram to Capture To Be Process Evaluating an as is business process in context of new requirements helps teams understand what potential changes in the business process are required. Additionally, if a business process requires changes, new requirements may be flushed out. Incorporate Changes- IBM Rational Requirements Composer provides quick multi-select options which allow a team to move existing BMPN elements and create space to add additional BPMN elements. Traceability - The true value is that requirements and other artifacts may be linked to tasks. IBM Rational Requirements Composer provides the full picture for teams. Not only can teams visualize their business process, they have the ability to understand what artifacts are related to that process. This information is made available in a transparent way through rich hover. An analyst may choose to highlight the elements in the process diagram to understand which have links, or an analyst may simply hover on an element and assess if there are pertinent links to other resources. Include a Web 2.0 Tag to Identify Artifacts for a Sprint The use of Web 2.0 tags helps an organization group multiple types of artifacts related to a release. The tags may be used later to isolate the artifacts and add them to a review and/or a collection. Page 109

110 Lab 4 Refine the Use Case Diagram and Specification In this lab, you will update the use case diagram and the related analysis artifacts that are impacted by the change. At the end of this module you will understand how to: Browse a use case diagram Update a use case diagram Modify a use case elaboration artifact. Collaborate with the rest of the team around the changes you have made Browse a Module used to document a Use Case Specification Create a Module Page 110 Define and Manage Requirements with IBM Rational Requirements Composer

111 Team Role You are now playing the role of Al, an Architect in the JKE Banking (Requirements) project. He helps identify the architecture and is specifically interested in Analysis and Design as well as UI Components. He would like to ensure there is reuse wherever possible. Al has Author role privileges. 4.1 Start the Requirements Management Application 1. If not already open, open the web browser and go to aternatively click RM in the browser bookmarks toolbar. 2. Log into IBM Rational Requirements Composer. Type al for both the User ID and Password and then click Log In. Lab 4 Page 111

112 You will then see All Projects and a list of the projects Al participates in: 4.2 Study and Navigate the Use Case Diagram The first task will be to familiarize yourself with the Use Case Diagram. 1. Open the use case diagram. Page 112 a. Open the JKE Banking (Requirements) project by selecting Show Artifacts. b. From the explorer, open the JKE Banking (Requirements)/JKE Enterprise Project/Use Case Content folder. Define and Manage Requirements with IBM Rational Requirements Composer

113 Lab 4 c. Select JKE Enterprise Diagram to open the Use Case Diagram d. The Use Case Diagram will open in the editor area. Page 113

114 2. Hover over the model elements and explore the use case diagram. 3. Scroll down to see the green use cases near the bottom of the diagram. These are the use cases that are related to Business Recovery Matters. Page 114 Define and Manage Requirements with IBM Rational Requirements Composer

115 Use Case Driven vs. Agile Processes In this example project, the use case diagram visually depicts the scenarios covered in JKE and the actors that perform them. JKE Enterprises follows a Use Case Driven approach (use cases), and JKE Business Recovery Matters follows an Agile approach (user stories ). This use case diagram has flexibility to support both requirements processes. a. Hover over Donor Chooses an Organization. The rich hover will contain a list of all linked artifacts. Click the link Donor Chooses an Organization to open this user story. Rich Hover Rich hover functions provide a quick view of linked items. User Stories User stories are a popular agile technique used for documenting functional requirements. In a user story, the interaction between the user and the system is captured as a brief conversation. User stories were traditionally hand-written on index cards, and are sometimes still referred to as cards for this reason. Lab 4 Page 115

116 4. The user story elaboration Donor Chooses an Organization will open. This user story elaboration was created from a template, and is meant to look like an agile-style story card. Templates Templates provide common, standardized structure and formatting to RRC artifacts. In addition to lending consistency, templates are also a good way to provide guidance and instruction to team members who will be writing requirements documentation. Page 116 Define and Manage Requirements with IBM Rational Requirements Composer

117 i. The Links drawer in the sidebar gives information about all incoming and outgoing links for the user story. By default, links are sorted alphabetically and grouped by type. ii. As part of the user story confirmation, an embedded image is provided to illustrate the expected result. In this case, the image is a user interface sketch. Click the whitespace to the right of the Embeds link Finalized Transaction to show the image in the main content page Lab 4 Page 117

118 We will explore UI sketching and storyboarding in the next lab. Embedded artifacts Embedded artifacts are automatically updated everywhere they are used, making documents much easier to keep up-to-date. iii. Page 118 Now, hover over the Finalized Transaction link to highlight the embedded image and to bring up the rich hover with quick information about the image. Define and Manage Requirements with IBM Rational Requirements Composer

119 b. Click the Artifacts Menu and choose the JKE Enterprise Diagram to return to the use case diagram. Navigating from the Artifact Menu Use the Artifacts Menu to quickly navigate between artifacts, particularly those that you have recently viewed or created. 4.3 Update the Use Case Diagram The use case diagram needs some changes to describe support donating to multiple organizations. 1. Add the user story elaboration that describes dividend processing for more than one organization. For your convenience, the user story elaboration has already been written for you and only needs to be linked to the use case. a. Click Edit to edit the diagram. This is will show the use case diagram editor Lab 4 Page 119

120 Editor The first time the editor is opened can take a few seconds as the plug-in is cached into the browser. b. Page 120 Scroll down and click the model element Donor chooses an Organization Define and Manage Requirements with IBM Rational Requirements Composer

121 Lab 4 c. Click the link icon in the hover menu to open the Links window. d. In the Links window, click the Add Link button. Page 121

122 Page 122 e. Set the link type to Illustrates. f. In the search area, type Donor Chooses. As the search results are displayed, one of them will be a user story elaboration named Donor Chooses Multiple Organizations. Define and Manage Requirements with IBM Rational Requirements Composer

123 g. Select the Donor Chooses Multiple Organizations user story elaboration, scroll down the dialogue and click OK to create the link. 2. Click Done to save your changes to the use case diagram and exit editing mode. 4.4 Modify a Use Case Elaboration Now that the document has been updated, make a change to the newly-linked use case elaboration. For this exercise, we'll make a simple change by adding a new glossary term. Lab 4 Page 123

124 1. Add a new glossary term to the newly-linked use case a. Page 124 Hover over the use case Donor Chooses an Organization and select the newly-linked use case Donor Chooses Multiple Organizations from the rich hover. Define and Manage Requirements with IBM Rational Requirements Composer

125 b. The use case elaboration document will open in the editor. Click the Edit button to modify the use case elaboration. c. Add a new glossary term to the use case. i. Lab 4 Underneath the Conversation heading, locate the text Registered User accesses account information via JKE.com. Highlight the text account to select it. Page 125

126 Adding Glossary Terms Capturing terms as you go along is a good practice for defining acronyms or terminology in a project. New glossary terms are visible and usable by the whole team immediately. RRC glossaries function like live, online dictionaries where terms are defined in a single central location. A quick keyboard shortcut to look up and add new terms is to click on or select some text and press Ctrl+spacebar. Note that this keyboard shortcut may not work in a virtual machine environment. The steps below will describe the regular mouse gestures in case the keyboard shortcut does not work. Page 126 ii. Click the Lookup Term button in the toolbar to search for existing terms starting with account. There are several terms in this project that contain the word account. iii. In the Glossary lookup window, select the term Account to add it to the use case. Define and Manage Requirements with IBM Rational Requirements Composer

127 Note that the newly-added term is displayed in blue text. This is a link to the Glossary definition of Account. 4.5 iv. Click Done to finish editing the use case. v. Click the Artifact Menu and choose the JKE Enterprise Diagram to return to the diagram. Notify Team of Changes Use the collaborative features of IBM Rational Requirements Composer to notify the rest of the team members of the changes you have just made. A comment will let Bob, Tanuj, and Deb know that Al has made some changes to the use case diagram, and can also contain a summary of the changes made. As these changes are of particular interest to Bob, he should also tag them with the bob tag created in Lab 2. This will make it easier for Bob to quickly locate everything that he has to act on. Lab 4 Page 127

128 1. Create a comment for this change so that Bob, Tanuj, and Deb know what you have modified. a. Click the Comments drawer in the sidebar if it is not already opened. b. Click the Comments button and select Create a new comment for Artifact. Comment targets Comments can be made for an artifact as a whole (e.g. a use case diagram), or on specific elements in that artifact (e.g. a single use case or actor in the diagram). Try to choose the comment target that best represents the scope of what you are commenting on. Page 128 Define and Manage Requirements with IBM Rational Requirements Composer

129 Lab 4 c. In the Subject line, type: Use Case Diagram updated for multiple organizations d. In the body of the comment, type: Hi team, I linked a new user story elaboration. Page 129

130 Page 130 e. Beside the Directed To box, click the... button to open the Select Users window. f. In the Select Users window, click Show All to show a list of all users. g. Select Bob, Deb, and Tanuj. You can select multiple users by holding down the Ctrl key as you click each one. Define and Manage Requirements with IBM Rational Requirements Composer

131 Lab 4 h. Click Add & Close to add them to the recipient list. i. Click OK to create the comment. If the comment already exists click cancel. j. The new comment is immediately shown in the Comments section in the sidebar. Page 131

132 2. Add the bob tag to the use case diagram. Page 132 a. In the upper right-hand side of the toolbar area, click the Select Tags icon to open the Select Tags window. b. In the Select Tags window, select the tag bob, check the Enterprise tag and click OK. Define and Manage Requirements with IBM Rational Requirements Composer

133 c. Lab 4 Verify that the bob tag has been applied to the use case diagram, alongside the existing Enterprise tag. Page 133

134 4.6 Browse a Module used for a Use Case Specification Module A module is a structured document that is composed of multiple artifacts each with their own ID number. In this part of the lab we will briefly describe the structure of a module and illustrate how a module could be used to capture a Use Case Specification. 1. Select the Modules drop-down and click on Browse Modules. a. Page 134 Select the Use Case Module (Formal) Template. Define and Manage Requirements with IBM Rational Requirements Composer

135 b. You create structure in a module by displaying artifacts as headings by promoting and demoting heading numbers and by modifying the order and hierarchy of the artifacts. i. Lab 4 Put a check in the box next to Artifact ID 361, 1.3 Intended Audience. Page 135

136 ii. c. Page 136 Select the pencil drop-down. A drop-down list appears where you can select to promote or demote the artifact in the hierarchy. You can change the hierarchy levels that are displayed in a module by selecting a level from Levels menu. Define and Manage Requirements with IBM Rational Requirements Composer

137 d. Lab 4 When you scroll through a module, a Preview window is displayed that shows the headings that are adjacent to your position in the scroll bar. This enables you to quickly preview the overall structure of the module. Page 137

138 e. You can open and edit an artifact in an Artifact Editor by double-clicking on the Artifact ID. This opens the base artifact in a separate editing window. i. Double-click on ID 149. ii. Artifact 149 opens up in an editing window. For definition of a base artifact, refer to the Help Topic, Reusing Artifacts and Modules. Page 138 Define and Manage Requirements with IBM Rational Requirements Composer

139 f. You can also edit an artifact in line by clicking the Edit icon next to the artifact. There are multiple text editing tools that are available for in-line editing. i. 4.7 Click the edit icon next to the artifact. Creating a Module You will now create a new module for a Use Case Specification to which you will add new and existing artifacts. We would normally base the Specification on a Template, but we are not using a Template in this case so that we can illustrate aspects of creating a module. 5. Lab 4 To create a module, click Create Module from the Modules menu. Page 139

140 a. Page 140 Type a name for the module Update Profile Account Information, select an artifact type. Define and Manage Requirements with IBM Rational Requirements Composer

141 b. Lab 4 Select the folder Use Case Content. Click OK. Notice the Template is set to None. Click Open Artifact to open the artifact in the Module Editor. Click Finish. The new empty module is created. Page 141

142 c. You can add new or existing artifacts to an empty module by clicking on these controls. In the Contents field enter Brief Description, set the Artifact Type to Heading, click on the pencil, then click on Display as Heading. Notice the Content with the Heading Number, the Artifact Type, and the Type and Format in the Overview. Page 142 Define and Manage Requirements with IBM Rational Requirements Composer

143 d. After module contains artifacts, you can add new or existing artifacts using the Add dropdown menu. Click Create New Artifacts. Type a name for the new artifact Applicable Actors, click on the pencil and select Display as Heading. The new artifact appears in a module. Lab 4 Page 143

144 Page 144 e. Create another artifact that is similar to this artifact by clicking Create Similar from the Artifact menu. The new artifact will be created with the same artifact type and it will also be displayed as a heading. Notice that you can create the new artifact after, before or below the existing artifact. These choices determine the initial numerical heading of the new artifact. f. For example, if you create the new artifact after an existing Heading 2 artifact, the new artifact will be displayed as Heading 3. Type a name Basic Flow of Events. If the heading number does not show then click on the pencil and select Display as Heading. Define and Manage Requirements with IBM Rational Requirements Composer

145 g. However, if you create the new artifact below an existing Heading 3 artifact, the new artifact will be displayed as Heading 3.1. Type a name for the new artifact- The registered user will identify which portion of the profile he/she would like to refine. Enter the Artifact Type Use Case Requirement, and click Finish. You might have to save the artifact by clicking on the disk icon. You might also have to click on the pencil and click on Display as Heading. Lab 4 Page 145

146 h. To add existing artifacts to this module, click Add Existing Artifacts from the Artifacts menu. For this demonstration, add the existing artifacts below as a child to Applicable Actors. Filter the display by folder. Add the 2 actors. Close the window. Page 146 Define and Manage Requirements with IBM Rational Requirements Composer

147 i. Notice that the newly added artifacts are not displayed as headings. To display the artifacts as headings, select each artifact and click Display as Headings from the Artifacts menu. Notice the heading numbers that appear before the artifacts. j. You might have to edit each of the Actors so that the name of the actor is visible. This is what you should end up with. Lab 4 Page 147

148 The entire module now has a readily visible hierarchy and structure. Page 148 Define and Manage Requirements with IBM Rational Requirements Composer

149 This was just an introduction to modules. There are many other useful capabilities of modules including: base-lining an individual module printing a module showing attributes in columns, and more To learn more about modules view these videos on YouTube Lab 4 For the next Lab we will return to the role of Bob, the Product owner, select Log Out from the user menu. Page 149

150 Page 150 Define and Manage Requirements with IBM Rational Requirements Composer

151 4.8 Summary In this exercise, you have browsed and updated a use case diagram (both the diagram and the use case specification document within a module) and sent notifications to your teammates about the changes you made. You were introduced to modules and how they might be used to document a Use Case Specification. Lab 4 Page 151

152 Realized Business Value Page 152 Explore Elements of Use Case Diagram The IBM Rational Requirements Composer Use Case diagram provides a simplified way to communicate the pertinent scenarios, actors and their associations. Use case diagrams are a very helpful communication vehicle to visually depict the key scenarios (use cases or user story elaborations) for a project. Capturing these details in a visual way and then prioritizing the scenarios is a key step before elaborating the scenarios as either use cases or user story elaborations. Hover to Examine Linked Resources - A Use Case diagram provides visibility to related resources. Use hover to see which artifacts are linked to use case elements.the hover gesture provides just enough pertinent detail for the artifact in question, and reduces the need to click through to see more information. Use Templates to Drive Consistency Artifact templates provide a boilerplate for artifacts. Templates can help ensure each time a use case and/or a user story elaboration are created, the sections remain the same. This consistency can help ensure teams are aware of recommended or mandated format for the artifact. Embed a Sketch to Provide Context Incorporate pertinent user interface details that may be related to a use case and/or user story elaboration. This visual context helps identify critical details that are related to the scenario. Collaborate with Team About Changes Use the commenting feature to inform the team regarding refinements made to the scenarios. This step is critical to inform teammates of potential changes that have an impact. Applying Tags for Filtering - Applying a tag will help the team identify information considered relevant by other team members. For example, a new scenario that should be considered for the upcoming sprint. A team can quickly execute a filter query to pull out specifc artifacts that have been suitably tagged. Define and Manage Requirements with IBM Rational Requirements Composer

153 Lab 5 Change the User Interface In this lab, you will learn how to use the Storyboard, Sketch and Part editors to illustrate the user interface and user interaction related to requirements. Specifically, we'll update the user interface changes that will be required to accommodate the new requirement of choosing multiple organizations to donate to. This will help the team verify that they understand the requirement and what the implications are to the user interface design and user interaction. This will also communicate to development what to implement. Illustrating the user work flow in a storyboard, as opposed to just illustrating a static web page in a sketch, also makes it easier to identify other potential implications of changing the user interface and work flow. Lab Scenario As described in the Instructor Demo, JKE is amidst a sprint and has been requested to add new functionality to meet customer s needs. The new functionality provides the ability for a donor to choose more than one organization to allocate dividends. In this module, we'll update the storyboard to illustrate the user interface changes that will be needed for this requirement. Lab 5 Page 153

154 Team Role You are now playing the role of Bob, an Analyst (Product Owner) in the JKE Banking (Requirements) project. Bob has Author role privileges. In this module you will learn: What Storyboards, Sketchs and Parts are and what they are used for. How to edit user-interface mockups using these tools. How to use storyboards to illustrate the work flow related to requirements. What inheritance is and how it can be used for more efficient creating and editing of artifacts. Overview of Storyboards, Sketches and Parts Storyboards, Sketches and Parts are all ways of visualizing and illustrating requirements through user interface mock-ups. Parts are typically used for reusable parts of a web page or application (e.g., viewlets, navigation components, etc.). They can be added to sketches, storyboards and other parts. Sketches are typically used to illustrate web pages or application screens. They can be added to storyboards and other sketches. Storyboards are used to illustrate a work flow of a task from the perspective of the user, by using a sequence of frames. Each frame can inherit contents from a previous frame, a sketch, or the contents can be defined in the frame itself. Page 154 Define and Manage Requirements with IBM Rational Requirements Composer

155 Inheritance Inheritance is an important concept that improves efficiency in creating and modifying user-interface mockups. For example, if there is a common component, such as a log-in viewlet, that appears in many web pages or work flows, you can create it once as a part, and then add the part to multiple sketches or storyboard frames. If you modify the part in the sketch, the changes are only saved in that sketch; if you modify the part itself, the changes will be propagated to all sketches that inherit from it. Parts can inherit from other parts, sketches from other sketches, and storyboard frames from sketches, parts or other frames. 5.1 Start the Requirements Management Application 1. If not already open, open your web browser and go to Alternatively click RM in the browser bookmarks toolbar. Lab 5 Page 155

156 2. Log into IBM Rational Requirements Composer. Type bob for both the User ID and Password and then click Log In. Troubleshooting User name and password are case sensitive. Ensure you use lowercase bob Page 156 Define and Manage Requirements with IBM Rational Requirements Composer

157 You will then see the All Projects page and a list of the My Projects for which Bob is a member. 3. Lab 5 As Al, has been making changes to some artifacts and adding some comments that might effect Bob, lets examine the project dashboard, by alternatively clicking the Home Menu (in the top left of the banner) pull down and selecting JKE Banking (Requirements). Page 157

158 4. From the JKE Banking (Requirements Management) project dashboard examine the Recent Changes and Comments viewlets Viewlet Date Stamp The date stamp will be different in this workbook from your experience in the workshop. Also some of the artifacts and comments will only appear if the optional lab sections are completed. 5. From the Artifacts menu, click the Browse Artifacts option. Page 158 Define and Manage Requirements with IBM Rational Requirements Composer

159 5.2 Open the Storyboard The user interface and task flow for donating contributions is currently illustrated by the Dividend Contribution storyboard. 1. In the left sidebar, click the Folders section, and go to the following folder: JKE Banking (Requirements Management) > JKE Business Recovery Matters Project > User Story Elaboration > Storyboards. In the artifact list, click Dividend Contribution to Multiple Organizations. Note We could also illustrate the necessary UI changes by modifying the original Dividend Contribution storyboard. However, in this lab, we will keep the original copy of the storyboard and work from a copy of the storyboard instead. That copy called Dividend Contributions to Multiple Organizations - has already been created in the sample project. Lab 5 Page 159

160 2. The storyboard illustrates the user interaction through a series of frames. The first thing you should see is a list of frames, as well as a series of thumbnails representing each frame at the bottom of the storyboard. To view the contents of the storyboard, click each of the thumbnails in order, starting with the first one. Each frame illustrates one step in the user interaction of a task. 5.3 Edit the Storyboard We will now modify the storyboard to illustrate the user interface changes required for the new requirement to donate to multiple organizations. 1. Click Edit in the top right of the editor. Page 160 Define and Manage Requirements with IBM Rational Requirements Composer

161 2. The first page that appears is the Frame List. This shows all the frames in the storyboard. Tip for viewing the storyboard You will likely have to scroll to see the entire contents of each frame. To avoid some scrolling, you can collapse the right sidebar by clicking the button on the splitter pane between the editor and the sidebar. You can also use the browsers Zoom capabilities (e.g., Ctl + + (plus) to zoom in and Ctl + (minus) to zoom out ). Lab 5 Page 161

162 3. Click the first frame, in the list 4. At the bottom of the storyboard are a series of thumbnails that also represent the different frames of the storyboard (see the picture above). To view the storyboard, click each of the thumbnails at the bottom of the page, starting with frame Starting in frame 4, you'll see where the donor starts specifying their dividend contribution, scrolling down the frame if necessary This is where the user interface needs to change to accommodate contributing to multiple organizations. Page 162 Define and Manage Requirements with IBM Rational Requirements Composer

163 Tip for updating the storyboard We could just make the necessary changes directly in the storyboard. However, because the content we want to modify is defined in a part, it is more efficient to modify the part. By doing this, the user interface changes will automatically be updated in all sketches that use that part, and the part can be reused later for other sketches and storyboards. 6. Click on the wizard part of the sketch (the gray box where the user selects the Organization, etc.); this is the part we need to modify. If necessary, scroll the frame to locate this. 7. In the toolbar that appears above the selection, click the left arrow icon (with tooltip Open Previous). This will open the artifact that this content is inherited from. Lab 5 Page 163

164 8. This will open the artifact Donate wizard pg 1, which is a user interface Part. Explanation of Inheritance Although the storyboard does not directly inherit from the Donate wizard pg1 part, it inherits from the Dividend contribution - page 1 sketch, which inherits from the Donate wizard pg 1 part. Since the sketch made no changes (overrides) to the part, clicking Open Previous just opens the part directly. Changing the part will propagate to the sketch which will in turn propagate to the storyboard. 5.4 Edit the Part 1. Click Edit, to edit the user interface part. Page 164 Define and Manage Requirements with IBM Rational Requirements Composer

165 We need to modify the part to allow for selection of multiple organizations. The following image shows what the part should look like when we are done editing it. 2. Lab 5 Move the Percentage fields down. a. Press and hold down the Control key. Click the Percentage label, the entry field to its right, and the % label. Release the Control key. b. Move the mouse over any of the edges of the selected controls until you see the Move cursor. Page 165

166 c. 3. Drag the controls down to just above the row of buttons at the bottom (using the leftmouse button). Add a list box below the Organization drop-down. This is where the multiple organizations will be listed. a. Page 166 Click Input Controls in the editor palette. Click List Box. Define and Manage Requirements with IBM Rational Requirements Composer

167 4. Lab 5 b. Click just below the Organization drop-down field. c. Resize the list box as necessary. Click and hold the bottom-right corner of the list box and drag it so that it is the same width as the Organization drop-down field and does not overlap the Percentage fields. d. If the list box is not left-aligned with the Organization drop-down field, drag the left edge of the list box until it is. e. Remove the list items in the list box. Click the top <Item> in the list box, and click the Delete button in the tool bar that appears above the selection. Do this for all the remaining items in the list box. Create Add and Remove buttons to the right of the current drop-down list. a. Click Buttons in the editor palette. Click Button. b. Click to the right of the Organization drop-down list to add the new button. Be sure to click inside the gray (panel) area; it should automatically expand to accommodate the new button. Page 167

168 c. Click the new button. This should enable you to edit the label. Type Add to change the button label. d. Do the same steps to add a Remove button; add it directly below the Add button. Tip Fine tuning the location of the buttons can be difficult using a mouse. Try to select a button and then press. (punctuation) on the keyboard. You can now use the keyboard arrows to place the button more precisely. Press. again to get out of the detailed move mode. Don't move the mouse before pressing. as the mouse will move the button. 5. Click Done to end editing and save all changes. The following image shows what the part should look like now. Page 168 Define and Manage Requirements with IBM Rational Requirements Composer

169 5.5 Continue Editing the Storyboard 1. We now need to return to the storyboard. Click the Artifacts menu in the banner area. The storyboard should be listed in the Recently Viewed section of the menu; click that to return. Otherwise you can use the browser's Back button to return. 2. Click Edit. 3. Double-click on frame 4 ( either from the list or the thumbnail ) to go to that frame. Lab 5 Page 169

170 4. You will see your changes from the part applied to frame 4 (and subsequent frames). 5. Change the text above the donation UI to indicate that you can select multiple organizations. This will illustrate using inheritance between the frames. a. Click frame 4 to edit that frame. You'll notice a series of green dots below the frames, starting with frame 4. This indicates that each frame in this series inherits its content and design from the previous frame (e.g., frame 5 is based on frame 4, frame 6 is based on frame 5, etc.). So any change made to frame 4 will propagate to all the subsequent frames in the series (unless a particular frame overrides that change). b. Page 170 Click the text below the Money That Matters label (starting with Use the wizard below... ). Define and Manage Requirements with IBM Rational Requirements Composer

171 6. c. Click it again to edit it. Click again at the end of the string. d. Add the text You can now choose multiple organizations. If you now click on each frame in the series, you should see this text applied on each frame. Note Since the text in the previous steps is actually defined in a part, it would normally be better to update it in the part, which would then propagate to the storyboard. However, for the sake of illustrating inheritance between frames, we updated it in the storyboard. Lab 5 Page 171

172 7. Next, we would need to further modify the storyboard to illustrate how the work flow would change with the new selection mechanism for selecting multiple organizations. However, for the sake of time we will not do that in this module. 8. Click Done to end editing and save the storyboard. 5.6 Apply a Tag 1. Apply the tag bob a. Click the Select tags icon in the top right of the editor (above the Edit button). b. Click to select the tag bob. Then click OK. You should then see it displayed in the list of tags at the top right of the artifact. Commenting If we wanted to explicitly notify the rest of team about the part and frame changes we could create a comment on the panel and direct it to the team. The Recent Change viewlet on the project dashboard will also indicate that there has been a recent change to the part and storyboad. Page 172 Define and Manage Requirements with IBM Rational Requirements Composer

173 5.7 Summary In this module, you have updated the Allocate Dividends storyboard to illustrate what user interface changes would be necessary to accommodate the requirement of donating to multiple organizations. In the process, you learned what Sketches, Parts and Storyboards are, and how to use them. You learned how Inheritance between these artifacts can be used to increase productivity in working with these artifacts. Lab 5 Page 173

174 Realized Business Value Page 174 Examine Storyboards, Sketches and Parts Storyboards help illustrate the user interaction through a series of frames. This technique is very helpful when describing steps in a scenario as visually depicted by the user interface. Text does not always provide the same level of context as a storyboard. Sketches identify a specific frame within a user interface. Sketches are also inputs to storyboards. A sketch can represent visually what a user may expect within the interface and help a development team reach concurrence regarding expected presentation and behaviors before going to far into development phases. Parts help teams identify a reusable element for a user interface. A part may appear in one ore more sketches and can be reused. Parts are useful by simply modifying a part in one location and then the changes are reflected everywhere the part is used. Edit a Storyboard and User Interface Part Editing a storyboard provides the ability for a team to make refinements as required in a scenario that will impact the user interface. IBM Rational Requirements Composer provides the ability to quickly add new wireframes representing steps in a scenario. Additionally, the storyboard may be leveraged as a canvas to incorporate potential changes that may impact a sketch and/or a part in a sketch without incorporating these changes to elements that are reused. This flexibility is useful because once the changes are approved, new sketches and or parts may be created as needed from the elements in the storyboard. Illustrate Requirement Workflow in the Storyboard Artifact templates provide a boiler plate for artifacts. Templates can help ensure each time a use case and or a user story elaboration are created the sections are the same. This consistency can help ensure teams are aware of suggested elements in a rich text artifact. Inheritance Aids Teams to Quickly Refine the UI Inheritance provides flexibility in user interface design as changes applied in the parent object may be attributed to child objects. In this scenario, we demonstrated both inheritance at the wireframe Define and Manage Requirements with IBM Rational Requirements Composer

175 level and inheritance for parts. Lab 5 Apply Tag for Filtering - Application of a tag will help the team identify the refinements made to the storyboard that should be considered for the upcoming sprint. A team can quickly execute a filter query to identify specific artifacts. Page 175

176 Lab 6 Conduct a Review The purpose of this module is to validate the requirement artifacts that have been worked upon in the previous modules and achieve stakeholder concurrence before proceeding with development. Rational Requirements Composer provides a review and approval work flow which is helpful in involving the larger team for approval on a single or collection of requirement artifacts. In this module, you will learn how to: 1. Create a Review 2. Types of Reviews 3. Assign Reviewers and Approvers for the Review. 4. Participate in a Review 5. Closing a Review cycle Page 176 Define and Manage Requirements with IBM Rational Requirements Composer

177 Information The cost of correcting errors increases exponentially throughout the development life cycle. Therefore, it is important to discover problems early enough to solve them quickly and inexpensively. Requirements Reviews are intended to discover problems with the Requirements before you spend significant time and work in implementing the wrong thing. This is not to say that you must have a complete set of requirements before implementation, but be sure to review, internally and with stakeholders, those that are selected for implementation in the early iterations and those that will have a broad impact on the system (often called Architecturally Significant Requirements) to ensure everyone's concurrence before investing significant effort in implementation. Team Role You are now playing the role of Bob, an Analyst (Product Owner), in the JKE Banking (Requirements) project. Bob has Author role privileges 6.1 Create a Review After finishing with the changes to the User Interface, Bob, would like to create a review to validate if Curtis is happy with the elaborated requirements and get his approval before Bob adds the content to the Release Plan. 1. From the Storyboard breadcrumb, click JKE Banking (Requirements Management). Lab 6 Page 177

178 2. This will show the artifacts page 3. Ensure no filters are selected, by clicking the Restore Default view icon, on the Views section. 4. Next, Expand Filter by Tag section and choose the tag bob. A listing of requirement artifacts that meet the selected criteria will be displayed in the view. Page 178 Define and Manage Requirements with IBM Rational Requirements Composer

179 5. Click the Check Box at the top of the list to select all of the artifacts in the view. 6. Click the Edit Pencil drop down list box next to any of the artifacts and select Create Review Containing 9 Artifacts. Lab 6 Page 179

180 7. In the New Review Name field type: Add Multiple Organizations - Sprint 2, select 'Formal' as the Review Type and click OK to create the review. Page 180 Define and Manage Requirements with IBM Rational Requirements Composer

181 Information Types of Reviews Informal reviews Requirements reviews can be informal, such as simply showing draft requirements to your colleagues or demonstrating a prototype. These informal reviews are excellent for getting the structure of the requirements correct and removing obvious mistakes. By keeping the review team small, it is easier to make rapid progress. However, informal reviews can miss important perspectives of critical stakeholders. Formal reviews Requirement reviews can be formal meetings. Start with careful preparation, so that you receive and organize comments before the meeting. The meeting itself should produce decisions on all review items. After the meeting, you must pursue the review actions to completion. If these actions involve a substantial amount of work or require a change to an artifact that is under configuration control, consider submitting Change Requests to prioritize and track the work. Formal reviews are more wide-ranging and expensive. They provide for more balanced reviews from multiple perspectives. However, formal reviews involve more people, which makes them more difficult to coordinate (thus the need for formality) and expensive in terms of work hours. The review Add Multiple Organizations - Sprint 2 is created Lab 6 Page 181

182 8. Click Add Participants to add Curtis as the Approver and Deb and Tanuj as Optional Reviewers. a. Page 182 Click Show All to display all users. Select Curtis and click the Approver option and click Add to add him. Define and Manage Requirements with IBM Rational Requirements Composer

183 b. 9. Lab 6 Next, let's add Deb and Tanuj as Optional Reviewers. Use CTRL-Left click to choose both and click Add & Close to complete the action. The reviewers will now display in the Participant list. Page 183

184 10. Click Save Review to save the changes. 11. Click Start Review to start the review This starts the review 12. Now that Bob has started the review, we will switch to Curtis so that he can review the artifacts, select Log Out from the user menu. Page 184 Define and Manage Requirements with IBM Rational Requirements Composer

185 6.2 Participate in Review Team Role Curtis, a Customer (Stakeholder), in the JKE Banking (Requirements) project. Curtis has Contributor role privileges 1. Lab 6 Type curtis for both the User ID and Password and then click Log In Page 185

186 2. From the All projects page, click the Home icon 3. Curtis' Requirements Dashboard is shown. Page 186 Define and Manage Requirements with IBM Rational Requirements Composer

187 Dashboards Provide a better whole-team collaboration on requirements, with improved on-boarding (time-toproductivity) of new team members, with better team and project transparency Dashboards provide information about the project status at a glance. It provides the option to drill down to get more complete information. It also represents the integration point for the data provided by all Jazz components. There are project and user dashboards. User dashboards can be tailored, by the user, to contain only those viewlets of interest. 4. One of the viewlets on Curtis's Requirements Dashboard is the Reviews viewlet. Click Add Multiple Organizations - Sprint 2 to open the review. Troubleshooting If you do not see the review in the Reviews widget, the review was not started by Bob. Lab 6 Page 187

188 5. Click the Use Case Specification Apply for Organizational Funding to open the artifact for review. The artifact review should look similar to this 6. Click the Approve drop down and click Approve with Comments. Page 188 Define and Manage Requirements with IBM Rational Requirements Composer

189 7. Type: Approved, however, please check the steps 6 through 9 of the basic flow for accuracy. Click Approve. 8. Click Add Multiple Organizations - Sprint 2 in order to navigate back to the review. 9. Click Allocating Dividends to a Cause to open the review for the Business Process Diagram. Lab 6 Page 189

190 10. Click Approve to approve the artifact 11. Click Add Multiple Organizations - Sprint 2 in order to navigate back to the review 12. From the review page, click Next to see the next page of Artifacts to be reviewed. 13. Check the check box for all of the artifacts that have not been approved and click Approve. Page 190 Define and Manage Requirements with IBM Rational Requirements Composer

191 14. Go to the next artifact page, and click the check boxes for the artifacts that have not been approved and click Approve. Repeat this step for the final page of artifacts. 15. Note that the review now shows as 100% completed. Completion status is showed per artifact completed for required reviewers and approvers. Lab 6 Page 191

192 16. Click Done 17. Click Yes, for the Confirm Review Done pop-up 18. The review now shows as Done. Page 192 Define and Manage Requirements with IBM Rational Requirements Composer

193 19. Lab 6 Now we shall return to, Bob, the product owner, so from the user menu click Log Out. Page 193

194 20. Type bob for both the User ID and Password and then click Log In 21. From the All projects page, click the Explore Dashboard icon Page 194 Define and Manage Requirements with IBM Rational Requirements Composer

195 This will show Bob's Requirement Dashboard Finalize Review (Optional) The following steps are optional. It is not required and will not impact the following steps of the scenario. It is listed to simply close the loop in the review. Curtis has completed his review of the artifacts as the Approver. Bob may now Finalize the review because Deb and Tanuj are Optional Reviewers. Finalizing the review changes the state of the review to read-only. Team Role You are now playing the role of Bob, an Analyst (Product Owner), in the JKE Banking (Requirements) project. Bob has Author role privileges Lab 6 Page 195

196 1. From Bob's Requirements Dashboard, in the Reviews viewlet, select the Add Multiple Organizations - Sprint 2 review. 2. Click Finalize Review to finalize the review. 3. From the Confirm Review Finalize pop-up, click Yes. Page 196 Define and Manage Requirements with IBM Rational Requirements Composer

197 Information Two-tier review One technique to get the best of both worlds is to use staged, or "two-tier", reviews. The first tier is informal and performed by a smaller team, possibly many times. The second tier is more formal and performed by the complete group, perhaps only once. First-tier review: The authors of the requirements and the development team review the requirements during the first-tier reviews to ensure that they are unambiguous, complete and consistent. It is important to include testers and developers to ensure that the requirements are verifiable and feasible. These reviews determine whether the requirements are ready for the larger community to review. First-tier reviews may be informal, formal, or a combination of the two. Second-tier review: Involve the larger group during the higher-tier review to get more minds working on the problem and to achieve concurrence that the requirements are suitable for implementation and validation. It is best to have one formal requirement review at the Life cycle Objective (LCO) milestone and, optionally, one at the Life cycle Architecture (LCA) milestone if significant changes have occurred that introduce unacceptable risk. Tiered reviews offer several benefits: 1. Eliminate the issues caused by minor edits during the first-tier reviews, allowing subsequent reviews to focus on functionality 2. Provide a professional look to the requirements, presenting both the requirements and their authors in the best possible light 3. Safeguard the time of stakeholders who are reviewing the requirements, thus preventing "review burnout", or diminished effectiveness from overload and stress 4. Provide the best opportunity for full, effective reviews. Lab 6 Page 197

198 4. Finalized review should look similar to this: 5. Return to Bob's personal dashboard by clicking the Home icon 6. This will show Bob's Requirement Dashboard Page 198 Define and Manage Requirements with IBM Rational Requirements Composer

199 7. The Reviews widget will be empty as Show my active reviews is selected: Selecting Show all reviews makes the Review re-appear with a Finalized icon: 6.4 Summary In this module, you learned that how Rational Requirements Composer offers a review and approval work flow that can be used for both informal and formal review of requirement artifacts. Reviews help discover problems early enough to solve them quickly and inexpensively by involving various stakeholder groups to achieve stakeholder concurrence to close requirements early. Lab 6 Create a Review and Types of Reviews - Reviews are invaluable in the sign off of requirements and other artifacts. IBM Rational Requirements Composer will aid teams in the validation and concurrence process, but more importantly, the historical information from the review is tracked in history. There are various types of reviews. These reviews include: Informal: An informal review may be used to Page 199

200 Page 200 help support peer reviews. By its name it is informal in nature and provides the ability for a team to review the most current version of the artifact. This type of review is very beneficial early in the development lifecycle and may be leveraged as a precursor to ready a team for a formal review. Formal: A formal review is leveraged to track formal sign off concurrence regarding static artifacts. This process can be very helpful as a team may validate with stakeholders approvals and the context (details) of the approved artifact. This process helps if there are ever disagreements regarding the solution delivered meeting the approved content. Review Roles IBM Rational Requirements Composer supports various roles for participants in the review process. This functionality is key because there may be instances where a stakeholder should be considered an approver and the team requires their review. As an approver, they may approve and or disapprove artifacts. In other cases, persons are simply reviewers. As a reviewer, artifacts may either be reviewed or abstained. This type of role is beneficial as it helps involve more participants in the review and ensures they are integral in the review process. The last role is an optional reviewer. This functionality allows teams to include additional persons in the review process, but does not require their vote to complete the review. Participate in a Review Phases Participating in a review will help provide the POT participants hands on experience about the IBM Rational Requirements Composer review functionality. A review may be phased in that a review can be paused at any point in time. The purpose of pausing a review is that it provides the ability to add new artifacts to a review and/or add a new version of an artifact to a review. An individual may also complete a participant review. Once the review is completed the results of the review will be locked down. Provide Feedback in Review All comments will be tracked in the history of the artifact. The history will denote that the comment occurred as part of a review. If there are any questions at a later time about the results of a particular participant's review, this information would be tracked in the history. Define and Manage Requirements with IBM Rational Requirements Composer

201 Lab 6 Finalize the Review The finalization of the review is key to locking down the results of the review once the review is complete. This step is crucial to impede people from changing the results of the review. Page 201

202 Lab 7 Leveraging the Requirements Across the Lifecycle In the previous module we discussed the concept of conducting a review. A review provides a collaborated mechanism to validate the artifacts in the review and gain concurrence. Completing a review and approving requirements is often a precursor to leveraging requirements across the lifecycle in development and test. Lab Scenario In this module, we will take the next step and demonstrate how a team may quickly change the status of artifacts that have been reviewed to "approved" and add the artifacts to a collection. The collection helps facilitate the organization of artifacts in a meaningful way for an organization. In our example, we are organizing the artifacts related to the release planning process. Next, requirements may be used as inputs to development and test; from the collection, we'll automate the creation of workitems and test cases. Once this step is complete, we'll review the lifecycle traceability coverage. At the end of this module, you will have an understanding of collections and traceability links and how these concepts apply to leveraging requirements across the lifecycle. Page 202 Define and Manage Requirements with IBM Rational Requirements Composer

203 Team Role You are now playing the role of Bob, an Analyst (Product Owner) in the JKE Banking (Requirements) project. Bob has Author role privileges. What is a Collection? A collection is a set of artifacts that is created for a specific purpose. Artifacts in the collection are typically in a specific state, for example, artifacts which are in an Approved state and are ready to be Implemented or Validated. Collections can be used to group a set of requirement artifacts which can later be used as input to other lifecycle artifacts such as work items in Rational Team Concert or test plans in Rational Quality Manager. Traceability links Through Collaborative Lifecycle Management (CLM) integration, you can create traceability links to new and existing artifacts in other Jazz-based products. You can establish links from requirements to development and test artifacts. After creating links, you can display a summary of the linked artifact, navigate to the artifact or use views to show these traceability links in the same matrix. Lab 7 Page 203

204 7.1 Filter using a tag to view requirement artifacts In this exercise, we want to filter the Requirements Dashboard to display only the requirement artifacts we want to work with. 1. From Bob's Requirement Dashboard, open the JKE Banking (Requirements Managment) project from My Requirements Projects widget by selecting Show artifacts 2. From the artifacts page click in the Filter by Folder section, the Clear filters icon, to clear the default folder filter. Page 204 Define and Manage Requirements with IBM Rational Requirements Composer

205 3. If not already open, expand the Filter by Tag section. a. Select the bob public tag. The artifacts view will now show artifacts tagged with the public tag: bob. Tags You can add user-defined, shared tags to new and existing artifacts. Use tags to categorize artifacts in a project. You can view all artifacts that have the same tag by filtering your display in the project area dashboard. Shared tags are available to all users in the project. Personal tags are only available to the user that creates them. Business Value Tags provide the ability to group artifacts across artifact types. For example, a tag may be used to group all requirements related to mobile devices. What we learned In this activity we have demonstrated the ability to use tags to filter and easily locate requirement artifacts. 7.2 Change status of the Requirements We will now change the status of the requirements to Approved. Lab 7 Page 205

206 Business Value Although these artifacts went through a review & approval cycle in Lab 6, this does not mean that the value of the 'Status' attribute was changed. Changing the attribute value allows filters to be used to look for 'Approved' artifacts. 1. Click the check box in the banner, next to the requirements and the arrow next to the edit pencil 2. and choose the option for Edit the attribute for 9 Artifacts (the actual number might vary depending upon completion of optional sections) Page 206 Define and Manage Requirements with IBM Rational Requirements Composer

207 3. Check the Status attribute and assign the value Approved from the list 4. Click Save What we learned In this activity, we have demonstrated the ability to change multiple artifacts at once which is very helpful in various phases of development. Teams can change multiple attributes at once for items like status to reflect approvals. Lab 7 Page 207

208 7.3 Add Approved Requirements to a Collection Now that the requirements are approved, we will add them to the existing Release Planning collection. Why use Collections? Collections can be used to group a set of requirement artifacts which can later be used as input to other lifecycle artifacts such as development plans in Rational Team Concert or test plans in Rational Quality Manager. 1. Group the artifacts by type, from the Grouping options menu by selecting Group by Type Grouping When there are large number of artifacts, grouping artifacts together can aid the organization of the artifacts page, especially if the artifacts are spread over many pages. Page 208 Define and Manage Requirements with IBM Rational Requirements Composer

209 2. Scroll down the page until the Feature artifact type grouping is visible and select, by clicking the check mark box for all the artifacts in that group. 3. Select the pencil icon, next to one of the checked artifacts, and choose from the menu Add 10 Artifacts to a Collection. The actual number might vary depending upon the steps completed in an earlier lab. Lab 7 Page 209

210 Planning Collection For this planning collection, we will include only high level requirements like features and user oriented requirements such as user story elaborations. Thus, requirements that do not meet this criteria are removed from this planning collection (additional low level requirements could be added to the Release 1 Capabilities Collection as they represent all capabilities for a Release). 4. Select the README folder from the Filter Display by Folder panel, to filter the display of existing collections, and select the Release 1 Planning Collection. Click the Add & Close button to confirm the collection association.. Page 210 Define and Manage Requirements with IBM Rational Requirements Composer

211 5. To confirm that Release 1 Planning collection contains the new artifacts, click the Collections menu (in the banner) and select Browse Collections. 6. From the list of Collections, click Release 1 Planning. 7. This will show the collection view for Release 1 Planning. Lab 7 Page 211

212 8. To reduce the number of artifacts shown, we will now click the Filter by Tag section and then the tag bob. 9. Let's examine another way to add items to a collection. a. Page 212 Click the Add Artifact icon, which will open the collection in edit mode and will show the Add to Collection dialog. Define and Manage Requirements with IBM Rational Requirements Composer

213 b. Type donor choose in the search field, and from the list of displayed artifacts, select the user story elaboration Donor Chooses Multiple Organizations. c. Select Add & Close to add the artifact to the collection Edit mode You will notice that the collection automatically opened the collection in edit mode after the artifact was added. Lab 7 Page 213

214 d. Click Done to save the collection, and close the editor What we learned In this activity we have learned how to add existing artifacts to an existing collection. This collection of related requirement assets can now be used to assist in sprint planning or test case creation. 7.4 Create Lifecycle Links In this exercise, we will create lifecycle links. Lifecycle links allow the requirements to be associated with their corresponding lifecycle artifacts in other applications, for example Work Items (Defects, Change Requests, Story, etc.) and Test Cases and Test Scripts Page 214 Define and Manage Requirements with IBM Rational Requirements Composer

215 Lab 7 Page 215

216 Traceability Links Requirements may be used as inputs to generate development and test content. The CLM solution provides flexibility for teams to create test and development artifacts from requirements in their tool of choice. Also, teams may apply an approach to create tasks identifying new artifacts which need to be created. We will demonstrate examples of each. Bob acts as a requirements analyst product owner, and will predominantly work in Requirements Composer. He can assist development and test by creating artifacts from requirements. Deb acts as a developer and will spend her time in Rational Team Concert. She may create work items from requirements. This task may be performed by leveraging a collection to define content for a release plan. Next, she may choose which requirements make sense to generate stories in the plan to distribute work to developers to build the solution. Task management may be useful to identify activities a person should perform. We will create a task related to the RTC work item in order to inform Tanuj test cases will need to be created from the requirements collection. Tanuj could create a Test Plan from a collection and generate test cases from the requirement content in the test plan in Rational Quality Manager. Information In this section, Bob would like to create some new content for consideration for the release plan. In order to complete this step, he will need to create an RTC story from the Support Windows 7 operating system requirement artifact. Business Value Creation of user story content allows a product owner to quickly inform the development organization of things he would like them to consider to add to the release plan and consider for sprint 2. Page 216 Define and Manage Requirements with IBM Rational Requirements Composer

217 1. We will now add some links, so lets first return to the project artifact page by clicking the JKE Banking (Requirements Management) breadcrumb 2. Ensure the tag filter, bob is selected to filter the requirement artifacts 3. Click Support Windows 7 operating to open the artifact. You may need to scroll the page. Lab 7 Page 217

218 4. And now add a Lifecycle Link Page 218 a. From the sidebar, click the Links section b. and then click the Add Link to Artifact icon c. Select from the list the Implemented By link type which will open the Create Link dialog. It may be necessary to scroll down the list to find this link type. Define and Manage Requirements with IBM Rational Requirements Composer

219 d. Choose Create New radio button. The contents of the dialogue will change. e. Enter the following for the new Story work item in Rational Team Concert that will be linked to the requirement in Rational Requirements Composer. Field Entry Summary Implement support for Windows 7 operating system Filed Against JKE->BRM Planned For Product Backlog Description Implement the support for Windows 7 operating system It should look similar to this: Lab 7 Page 219

220 Page 220 f. At the bottom of the dialogue, click the OK button. Depending upon screen resolution it might be necessary to scroll the window. g. Verify that the new story has been created Define and Manage Requirements with IBM Rational Requirements Composer

221 h. And hover over the link to view the contents of the work item. Information Now, Bob will inform Tanuj that there are new requirements ready for test cases. Bob will create a work item task to inform Tanuj to complete this step. Business Value RTC Task management helps teams identify pertinent tasks as part of the development process. This step is performed as test organizations generally will create their own test cases versus having a requirements analyst create them. Additionally, the linkage between a task and a work item helps outline which activities are pertinent for a given work item. For example, a task may be created as in this case to indicate a test case needs to be created for test coverage. Another example is an impact analysis task which requests a team to review the impact for including a change request upon requirements and development resources. Lab 7 Page 221

222 5. Now that the link as been create, navigate to the Story work item by clicking on the link in the Links sidebar. This is will show the created Story in the work item editor. Page 222 Define and Manage Requirements with IBM Rational Requirements Composer

223 6. Lab 7 For the new story, create a child task by selecting the Link tab, Add Related and clicking Children. a. select the Task type and b. at the bottom of the dialogue, click on Create Linked Task Page 223

224 c. and assign these fields: Field Summary Entry Create the test case for Implement support for Windows 7 operating system Filed Against JKE->BRM Planned For Product Backlog Description Create the test case for Implement support for Windows 7 operating system Owned by Tanuj It should similar to this: d. Page 224 To create the task, Click Save. Define and Manage Requirements with IBM Rational Requirements Composer

225 e. Verify that the new task was automatically linked to its parent story, by using the rich hover over the link in the Quick Information area. f. Log Out and close the browser 7.5 Open the Quality Management application 1. Open a new Firefox web browser, and click QM in the browser bookmarks toolbar. Business Value Even though Tanuj's focus is testing, he has exposure to the development lifecycle through his dashboard. The dashboard provides an initial interface point for him to evaluate if there are new tasks. The dashboard provides quick available information across the lifecycle. Lab 7 Page 225

226 2. Type tanuj for both the User ID and Password and then click Log In. Troubleshooting User name and password are case sensitive. Ensure you use lowercase tanuj Page 226 Define and Manage Requirements with IBM Rational Requirements Composer

227 3. Lab 7 From the project dashboard, examine the My Tasks viewlet to sees new tasks assigned to Tanuj. a. Open the task, Create the test case for Implement support for Windows 7 operating system b. Change the state of the task to Start Working Page 227

228 Page 228 c. and click Save d. Navigate back to Tanuj's Quality Management Dashboard by clicking the browser back button. e. Create a Test Case by selecting the Construction pull-down menu Construction and select Create Test Case Define and Manage Requirements with IBM Rational Requirements Composer

229 f. Enter the following fields in the Summary Section and press Save: Field Entry Test Case Name Test support for Windows 7 operating system Owner Tanuj Description Test support for Windows 7 operating system Weight 100 It should look some similar to this: Information Tanuj will now link the RTC user story to the newly created test case. Performing this step to create the linkage represents coverage between development and test. Lab 7 Page 229

230 Page 230 g. Select the Development Items section and Add Development Items: h. Search for the existing Implement support for windows 7 operating system Work Item, and select it from the displayed Matching Work Items Define and Manage Requirements with IBM Rational Requirements Composer

231 i. To add the work item to the test case, click OK j. Click Save to update test case It should look some similar to this: Lab 7 Page 231

232 4. Log out and close the browser Troubleshooting We close the browser to ensure that when switching between applications the user name is not cached. For normal operations this should not be needed because typically only 1 person uses a computer unlike this lab where we change between user roles. Information Now, we would like to represent that a requirement is covered by the newly created test case. We will complete this step as Bob. The purpose of performing this step is to represent the coverage between requirements and test. This link is important to create because it shows that a requirement is covered by a test case. Page 232 Define and Manage Requirements with IBM Rational Requirements Composer

233 7.6 Start the Requirements Management application 1. Open your Firefox web browser and click RM in the browser bookmarks toolbar. 2. Type bob for both the User ID and Password and then click Log In. 3. From the All Projects page, select Show Artifacts for the JKE Banking (Requirements Management) project. 4. From the Artifacts page, in the top right hand corner, search for the artifact: Support Windows 7 operating system and click the listed Feature. Lab 7 Page 233

234 5. Go to the Links section in sidebar and add new Validated By link. Page 234 a. Select the Add link to artifact button and select Validated By link type which will open the Create Link dialog b. Scroll down the list, and click the Validated By link. Define and Manage Requirements with IBM Rational Requirements Composer

235 Lab 7 c. From the displayed dialogue, select the Choose Existing radio button d. And filter the test case list for Test support for Windows 7 operating system, by typing Test support in the filter area. Page 235

236 Page 236 e. Select the check box for the Test Case: Test Support for Windows 7 operating system f. Click OK to create the Validated By link to the requirement. You might need to scroll down the web page to locate the button at the bottom of the dialogue. g. Verify the new Validated By link has been by hovering over the new sidebar link. Define and Manage Requirements with IBM Rational Requirements Composer

237 Information In this activity we have demonstrated how to effectively create links from requirements to other lifecycle artifacts and how to navigate through these links. Lab 7 Page 237

238 7.7 (Optional) Update the Product Backlog Bob now needs to review the Product Backlog and prioritize the new development story associated to the requirement with regard to the other development items. The team is about to begin the next sprint, so this is his opportunity to prioritize the Product Backlog and make sure his most important stories are addressed by the team. Team Role You are still performing the role of Bob, the Product Owner. In this section you will use Rational Team Concert Web UI to review and prioritize the Product Backlog for the development team. Product Backlog The Product Backlog is the master list of all functionality desired in the product. When a project is initiated there is no comprehensive, time-consuming effort to write down all foreseeable tasks or requirements. Typically, a project team writes down everything obvious, which is almost always more than enough for a first Sprint. The Product Backlog is then allowed to grow and change as more is learned about the product and its customers 1. Use the Home menu to navigate to the Change and Configuration Management section of the drop down and click the JKE Banking (Change Mangement) project Page 238 Define and Manage Requirements with IBM Rational Requirements Composer

239 2. From the JKE Banking (Change Management) project, click the Planning tab and select the name of the Current Plans viewlet. 3. From the list of plans, select the Product Backlog Lab 7 Page 239

240 4. The Planned Items page provides several views of the work items in the project's plan. The development story Implement support for Windows 7 operating system is the highest priority for Bob now, so he will check its priority in the Product Backlog and make adjustments so the new development story is at the top of the list. Page 240 a. Select Ranked List from the View As dropdown. b. Select the Implement support for Windows 7 operating system story, move the mouse pointer to its left and using the drag handle, drag and drop the work item to the top of the list. This ranks the story ahead of all the other work in the Product Backlog. c. Save the Plan Define and Manage Requirements with IBM Rational Requirements Composer

241 Information In this activity we have demonstrated how to effectively use the web planning features to prioritize development stories linked with requirements. Lab 7 Page 241

242 7.8 Viewing the Lifecycle Relationships In this exercise you will take a look at some of the out-of-the-box filters which may be used to understand lifecycle relationships. This information is available by using/creating filters in Rational Requirements Composer or by leveraging lifecycle widgets available in the Requirements dashboard. Traceability Views Traceability views provide appropriate context information to different roles from their tool of choice. This view provides to the analyst (Bob) important details of development and testing for the requirements. Traceability views are also available in other Jazz products so different roles can 1. Using the Home menu, open the Requirements Management JKE Banking (Requirements Management) project dashboard 2. From the displayed project dashboard, examine the My Requirements Projects viewlet, and for the JKE Banking (Requirements Management) project, click Show artifacts. Page 242 Define and Manage Requirements with IBM Rational Requirements Composer

243 3. Expand the Views section and select the saved view Release 1 Features (Lifecycle Coverage) Note: Saved views clear any existing filters. 4. Lab 7 Once you have selected the saved view, this filter will display a list of requirements and corresponding columns that will help you to understand the lifecycle relationships Tracked By, Implemented By and Validated By. If needed collapse the sidebar. Page 243

244 5. Expand the Click the Filter by Tag section, via a click, and select the additional tag bob Note that it is easy for Bob to see that one of the features, Support Windows 2008 server, does not have a corresponding work item or test case. Business Value Using the lifecycle coverage filter allows for quick identification of missing artifacts across the lifecycle. 6. Now lets see the impact if we change the status of one of the linked relationship. For the artifact Support Windows 7 operating system click, the Validated By link, Test support for Windows 7 operating system. This will open the test case Page 244 Define and Manage Requirements with IBM Rational Requirements Composer

245 7. Lab 7 You will notice that Bob does not have permissions to edit the test case. Log Out and type tanuj/tanuj and press Log In. Page 245

246 8. Set the test case Priority to High 9. And click Save to save the changed priority. Page 246 Define and Manage Requirements with IBM Rational Requirements Composer

247 10. Log out from Tanuj, close the browser, and start again the RM web application, with bob/bob. electing the saved view Release 1 Features (Lifecycle Coverage), adding the filter by tag bob and collapsing the sidebar so it looks similar to this 11. For the artifact Support Windows 7 operating system you will notice several icons: Lab 7 Page 247

248 12. Hover over the icon (indicator) on the left, and you will see that there are 2 linked artifacts ( Implemented By and Validated By ) that have changed significantly. One changes was for the Development Task to Implement support for Windows 7 operating system and the other for the Test Case Test support for Windows 7 operating system. So we should examine the changes in the Development Task and Test Case to see if it has impacted the requirement 13. We know from the previous steps that the only change to the Test Case, by Tanuj, was its priority and that it has no impact on the requirement, so let's clear the suspect indicator. From the hover click Clear. Pressing Clear, clears the suspect indicator for this artifact 14. Click Refresh to refresh the Artifacts page Page 248 Define and Manage Requirements with IBM Rational Requirements Composer

249 15. Lab 7 and examine the changes in icon in the Validated By column, where the suspicion icon on the Test Case is no longer shown. Page 249

250 Suspect traceability Suspect traceability indicates the potential impact of changes to linked artifacts. Suspicion indicators identify the artifacts that team members might need to modify to maintain logical consistency between the linked artifacts. Links between artifacts in a project or between projects across the lifecycle represent important traceability relationships and dependencies. Stakeholders must be aware of any change that can impact related artifacts. With suspect traceability, linked artifacts are marked with indicators to show that the artifacts might be affected by changes. Administrators can create suspicion profiles, which specify which projects, link types, artifact types, and attributes to watch to determine if a change puts linked artifacts in a suspect state. For example, an analyst might want to know if there is a change to a "planned iteration" attribute in a test case that is linked to a requirement. However, the analyst might not be concerned if the "owner" attribute for the test case is changed. You can view suspect indicators in various contexts and access the affected artifacts. You can remove the indicators if you determine that the changes are not significant, or when necessary adjustments are made in the linked artifacts to accommodate the change and restore consistency. Business Value To easily see a change by another member of the team that might impact a requirement artifact. Page 250 Define and Manage Requirements with IBM Rational Requirements Composer

251 16. Lab 7 Log Out as Bob, as we will be playing a different role in the next lab. Page 251

252 7.9 Summary In this module, you were able to leverage the requirements across the lifecycle. You started by locating requirements using a personal tag filter. You changed the status of these requirements to approved and added them to the Release 1 Planning collection. Lifecycle traceability links (requirements, development tasks, and test cases) were established directly in the tool. These relationships will help different roles in the team assess the requirements coverage over the lifecycle of the project. The lifecycle relationships were visible via the lifecycle traceability view in the Requirements dashboard. Realized Business Value Page 252 Filter Requirements Leveraging Tags After a review is completed teams often would like to change the status of artifacts to indicate they have been approved. This step is important from a metrics perspective to evaluate which artifacts have been approved. This step may be completed quickly by using the tagging feature and simply filtering for requirements based on a specific tag. Change Status of Attributes In-Line in Grid Using Multi-Select Organizations require the ability to quickly change attributes during phases of development. A common scenario is changing the status of requirements as progression occurs through various phases of development. IBM Rational Requirements Composer meets this need via in-line editing in a grid view. An analyst may quickly filter to isolate requirements using a filter and select the appropriate column they would like to change. Next, the attribute value may be chosen like status approved with relatively minimal clicks. Refine Release Collection Add New Requirements A common theme for organizations is to group requirements for a release, iteration and/or sprint. Teams require a simple way to identify which requirements are in a given release. IBM Rational Requirements Composer collections meet this need. A collection is simply a grouping of one or more artifacts. There are instances where teams must accommodate change requests and modify the release plan. Teams may quickly accommodate this need by adding the new requirements to the collection. This step is beneficial as it provides a historical reference from a Requirements Management perspective to requirements which should be considered for a Define and Manage Requirements with IBM Rational Requirements Composer

253 release plan. In Rational Team Concert the collection may be used to seed the release plan. Create Lifecycle Links Lifecycle links help identify which requirements are accounted for in both development and test. IBM Rational Requirements Composer helps teams quickly identify the kind of link through the link type. The following link types are pertinent: Implemented By: Implemented By identifies those artifacts which have an associated work item in RTC. Implemented By helps teams identify those requirements that are considered to be part of a release and has an RTC story in the release plan Validated By: Validated By identifies those artifacts that are covered by test artifacts. An analyst may quickly ascertain if there is test coverage, and what the results are of the test execution. These links provide transparency across the lifecycle. Tracked By: There may be cases whereby a change request may be captured. In order to identify the impact of a change request, an impact analysis task may be created. These types of tasks are beneficial for teams to evaluate the impact upon development, test, and requirements. Tasks: There are other types of tasks that can be created. Child tasks may be created to request a team member to complete an activity. One example may be to request the creation of a test case. Lab 7 Execution of Lifecycle Traceability Filter Tools in a CLM solution like IBM Rational Requirements Composer provide transparency across the lifecycle. Teams can create saved filters which provide details regarding test coverage and development execution. These filters are extremely beneficial to quickly provide details in a role's tool of choice. For example, a requirements analyst will typically spend most of his/her time conducting RM tasks. As a result, it is important to have lifecycle information at their disposal without having to move into another tool. Page 253

254 Lab 8 Status of Project Different roles on the team will have varying interests in keeping track of a project's requirements-related activities from keeping track of very detailed information to staying at a high-level to understand the overall status. Rational Requirements Composer offers many different views and customization options to allow users to quickly find the desired information. Lab Scenario In this module, we will look at the typical activities of an executive-product owner. The important activities for an executive is to evaluate project status, coverage, and lifecycle considerations. In this module, you will learn: Options for evaluating project status, requirements coverage and lifecycle relationships Usages for Dashboards, Widgets and Views how to customize the information displayed that is most relevant How to export a filtered view as a report Page 254 Define and Manage Requirements with IBM Rational Requirements Composer

255 Team Role You are now playing the role of Ursula, a Project Executive in the JKE Banking (Requirements) project. Ursula has Author role privileges. 8.1 Start the Requirements Management application 1. Open your Firefox web browser and go to Alternatively click RM in the browser bookmarks toolbar. Lab 8 Page 255

256 2. Type ursula for both the User ID and Password and then click Log In. Page 256 Define and Manage Requirements with IBM Rational Requirements Composer

257 3. Click Explore Dashboard to examine the JKE Banking (Requirements Management) project dashboard. Dashboards, Widgets and Filters Dashboards are a web client component intended to provide information about the project status at a glance. They provide the option to drill down to get more complete information. They also represent the integration point for the data provided by all Jazz components. Dashboards have a title and one or more page tabs. Page tabs have one to three columns. Columns contain basic building blocks widgets. Widgets are rectangular regions in dashboards that perform a useful function. The actual content shown in a widget depends on the widget type as well as the way the particular instance has been configured. Widgets can be configured in a number of ways, showing different information as a result. Views Use views in the Project Artifacts page to display requirement artifacts based on specific criteria. You can quickly filter by Tag, Attribute or Folder Views can be saved for reuse by the project team Lab 8 Page 257

258 8.2 Review JKE Banking (Requirements) project's Dashboard Being an executive, Ursula is interested in understanding the overall status of the team's work. A good starting place is the JKE Banking project Dashboard, where different views are available reflecting ongoing project activities. 1. Examine the General tab. Observe the team activities that are going on in the Recent Changes, Reviews and Comments viewlets. Page 258 Define and Manage Requirements with IBM Rational Requirements Composer

259 Widgets displayed on JKE Banking (Requirements) project's General Tab include: Lab 8 Requirements Tracing-Implemented by - Lists all requirements that have corresponding work items in Rational Team Concert. The work items are displayed as children items of the requirement to which they correspond. Note: This widget will only display results when you establish cross-server communication between your Rational Requirements Composer server and your Rational Team Concert server. Requirements Tracing-Validated by - Lists all requirements that have corresponding test cases in Rational Quality Manager. The test cases are displayed as children items of the requirement to which they correspond. Note: This widget will only display results when you establish cross-server communication between your Rational Requirements Composer server and your Rational Quality Manager server. Reviews - Shows reviews in all projects for which you have membership. Click on a review link to access the corresponding review page. Recent Changes - Shows recently modified requirements in all projects for which you have membership. Click on an artifact or resource link to access the corresponding requirement page. My Requirements Projects - Lists requirement projects for which you have membership. Click on a project link to access a list of all artifacts in the project. Comments - Lists recent comments in all projects for which you have membership. Also shown are the artifacts or requirements to which the comments are related. Click on an artifact or requirement in this widget to access the corresponding artifact or requirement page, respectively, or click on a commentator's name to send them a message via . Page 259

260 2. Examine the Development tab. Observe the stories in the New Unassigned Stories, and Done Stories viewlets. Widgets displayed on JKE Banking (Requirements) project's Development Tab include: 3. My Work Item Changes - Shows a feed of work item changes of which the logged-in user is the creator, owner, modifier, or a subscriber. Work Item Changes displayed on JKE Banking (Requirements) project's dashboard are: New Unassigned Stories, Done Stories, Open Requirement Change Requests and Open Impact Analysis Tasks. Work Item Queries - The Work Items widget shows a number of executable queries. Queries can be added from the list appropriate for the current scope of the widget. Return to the General Tab and user rich hover to see additional details this allows an executive or other stakeholders to quickly find lower-level information about a particular item in their dashboard. For example, expand the comment Use Case Specification updated and rich-hover over the Apply for Organizational Funding link to see the details (Primary Text, Location, Tags, Attributes, Comments and Links). Page 260 Define and Manage Requirements with IBM Rational Requirements Composer

261 Click on Apply for Organizational Funding to see the comment below. Business Value This hover technique allows the "casual executive" or other stackholder the ability to quickly scan new content without requiring many button clicks. Lab 8 Page 261

262 Customizing the level of detail In the remainder of this module, you will see how Ursula can get more detailed information quickly on items in the project dashboard. In addition, you will see how she can customize the dashboard utilizing widgets and find various artifacts using her own filters and previously saved filters. 8.3 Customize the Project Dashboard Now, let's take a look at how the project dashboard can easily be modified by adding or customizing a viewlet. Business Value Viewlets provide a user the ability to customize the type of information he/she would like to see in the project dashboard. This functionality is very helpful for agile organizations where people play multiple roles and are required to be aware of content across the lifecycle. 1. As Ursula is a project executive, she has rights to modify the project dashboard. From the drop down menu next to the General tab, select Add Widget Page 262 Define and Manage Requirements with IBM Rational Requirements Composer

263 2. Select the Requirements Management Catalog, then click the Requirements Category on the left, then the Requirements Tracing widget and click Add Widget to add the widget to the dashboard. It will show once it has been added. There are a number of different widgets available take a moment to read through the list to familiarize yourself with the options. Lab 8 Page 263

264 3. Close the Add Widget options by clicking the X in the upper right corner. 4. Select the drop down arrow of the added viewlet in the upper right corner of the widget settings and selecting Settings to configure the Requirements Tracing Widget. Page 264 Define and Manage Requirements with IBM Rational Requirements Composer

265 5. Configure the Requirements Tracing widget by selecting the Project: JKE Banking (Requirements Management), and a Collection: Release 1 Planning and click OK. 6. Select the Tracked By Link Type click OK. Lab 8 Page 265

266 Business Value The widget are customizable and allow one to identify what type of information to display (e.g. I can identify which requirements are related to a release in a collection, what type of relationships I'd like to see such as those requirements which are "implemented" in development as well as the status of the requirements. 7. Select the Requirements Tracing viewlet heading and drag to below the Money that Matters Sample description. Drop the viewlet in its new postion 8. Examine the results of the Requirements Tracing viewlet. You will notice that there are no results as there are no Change Requests or Defects linked to any requirements contained in Release 1 planning collection. Page 266 Define and Manage Requirements with IBM Rational Requirements Composer

267 9. To save the changes to the Project Dashboard,click Save. Though Ursula made these changes to the Project Dashboard, she could have made them just for herself. Each user can create their own personal dashboard and customize. Lab 8 Page 267

268 8.4 Work with Views 1. From the banner Artifacts menu, click Browse Artifacts. 2. Under Filter by Folder section, expand the JKE Business Recovery Matters Project folder, and select the Features folder. Collapse the sidebar Page 268 Define and Manage Requirements with IBM Rational Requirements Composer

269 3. Now select the Filter by Attribute section and click More Attributes. 4. Expand the drop down list Select Attributes to see the different choices available. Lab 8 Page 269

270 5. Close the Select Attribute drop down and click the Name attribute and select the drop down contains to see the different options available. This allows for greater flexibility when filtering the list of artifacts. Leave the selection set to contains. 6. Enter mobile in the Name field and click Apply. Examine the results. Page 270 Define and Manage Requirements with IBM Rational Requirements Composer

271 If this is a filter criteria that will be used often, then the filter can easily be saved and reused. 7. To save it, open the Views section and click the Save View icon. Business Value Saved views are helpful in that they provide a quick way to query regarding pertinent information. The views may be saved and used later to provide quick access to those details. Lab 8 Page 271

272 8. Provide a name for the view, such as Mobile Features and enter a description for the criteria that were used. In this example, make it a Personal view and click OK. Difference between a Personal vs Shared View Personal: May only be viewed by the author of the view and is "coloured" in green Shared: May be leveraged by anyone in the project Business Value Personal views are really helpful to create insightful queries for a specific user. This function can help limit the amount of "clutter" by always creating shared views. Page 272 Define and Manage Requirements with IBM Rational Requirements Composer

273 9. Notice that the personal filter is now in green text and shows up in the list of Views 10. Review the remaining list of Views that are part of this project: Select the filter Elaborated User Stories (Lifecycle Coverage) Business Value Views with lifecycle coverage are very helpful as they provide breath of information outside of requirements and are helpful when evaluating coverage questions: 11. Lab 8 What requirements are implemented? What requirements are tested? Select the Change Column Display Settings icon from the toolbar Page 273

274 12. Experiment with adding and removing columns by selecting one or more columns, then clicking the Add>> or <<Remove buttons, then clicking OK. Business Value The options to choose which columns to display helps provide only those pertinent details related to the artifacts. One may pick the necessary details such as "where did these requirements come from?" This information may be captured in the "Origin" attribute. Page 274 Define and Manage Requirements with IBM Rational Requirements Composer

275 Views Tips You can filter your requirement objects based upon their links to related objects in other tools such as Rational Team Concert (workitems) and Rational Quality Manager (test cases). Under Choose which columns to show, ensure that the Validated By and Implemented By columns are included in your view. Implemented By links display associations with development artifacts. Validated By links display associations with test artifacts. You can even filter based upon these links to show traceability or perform a gap analysis. To filter the displayed requirements based upon these link attributes, go to the Filter by Attribute section, and expand the Linked artifacts filter. Select exists to display only artifacts that have links with the selected values. Select does not exist to display all artifacts that do not have links with the selected values. For the Link type, select the link type that you wish to filter on (Implemented by and/or Validated by). 13. Lab 8 Examine the other shared views such as Features with Unattempted Test Cases, Release 1 Core Features (Lifecycle Coverage), High Priority Features (Gap Analysis), and Satisfy High Priority Goals (Tree View). Page 275

276 Using Saved Views Saved views allow project teams to quickly access those artifacts that are of interest. Here are some example saved views that are part of this project: Page 276 Elaborated User Stories (Lifecycle Coverage): Displays elaborated user stories and their coverage by work items and test cases Features with Unattempted Test Cases: Display features that are linked to test cases in an unattempted state High Priority Features (Gap Analysis): Displays features that are in a "must" business priority but are not linked to a user story via the satisfied by link Release 1 Core Features (Lifecycle Coverage): Displays release 1 features and their coverage by work items and test cases Satisfy High Priority Goals (Tree View): Displays stakeholder needs satisfied by features, features satisfied by user stories, user stories satisfied by or illustrated by other graphical artifacts Define and Manage Requirements with IBM Rational Requirements Composer

277 8.5 Generate a Report from a View Ursula is preparing for a meeting with a customer review board. She would like to take some details of the Stakeholder Needs information with her for this meeting. This can easily be done by selecting the view that will best highlight the desired information and generate a report from that view. Business Value The OOTB reports provide the ability to generate formal documentation in the form of Word documents, HTML, PDF and/or XSL-FO. This content is especially helpful to provide to external stakeholders who may not have access to RRC. 1. Select the Satisfy High Priority Goals (Tree View) view from the Views section. 2. Select Generate a document-style report for this view from the toolbar icon Lab 8 Page 277

278 Business Value Generating reports from views allows a team to quickly create a document with just the details they need. There is no understanding of a report interface required to quickly generate these OOTB reports. Page 278 Define and Manage Requirements with IBM Rational Requirements Composer

279 3. Select Traceability Report and click Next 4. Review the two trace tree artifacts artifacts for the report and click Next Lab 8 Page 279

280 Information The Select the Artifacts dialog allows you to fine tune the objects that will be included in the report. By default, only the artifacts displayed in the view are included in the dialog. However, you may add or remove artifacts to include in the report by selecting the Add... button or Remove button. 5. Enter the following fields in the Create a Report dialog. Page 280 Field Entry Name Stakeholder Needs Report Type Adobe PDF Optimize report generation Sophisticated Formatting Author Name Ursula Company Name JKE Define and Manage Requirements with IBM Rational Requirements Composer

281 Information Depending upon the type of report to be generated, options to include additional data may be selected such as add comments, attributes and requirements. These options provide one the ability to see ancillary although important information in the report. 6. Lab 8 Select Next and Finish to begin the report generation. You can follow the report generation progress at the top of the dialog box Page 281

282 7. Select Finish to generate the report. Page 282 Define and Manage Requirements with IBM Rational Requirements Composer

283 8. Lab 8 Click Close when the generating is complete and examine the report opening it with Adobe Reader program. Page 283

284 Business Value The document export capabilities in Rational Requirements Composer are based on a common component called Rational Reporting for Document Generation (RRDG). This component comes with the example templates that you saw in this exercise. There are RRDG add-ons that will give you further functionality to customize document templates to better meet your reporting needs. 8.6 Summary In this module, you learned that Rational Requirements Composer offers many different views and customization options to allow users to quickly find the desired information. You examined different options for evaluating project status, requirements coverage and lifecycle relationships, by working with dashboards, widgets and filters. Finally, you saw how to export a filtered view as a report. Realized Business Value Page 284 Examine Contents of User Dashboard & Customization IBM Rational Requirements Composer has dashboards that provide quick access to project data. The Project Dashboard is broken into a series of widgets that provide detailed Define and Manage Requirements with IBM Rational Requirements Composer

285 data elements describing pertinent RM details including recent changes, review details, comments, and lifecycle traceability coverage. Additional tabs are available for Change Management which provide details for open workitems, etc... Analysts have many options for flexibility and can customize the dashboard to meet their needs. Tips for Creating & Executing Views Teams may create filters to isolate the kinds of information that is important to them. These type of details may be based on obtaining attribute status information, evaluating the tags, how many requirements are in a release, and understanding coverage by evaluating which requirements have Validated By and or Implemented By Links. Creating saved filters that answer these questions help teams find the information they need quickly. Project Status & Gaps Filters provide quick means to understand project status for executives and product owners. IBM Rational Requirements Composer may provide quick details through filters. These details answer the most looming types of questions including: Lab 8 Where are we in development for this set of requirements? (A trace filter of requirements with implemented by links will answer this question.) Where are we with testing and what are the results of the tests; are there any blockers? (The validated by filter which includes test execution results will answer this question.) Do we have adequate test coverage? (Executing the filter with validated by and filtering to find those requirements which do not have a test case will list requirements that do not have adequate coverage.) Now that I know we have development coverage, how many work items are open (The Development Tab) and status widget provides this type of detail. Generate a Report from a View - IBM Rational Requirements Composer provides several out of the box reports. These reports may be executed against a result set from a saved filter. This functionality is very beneficial for organizations which require hard copies of reports. The report may be generated in the following formats: Microsoft Word, Adobe PDF, and HTML. This functionality allows teams to Page 285

286 provide these details to a stakeholder whom may not have access to the tool. Page 286 Define and Manage Requirements with IBM Rational Requirements Composer

287 Appendix A Troubleshooting Include this section IF APPLICABLE. Remove this section if you do not need it subsequent appendices will automatically renumber. Additional appendices if applicable: Appendix B FAQs Appendix C Sources Appendix Page 287

288 Appendix B Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo , Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Page 288 Define and Manage Requirements with IBM Rational Requirements Composer

289 Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. All references to fictitious companies or individuals are used for illustration purposes only. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Appendix Page 289

290 Appendix C Trademarks and copyrights The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM AIX CICS ClearCase ClearQuest Cloudscape Cube Views DB2 developerworks DRDA IMS IMS/ESA Informix Lotus Lotus Workflow MQSeries OmniFind Rational Redbooks Red Brick RequisitePro System i System z Tivoli WebSphere Workplace System p Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. See Java Guidelines Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce. Other company, product and service names may be trademarks or service marks of others. Page 290 Define and Manage Requirements with IBM Rational Requirements Composer

291 NOTES

292 NOTES

293 Copyright IBM Corporation 2011 The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. This information is based on current IBM product plans and strategy, which are subject to change by IBM without notice. Product release dates and/or capabilities referenced in these materials may change at any time at IBM s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at Copyright and trademark information at ibm.com/legal/copytrade.shtml Other company, product and service names may be trademarks or service marks of others.