This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
sewechad
Level 4
‎Jun 28, 2019 02:53 PM

2019 R1 Feature Clarifications on the Inventory Details Usage Tab

The usage tab introduced in 2019 R1 release needs the following clarification:

  1. Distribution – What does internal mean? From the documentation, the example provided is for development tools that is not part of the final build. We think internal distribution should be defined as for software that is package with the build but only distributed to internal company users. You should have a separate entry called “Not Distributed” for components that are not in the final build (i.e. test harness codebase).
  2. Part of Product – This question should come before distribution. If component is not part of the final build and not part of the product, then it would not be distributed. If “No” is selected for “Part of Product”, then the “Distribution Type” should default to “Not Distributed”.
  3. Linking – Please define “Not Linked”. We assume code copied into program source file would be an example of “Not Linked”
0 Kudos
(1) Reply
alexrybak
Revenera
Revenera
‎Aug 16, 2019 05:19 PM

 

  • Distribution – What does internal mean? From the documentation, the example provided is for development tools that is not part of the final build. We think internal distribution should be defined as for software that is package with the build but only distributed to internal company users. You should have a separate entry called “Not Distributed” for components that are not in the final build (i.e. test harness codebase).

We intended for Internal to mean that the OSS component is not part of the artifacts distributed outside the company or only used internally. I do think your suggestion makes sense. We will consider making a change in an upcoming release.

  • Part of Product – This question should come before distribution. If component is not part of the final build and not part of the product, then it would not be distributed. If “No” is selected for “Part of Product”, then the “Distribution Type” should default to “Not Distributed”.

Currently, the usage fields are independent. We have plans to add additional functionality to these fields, including making them available for advanced inventory search and policies. When we make those improvements, we can implement what you are suggesting.

  • Linking – Please define “Not Linked”. We assume code copied into program source file would be an example of “Not Linked”

An example of not linked would be "mere aggregation". An example could be a utility or driver for a given application may be included in the distribution, but the artifacts are not compiled into the product code and not packaged as part of the product artifacts. They happen to be on the same disk or download directory.

 

0 Kudos