1 / 5

QM link to RTC/DOORs

QM link to RTC/DOORs. Workitem. TestCase B. Requirement A. QM sends request using RTC Concept URL GCUrl (in the request header) RTC ignores the GCUrl RTC stores QM concept URL Enhancement: RTC could store the GCUrl as another field (comments…). 1. 1. Concept link. 2. 2.

cruz
Download Presentation

QM link to RTC/DOORs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. QM link to RTC/DOORs Workitem TestCase B Requirement A • QM sends request using • RTC Concept URL • GCUrl (in the request header) • RTC ignores the GCUrl • RTC stores QM concept URL • Enhancement: RTC could store the GCUrl as another field (comments…) 1 1 Concept link 2 2 Concept link 3 3 4 4

  2. Concept links localized to a configuration • The global configuration is used to tie together local configuration across the applications. • When a tool does a rich hover or artifact picker, the tools now pass along the global configuration information. The tools then use this to find the correct version to display for that concept. Global Configuration 2014 TestCase B Requirement A 1 1 RM 2014 stream QM 2014 stream 2 2 Concept link 3 3 4 4

  3. From RTC/DOORs – show QM Rich hover = Baselines = stream merge • UserA in RTC sends request using • QM Concept URL • When no config is specified, QM will use userA’s latest selected configuration • Enhancement: QM could display inside the rich hover the QM local configuration used • Could provide a way for user to change the configuration somehow WorkItem Concept link 1st created, - backlink created using concept url - concept url is stored on both sides Base (common) product Concept link + GCUrl in request header Europe Variant Concept link  QM will use userA’s latest selected configuration US variant China Variant h

  4. From RTC/DOORs – GET/PUT(CRUD) QM Resource = Baselines = stream merge • UserA in RTC sends GET/PUT request using • QM resource concept URL • When no config is specified, QM will use userA’s latest selected configuration • QM currently logs a warning in the log saying no config is specified. • Since no config is specified in the request, QM is using userA’s latest selected configX • User can either supply the GCUrl or change their latest config selection in QM WorkItem Base (common) product Concept link Europe Variant  QM will use userA’s latest selected configuration US variant China Variant h

  5. From RTC/DOORs – show QM Picker (selection, create new) = Baselines = stream merge • UserA in RTC sends request using • QM picker URL • When no config is specified, QM will use userA’s latest selected configuration • Enhancement: QM could display the QM local configuration used to • Could provide a way for user to change the configuration somehow WorkItem Base (common) product QM picker URL Europe Variant  QM will use userA’s latest selected configuration US variant China Variant h

More Related