Blogs about Jazz

Blogs >

Jazz Team Blog

2020 January

Reporting on Linked Lifecycle Data with IBM Engineering Lifecycle Optimization – Publishing | Part Six – Reporting from Engineering Test Management

Introduction In this posting, we’ll continue the series by seeing how we start a traceability report from IBM Engineering Test Management (ETM). ETM has two reportable APIs: OSLCV2 Supports 15 concepts (Test Plan, Test Case, etc.) Supports POX (redirects to reportable REST) Reportable REST Supports 48 concepts No POX support – links for schemas and […]

Reporting on Linked Lifecycle Data with IBM Engineering Lifecycle Optimization – Publishing | Part Five – Reporting from Engineering Workflow Management

Introduction In the previous blog postings we’ve covered how to report on links from requirements to models, test cases and work items, and from model elements to test cases, work items, and requirements. In this article, we’ll cover how to start the report from a work item and obtain the links to those other artifact […]

Reporting on Linked Lifecycle Data with IBM Engineering Lifecycle Optimization – Publishing | Part Four – Reporting from Rhapsody Model Manager

Introduction In the previous article, we covered how to report on links from requirements to model elements in Rhapsody Model Manager as well as test cases and work items. In this article, we’ll cover how to create a template that reports on the model and gets the links to other artifacts. Once you have the […]

Reporting on Linked Lifecycle Data with IBM Engineering Lifecycle Optimization – Publishing | Part Three – Reporting from DOORS Next

Introduction In this article, we’ll build our first template. We will start by reporting on a single requirement in IBM Engineering Requirements Management – DOORS Next. In a real template, we would usually report on something like all the requirements in a module, but our focus here is on linked lifecycle data. We’ll see how […]

Reporting on Linked Lifecycle Data with IBM Engineering Lifecycle Optimization – Publishing | Part Two – Using a REST Client to Interrogate Resources

Introduction When building templates it is often useful to be able to send a GET request to a data source, in the same way, that PUB does. This is often the only way you can find out how linked data actually appears in its reportable form, and guides the building of your template. To do […]

Reporting on Linked Lifecycle Data with IBM Engineering Lifecycle Optimization – Publishing | Part One – Introduction

Introduction This is the first of a series of articles covering how to author reports in IBM Engineering Lifecycle Optimization – Publishing (PUB) Document Studio that report specifically on linked data, for example, requirements satisfied by model elements, rather than a detailed report on a single data source. A POX on It! Most of the […]