Categories
Requirements

Renaming the IBM Continuous Engineering Portfolio

Renaming the IBM Continuous Engineering Portfolio

Imran Hashmi Canadian Hub for Requirements Management

The IBM Continuous Engineering and Collaborative Lifecycle Management solutions have a rich heritage in helping teams around the world to develop products and applications faster, in a more dependable way, and at a higher quality. Over time we have come to see that the biggest challenges — and where we can offer the most help — are with teams addressing their engineering lifecycle: software engineering, certainly, and also systems engineering and the many other engineering disciplines that are necessary to create the amazing products and systems that power our economy today.  We are addressing Engineering Lifecycle Management, and we are renaming our products to make that more obvious.

Why are we renaming the products?

Two reasons: to make it easier to identify each product’s primary function by its name, and to communicate our focus and investment in helping teams to implement effective Engineering Lifecycle Management.

When will I see the new names?

The products are being renamed in a phased manner. Web pages will start referencing the new names in the coming months.  The v6.0.6.1 products and product documentation (released today!) retain the old names, and we intend to adopt the new names in the follow-on release.

Why are we renaming the products in a phased manner?

This phased approach gives you (and us!) time to adjust to the new names.  For example, if you have written your own documentation or training materials for your customers, you can update and use them with the Jazz v6.0.6.x release family while you make plans for more significant changes when you adopt the follow-on release.

What products are being renamed?

Here are the major changes:

Imran Hashmi Canadian Hub for Requirements Management
IBM Engineering Lifecycle Management (ELM) – formerly CLM and CE,
IBM Engineering Requirements Management DOORS Family (DOORS) – formerly Rational DOORS
IBM Engineering Requirements Management DOORS Next (DOORS Next) – formerly Rational DOORS Next Generation (DNG)
IBM Engineering Requirements Quality Assistant (RQA) – formerly IBM Requirements Quality Assistant (RQA)
IBM Engineering Workflow Management (EWM) – formerly Rational Team Concert (RTC)
IBM Engineering Test Management (ETM) – formerly Rational Quality Manager (RQM)
IBM Engineering Systems Design Rhapsody (Rhapsody) – formerly Rational Rhapsody
IBM Engineering Systems Design Rhapsody – Design Manager (RDM) – formerly Rational Design Manager (RDM)
IBM Engineering Systems Design Rhapsody – Model Manager (RMM) – formerly Rational Model Manager (RMM)
IBM Engineering Lifecycle Optimization (ELO) – new umbrella name for offerings that surround and extend ELM
IBM Engineering Lifecycle Optimization – Engineering Insights (ENI) – formerly Rational Engineering Lifecycle Manager (RELM)
IBM Engineering Lifecycle Optimization – Publishing (PUB) – formerly Rational Publishing Engine (RPE)
IBM Engineering Lifecycle Optimization – Method Composer (MEC) – formerly Rational Method Composer (RMC)
IBM Engineering Lifeycle Optimization – Integration Adapters (IA-product) – formerly Rational Lifecycle Integration Adapters (RLIA for product)

Are the products changing when the names change?

They are the same market-leading engineering lifecycle management products. Even the part numbers are the same. As you would expect, future enhancements will be introduced in releases of the newly-named products.

For more information, please see the FAQ for Engineering Portfolio Renaming for Customers.

We recognize that product development is getting more complex while the product lifecycle is shrinking, customers are becoming more technically savvy and demanding, and compliance and regulatory requirements are growing. We want to make sure our product naming does not compound this complexity, and we believe this renaming will promote simplicity and clarity over time.

No tags for this post.
Categories
Requirements

What is IBM ELM/ALM?

What is IBM ELM/ALM?

IBM® Engineering Lifecycle Management (ELM) integrates ELM products to provide a complete set of applications for software or systems development. ELM includes IBM Engineering Requirements Management DOORS® Next (DOORS Next), IBM Engineering Requirements Management DOORS (DOORS), IBM Engineering Workflow Management (EWM), and IBM Engineering Test Management (ETM), IBM Engineering Systems Design Rhapsody® – Model Manager (RMM), and IBM Engineering Lifecycle Optimization – Engineering Insights (ENI) with Jazz™ Team Server. This solution is designed for requirements analysts, developers, systems engineers, and testers. 

