Project

General

Profile

Feature #3224

Feature #3019: [NoVal rework] collection issue

constraint for non-NoVal ports

Added by Anonymous almost 3 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
12/08/2017
Due date:
% Done:

0%

Estimated time:

Description

If a port is specified to always contain a value (i.e., NoVal is not allowed) then an analysis needs to be implemented to check that the port is always assigned a value.

At present this analysis can be broken in following sub-analyses:
  1. Ports connecting a channel should both have the same specification (either for both NoVal is allowed or not)
  2. For atomic components we can either use formal verification or it can also be checked statically (at least IMO). If output port p is specified as "NoValAllowed = false", then the check would be:
    • In case behaviour is code spec just check that every branch is assigning a value to p
    • in case of state automaton check that p is assigned in every transition
    • Of course model checker can be used to check this, but IMO that is a bit of an overkill

History

#1 Updated by Vivek Nigam almost 3 years ago

  • Assignee changed from Vivek Nigam to Anonymous

Open AF3 file:
specification/test-data/Test-Constraint-NoValAllowed
(Ignore the x in the Component Architecture.)
There you should be able to activate the constrain
Component COnstraints Group -> Provided all inputs....
Then 3 components should be marked with x.

#2 Updated by Anonymous over 2 years ago

  • Target version changed from AF3 2.13 RC1 (Feature Freeze) to AF3 2.14 RC1 (Feature Freeze)

#3 Updated by Anonymous about 2 years ago

  • Assignee changed from Anonymous to Anonymous

#4 Updated by Johannes Eder over 1 year ago

  • Target version changed from AF3 2.14 RC1 (Feature Freeze) to Backlog

#5 Updated by Anonymous over 1 year ago

  • Status changed from New to Resolved
  • Assignee changed from Anonymous to Johannes Eder

Implemented in #3644.
Please close

#6 Updated by Anonymous over 1 year ago

  • Target version changed from Backlog to Team Programming July 2nd 2019

#7 Updated by Johannes Eder over 1 year ago

  • Status changed from Resolved to Closed
  • Assignee deleted (Johannes Eder)

Also available in: Atom PDF