The Software and Systems Engineering Experts​
The Software and Systems Engineering Experts​
SmarterProcess logo

Contacts

SmarterProcess / ReqPro

ul. Antoniego Pajdaka 5/98
03-134 Warsaw, Poland
NIP : 8921405210
Regon : 146293701

About Products

About us

Requirements, IBM Engineering Lifecycle Management

IBM Engineering Requirements Management DOORS Nextformerly DOORS Next Generation (DNG)

Write, link, review and baseline requirements in the browser, with traceability that holds up in an audit.

Overview

What is IBM Engineering Requirements Management DOORS Next?

IBM Engineering Requirements Management DOORS Next, formerly IBM Rational DOORS Next Generation, is IBM’s requirements management tool, used in the browser. Teams capture, link and version requirements, trace them to design, tests and work items, and reuse them across product variants.

It succeeds DOORS 9. Change and configuration management are built in, with a baseline for each release, so you can show what was approved and when.

Reviewers at partners and suppliers need only a browser, on premises or in the cloud.

Requirements link through OSLC to models in IBM Engineering Rhapsody, work items in IBM Engineering Workflow Management and tests in IBM Engineering Test Management, so every change shows its impact across the lifecycle.

Suppliers and OEMs exchange specifications in Requirements Interchange Format (ReqIF), with history and attributes kept.

Your starting point

Where is your team starting from?

Pick the column closest to your team. Each shows what changes with DOORS Next and where we usually start the work.

From Word and Excel

  • Today: Requirements in Word and Excel, sent by emailWith DOORS Next: One live specification everyone edits
  • Today: Traceability rebuilt by hand before each auditWith DOORS Next: Links kept as you work, reports on demand
  • Today: Each project structured differentlyWith DOORS Next: Shared types, templates and attributes

DOORS Next QuickStart

From IBM DOORS 9

  • Today: Copies of modules for every variantWith DOORS Next: One stream per variant, shared requirements
  • Today: Desktop client on every reviewer’s PCWith DOORS Next: A browser link for partners and suppliers
  • Today: DXL scripts only one person understandsWith DOORS Next: SmarterWidgets 2.0 and standard DOORS Next features cover most of them

DOORS 9 to DOORS Next migration

From another requirements tool

  • Today: Requirements locked in another tool’s formatWith DOORS Next: Import from ReqIF, Word or CSV, with attributes mapped to your types
  • Today: Two tools running side by side during the switchWith DOORS Next: IBM Engineering Integration Hub keeps Jama Connect or Polarion in sync until the last project moves

Requirements engineering consulting

Already on DOORS Next

  • Today: Servers to install and patchWith DOORS Next: IBM SaaS or hosting by SmarterProcess
  • Today: Licenses bought years ago, never reviewedWith DOORS Next: A license mix sized from real usage

Managed ServiceLicense review

Product tour

See DOORS Next before your first demo

Global configuration with streams for each product variant

Product variants from one specification

Global configurations reuse one specification across platforms and customers. Each variant keeps its own baseline and history, and models and tests follow the same configuration.

IBM Engineering Lifecycle Management Global Configuration Management

Impact analysis diagram of linked requirements

Traceability and impact analysis

Drag a requirement onto a design, test or work item to link them, then see what a change affects before you approve it. Sketch use cases, flowcharts and business processes next to the text.

Audit history of changes for one requirement

History, reviews and approvals

Every change to a requirement is recorded: who, when and what. Formal reviews, comments in context and electronic signatures add the approvals assessors ask for.

Filtered list of requirement artifacts

Views, filters and dashboards

Each team keeps its own saved views and AND/OR filters. Managers follow progress on dashboards.

Requirements specification module

ReqIF exchange

Exchange specifications with OEMs and suppliers in Requirements Interchange Format (ReqIF), without losing history or links.

DOORS Next module with the Requirements Quality Analysis panel: score 2 out of 10, three issues (imprecise verb, missing unit, passive voice) and a recommended rewrite

AI agents IBM Engineering AI Hub

Requirement quality analysis scores each requirement against industry standards, names the issues and proposes better wording. The Engineering Assistant answers questions about a specification in plain language, with summaries and translations. Nothing changes in the module until an engineer accepts a suggestion.

Compliance

Evidence for the standard your assessor uses

What each standard asks for, and what DOORS Next gives you to show it.

Automotive

