Project

General

Profile

Feature #3019

[NoVal rework] collection issue

Added by Anonymous about 3 years ago. Updated 7 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
Start date:
08/04/2017
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

Collection issue for NoVal rework.

perceived tasks:
1) UI + model change: Add a checkbox to state if the port can be a noVal or not.
2) Update transformation to the model checker
3) Modify code generator accordingly
4) investigate if simulator semantics need to change and change if necessary

Later some static analysis should be incorporated too. Currently I can think of a simple one implemented as a constraint: check if a NoVal port is read in any transition without checking if it is not NoVal


Subtasks

Feature #3020: [NoVal rework] addition of a flagRejected

Feature #3224: constraint for non-NoVal portsClosed

Feature #3228: behaviour when a NoVal input port is readRejected

History

#1 Updated by Anonymous almost 3 years ago

  • Assignee changed from Anonymous to Vivek Nigam

#2 Updated by Anonymous almost 3 years ago

  • Project changed from AF3 Phoenix to Analysis
  • Target version deleted (AF3 2.12 Post-release)

#3 Updated by Vivek Nigam over 2 years ago

  • Target version set to AF3 2.14 RC1 (Feature Freeze)

#4 Updated by Anonymous almost 2 years ago

  • Assignee changed from Vivek Nigam to Anonymous

#5 Updated by Johannes Eder over 1 year ago

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

#6 Updated by Anonymous about 1 year ago

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

#7 Updated by Anonymous about 1 year ago

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

#8 Updated by Johannes Eder 7 months ago

  • Status changed from New to Rejected
  • Assignee deleted (Anonymous)

Also available in: Atom PDF