Project

General

Profile

Feature #2885

[Trace] Constraint to ensure a component matches its functional requirement interface

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

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

100%

Estimated time:

Description

Step by step:
  1. create a requirement
  2. create a functional aspect to it
  3. create a component with input and output of type booleans into it
  4. create a component architecture
  5. create a component
  6. trace it to the requirement previously created

There should be an error saying the traced component does not match the requirement.

History

#1 Updated by Anonymous over 3 years ago

done for component, verify for states/transitions

#2 Updated by Anonymous over 3 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

#3 Updated by Anonymous almost 3 years ago

  • Assignee changed from Anonymous to Anonymous

#4 Updated by Anonymous over 2 years ago

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

#5 Updated by Anonymous over 2 years ago

  • Status changed from Resolved to Closed

Tested.

#6 Updated by Anonymous over 2 years ago

  • Status changed from Closed to Feedback
  • Assignee changed from Anonymous to Anonymous

Filip, how did you tested this?
I follow the steps (functional aspect should actually be formal specification aspect) mentioned but I don't see any error

#7 Updated by Anonymous over 2 years ago

  • Status changed from Feedback to In Progress
  • Assignee changed from Anonymous to Saad bin Abid

I tested and there was no error, but it should be an error message.

#8 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