Essentials of IBM Rational DOORS Next Generation v6.0.5 (IBM Engineering Requirements Management DOORS Next) – ODC8005G CR,ILO
Course Code: ODC8005G
Brand: Engineering Lifecycle Management
Category: Watson Internet of Things
Skill Level: Intermediate
Business Analyst, Systems Engineer, Software Engineer, Requirements Engineer, Requirements Manager, Requirements Team Leader
no pre-requisites for this course.
Analysts and engineers learn how to define, elaborate, organize, and manage textual and graphical requirements and requirements-related information in IBM Rational DOORS Next Generation v6.
Please note that as of version 6.0.6, the IBM Rational DOORS Next Generation (RDNG) has been renamed to IBM Engineering Requirements Management DOORS Next (DOORS Next)
This course teaches analysts and engineers how to define, elaborate, organize, and manage textual and graphical requirements and requirements-related information in IBM® Rational® DOORS Next Generation v6. Rational DOORS Next Generation is a key component of the Rational solution for Collaborative Lifecycle Management (CLM). The product provides requirements definition and management capabilities in a fully-integrated environment that can also include IBM® Rational Team Concert for change and configuration management, and IBM® Rational® Quality Manager for quality management.
- View and work with requirements and requirements-related information in a collaborative context using.
- Global Configuration Capture, define, elaborate, and edit requirements and requirements-related information, and create hierarchically organized requirements documents.
- Create and manage traceability relationships between requirements and requirements- related information.
- Manage requirements throughout a project lifecycle.
Leverage Global Configuration features View and work with requirements and other artifacts in a collaborative context Create and edit requirements documents and other artifacts, including both textual and graphical artifacts Create, manage, and view traceability relationships between requirements and other artifacts