Blogs about Jazz

Blogs >

Jazz Team Blog

Rational Publishing Engine

What’s new in IBM Engineering Reporting v7.0.1?

Tags: , , , , , ,

IBM Engineering (ELM) delivered their second release this year, only a few months after ELM 7.0. Since 7.0.1 has come so soon after 7.0, we recommend that anyone planning to upgrade should go straight to 7.0.1. Even though this was a relatively short release, there are a number of valuable enhancements delivered. This blog covers […]

What’s New in IBM Engineering Reporting v7.0

In this post, I will use the new names of IBM Engineering Lifecycle Management (ELM) 7.0, previously known as the IBM Continuous Engineering solution. You can read more about the renaming activity in the blog post: Renaming the IBM Continuous Engineering Portfolio. In the details below, you will see the new names along with old […]

What’s new in Rhapsody Model Manager 7.0 and Rhapsody 9.0

The rising complexity of the products and systems being developed globally is driving engineering teams to seek effective model-based engineering practices, including model-based systems engineering (MBSE). Rising compliance demands such as ISO-26262/ASPICE in automotive and DO-178 C and ARP 4754 for aerospace and defense are driving the need for rigorous change management and lifecycle traceability. […]

What’s new in IBM Engineering Lifecycle Management V7.0

After more than 1,800 plan items, stories and tasks across all of our product and application teams, V7.0 is nearly here. So what’s new? First, the name is new. As we mentioned last year (Renaming the IBM Continuous Engineering Portfolio and Insights and scale: Redefining Enterprise Lifecycle Management solutions) we have renamed our Jazz-based solutions to be […]

Data driven approach for generating multiple output documents with IBM Engineering Lifecycle Optimization – Publishing

This article covers how to design a template using IBM Engineering Lifecycle Optimization – Publishing (PUB) Document Studio to report for multiple user input values. Instead of having multiple document specification (.dsx) files for each user input and running them using a batch file, we are going to use a single document specification file that produces multiple output documents.

Reporting on Linked Lifecycle Data with IBM Engineering Lifecycle Optimization – Publishing | Part Seven – Reporting on JRS

Reporting on a reporting tool. Initially, it sounds like an odd concept right? It’s actually a very useful capability. Jazz Reporting Services Report Builder (JRS) provides a web-based UI for designing reports. These reports are primarily focused on presenting live data, typically on dashboards, in the form of tables or graphs. While these can be […]

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

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 data […]

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

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 types. […]

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

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 links, […]

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

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 other […]

Older Posts >