SystemWeaver offers a number of coverage views that enable users to relate items to each other. The views are all well-suited for tracking and managing these relationships, are configurable, and support multiple configurations. However, each offers different mapping options. This article provides a brief overview of the coverage views and their differences so that you can chose the most appropriate one for your use case. 


Coverage Item > Item

This view supports mapping between two different structures - one that holds items and the other that contains parts to those items. This view differs from the other two in that it supports the creation of a part relationship between two items. It is only the part that is created and not a (mapping) item. 


Data Pattern


Example


Pros

  • Ideal for simple mapping use case
  • "Map to New" enables users to create a new mapped item directly via the view

Cons

  • To maintain traceability, users must take out a new version of the mapped item.


Read more about configuring the view and how it is used


Coverage (Mapping Item)

This view supports mapping between one primary item (left side) and one or more secondary items (right side). Both a mapping item (of one item type) and a mapping part are created to map one or more left-hand side item types with one or more right-hand side item types. The method created a loose relationship that isn't visible when using the Reference view. The mapping item is the object that establishes the relationship.


Data Pattern


Example


Pros

  • Stable versioning allows for improved version handling of the mapped items
  • Support for mapping multiple item types

Cons

  • An extra item is created for each mapping (may not be seen as significant)


Read more about configuring the view and how it is used


Coverage Matrix

This view supports mapping between one primary item and one or more secondary items. Both a mapping item (of one or two item types) and a mapping part are created to map one or more primary item types with one or more secondary item types. The method created a loose relationship that isn't visible when using the Reference view. The mapping item is the object that establishes the relationship.The view provides ideal support for Hazard Analysis and Risk Assessment (HARA) work.


Data Pattern


Example


Pros

  • Stable versioning allows for improved version handling of the mapped items
  • Explicit support for not-applicable cases thanks to separate Applicable/Not-Applicable mapping item types

Cons

  • An extra item is created for each mapping (may not be seen as significant)


Read more about configuring the view and see examples of how it is used