Project

General

Profile

Feature #2907

[Check] New constraint to ensure that every signal defined in requirement should exist in the component architecture

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

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
03/29/2017
Due date:
% Done:

0%

Estimated time:

Description

Suppose a requirement defines a signal "x".
Suppose the same project contains a component architecture which does not have the signal "x" as input.

Current situation : no complaint from AF3

Expected: constraint (which can be activated or not: maybe some user don't want this feature) which checks whether all signals have a corresponding port.

History

#1 Updated by Anonymous over 3 years ago

We could implement this in our "mini-team programming session"

#2 Updated by Anonymous almost 3 years ago

  • Status changed from New to In Progress

Now we have most of the things to be able to create this constraint

#3 Updated by Anonymous over 2 years ago

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

#4 Updated by Anonymous over 2 years ago

  • Assignee changed from Anonymous to Saad bin Abid

@Saad, I assign this to you as the "constraint" expert

#5 Updated by Johannes Eder over 1 year ago

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

Also available in: Atom PDF