Item Suspect Integrity and How to Use it

Showing Suspect Items

Changing an item may impact related items. For example, changing a stakeholder requirement may necessitate changes to the system requirements linked to it, cascading the change to the product configuration items.

Item integrity shows items that are ‘suspect’

Items are classed as suspect when an item changes after a link was made:


Visual explanation of suspect
As the ‘from’ item has been modified the ‘to’ item becomes suspect

Cradle provides three methods of showing items that are suspect which can be set/chosen in Preferences, these methods are:


  • Off
  • Suspect
  • Suspect due to my changes
Item integrity options in Preferences
Item integrity options in Preferences

If you enable Suspect or Suspect due to my changes in preferences, suspect items will be shown in red.

Confirming Integrity

Once you have reviewed the item suspect item there are two courses of action. One to change the item to comply with the changes ‘further up the hierarchy’, or just to confirm there are no changes needed. Integrity can be confirmed by a user-with read-write access, confirming integrity is recorded in the item’s change history.

Confirm item integrity
Confirm item integrity

You also have the option to view suspect item in WebAccess you have to choose your method in options but items will be highlighted in red in queries if they are classed as suspect.

Enabling suspect integrity in WebAccess
Enabling suspect integrity in WebAccess
Article Updated 04/02/2019 – Moved image and give example of when an item would become suspect