The following diagram shows the development lifecycle that the solutions support. To see overviews of the applications that are represented in the image, click the boxes. For example, clickValidate and verify to see an overview of ETM.

This image shows the functions in the development lifecycle supported by the solutions.

To support the development lifecycle, ELM products let you link artifacts across applications, as shown in the following figure and examples: Figure 1. ELM connects analysts, developers, and testers

This graphic shows the relationships between ELM disciplines, as described by the following examples.

Requirements:

  • Requirements are implemented by iteration plans and validated by test plans.
  • Requirements are elicited, documented, elaborated, and validated by analysts. Their implementation progress is tracked in work items, and their correctness is validated by test cases.

Implementation:

  • Project managers and development managers use iteration plans to implement requirements in the context of a development schedule.
  • Team leads plan the iterations using iteration plans, where the work is divided further into tasks.
  • Developers work on defects that are submitted by testers as a result of test execution.

Testing:

  • The test team links requirements to test plans and test cases. 
  • Testers link test cases to work items to ensure coverage of the implementation.
  • Testers run test cases and submit defects for test failures.

ELM integrates the work of analysts, developers, and testers by providing the following cross-application features:

  • Link between artifacts across applications: For example, you can link test cases to work items and requirements.
  • Hover over a link to see details about the link target: For example, testers can monitor the status of a defect that they reported to the development team.
  • Track status across projects by adding widgets from different applications to a dashboard: For example, you can add a widget that shows the defects that are blocking testers.

Jazz Team Server

The Jazz Team Server provides the foundational services, such as user management and license management, that enable the ELM applications to work together as a single logical server. In this way, the Jazz Team Server serves as an integration hub for the applications. After you install the ELMproducts, you install product license keys into the Jazz Team Server to permit access to the capabilities provided by the applications. For details about the topologies supported for new or upgraded installations, see Planning the deployment and installation.

Products and applications

For a detailed overview of the products and applications in ELM, see the following topics:

Part of the Jazz community 

ELM products are developed transparently on the open and extensible Jazz platform. On Jazz.net, you can download the products and their milestones, track development schedules, join discussion forums, open enhancement requests, and interact with the product developers. To learn more about the products, see the developer-written articles in the Jazz.net library or the topics about complex deployment scenarios on the Deployment wiki.

More information

To learn more about ELM, see these resources: 

  • ELM on Jazz.net: Learn about the new features, read the release notes, and download the binaries to install the solution.
  • ELM videos: These videos highlight the configuration management capabilities of the solution. 
  • ELM sandbox: You can try a series of exercises in an online sandbox to learn more about a broad range of capabilities across the application development lifecycle.
  • ELM on Jazz.net: Learn about the new features, read the release notes, and download the binaries to install the solution.
  • ELM demo series: This set of recorded demonstrations offers a full lifecycle walk-through, and videos that highlight specific industry needs, in-depth tools, and practice topics.
Categories
Requirements

Make large public works projects run smoothly

Make large public works projects run smoothly

Rail Projects Victoria uses IBM requirements management SaaS solution in their massive Metro Tunnel Project

By Thomas Hollowell | 3 minute read | September 11, 2019

Imran Hashmi Canadian Hub for Requirements Management

IBM’s requirements management solutions have been used for years to help organizations build software and hardware systems. And now, an IBM software as a service (SaaS) solution helps government and engineering/constructions projects to run smoothly. One particularly high-profile application of this solution is the Melbourne Metro Tunnel Project.

The largest investment ever in public transport in Melbourne, Australia

Rail Projects Victoria (RPV) uses IBM’s technology to simplify the management of the delivery of the Metro Tunnel Project. This AUD 11 billion (11 billion Australian dollars) initiative creates a new underground pathway for trains to accommodate over 500,000 new passengers during peak hours each week. Construction involves the cooperation and collaboration of many different public and private organizations.