ISO 26262 · ASPICE
  • Requirements with a unique ID, status and attributes through the safety lifecycle

    Typed artifacts with IDs, attributes and workflow states, shared through project templatesISO 26262-8, clause 6
  • Bidirectional traceability and consistency between requirement levels

    Link types between levels, traceability views and suspect links when a source changesASPICE SYS.2, SWE.1
  • Configuration and change management

    Baselines per release, change sets with approval, ReqIF exchange with OEMs and suppliers in both directionsISO 26262-8, clauses 7 and 8; ASPICE SUP.8, SUP.10

Aerospace & Defense

DO-178C · DO-254 · ARP4754A
  • Trace data between system, high-level and low-level requirements

    Links across modules and levels, traceability reports for the certification packageDO-178C 5.5, 11.21
  • Requirements reviewed and verified against the level above

    Formal reviews with comments in context and electronic signatures
  • Configuration management with baselines and change control

    Baselines, streams and change history for every artifactDO-178C section 7

Medical Devices

IEC 62304 · ISO 14971
  • Software requirements, including risk control measures

    Requirement types for hazards and risk controls in one moduleIEC 62304, 5.2
  • Traceability from hazard to risk control, requirement and verification

    Links from hazard to control to test, with views that show gapsIEC 62304, 7.3.3
  • Configuration management of software and documents

    Baselines and full change history for auditsIEC 62304, section 8

Railway

EN 50716 · EN 50126
  • Requirements traceable through the RAMS and software lifecycle

    Links from system and safety requirements down to software requirements and testsEN 50126, EN 50716
  • Hazards and safety requirements kept in step

    Hazard records as artifacts linked to the requirements that mitigate them
  • Controlled modification and change

    Change sets, impact analysis and baselines per delivery

Trusted in regulated industries

Our CustomersCustomers and Partners

Our clients build products under strict standards and regular audits. We supply licenses, implementation, hosting and training.

Our clients build products under strict standards and regular audits. We supply licenses, implementation, hosting and training.

Our Partners

We are a partner and reseller of these technology providers.

FAQ

Questions we hear before a DOORS Next project

Which license model fits us: authorized, floating or IBM tokens?

Authorized licenses suit daily users, floating licenses suit occasional users, and IBM tokens cover several IBM Engineering Lifecycle Management products. We size the mix from your user list and usage logs.

On premises, IBM SaaS or SmarterProcess hosting: what is the difference?

On premises gives you full control and your own upgrade schedule. IBM SaaS removes the servers. SmarterProcess hosting is a dedicated environment that we run, upgrade and back up for you.

How do we migrate from DOORS 9, including DXL scripts?

Project by project, with migration packages or ReqIF. We review DXL first: SmarterWidgets 2.0 covers many scripts, built-in features cover others, and the rest are rewritten. Both tools stay linked through OSLC during the move.

Can we exchange requirements with suppliers via ReqIF?

Yes, round-trip, with history kept and attributes mapped to your own types. Requirements Interchange Format (ReqIF) is an XML file format for exchanging requirements and their metadata between tools from different vendors.

Which AI features are available, and in which deployment?

AI comes with IBM Engineering AI Hub, an add-on to DOORS Next. Version 1.4 includes requirement quality analysis, the Engineering Assistant and governed Model Context Protocol (MCP) tools, so your own AI tools can work with IBM Engineering Lifecycle Management data under the same permissions. It runs in the cloud, on premises or air-gapped, on Red Hat OpenShift or Kubernetes, with watsonx.ai, Amazon Bedrock or Azure AI as the model provider. See IBM Engineering AI Hub.

Does it work with Jira and GitLab?

Yes, through OSLC connectors. To sync requirements with Jira, Jama Connect or Polarion ALM, see IBM Engineering Integration Hub.

How do teams move from copies to product lines?

Step by step: baselines give enduring reference points, change management adds a controlled process with a full audit trail, parallel development runs several releases at once, product variants share what is common, and product line engineering brings a high level of reuse. You reuse approved and tested resources, so you get fewer defects, lower development cost and a shorter time to market.

What is new in DOORS Next 7.2?

Advanced filters now work with enumerated attributes, using all match, some match, not all match and none match. New REST APIs help keep type systems consistent across components.

Which documents can DOORS Next produce on its own?

The document-style report wizard creates requirements and use case specifications, traceability reports, audit history and reviews, and prints a module as a book or a table. Output formats include HTML, PDF, XSL-FO and MS Word. For custom templates, add IBM Engineering Lifecycle Optimization – Publishing.

Do requirements still matter when AI writes code?

Yes. AI can speed up coding, but requirements remain essential to keep control of software development at enterprise scale. Spec-driven development reinforces the need for clear, governed requirements to guide delivery, manage change and reduce risk.

Talk to our consultants

Leave your details and we will get back to you, usually within one business day.

    We will only use your details to respond to your inquiry. Privacy policy