-
Notifications
You must be signed in to change notification settings - Fork 10
Closed
Description
Summary
Check Flow Latency Analysis is not computed for feature group connections
Expected behavior
connections/flows through aadl feature groups should produce a report when "Check Flow Latency" analysis is executed
Actual behavior
The latency report is not generated
Steps To Reproduce
- Instantiate Air_Vehicle.impl
- Select Analyses --> Timing --> Check Flow Latency
- Use analysis defaults
- Verify no report is created
package Embedded_Computer_Architecture
public
feature group EventDataExchanges
end EventDataExchanges;
system Air_Vehicle
end Air_Vehicle;
system implementation Air_Vehicle.impl
subcomponents
cockpit: abstract Cockpit;
mission_System: system Mission_System;
sensor: system Sensor;
connections
ms_to_cockpit: feature group mission_System.p1 -> cockpit.p1;
sensor_to_ms: feature group sensor.p2 -> mission_System.p2;
flows
Sensor_Flow: end to end flow
sensor.flowSource ->
sensor_to_ms ->
mission_System.flowPath ->
ms_to_cockpit ->
cockpit.flowSink;
properties
Latency => 100 ms .. 200 ms applies to Sensor_Flow;
end Air_Vehicle.impl;
abstract Cockpit
features
p1: feature group inverse of EventDataExchanges;
flows
flowSink: flow sink p1;
properties
Latency => 0 ms .. 25 ms applies to flowSink;
end Cockpit;
system Mission_System
features
p1: feature group EventDataExchanges;
p2: feature group inverse of EventDataExchanges;
flows
flowPath: flow path p2 -> p1;
properties
Latency => 100 ms .. 100 ms applies to flowPath;
end Mission_System;
system Sensor
features
p2: feature group EventDataExchanges;
flows
flowSource: flow source p2;
properties
Latency => 0 ms .. 25 ms applies to flowSource;
end Sensor;
end Embedded_Computer_Architecture;
Desktop (please complete the following information):
- OSATE Version: v2.11
- Operating System: Windows 10
Reactions are currently unavailable