Blogs about Jazz

Blogs >

Jazz Team Blog

Design Management

IBM Engineering Lifecycle Management v7.0 is here!

We are extremely excited to announce the availability of the IBM Engineering Lifecycle Management (ELM) 7.0 solution on jazz.net! What you’ll be seeing is the result of months worth of person-hours, spanning some 1,800 plan items, stories, and tasks across the entire ELM product portfolio. With the general availability release of ELM 7.0, we’ve also […]

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

Reporting on Linked Lifecycle Data with IBM Engineering Lifecycle Optimization – Publishing. Part Eight – Reporting on RMM Traceability Statistics

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

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

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

Reporting on Linked Lifecycle Data with IBM Engineering Lifecycle Optimization – Publishing | Part One – 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 ELM […]

Work with IBM to influence the Engineering Lifecycle Management User Experience!

Do you want to explore early design ideas and influence the direction of the IBM Engineering Lifecycle Management (ELM) solution? We have just the opportunity for you! The ELM UX team is running feedback sessions over the coming weeks and months and we hope you will join us as we design exciting ways to positively […]

Older Posts >