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

consistency check action too aggressive in checking coverage #127

Open
reteprelief opened this issue Apr 11, 2017 · 1 comment
Open

consistency check action too aggressive in checking coverage #127

reteprelief opened this issue Apr 11, 2017 · 1 comment

Comments

@reteprelief
Copy link
Contributor

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.

reteprelief added a commit that referenced this issue Apr 13, 2017
have an explicit occurrence probability property.
Relates to issue #127.
@reteprelief
Copy link
Contributor Author

Temporarily removed action from menu.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant