In this article, we’ll build our first view. Later we’ll make it look visually appealing and introduce some dynamic visualization but we’ll start by simply reporting the data we are interested in and see just how quickly and easily views can be designed.

In this series of articles, we’ll be exploring how to build views in IBM Engineering Lifecycle Optimization – Engineering Insights (ENI) that allow you to visualize and analyze your engineering data in a powerful, dynamic way. We’ll see just how quickly and easily these views can be built, starting with some very basic concepts before […]

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.

Rhapsody Model Manager (RMM) provides two reporting schemas: Rhapsody Model Schema Provides some basic information about the model stored in RMM If you intend a more detailed report then you should design and run the report against the Rhapsody desktop client Rhapsody Traceability Statistics Schema Provides statistical information of traceability from model elements in RMM […]

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

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

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

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

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

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