IPXACT views with both component and design references

[Khushi]

For a subsystem level IPXACT we need to specify both componentInstatiationRef and designInstantiationRef.

We can have either a single view with both <ipxact:componentInstantiationRef> and <ipxact:designInstantiationRef>

or

We can have two different view one each for <ipxact:componentInstantiationRef>, <ipxact:designInstantiationRef>

Which one of the above is recommended or both are valid ?

Is there any difference between these two ? 

Thank you

Khushi

[Jason H]

Hi Khushi,

A componentInstantiationRef points to the name of a componentInstantiation in the same document. Basically, it contains view-specific information about the current component (I like to think of it as describing "how to instantiate this component in this view"). A designInstantiationRef references a designInstantiation in the same document, where the designInstantiation references the VLNV of a separate design document for that view. The only reason you would want to reference them in different views is if they weren't both valid in the same view.

In my experience, we always reference a local componentInstantiation and a designInstantiation for any view of a hierarchical component. There may be some scenario I could invent where you may want them separate. Maybe you have a documentation view in which the docs should be generated at that component, but not the implementation underneath. They maybe you could have

<model>
  <views>
    <view>
      <name>rtl</name>
      <componentInstantiationRef>ci-rtl</componentInstantiationRef>
      <designInstantiationRef>di-rtl</designInstantiationRef>
    </view>
    <view>
      <name>documentation</name>
      <componentInstantiationRef>ci-rtl</componentInstantiationRef>
    </view>
  </views>
</model>

I've never encountered such a requirement, though.