HTii leads packed IBM conference seminar on DOORS NG requirements management

An HTii team conducted a standing-room-only seminar March 20 at IBM InterConnect 2017 in Las Vegas on requirements management with the newest version of Rational DOORS Next Generation.

HTii’s Adam Hammett and Andrew Ridenour led some 50 participants in the packed session through the main functions of DOORS NG version 6.03 and best practices for managing changes to requirements in the multiuser online database.

“Many people thanked us after the seminar and asked for a copy of our presentation,” Hammett said. “They said it helped them a lot – especially if they were fairly new DOORS NG users.”

DOORS NG is a web-enabled version of IBM’s legacy standalone DOORS program. Both are used to manage requirements for complex engineering projects, such as new software, pharmaceuticals and military weapons.

“Requirements spell out the capabilities and characteristics the end product should have, but they can change greatly during design and development,” Ridenour said. “A big project can have thousands of requirements, and keeping track of changes to them can be a huge challenge.”

An IBM Silver Business Partner, HTii is a recognized expert in managing requirements, especially for customers migrating from DOORS to DOORS NG. The company’s clients come from Navy aircraft programs, heavy industry and state government.

Hammett is a co-leader of the global DOORS and DOORS NG User Group, and the company has conducted seminars and webinars at previous InterConnects and other smaller conferences.

In this year’s InterConnect, the HTii team explained operations in DOORS NG that perform functions similar to those in legacy DOORS. The two experts also provided “use cases” with new DOORS NG functions that maintain quality control over changes made during the team collaborations now possible in the web-enabled version.

DOORS NG manages these changes by working with requirements in three main configurations: a fixed “baseline” set of approved requirements, requirements “streams” that include changes made during an ongoing discussion and “change sets” containing proposed changes under review.

Said Hammett: “Used properly, these configurations make requirements change management – even in an active online collaboration – an orderly, efficient process with minimal chance for error.”