Project

General

Profile

Feature #4047

Reconfiguration synthesis related parameters for platform architecture

Added by Simon Barner about 2 months ago. Updated 9 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Start date:
08/17/2020
Due date:
08/21/2020
% Done:

0%

Estimated time:

Description

To be implemented as annotation in org.fortiss.af3.platform

  • MaxLoad: ExecutionUnit -> double \in [0;1] (represents the timeBudget parameter in the reconfiguration synthesis formalization)
    • Maximum percentage that the sum of the WCETs of all tasks allocated to an ECU may consume of the LCM of these tasks' periods.
    • The very same load annotation shall also be used for the deployment constraint requested in #4040
    • Check of value bounds: Override public <U> void setAnnotationValue(U value, T specification) throws Exception of value provider
To be implemented as annotation in org.fortiss.af3.reconfiguration
  • isolated: ExecutionUnit -> Boolean: Flag if the ECU is isolated (i.e., considered defective)
  • Task type: Task -> {MASTER, HOT_STANDBY, COLD_STANDBY}: Deployment type of Task [done]

Related issues

Related to Feature #4040: CPU load constraint.New07/01/2020

History

#1 Updated by Simon Barner about 2 months ago

#2 Updated by Simon Barner about 2 months ago

  • Description updated (diff)

#3 Updated by Simon Barner about 2 months ago

  • Description updated (diff)

RUL is already part of #4050

#4 Updated by Simon Barner about 1 month ago

  • Priority changed from Normal to High

#5 Updated by Simon Barner about 1 month ago

  • Description updated (diff)

#6 Updated by Simon Barner about 1 month ago

  • Description updated (diff)

#7 Updated by Simon Barner 9 days ago

  • Status changed from New to In Progress
  • Priority changed from High to Normal

I have merged the "Is isolated" annotation (see https://git.fortiss.org/af3/rise/-/merge_requests/2).

Having a closer look at max load, I now think that it would be better to not have this parameter in the input metamodel, but to specify it as a constraint (using a pattern), similar to the memory utilization constraint.

See org.fortiss.af3.exploration.ui.perspective.targetdef.constraint.pattern.MemoryPatternFXController for a starting point.

-> This can be postponed, and the constraint can be added to initial version of the synthesis.

Also available in: Atom PDF