Engineering Systems Design Rhapsody – Model Manager

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

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

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

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

If you’ve been following our progress on the IBM Engineering Lifecycle Management v7.0 release here on jazz.net you can see that we are in the final stages of our release candidate milestones. Release candidates are functionally complete, meaning all the features targeted for v7.0 have been delivered to the release and we have entered the […]

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