Skip to content
This repository was archived by the owner on Oct 3, 2024. It is now read-only.
This repository was archived by the owner on Oct 3, 2024. It is now read-only.

consistency check action too aggressive in checking coverage #127

Description

@reteprelief

It currently checks that each transition covers all error events and all error sinks.
It should check that for a given error state there exists an outgoing transition that references each error event/incoming propagation.

In general we need to revisit all consistency checking rules as to whether they are too strict.
See http://aadl.info/aadl/osate/osate-doc/osate-emv2/consistency.html for the consistency rules being checked. We also need to make sure they align with the consistency rules in the standard.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions