Reporting on requirements

Essentials of IBM® Rational® DOORS Next Generation V4.01
Reporting on requirements 1© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
© Copyright IBM Corporation 2013
Reporting on requirements
Contents
Module overview -2
Document-style reports -3
Print options from within the artifact -4
Document-style reports -6
Application reports -7
Rational Reporting for Document Generation -8
Predefined document-style reports -9
Creating a document-style report -11
Opening a saved document-style report -15
Rational Reporting for Development Intelligence-
18
Rational Reporting for Development Intelligence-
19
Flow of information for data warehouse reporting
-20
Pre-defined development intelligence reports -21
Viewing reports -22
Coverage of Requirements by Development
Items -24
Lab: Generating document-style reports -31
Review -32
Module summary -33

2 © Copyright IBM Corporation 2013
Module overview
After you complete this module, you should be able to
do these tasks :
 Generate requirements report documents
 Explain the reporting capability that is available through
IBM® Rational® Reporting for Development Intelligence

Topics
> = Current topic
> Print an artifact
 Document-style reports
 Rational Reporting for
Development Intelligence

Print options from within the artifact
Artifacts have pre-set print options.
In the case of a module, printing is
based on the information visible in the
content, which because of filters and
display options may or may not be
complete.
When printing, you have the options
to include comments on artifacts, the
columns displayed which include
attributes and link information

Example of printing a module: book layout

Topics
> = Current topic
 Print an artifact
> Document-style reports
 Rational Reporting for

Application reports
With the Requirements Management (RM) application for Jazz™ solutions ,
you can generate document-style reports or view report data on dashboards.
Produce document-style
reports
Produce dashboard-based
reports that pull data from
a data warehouse
You can create predefined reports by using
the report templates that are included with the
Requirements Management (RM)
application.
The RM application currently includes
predefined reports in two formats:
•IBM® Rational® Reporting for Document
Generation uses a runtime version of IBM®
Rational® Publishing Engine to produce
document-based reports.
•Rational Reporting for Development
Intelligence uses business-intelligence
technology to produce dashboard-based
reports that pull data from a data warehouse.

Rational Reporting for Document Generation
IBM® Rational® Reporting
for Document Generation
uses a runtime version
of IBM® Rational® Publishing Engine to produce document-
style reports.
Document-style reports serve these purposes:
 Capture detailed, point-in-time information
 Capture specifications that are handed off to a design team
 Can be contractual deliverables or the basis of a contractual relationship
To customize these reports, you must have a licensed version of
Rational Publishing Engine.

Predefined document-style reports
The RM application includes a set of predefined document-style reports
that you can run.
Name Description
Use-Case Diagram Specification Shows organized requirements by use case diagram
Requirements Specification Shows both functional requirements, such as use cases,
and nonfunctional requirements, such as supplementary
requirements
User Interface Specification
(Screen Flow Diagram, Sketches,
and Storyboards)
Shows the artifact description and artifact type in
addition to pictures of the specified graphical artifacts
Traceability Reports Shows a requirement-centered view of links to work
items that implement the requirement and test suites
that validate the requirements
Audit History Shows a history of changes to the selected artifacts
Reviews Provides a detailed summary of the current state of the
selected reviews and their associated artifacts
This slide lists the predefined document-style
reports that you can generate.
To customize a report, you must have a
licensed version of Rational Publishing
Engine.

Example: Requirements specification report
Report:
Release 1 Features, with
attributes included
Optimized for
performance
Optimized for
sophisticated
formatting

Creating a document-style report
Filter the artifacts on the Artifacts page, and
then click the Generate a document-style
report for this view icon.
The report is generated based on the
artifacts in this view.

Creating a document-style report (continued)
Add or remove the artifacts to
include in the report.
Select the type of report.
In the Report wizard, you can customize the
list of reports to match your organizational
standards.
Custom report templates that are generated in
Rational Publishing Engine can be installed
on the server. Then, the templates are
available to all users when they run the
Report wizard. To create custom report
templates in Rational Publishing Engine, you
must have a Rational Publishing Engine
license.

Enter a name for the report, and
select a file type.
Optimize generation for performance or
formatting.
Customize the report to include information
such as the author, company, footer text,
attributes, comments, or company logo.
You can generate reports in the following
formats: Adobe® PDF, Microsoft® Word,
HTML, and XSL Formatting Objects (XSL-
FO).
Note: XSL-FO is a standard unified
presentation language for documents. You
can use this format with post-processors to
generate printable or renderable output. You
can also use this format with scripts to post-
process your results.

You can save the report as an artifact in the
project. Specify the artifact type, folder, and
tags.
Click Finish to generate
the report.

Opening a saved document-style report
When you open a document-style report that
you saved as an artifact in the project, you
are prompted to open it in an external
application.

Generating document-style reports in other ways
You can generate a
report document from a
saved view.
You can generate a
report document from a
collection.
You can also use Rational Publishing Engine
to generate report documents.

Generating a document-style report from a review
You can generate a Reviews report
from within a review.

Topics
> = Current topic
 Print an artifact
 Document based reports
> Rational Reporting for

Rational Reporting for Development Intelligence
Rational Reporting for
uses business-intelligence
technology to produce reports that pull data from a data
warehouse.
Development intelligence reports have these characteristics:
 They are primarily graphical, such as pie charts, graphs, and scorecards.
 They communicate status, monitor progress, diagnose problems, identify
corrective actions, and more.
 They are a decision-support tool for managing projects and programs.
The report author can customize report templates by using the
IBM® Cognos® Report Studio or IBM® Cognos® Query Studio.
Rational Reporting for Development Intelligence must be
installed and configured separately by an administrator.
For more information about how to
customize Rational Reporting for
Development Intelligence reports, see these
resources:
•Reporting tutorials in the information center
at
http://pic.dhe.ibm.com/infocenter/clmhelp/v4
r0/index.jsp?nav=%2F2_5
•Demonstration videos on YouTube at
http://www.youtube.com/playlist?list=PL41F
90AA10F4744B8

