DOORS Next as an OSLC service provider

Edit online

DOORS® Next provides user interface (UI) elements and operations to applications that consume services from the DOORS Next domain for data sharing.

UI elements

The DOORS Next application provides the following UI elements for other products to consume in compliance with the DOORS Next domain specifications V1 and V2:
  • Delegated UI dialog box for the selection of requirement resources
  • Delegated UI dialog box for the selection of requirement collection resources (views)
  • Delegated UI dialog box for the creation of requirement resources
  • UI previews (compact rendering, rich hover) at displayed links to requirement resources
  • UI previews (compact rendering, rich hover) at displayed links to requirement collection resources
  • Factory resource for the programmatic creation of requirement resources

OSLC operations

The following table lists the operations that DOORS Next provides in compliance with the indicated DOORS Next domain specifications.
Table 1. OSLC operations
Operation DOORS Next V1 DOORS Next V2 Oasis Working Draft
Service Discovery Yes Yes  
POST for requirement creation Yes Yes  
GET on a Requirement Yes Yes  
GET on a Requirement Collection Yes Yes  
Resource Shape No Yes  
QUERY on Requirement and Requirement Collection No Yes  
QUERY on OSLC links No Yes  
POST for baseline creation     Yes
GET for baselines and streams     Yes
Note: For information about configuration management operations, refer to the Oasis Working Draft.
  • The POST operation creates a requirement as the first artifact in a requirements collection. POST is not available at the database level of the service discovery tree.
  • DOORS Next internal links are not included in the results of the V1 GET operation.
  • DOORS Next external links are not included in the results of the V1 GET operation.
  • DOORS Next internal outgoing links are included in the results of the V2 GET operation.
  • DOORS Next external links are included in results for the V2 GET operation.

Modules that are located within a collection are not available to OSLC consumers through a GET operation. An attempt to add a module to a collection through a PUT operation will fail.

For basic instructions for using OSLC in DOORS Next, see the article Using OSLC capabilities for IBM® Engineering Requirements Management DOORS Next.

For more information about the OSLC DOORS Next implementation in Engineering Lifecycle Management and other products that are based on Jazz technology, see the Open Services for Lifecycle Collaboration Workshop.

For information about developing OSLC-compliant Eclipse applications, see the Eclipse Lyo web site.

For information about enabling links between DOORS Next and other Engineering Lifecycle Management applicationDOORS Next and other DOORS Next tools, see Linking to development, design, test, and requirement artifacts.

For information about configuring the integration with IBM Engineering Requirements Management DOORS , see Integrating DOORS Next and DOORS.