Re-using stream or Baseline in GCM
When we reuse stream or baseline in GCM will that create copy of actual content?
Example: We have a Stream/Baseline with 500 requirement in GC and want to reuse this stream/baseline to another stream. If we do so, data will get duplicated? i.e the requirement count is now 1000.
|
2 answers
|
When you create a new stream from another Stream/Baseline in GCM (or even local configuration), the content of original stream is replicated in the new stream.
From usability point of view, these are requirements from original stream that are re-used in the new stream. If you notice, the ID of the requirement will be the same. So multiple versions of requiements are held in different streams/baselines.
So if you're looking for a count, from sizing perspective (monitoring resource usage), then yes, the count will be 1000. Here we use the term versions instead of requirements. |
Geoffrey Clemm (30.1k●3●30●35)
| answered Feb 10 '20, 10:39 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER It depends on what you mean by "re-use in GCM". If you mean you are adding that stream/baseline to a new global stream, then nothing is copied ... you simply re-use the same artifact versions in both the original and in the new global stream/baseline (so still 500 versions). If you are creating a new global stream by branching from an existing global baseline, then again, no new artifacts are created ... you just get a new global stream that has the same contributions as the baseline you are branching (again, still 500 versions).
If you mean that you are delivering/merging from one local application stream to another, then this depends on what local application you are using. If you are using EWM(aka RTC) or RMM, then no new versions are created ... you simply re-use the appropriate versions (still 500 versions). In the case of RQM and DNG, you may get some new physical version records because of the way structured version data is stored in RQM/DNG, but from an end-user's perspective, there are no new versions unless a merge was required.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.