Flow of information for data warehouse reporting
You can use the data in the data warehouse to report on themes, trends,
aggregations, and other relationships among data.
Data is collected from the applications of the Rational solution for
Collaborative Lifecycle Management (CLM). Then, the data is then stored in
the data warehouse, where data can be transformed to represent various
relationships.

Pre-defined development intelligence reports
Name Description
Coverage of Requirements by
Development Items
Shows pie and bar charts that include percentages and absolute
numbers of requirements that are linked to development items.
Test Cases
Shows pie and bar charts that include percentages and absolute
numbers of requirements that are linked to test cases. Provides a
report that shows a list of not-linked and linked requirements and
what the linked requirements link to.
Test Case Trend
Shows the trend of test coverage over time.
Requirement Blocked by Open
Defects
Shows the requirements that use the affected_by link to link to
defects. Also shows the names, severity, and status of the defects.
Requirements Distribution Shows bar charts of requirements that are grouped by status and
priority.
Requirements Execution
Results
Shows the requirements, test plans, test cases, last test execution
results, and defects that are linked to results.
Requirements Traceability Shows requirements trace to development items, from
requirements to test cases, to test results, to defects.
Drill-through reports are detailed list reports
that can be accessed from the graphical
reports. These drill-through reports are
available:
Requirements List (Development Item
Coverage)
Shows a list of non-linked and linked
requirements that is based on selected type
and coverage parameters. The information
that is shown includes the tag, name, type,
status, priority, and customer priority.
Requirement List (Priority Types)
Shows a list of non-linked and linked
requirements that is based on selected priority
and type parameters. The information that is
shown includes the ID, tag, name, type,
priority, stability, status, and difficulty.
Requirement List (Status Type)
Shows a detailed list of work items that is
based on selected status and type parameters.
The information that is shown includes the
tag, name, type, status, priority, and customer
priority.
Requirement List (Test Coverage)
Shows a list of requirements that is based on
selected requirement type and test coverage
parameters. The information that is shown
includes the tag, name, type, status, priority,
and customer priority.

Viewing reports
After you start Rational Reporting for Development
Intelligence, click Sample Report Definitions, click
the RM folder, and then click Data Warehouse
Reports.

Viewing reports (continued)
Click a report to run and view it.
Drill-through reports are detailed
reports that are usually invoked by
data warehouse reports. You can
also run the reports independently.
This slide shows the list of data warehouse
reports that are in the RM application. Drill-
through reports are detailed reports that are
usually invoked by data warehouse reports.
However, you can run the reports
independently.
Many reports provide parameter values that
you can select to determine which artifacts
are included in the report. For example, in
some reports, if you adjust the Project,
Priority, and Type values, you can filter the
information in your report. In addition, in
many reports you can click graphics to
display more information by opening a drill-
through report.
You run the report from the IBM® Cognos®
Connection.

Coverage of Requirements by Development Items
Click the “Not covered” section of the
graphic to see a detailed list of uncovered
requirements.
Select parameters for the report.
Reports are displayed in IBM® Cognos®
Viewer.
Requests, such as development items, must
be linked to most requirements to ensure that
requirements can be traced to development
artifacts. To verify that requests are linked to
requirements, you can view the pie chart to
see the percentage of requirements that are
covered by links to development items and
the percentage of requirements that are not
covered, or have no associated requests. If
requirements are not linked to requests,
investigate to find out why, and create links if
necessary.

Navigate to list a report of uncovered requirements
Reports include a description
of what they show.

Coverage of Requirements by Test Cases
Normally, most requirements are linked to
defined test cases. To verify that most
requirements are linked to test cases, view the
pie chart to see the percentage of
requirements that are covered by test cases,
and the percentage of requirements that are
not covered, or that have no associated test
cases. If requirements do not have test cases,
investigate to find out why, and create test
cases if necessary.
Watch for requirements that are not linked to
test cases.

Requirements Blocked by Open Defects
This report shows the requirements of a
project, focuses on an artifact type, and list
the linked open defects. You can filter by
severity to find blocking or major defects.

Requirements Distribution
This report shows the number of
requirements for each status, priority, and
stability. Usually as the project progresses,
the number in the initial statuses, such as
"Proposed," decreases, and the number in
later statuses, such as "Incorporated,"
increases. Otherwise, requirements might not
be satisfied. Look for a reasonable
distribution by priority and stability. Not
everything can be high priority. Too much
"Low" stability might indicate a problem.

Requirements Execution Results
This report shows test execution results that
are traced from test cases in IBM®
Rational® Quality Manager and defects in
IBM® Rational Team Concert™.

Requirements Traceability
This report shows the requirements of a
project and a type that link to open
development items. The report shows the
name and type of each development item. To
navigate through the artifacts, click the
names of the requirements and development
items.

Lab: Generating document-style reports
After you finish this lab, you
should be able to do these
tasks:
 Generating a document-style
report for a Module
 Print a report based on a view

Review
 How do you generate a
document-style report?
 What are the predefined
document-style reports in the
RM application?
 How do the reports that
Rational Reporting for
produces differ from the
reports that Rational
Reporting for Document
Generation produces?

Module summary
In this module, you learned how to do these tasks :
 Generate requirements report documents
 Explain the reporting capability that is available through
Rational Reporting for Development Intelligence

Reporting on requirements

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (20)

Semelhante a Reporting on requirements

Semelhante a Reporting on requirements (20)

Mais de IBM Rational software

Mais de IBM Rational software (20)

Último

Último (20)

Reporting on requirements