The purpose of the Coverage view Item > Item is to keep track of and manage the relationships between two different structures, where one of them contains parts to items contained in the other structure. Some of the advantages of using this view to do this work instead of, e.g., the structure tree, are:
- Provides user-friendly functionality
- Supports easy version handling (e.g., highlights version inconsistency, offers quick fix for inconsistencies)
- Provides built-in consistency checks (e.g., out of scope cases, not mapped, etc.)
- Offers filters so you can work efficiently
- Familiarity with SystemWeaver concepts such as Items, Parts and Attributes
- An SW Architect has configured and activated the view via Configure the explorer
- You must have write access to the items you are mapping. Write access to the top-item in the structure is not necessary
The view is accessible via menu options on the ribbon that have been configured by an Architect. An option becomes available when an item is selected for which the view has been configured. Below is one example of a configured option.
Example Menu Option
They are also available via the View drop-down at the bottom of the list by ribbon group name.
Getting Acquainted with the View
The view is divided into a two panes, one for each of the structures. The view can be resized horizontally to view more of the right-hand pane by grabbing and dragging to fit your structure viewing needs.
It is also possible to resize vertically should you have a long list of Faulty mappings.
The left and right side panes in the view are configurable. The left side will display as a item structure tree while the right-hand side will be presented as a Context Tree, Grid or Structure Tree. Examples of these 3 types are shown below.
Uses a SystemWeaver context as a basis for building a tree.
The column with highlighting is the Indicator column. What is shown here is dynamically dependent on what is the focused item on the other side. Specifically, it marks green those items in the list which are mapped to the selected item.
- Selecting an item on the left side will highlight the mapped item(s) on the right side as well as the selected item in the main tree structure as shown in the above example.
- Selecting an item on the right side will highlight the mapped item(s) on the left side. The selected item on the right side will not be highlighted in the main tree structure.
The Name column shows the item name.
The Mapped column shows the mapping status. It shows whether the item on the row is mapped or unmapped, or if there are any version inconsistencies. The item can also be excluded from the mapping (out of scope).
- If the background color is gray, the item on the row is not a mappable item. Most often these are grouping or structure items.
- If the background is white, the item is mapped.
- If the background is red with the text "Not mapped", the item is not mapped.
- If the background is yellow, with the text "Version x => y", the item that is mapped has another version than that in the actual structure.
The To column shows how many unique items that the item is mapped against.
- If the background is yellow, the item is mapped against at least one item with version inconsistency in the mapping.
Status will show the item status.
If the item on the row has a Primary attribute defined for its item type, the value will display in this column. Typically, it identifies any item, like the requirement ID of a requirement.
Above Faulty Mappings, the Description of the selected item in the view is displayed.
A list of faulty mappings is displayed at the bottom of the view. This pane can be resized or hidden on-the-fly.
To map a left-side item to a right-side item, select the two items and click Map. Multi-select is supported in the right-side pane as shown below.
Map to New
It is possible to map to a new item on the left side, so that, in the below example, a new design function is created to be mapped to the selected right-side item. This option is available if the configuration allows for it.
The "Mapped" and "To" (indicating to how many items on the other side it is mapped) columns will be updated.
Removing an Existing Mapping
To remove mappings, select the mapped items and click Remove mapping. It is possible to multi-select items in the right-side list to remove a common mapping to one item on the left.
Fixing Right Side Version
If an existing mapping contains a version of a right-side item that does not match the version of that item in the main tree structure, a version mismatch will occur as described above in Getting Acquainted with the View. To fix a right-side version, select the left and right items where there is a mismatch and click Fix sec. version. Version mismatches are handled one at a time.
In the below example, the version of "Audio control" in the mapping is "2", but a version "3" exists in the main structure.
Below the two models, you can select filters for different tasks, and you will learn that using these filters are essential to working efficiently with the view.
The filter options are described below.
Match: Selecting this filter will display only those items which are mapped to the item currently focused in the corresponding tree structure, i.e., those items for which the leftmost indication column is lit up.
Not mapped: Selecting this filter will display only those items that are not yet allocated, i.e., those items for which the mapping status column has red background color, with the text "Not mapped".
Version mismatch: Selecting this filter will display only those items that have been mapped, but a version inconsistency has appeared because one of the structures has been updated. This corresponds to the status column having the color yellow.
To - Version mismatch: This filter will display only those items that have been mapped, but where there is a version inconsistency because one of the structures has been updated. This corresponds to the status column having the color yellow.
You can choose to select several filters at once in which case you will see those items satisfying at least one of the selected filters, i.e., you will see the union of satisfying result sets.
Handling Faulty Mappings
At some point during your work, models may change and, as a result of this, faulty mappings may appear. For example, a design function or or function specification may be removed from the model after mappings between function and design have already been made. The view displays any problem mappings along with their Error type will display in the Faulty mappings section.
In the above example, the "Phone" design function is mapped to two unique functions, but only one of them is in the structure. One is out of scope. Similarly, the "VehicleSpeed" design function is mapped to one item, but it is not in the structure. Its mapping is also out of scope.
If the mappings are no longer to be part of the scope, then they can be removed to resolve the faulty mappings. To do this, right-click on each and select Remove mapping.
Editing Attributes in Right-Side Grid
If configured by an Architect to allow it, it is possible to edit attribute values directly in a right-side grid. The type of editor presented will depend on the attribute type. In the below example, "Verification" is an enumeration attribute, and Annotation is a string attribute.