Project

General

Profile

Feature #2950

Feature #2658: Hierarchic Platform

Generic Allocation Meta-Model

Added by Alexander Diewald over 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
11/23/2017
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Subtasks

Feature #3188: Adapt Schedule MetaModel to Allocation MetamodelClosed

Feature #3220: Add Component to ExecutionUnit AllocationClosedSimon Barner


Related issues

Related to Feature #2883: [Requirement] Find a nice solution to model tracesClosed03/20/2017

Related to Change Request #3067: Change allocation within task modell to generic allocation modelClosed08/31/2017

Related to Feature #2662: [UI] TransceiverPort editorRejected08/01/2016

History

#1 Updated by Alexander Diewald over 3 years ago

  • Due date changed from 05/17/2017 to 05/19/2017

#2 Updated by Simon Barner over 3 years ago

  • Project changed from Design Space Exploration to AF3 Phoenix

#3 Updated by Simon Barner over 3 years ago

  • Related to Feature #2883: [Requirement] Find a nice solution to model traces added

#4 Updated by Johannes Eder about 3 years ago

  • Related to Change Request #3067: Change allocation within task modell to generic allocation model added

#5 Updated by Simon Barner almost 3 years ago

  • Parent task set to #2658

#6 Updated by Simon Barner almost 3 years ago

  • % Done changed from 0 to 80

An initial version of the allocation framework is available, with specializations for Logical Architecture -> Partition Architecture and Partition Architecture -> Physical Architecture allocations.

#7 Updated by Simon Barner almost 3 years ago

  • Status changed from New to In Progress

#8 Updated by Simon Barner almost 3 years ago

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

#9 Updated by Simon Barner almost 3 years ago

#10 Updated by Simon Barner over 2 years ago

  • Status changed from In Progress to Resolved
  • Assignee changed from Simon Barner to Anonymous

See af3.allocation[.ui].

Simplest test:
  • Create Component Architecture with one component
  • Create Task Architecture with one Task
  • Create "Allocations" root element
  • Add Component to Task Allocation
  • Map component to task

#11 Updated by Anonymous over 2 years ago

  • Status changed from Resolved to Closed

Tested, code reviewed

Also available in: Atom PDF