Anonymous | Login | Signup for a new account | 2021-04-17 02:15 UTC | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0000940 | Taste | [All Projects] TASTE GUI Windows | public | 2020-11-27 13:48 | 2020-11-27 13:48 | ||||||
Reporter | ellidiss | ||||||||||
Assigned To | ellidiss | ||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||
Status | assigned | Resolution | open | ||||||||
Platform | All | OS | OS Version | ||||||||
Summary | 0000940: Add support for implicit connections between functions with modes and the mode_automaton | ||||||||||
Description | In the context of MOSAR we introduced the modes/configurations support in TASTE. It implies: All this changes will be published in the project release. The support for modes in a function needs a connection between the mode automaton and the function. Until now the connection is visible in the editor. This ticket was opened to add an implicit support for this connection in the TASTE editor. When a function has modes configured (in the function properties) and there is a 'mode_automaton' component present. TASTE editor should add a required interface named 'configuration_status' to the function and connect it to the 'mode_automaton' when serializing the model in AADL as a file. This connection should be implicit and not visible in the editor. To this end, TASTE editor should not present the same connection when loading a AADL model with such connection. | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | ![]() | ||||||||||
![]() |
|||
Date Modified | Username | Field | Change |
2020-11-27 13:48 | ellidiss | New Issue | |
2020-11-27 13:48 | ellidiss | Status |
new => assigned |
2020-11-27 13:48 | ellidiss | Assigned To |
=> ellidiss |
2020-11-27 13:48 | ellidiss | File Added: illustration.png |
Copyright © 2000 - 2011 MantisBT Group |