Categories
Design Requirements Testing Workflow

The Engineers Never Stopped Working

Amidst business and economic disruption, modernization of market-leading engineering lifecycle management solution continues

By  William Streit | 2 minute read

This isn’t the first time a massive sea change has forced us to suddenly change the way we live and work, and it won’t be the last. It’s during these times that engineering teams provide the great breakthroughs that will take us through the next evolution of business and operations.

As we all work to define what the ‘new normal’ looks like, we expect to see continued disruption across industries and marketplaces. Companies will lean on their engineering and development teams to stretch their limits of creativity and productivity. Now more than ever, tools for product design and development require an end-to-end view across the entire engineering lifecycle.

Throughout our recent IBM Engineering European Academy, we heard repeatedly from customers and business partners that while some of their operations were forced to halt, their engineering teams continued to work. There was a clear theme – engineering teams have been and will continue to lead business through recovery. And success will be directly related to these teams’ ability to respond and adapt, quickly and efficiently.

Over the last several months IBM has continued work on modernizing its Engineering Lifecycle Management (ELM) solution. The introduction of IBM ELM V7.0.1 represents evolution of our entire systems and software development lifecycle offering.

Continuous Improvements for the ELM Products

The ELM V7.0.1 updates represent the ongoing work to roll out improvements across the entire engineering lifecycle management solution – across requirements, test, workflow management and systems design. Our focus has been on improving usability, productivity, and building capabilities that integrate with industry models and standards.

As we emerge from hibernation, the demand for first-to-market competitive advantage will force systems and software development teams to step up to the challenge – increasing productivity while still improving quality and accelerating time to market.

The latest enhancements in the ELM portfolio include improved Agile capabilities, simplifying model-based systems engineering (MBSE) usage, expanded industry standard capabilities (i.e. AUTOSAR enhancements, SAFe 5.0 inclusion, GIT integration, ASPICE capability expansion), broader capabilities around validation & verification (V&V), improved visualization of data, and overall performance.

Delivering an integrated, end-to-end development lifecycle solution enables engineering teams to focus on product development – not searching for data, converting or migrating information, manually tracing between requirements, tests, workflow, or continually validating data currency.

What’s next for ELM?

We’ll keep listening to our customers, industry groups, and the marketplace – working together to deliver continuous improvements to our products. IBM is committed to ensuring systems and software development teams are equipped with the tools they need to develop products in a smarter, safer and more cost-effective way.

Albeit the near-term future is still unclear, it is certain that engineering and development teams will be even more critical as companies pivot to new markets, products, and strategies. And we’ll keep helping our customers manage the growing complexity of product engineering with the speed necessary to deliver faster business outcomes.

Explore IBM Engineering Lifecycle Management

Get the IDC Analyst Report on Digital Transformation in Product Development

Categories
Design Requirements Testing Workflow

Deploy your requirements management in a private cloud, with AI. Yes, now.

New release of IBM Engineering Requirements Quality Assistant Now Available on OpenShift

By  Erin O’Connor | 1 minute read |

Every systems and software project starts with requirements, and getting them right lays the foundation for all the development work that follows. Many companies actually allocate additional resources to ensure their requirements meet the highest standards. This can pay significant dividends in improving productivity and product quality. It also makes the requirements process the most logical area to leverage AI.

Imran Hashmi IBM ELM engineering lifecycle management

Responding to customer requests for more independence and security around their use of AI, we have enhanced our Engineering Requirements Quality Assistant (RQA) to run in an OpenShift container. This greatly enhances the ELM solution base to offer a ‘run anywhere’ model for requirements.

When the Watson AI technology for requirements launched initially, we wanted the product to be easy to use and work in conjunction with our customers’ existing requirements management solutions. This is the second generation, running on OpenShift, allowing our customers to run their requirements in a private cloud.

Watch the Requirements Quality Assistant video

Why the move to OpenShift?

  • The new RQA solution provides greater deployment flexibility, managed anywhere OpenShift 4.3+ is available
  • Keep your data behind your network firewall vs. on a public cloud
  • The OpenShift container environment also helps lower cost of operations and administration overhead

This new release enables customers to run RQA in the same environment as the rest of their software, retaining complete control of their requirements process, which is especially important for companies working on high security projects. The new capabilities will become available this Fall.

Follow along in the Engineering Academy to get all your questions answered directly. See if the availability of RQA on OpenShift can help you improve productivity and continuity.

About Requirements Quality Assistant

Imran Hashmi IBM ELM engineering lifecycle management

The Engineering Requirements Quality Assistant (RQA) product helps remove risk and ambiguity in requirements authoring, comes pre-trained based on indicators consistent with INCOSE standards so it is useful right out of the box, and can actually provide authors coaching to improve the quality of requirements. We have also introduced a bundle of IBM Engineering Requirements Management DOORS Next and Engineering Requirements Quality Assistant to make acquisition easier.

All of these enhancements are part of commitment to help our customers find efficiency in their processes and provide the tools needed to maintain resiliency in an ever-changing market.

Talk to requirements experts through the Engineering Academy

Get the AI-Driven Requirements Guide

Categories
Design Requirements Testing Workflow

OSLC in the DOORS Next Generation Environment

Part 1

OSLC in the DOORS NextGeneration Environment

Part 2

Categories
Design Requirements Testing Workflow

Let IBM Watson Assess Your Requirements with IBM RQA

Presenter: Jim Herron – Technical Professional of Island Training

Your engineering requirements drive development – if they contain errors, so will your products. Add IBM Engineering Requirements Quality Assistant to DOORS Next or DOORS 9 to increase requirement quality during creation. Using Watson Natural Language Service and pre-trained AI, Requirements Quality Assistant has built-in quality indicators designed to be consistent with guidelines from the International Council on Systems Engineering (INCOSE) for writing complete, clear, and testable requirements to accelerate your review process, increase requirement quality and reduce training for junior requirements engineers. This webinar will show you how IBM RQA will allow you to assess your requirements with Watson AI.


Listen to April 30th recording here.

Categories
Design Requirements Testing Workflow

What’s New in IBM Engineering Lifecycle Management 7.0 Enterprise Deployments

Presenter: Tim Feeney and Paul Ellis of IBM

In addition to all the significant functional enhancements IBM Engineering Lifecycle Management (ELM) v7.0, the release also includes many important changes and improvements related to enterprise deployment. In this session, we will highlight these changes and other best practices and guidance updates. With the DOORS Next platform being one of the more significant architectural changes in this release, we will review the new scale limits and highlight best practices to ensure a successful migration.


Listen to May 7th recording here.