Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions lobster/tools/core/report/requirements/requirements.trlc
Original file line number Diff line number Diff line change
Expand Up @@ -196,9 +196,10 @@ req.System_Requirement_Aspect Multi_Level_Source_Files {

req.System_Requirement_Aspect Message_Trace_Coverage {
description = '''
IF an item contains a "message" and traces to another item,
THEN the traced item shall have 100% coverage,
AND the item with the message shall have 0% coverage.
IF an item contains a "message",
THEN the item shall be counted as "not okay",
regardless of whether it traces to another item or not.
ELSE the item shall be evaluated according to the general tracing policy.
Comment on lines +199 to +202

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs further investigation.

  1. It seems there is a bug, see test pr for lobster-report #460
  2. We need to decide about precedence: If an item has got a "message" AND a "justification", what is the expected item status?

@phiwuu phiwuu Sep 9, 2025

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Conclusion: "message" takes precedence over "justification". If both are given, then the above requirement still applies. But if a justification is given, then most of the tools append a "message" saying that the item does not need to be traced. And then suddenly this requirement would apply, and the item would be counted as "not okay".

'''
}

Expand Down
Loading