val app4_wr_input_d : Transaction = Transaction(app4 write input_d)
defines a read transaction called '''app4_wr_input_d''' between the initiator of app4 and the input_d data.
The location of the application and the data are provided in the SimpleSoftwareAllocation trait.
A transaction or a scenario is only '''declared''' here, it will be considered during the interference analysis if it is
actually used. This is done in the SimpleKeystoneLibraryConfiguration files.
A transaction should be a path from an initiator to a target, if several paths are possible a warning will be raised.
Check the transaction and scenario libraries w.r.t. the transactions computed with the actual
the ideal (but not requested situation) is one-to-one libraries
definition of the platform
Check the transaction and scenario libraries w.r.t. the transactions computed with the actual
the ideal (but not requested situation) is one-to-one libraries
definition of the platform
Map from the user defined transaction to the physical transaction id
this map does not contain user transactions with multi-path (contained in ...)
WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION
Map from the user defined transaction to the physical transaction id
this map does not contain user transactions with multi-path (contained in ...)
WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION
Map from the physical transaction id to the user defined id(s)
It is possible that a physical transaction is linked to several (or none) user defined transactions
WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION
Map from the physical transaction id to the user defined id(s)
It is possible that a physical transaction is linked to several (or none) user defined transactions
WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION
Map from the used scenario and the application involved in these scenarios
WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION
Map from the used scenario and the application involved in these scenarios
WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION
Map from the physical scenario id (set of transaction id) to the user defined scenario(s)
It is possible that a scenario is linked to several (or none) user defined scenarios
WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION
Map from the physical scenario id (set of transaction id) to the user defined scenario(s)
It is possible that a scenario is linked to several (or none) user defined scenarios
WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION