Tip:
Highlight text to annotate it
X
Hi. This video will show you the main features of the Rational Engineering Lifecycle Manager
Views screen.
Views help teams visualize work—requirements, work items, design models, and test cases--
to be completed for a product release. The visibility of the different parts, such as
requirements and test cases, help teams remain on-task to meet product goals by specific
milestones.
Typically, an administrator or IBM service representative creates custom views for a
team. Custom views that have been shared are available in the Shared Views screen. If custom
views were not created, your team will use the views in the Sample folder, available
in the Shared Views screen.
In this tour, we'll work with views in the Sample folder, which contains 7 sample views.
First let’s open the Traceability from Task to Test Case view, which is a predefined query
that gathers artifacts with a relationship to a task and then organizes the artifacts
in a workflow from the task through the test case.
The arrows show the relationships between Task 616 and the Team Concert tasks, the DOORS
requirements, the Rhapsody design model element, and the Quality Manager test cases.
Let’s select Task 619, ASIL determination. Notice that the artifact is highlighted with
blue while the task and requirements that have a relationship to it are outlined in
yellow. (pnt w/arrows)
Let’s hover over Task 619 and click Show Detail. You can see all of the details for
the work item, including subscribers, dependencies, blocks, and parent or child work items, which
are the linked data. To open the work item in the native tool, click here or here. Notice
that Task 619 has a relationship to Task 616. Task 619 is a child of parent Task 616.
Now let’s hover over requirement FSR13 and click Show Detail to view the DOORS requirement
description. You can read the heading, text, and many other attributes. The requirement
shows that there is one link from DOORS out to another artifact. The requirement has relationship
to Task 619. To read the Task 619 work item in Team Concert, click the link.
When you click an artifact , you can act on it by choosing an action in the
menu. You can: * Open the artifact in its native tool (focus
over this) * Run the query that gathers the information
for that artifact. * Start an analysis of the artifact to view
other artifacts that have a relationship to the target.
Actions that display at the bottom of the menu run queries that populate views.
In any view, use the toolbar in the upper right to search for text, generate a report,
or edit the view.
(Back to Shared Views) Different views show you different artifacts. The gathered artifacts
are driven by the query that is included in each view, and then organized according to
the defined layout. Again using Traceability from Task to Test Case, let’s take a look
at the query. This and all queries are written using SPARQL, which is the query language
for Linked Lifecycle Data. You must know the SPARQL query language to create or modify
queries. Traceability from Task to Test Case contains a query that gathers a Team Concert
work item. The Parameter value is set to find work item 616.
The view layout is set to organize the data in a grid layout, with text organized according
to artifact type and other layout definitions.
(Back to Shared Views) Now let’s create a view. Susan needs a view for work item 533
so she can see the task breakdown for that work item. Click Create View. Type a view
name, in this case, Susan’s WI 533, task breakdown. Select a view template, in this
case, Task breakdown. Select a folder to copy the template to, in this case, My Views.
The Parameter value is the number of the work item, in this case, 533.
The new view is available in My Views. Susan has 4 views. She can share one view by clicking
Move or Copy Selected View, and then choosing to move or copy the view to the Shared Views
folder to make it available to her team. She can share multiple views by multi-selecting
check boxes and then clicking Move or Copy Selected Views here.
Susan might decide to create a folder and move the appropriate views into the folder.
For example, Susan could create a folder called SuperCar 2.0 views, which holds all of the
views she creates for the SuperCar 2.0 product that she’s working on. Then she can move
the views into the folder. Note that you can move folders into folders and delete folders
and all of the content. If you want to delete a folder but keep one or more views in the
folder, be sure to move the views before deleting the folder.
Thank you for watching this video.