AF3 issueshttps://git.fortiss.org/af3/af3/-/issues2023-10-16T14:25:43Zhttps://git.fortiss.org/af3/af3/-/issues/4334If metrics change a backlog file should be built and the file starts new with...2023-10-16T14:25:43ZKonstantin BlaschkeIf metrics change a backlog file should be built and the file starts new with the updated set of metricsAF3 2.24 - Feature FreezeKonstantin BlaschkeKonstantin Blaschkehttps://git.fortiss.org/af3/af3/-/issues/4327Closing AF3 from DSE perspective: requests to confirm closing pseudo resource...2023-10-12T14:17:33ZSimon BarnerClosing AF3 from DSE perspective: requests to confirm closing pseudo resources and inconsistent save button enable stateProblem 1:
The views "Constraints", "Objectives", "Dashboard", "Synthesis" etc. are shown in a dialog to confirm to save resources when closing AF3 after the DSE has been modified.
Steps to reproduce
- Import ACC example
- Import into D...Problem 1:
The views "Constraints", "Objectives", "Dashboard", "Synthesis" etc. are shown in a dialog to confirm to save resources when closing AF3 after the DSE has been modified.
Steps to reproduce
- Import ACC example
- Import into DSE
- Open Constraints view
- Create any constraint (e.g., arbitrary allocation constraint)
- Close AF3
- Observe that one should confirm that a resource with name "Constraints" should be saved before closing
Expected behavior: One should be asked if the model "ACC.af3_23" should be saved before closing
Problem 2: When the "DSE Navigator" is active, the save button is not enabled although the project has been modified (e.g., after adding a constraint)
Steps to reproduce
- Import ACC example
- Import into DSE
- Open Constraints view
- Create any constraint (e.g., arbitrary allocation constraint)
- Click into "DSE Navigator" view and observe that the save button is disabled
- Click into "Synthesis Navigator" view and observe that the save button is enabled againAF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/4275DSE: Sorting columns is disabled after selecting/exporting the first solution2023-03-29T06:33:51ZSimon BarnerDSE: Sorting columns is disabled after selecting/exporting the first solutionIn the frame of https://git.fortiss.org/af3/af3/-/issues/4274, a workaround was implemented in `ButtonColumnLabelProvider.ButtonSelectionAdapter.widgetSelected(SelectionEvent)` to disable sorting of columns after the first solution was s...In the frame of https://git.fortiss.org/af3/af3/-/issues/4274, a workaround was implemented in `ButtonColumnLabelProvider.ButtonSelectionAdapter.widgetSelected(SelectionEvent)` to disable sorting of columns after the first solution was selected/exported. The reason is that the enabled/disabled state of buttons is not adapted to updated order after sorting.AF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/4262getEClassForClass gives unexpected result in presence of inheritance2023-03-29T06:35:07ZUlrich SchöppgetEClassForClass gives unexpected result in presence of inheritanceSuppose there are two EClasses `A` and `B` where `A` is a supertype of `B`. In this situation, the call `getEClassForClass(A.getInstanceClass())` may return either `A` or `B`. It is unexpected that `B` can be returned.
It seems that `ge...Suppose there are two EClasses `A` and `B` where `A` is a supertype of `B`. In this situation, the call `getEClassForClass(A.getInstanceClass())` may return either `A` or `B`. It is unexpected that `B` can be returned.
It seems that `getEClassForClass(clazz)` picks the first EClass whose instance class is assignable to `clazz`. Depending on the order of the packages in the package cache, this can be either `A` or `B`:
```java
// Query all registered EPackages for the given clazz
for(EPackage ePackage : ePackagesCache) {
for(EClassifier eClassifier : ePackage.getEClassifiers()) {
if(eClassifier instanceof EClass && eClassifier.getInstanceClass() != null &&
clazz.isAssignableFrom(eClassifier.getInstanceClass())) {
eClass = (EClass)eClassifier;
clazz2EClassCache.put(clazz, eClass);
return eClass;
}
}
}
return null;
```
Should this code be changed so that it returns not just any EClass whose instance class is assignable to `clazz` but a most general one?
```java
// Query all registered EPackages for the given clazz
for(EPackage ePackage : ePackagesCache) {
for(EClassifier eClassifier : ePackage.getEClassifiers()) {
if(eClassifier instanceof EClass && eClassifier.getInstanceClass() != null &&
clazz.isAssignableFrom(eClassifier.getInstanceClass())) {
if(eClass == null || /* eClassifier is more general then eClass */ eClassifier
.getInstanceClass().isAssignableFrom(eClass.getInstanceClass())) {
eClass = (EClass)eClassifier;
clazz2EClassCache.put(clazz, eClass);
}
}
}
}
return eClass;
```AF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/4241Support multiple Data dictionaries2023-03-29T06:35:16ZSimon BarnerSupport multiple Data dictionariesThe current assumption is that there is exactly one data dictionary per project. This however conflicts with topics such as architecture synthesis and reuse that will create/use more than one data dictionary.
In this issue, the followi...The current assumption is that there is exactly one data dictionary per project. This however conflicts with topics such as architecture synthesis and reuse that will create/use more than one data dictionary.
In this issue, the following changes should be performed:
- [x] Relax constraints in the compositor to enable creating more than one data dictionary
- [x] Update {ComponentArchitecture, DataDictionary}Utils.findDataDictionary() to return "right" DataDictionary, i.e the one that is already used for other elements in the same logical architecture
- [x] Provide a solution to pick a data dictionary for the first type that is assigned within a logical architecture.
Testing
- [ ] Test model migrator that handles removal of `DataDictionaryRefSpec` annotation with attached copy of [ACC.af3_23](/uploads/ff80081a2376edf6621cc05ebac2981d/ACC.af3_23). The models in branch 4241 have already been migrated to fix the test suite
- [ ] Check that selecting a struct for a port in either of the data dictionaries defined in [multipe_dd_test.af3_23](/uploads/e8c11d8a24bc8d8a22dc47b86d8a79b5/multipe_dd_test.af3_23) "locks" the data dictionary for the other. Setting both ports to an atomic data type should offer all data types again
- [ ] (Co-)simulation still works
- [ ] Code generation for the rovers worksAF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/4228Write the user documentation for the architecture pattern synthesis2023-03-29T06:35:30ZTiziano MunaroWrite the user documentation for the architecture pattern synthesisA new page for the architecture pattern synthesis shall be added to the DSE section of the user documentation.
* *Title*: Architecture Pattern Synthesis
* *Section*: Design Space Exploration (DSE)
* *URL*: `dse/architecture_pattern_synt...A new page for the architecture pattern synthesis shall be added to the DSE section of the user documentation.
* *Title*: Architecture Pattern Synthesis
* *Section*: Design Space Exploration (DSE)
* *URL*: `dse/architecture_pattern_synthesis.html`AF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/4222Create PlatformGraph and TaskGraph2023-03-29T06:35:51ZSimon BarnerCreate PlatformGraph and TaskGraphProvide JGraphT based abstractions to ease exploration of topology.
- Platform: Extract from RouteUtils where such a graph is already used internally
- Task: Create from scratchProvide JGraphT based abstractions to ease exploration of topology.
- Platform: Extract from RouteUtils where such a graph is already used internally
- Task: Create from scratchAF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/4195Deployment synthesis fails for trivial allocation problem with one task and o...2023-04-03T07:30:07ZSimon BarnerDeployment synthesis fails for trivial allocation problem with one task and one execution unitFor the trivial allocation problem with exactly one task T and one execution unit E, the deployment synthesis does not find the allocation of T to E. If I remember correctly this is because the code producing the formalization iterates o...For the trivial allocation problem with exactly one task T and one execution unit E, the deployment synthesis does not find the allocation of T to E. If I remember correctly this is because the code producing the formalization iterates over the set of signals (and there is none). This problem also occurs if there are two or more (unconnected) tasks.
See[trivialalloc.af3_23](/uploads/f8201b9ce342043b7aceea92ecddcf2e/trivialalloc.af3_23)
Note: For a task architecture that contains a lonely task that is not connected to any of the other tasks by means of a signal, but that contains at least one other signal, the correct solution is returned (see [lonelytask.af3_23](/uploads/0a501b854ef728efd6c72f0f4d4c99a6/lonelytask.af3_23))AF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/4187Diagrameditors: Add context menus to show/hide connector and connection labels2023-03-29T06:37:17ZSimon BarnerDiagrameditors: Add context menus to show/hide connector and connection labels#4184 changed the visualization of TaskArchitectures to show connector names rather than connection names.
While this considerably cleans up the diagram, it might be desirable in some cases to show connection names as well.
Therefore, ...#4184 changed the visualization of TaskArchitectures to show connector names rather than connection names.
While this considerably cleans up the diagram, it might be desirable in some cases to show connection names as well.
Therefore, the following context menu entries shall be created:
Display > Show/Hide connector names
> Show/Hide connection names
Reasonable defaults which options are initially shall be defined for the following viewpoints
- ComponentArchitecture
- TaskArchitecture
- PartitionArchitecture
- PlatformArchitectureAF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/4045Function Architecture2023-03-29T06:48:01ZSimon BarnerFunction ArchitectureGoal: Create minimal *Functional Architecture* as dedicated viewpoint
- Definitions of functions
- Decomposition of functions
- Mapping of (atomic) functions to (logical components)
*(from redmine: issue id 4045, created on 20...Goal: Create minimal *Functional Architecture* as dedicated viewpoint
- Definitions of functions
- Decomposition of functions
- Mapping of (atomic) functions to (logical components)
*(from redmine: issue id 4045, created on 2020-07-22)*
* Relations:
* child #4046AF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/4040CPU load constraint.2023-03-29T07:07:02ZSimon BarnerCPU load constraint.As \#4038, but for Tasks and ECUs.
*(from redmine: issue id 4040, created on 2020-07-01)*
* Relations:
* relates #4047As \#4038, but for Tasks and ECUs.
*(from redmine: issue id 4040, created on 2020-07-01)*
* Relations:
* relates #4047AF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/4039Bus load constraint2023-03-29T07:07:24ZSimon BarnerBus load constraintThe DSE should provide a bus load constraint that puts a limit onto the
maximum admissible bus load for deployments.
Possibly based on formalization of bus bandwidth optimization objective.
*(from redmine: issue id 4039, created on 20...The DSE should provide a bus load constraint that puts a limit onto the
maximum admissible bus load for deployments.
Possibly based on formalization of bus bandwidth optimization objective.
*(from redmine: issue id 4039, created on 2020-07-01)*AF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/3952Color contrast in some JavaFX diagram editors is very low2023-04-03T07:22:49ZSimon BarnerColor contrast in some JavaFX diagram editors is very lowThe task of this ticket is to go through all diagram editors and to
check if the labels of all model elements are readable (by instantiating
all model elements in a test model).
See attachment for an example.
Possible resolution: make ...The task of this ticket is to go through all diagram editors and to
check if the labels of all model elements are readable (by instantiating
all model elements in a test model).
See attachment for an example.
Possible resolution: make background color lighter, use brighter font
color (white?)
*(from redmine: issue id 3952, created on 2020-03-17)*
* Uploads:
* ![Image_Pasted_at_2020-3-17_15-44](/uploads/b32d1f04b4da92a1da30975bfdc24e99/Image_Pasted_at_2020-3-17_15-44.png)AF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/3941Allocations editor: Creating a mapping in one tab removes all targets in the ...2023-04-03T07:24:56ZDummy AF3-DevAllocations editor: Creating a mapping in one tab removes all targets in the other tabs.To reproduce:
\- Download the attached model
\- Open the Allocations, “Components → Hardware” editor
\- Check that the “Ports → Transceivers” and “OutputPorts →
Transmitters” tabs have entries for both source and target
\- Go to the ...To reproduce:
\- Download the attached model
\- Open the Allocations, “Components → Hardware” editor
\- Check that the “Ports → Transceivers” and “OutputPorts →
Transmitters” tabs have entries for both source and target
\- Go to the “InputPorts → Receivers” tab and map Input0 to
RaspberryPI.DPadUp
- Check the “Ports → Transceivers” and “OutputPorts → Transmitters” tabs
again
Expected behaviour:
Entries of the “Ports → Transceivers” and “OutputPorts → Transmitters”
tabs should be unchanged.
Obtained behaviour:
Entries for the targets of the “Ports → Transceivers” and “OutputPorts →
Transmitters” tabs are gone.
Notes:
\- Does not affect the “Components → Hardware” tab.
\- Does not affect tabs that haven’t been opened before doing the
mapping.
- Closing and opening the Allocations editor restores all removed
entries
*(from redmine: issue id 3941, created on 2020-03-04)*
* Uploads:
* [Multiplatform_test.af3_23](/uploads/148631c4a6f716190cd90867aea2652d/Multiplatform_test.af3_23)AF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/3855Extend documentation for partition architecture2023-03-29T07:09:51ZSimon BarnerExtend documentation for partition architecture
*(from redmine: issue id 3855, created on 2019-10-16)*
*(from redmine: issue id 3855, created on 2019-10-16)*AF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/3662Timing Specification: Documentation2023-03-29T07:10:23ZJohannes EderTiming Specification: DocumentationWhen creating a Timing Specification, the expected editor does not open
(ModelEditorBinding is a ModelEditorNotAvailableBinding ?!). The Timing
Specification elements are furthermore not editable by right clicking on
the elements in the ...When creating a Timing Specification, the expected editor does not open
(ModelEditorBinding is a ModelEditorNotAvailableBinding ?!). The Timing
Specification elements are furthermore not editable by right clicking on
the elements in the navigator (but maybe this is intentional).
*(from redmine: issue id 3662, created on 2019-02-28)*AF3 2.24 - Feature FreezeSimon BarnerSimon Barnerhttps://git.fortiss.org/af3/af3/-/issues/3290Axis selection in the DSE visualization is not kept when switching visualizat...2023-10-23T07:26:48ZAlexander DiewaldAxis selection in the DSE visualization is not kept when switching visualizationsHow to reproduce.
-----------------
1\. Import the attached model into AF3.
2. Open the DSE perspective.
3. Open the DSE project from the imported model. (Home —>
“Open/Change DSE Project —>Unfold ”Acc" —>Select DSE node)
4. Op...How to reproduce.
-----------------
1\. Import the attached model into AF3.
2. Open the DSE perspective.
3. Open the DSE project from the imported model. (Home —>
“Open/Change DSE Project —>Unfold ”Acc" —>Select DSE node)
4. Open the Deployment Synthesis. (Synthesis —>Deplyoment
synthesis)
5. Select the additional Rule Set “DSE-User” (right).
6. Launch the DSE by clicking “Generate”.
7. Open the visualization.
8. Select 4D chart and set the axes.
9. Click Spider Chart or Table
10. Click “4D Chart” and notice the reset comboboxes.
Solution
--------
Add status fields for the selection in the backend GUI code.
*(from redmine: issue id 3290, created on 2018-02-27)*
* Uploads:
* [ACC.af3_23](/uploads/6d7efc2de37d5d1f01be9e870234c6c0/ACC.af3_23)AF3 2.24 - Feature Freezehttps://git.fortiss.org/af3/af3/-/issues/3253Implement hashCode methods for DSML elements implementing "equals"2023-10-23T07:27:00ZAlexander DiewaldImplement hashCode methods for DSML elements implementing "equals"Current status
--------------
Some EClasses in the DSML, e.g., the ModelElementLiteral, override the
equals method but not the hashCode method. This is strongly discouraged
by the Java API Designers since it can easily cause inconsisten...Current status
--------------
Some EClasses in the DSML, e.g., the ModelElementLiteral, override the
equals method but not the hashCode method. This is strongly discouraged
by the Java API Designers since it can easily cause inconsistent
behavior, e.g., in sort algorithms.
Resolution
----------
Implement hashCode methods where there are equals methods and align them
with the logic of these methods.
*(from redmine: issue id 3253, created on 2018-01-29)*AF3 2.24 - Feature Freezehttps://git.fortiss.org/af3/af3/-/issues/4355SysML Exporter: encoding of atomic data types2024-01-15T17:36:21ZSimon BarnerSysML Exporter: encoding of atomic data typesThe SysML currently has two some shortcomings in the handling of atomic data types
- [x] Atomic data-types used for input/output ports of logical components (Component "AtomicTest") in the attached example [SysML_Type_Test.af3_23](/upl...The SysML currently has two some shortcomings in the handling of atomic data types
- [x] Atomic data-types used for input/output ports of logical components (Component "AtomicTest") in the attached example [SysML_Type_Test.af3_23](/uploads/b3a1a11efc00d6248226ac9a2b0221b4/SysML_Type_Test.af3_23) are not traced to SysML data types. Example for int"
```
<packagedElement xmi:type="uml:Class" xmi:id="_E-xCE53GEe6BbL6kUh0ULg" name="lvClass_AtomicTest" visibility="public">
<ownedAttribute xmi:type="uml:Port" xmi:id="_E-xCFJ3GEe6BbL6kUh0ULg" name="lvPort_inInt" visibility="public" aggregation="composite"/>
```
- [x] For annotations, the tracing of data types seems inconsistent, e.g. for tasks:
- WCET: BigDecimal annotation of Task, mapped to a dataType_packagedElement_Integer, default value with uml:LiteralInteger
- RamRequirement: Long annotation of Task, mapped to a dataType_packagedElement_Complex, default value with uml:LiteralReal
- FlashRequirement: Long annotation of Task, mapped to a dataType_packagedElement_Integer, default value with uml:LiteralReal
```
<packagedElement xmi:type="uml:Class" xmi:id="_E-xCRJ3GEe6BbL6kUh0ULg" name="taClass_Task" visibility="public">
<ownedAttribute xmi:id="_E-xCRZ3GEe6BbL6kUh0ULg" name="FlashRequirement">
<type xmi:type="uml:DataType" href="platform:/plugin/org.eclipse.papyrus.sysml16/resources/library/SysML-Standard-Library.uml#SysML.package_packagedElement_Libraries.package_packagedElement_PrimitiveValueTypes.dataType_packagedElement_Integer"/>
<defaultValue xmi:type="uml:LiteralReal" xmi:id="_E-xCRp3GEe6BbL6kUh0ULg" value="100.0"/>
</ownedAttribute>
<ownedAttribute xmi:id="_E-xCR53GEe6BbL6kUh0ULg" name="RamRequirement">
<type xmi:type="uml:DataType" href="platform:/plugin/org.eclipse.papyrus.sysml16/resources/library/SysML-Standard-Library.uml#SysML.package_packagedElement_Libraries.package_packagedElement_PrimitiveValueTypes.dataType_packagedElement_Complex"/>
<defaultValue xmi:type="uml:LiteralReal" xmi:id="_E-xCSJ3GEe6BbL6kUh0ULg" value="200.0"/>
</ownedAttribute>
<ownedAttribute xmi:id="_E-xCSZ3GEe6BbL6kUh0ULg" name="WCET">
<type xmi:type="uml:DataType" href="platform:/plugin/org.eclipse.papyrus.sysml16/resources/library/SysML-Standard-Library.uml#SysML.package_packagedElement_Libraries.package_packagedElement_PrimitiveValueTypes.dataType_packagedElement_Integer"/>
<defaultValue xmi:type="uml:LiteralInteger" xmi:id="_E-xCSp3GEe6BbL6kUh0ULg" value="300"/>
</ownedAttribute>
</packagedElement>
```
- [x] Quite a lot of code duplications and magic constants in AF3SysMLToEMFMapping::addAnnotations*(), e.g. the following
```
FlashRequirement flashReq = getAnnotation(task, FlashRequirement.class);
if(flashReq != null && flashReq.getValue() != 0) {
Property flashReqProp = createUMLProperty("FlashRequirement", false, false);
flashReqProp.setRealDefaultValue(flashReq.getValue());
flashReqProp.setType((DataType)sysMLDataTypes.get(2));
taskClass.getOwnedAttributes().add(flashReqProp);
}
```
could be replaced by this, and further siblings of addLongAnnotation should be implemented (see branch 4355 https://git.fortiss.org/af3/af3/-/commits/4355)
```
/**
* Adds annotations for tasks, including {@link Comment}, {@link FlashSize}, {@link RamSize} and
* {@link Wcet} values.
*/
private void addAnnotationsTasks(Task task, Class taskClass) {
addComment(task, taskClass);
addLongAnnotation(task, taskClass, FlashRequirement.class, "FlashRequirement");
RamRequirement ramReq = getAnnotation(task, RamRequirement.class);
if(ramReq != null && ramReq.getValue() != 0) {
Property ramSizeProp = createUMLProperty("RamRequirement", false, false);
ramSizeProp.setRealDefaultValue(ramReq.getBytes());
ramSizeProp.setType((DataType)sysMLDataTypes.get(1));
taskClass.getOwnedAttributes().add(ramSizeProp);
}
Wcet wcet = getAnnotation(task, Wcet.class);
if(wcet != null && wcet.getValue() != null && !(wcet.getValue().toString().equals("0"))) {
Property wcetProp = createUMLProperty("WCET", false, false);
wcetProp.setIntegerDefaultValue(wcet.getValue().intValue());
wcetProp.setType((DataType)sysMLDataTypes.get(2));
taskClass.getOwnedAttributes().add(wcetProp);
}
}
private void addAnnotation(IModelElement modelElement, Class sysmlClass,
java.lang.Class<? extends IAnnotatedSpecification> anType, String anName,
EClass umlLiteral, java.lang.Class<? extends Number> javaType, int dataTypeIndex) {
Object value = AnnotationUtils.getAnnotationValue(modelElement, anType, javaType);
if(value != null) {
Property property = createUMLProperty(anName, false, false);
ValueSpecification defaultValue = property.getDefaultValue();
if(umlLiteral.equals(UMLPackage.Literals.LITERAL_REAL)) {
if(!(defaultValue instanceof LiteralReal)) {
defaultValue = property.createDefaultValue(null, null,
UMLPackage.Literals.LITERAL_REAL);
}
((LiteralReal)defaultValue).setValue(Double.valueOf(value.toString()));
} else {
// TODO (see
// https://git.eclipse.org/c/uml2/org.eclipse.uml2.git/plain/plugins/org.eclipse.uml2.uml/src/org/eclipse/uml2/uml/UMLPackage.java)
// LITERAL_INTEGER
// LITERAL_STRING
// LITERAL_BOOLEAN
// LITERAL_NULL ???
// LITERAL_SPECIFICATION ???
// LITERAL_UNLIMITED_NATURAL ???
}
// TODO: Is sysMLDataTypes and UMLPackage.Literals.* the same?
property.setType((DataType)sysMLDataTypes.get(dataTypeIndex));
sysmlClass.getOwnedAttributes().add(property);
}
}
private void addLongAnnotation(IModelElement modelElement, Class sysmlClass,
java.lang.Class<? extends IAnnotatedSpecification> anType, String anName) {
// TODO: Check if Long annotations should be encoded as LITERAL_REAL or LITERAL_INTEGER (or
// something else)
addAnnotation(modelElement, sysmlClass, anType, anName, UMLPackage.Literals.LITERAL_REAL,
Long.class, 2);
}
```AF3 2.25 - New Feature HackathonKonstantin BlaschkeKonstantin Blaschkehttps://git.fortiss.org/af3/af3/-/issues/4354Create weight annotation2024-01-15T17:09:16ZSimon BarnerCreate weight annotationThe weight annotation shall enable to specify the weight of technical components. It is a "sibling" of the HW cost annotation in terms of registration (execution units, ...) and integration in the tool:
- Annotation editor
- DSE hardware...The weight annotation shall enable to specify the weight of technical components. It is a "sibling" of the HW cost annotation in terms of registration (execution units, ...) and integration in the tool:
- Annotation editor
- DSE hardware optimization pattern editor
- SysML exporterAF3 2.25 - New Feature HackathonSimon BarnerSimon Barner