IBM’s DOORS® Next requirements management SaaS solution was implemented by the RPV team to provide a single, collaborative, secure environment to capture, trace, analyze and manage project requirements in real-time. And as it does so, it preserves the data privacy and intellectual property of the various organizations delivering the project.

Collaborators no longer need to gather updates from different companies’ systems. Instead, they use the IBM solution to obtain a single, reliable source of information. It’s securely controlled and selectively shared with each organization as needed. This improves project predictability, minimizes rework and increases communication.

IBM business partners in Australia—including Acmena—are supporting this project. Acmena, is supporting this project, and is using this solution as a platform to share requirements on large public works projects in New Zealand and Australia. Recently several large engineering/construction firms in the US and Canada have also turned to IBM’s requirements management SaaS solution for managing large public construction projects. One firm is a consortium developing rail and light rail transit infrastructure in Canada. Another client is one of the top five largest contractors in North America.

Read how Rail Project Victoria is staying on track with IBM

Three reasons construction firms choose IBM SaaS requirements management

  1. Increasing competition and greater project complexity are driving architectural, engineering and construction (AEC) firms and public entities to seek ways to reduce costs and improve project performance. For AEC firms, requirements are the basis for project planning, risk management and acceptance testing. They define what the stakeholders need and what the product must meet in order to satisfy those needs.
  2. The project development process often lacks identification, management and traceability of the requirements. IBM’s requirements management solution, DOORS Next, helps solve these gaps.
  3. Requirements management tools are not as prevalent in the construction industry as they are in the system and software world. The large number of diverse stakeholders in these large construction projects significantly increases complexity and makes coordination of effort difficult – hence the need for a requirements management solution to keep everyone on the same page.

Why software as a service?

Typically, an organization chooses a SaaS solution for a variety of reasons. These include the desire to lower overall cost, increase efficiency, improve productivity or enable flexibility. However, large engineering and construction projects are unique in that they often involve dozens of different organizations. A cloud-based solution allows these companies to collaborate without compromising corporate firewalls. Organizations can scale up and down depending on their involvement in various stages of the project. They don’t need to make a capital investment in hardware and software.

Learn more about how the IBM DOORS Next requirements management solution can help you keep your large construction projects on track.

Read these articles about the Rail Projects Victoria (RPV) project:

Rail Projects Victoria: Requirements Management

IBM keeping the AU$11 billion metro tunnel on track

Vic Metro Tunnel Project employs IBM tech

IBM and Rail Projects Victoria keeping the $11B Metro Tunnel on track

No tags for this post.
Categories
Requirements

Systems Engineering for the Internet of Things

Systems Engineering for the Internet of Things

Today’s connected world is increasing product complexity, putting systems engineers at the heart of a new challenge to deliver products faster and with improved quality. IBM Engineering offers a variety of cloud-based tools to help teams better collaborate, improve requirements, manage workflow and testing. Learn more about systems engineering lifecycle solutions from IBM Watson IoT: https://ibm.co/ibmelm #systemsengineering #IBM #WatsonIoT

No tags for this post.
Categories
Requirements

What’s new in IBM Engineering Lifecycle Management 7.0.2

by Daniel Moul

Good engineering practices, tools and people give organizations a competitive edge, enabling teams to be more productive with fewer errors while developing increasingly complex products and systems. Our focus for 7.0.2 has been increasing the productivity of practitioners using the IBM Engineering Lifecycle Management solution. Below are some of the high points.

Making use of traceability for change impact analysis and reporting

  • Simplified linking: drag-drop or copy-paste links within and between requirements, tests, and work items
  • Simplified linking: more intuitive work item linking and navigation in the context of global configurations; by mapping relationships from the Global Config to a release defined in Engineering Workflow Management (EWM), and asserting release-to-release relationships in EWM, practitioners now see all relevant work items in a particular GC context, navigation from a work item to a versioned requirement, test or model element, and practitioners can report on these relationships using Report Builder and Engineering Insights.
  • Report on models managed by Rhapsody Model Manager (RMM) and traceability with other artifacts in the engineering lifecycle (beta).
  • Report on files managed by the Jazz SCM (part of EWM) and traceability with other artifacts in the engineering lifecycle (beta).

New efficiencies for teams adopting IBM Engineering to improve Automotive SPICE maturity and functional safety (ISO 26262)

  • New ISO 26262 content in IBM Automotive Compliance.
  • New token license enforcement, simplifying license compliance.

Awareness of change for requirements engineers

  • A new requirements comparison report is available for practitioners in the configuration compare/deliver workflows. The Reportable REST API was enhanced to include change information, and a PUB template provided, which you can use to create your own reports that make use of change information.
  • Module audit history is visible in the web.

New efficiencies for V&V test teams

  • Make use of custom execution states in test step results, new options to include more information when duplicating execution records, and improved offline text execution, including use of execution variables.
  • Try out the technical preview of ETM multi-component support, which provides easier test reuse (a test plan can include test assets from multiple components) and also simplifies creating affinity between requirements and tests in similarly-scoped components.
  • We tested Engineering Test Management with 20M artifacts and 2500 global configuration contributions managed by one ETM server. Details will be in the usual place on the Deployment wiki.

New efficiencies for team members using work items to plan and track their work

  • Beyond the simplified linking mentioned above, large attachments can be stored in an external content registry, including a file system or WebDAV server like Artifactory.

New efficiencies for developers using the Jazz SCM

  • Massive speed-up when updating the sandbox in Jazz and Jenkins builds using optimized incremental loads when there are no significant changes, now also possible when using load rules (we saw 96% speed-up in our development environment: from 27 minutes to less than one minute in one test; your mileage may vary).

New efficiencies for teams using EWM and Git

  • When using GitHub and a Chrome browser, it’s easier to link a commit or pull request with a work item using a new graphical picker.
  • A new Git diagnostic page makes integration issues visible and provides guidance for EWM administrators to resolve them.

New efficiencies in reporting and document generation

  • Report Builder terminology changes make it easier for practitioners to develop their own mental model about how reporting works.
  • It’s now easier to find the report you’re looking for in Report Builder using different report groupings.
  • Column headings do not scroll with the data, making it easier to relate columns of data and their meaning when working with tables that have many rows.
  • For Publishing Document Builder report administrators, creating connections are easier, and it’s easier to find connections when associating them with data sources.

New efficiencies when setting an owner or subscriber

  • In most places the people picker dialog box uses heuristics to anticipate the people you are likely to pick, reducing users’ overheads.

New efficiencies monitoring, starting and stopping applications

  • New REST APIs provide readiness and liveness probes, simplifying startup and heartbeat monitoring.
  • We did work to streamline application startup and shutdown. Additionally, if you are still using traditional WebSphere Application Server, you likely can get even faster startup and shutdown by moving to WebSphere Liberty, which we are now recommending for all deployments.

Complying with your corporate security & identity management policies

  • You can use application passwords for authenticating when using non-web clients; this provides a way to implement multi-factor authentication for these clients (it’s already available for web clients).
  • Delegate to your corporate third-party identity provider over OpenID Connect (OIDC) or SAML.
  • Distributed logout: when a user logs out of one ELM application, other ELM applications using the same browser session are notified and will log the user out.

Keeping things fresh: updates to the specified operating environment (a.k.a. system requirements)

  • Added RHEL 8.2 on all supported hardware platforms and SUSE 15 on x86-64
  • EWM workstation support includes Ubuntu LTS 20.04
  • Added Eclipse 4.16 (separate Eclipse p2 install), including optionally running Eclipse on OpenJDK 11
  • Updated GitHub, GitLab, and Gerrit versions

For more information on Engineering Lifecycle Management 7.0.2, see the more detailed “What’s New” posts and the various “New & Noteworthy” documents, for example, starting with Workflow Management. A Release Candidate 2 (RC) is available now, and the generally available (GA) version is coming soon.

Daniel Moul
Offering Management

No tags for this post.