You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
what is the exact meaning of this annotation [calculation] ?
Documentation below says it means calculation is ready-made :
However do not understand how it is exactly working, notably in regards of these two main sets of concerns :
let' stay with example of [calculation] for FloatingAmount
question 1 : Given the various features of rate returns payout terms (e.g. averaging, compounding, 2021 overnights styles, discounting, etc.) plus possible combinations of these terms…
is the whole scope exhaustively implemented
and successfully tested
and if yes, based on what test file distribution ?
and test documentation ?
question 2: after first quick look I had across functional objects involved/composed together for eventually calculating the FloatingAmount and I could see lot of input are “external input” thus not being resolved from the Payout path values per se… that is to say there is no automation processing here because an extern
meaning there is actually no automation processing
because there are gaps to manually fulfill, whereas should be resolving per functions, between Event model where agreements on terms is represented and related Process model based on “func” objects for the purpose of automating the execution of the Event model… as far as I can understand at this stage… if so, how to assess exactly where we stand in regards of target where ideally would have fully smart implementation i.e. “Trade -> Fixing -> “func” -> Calculation results” ?
The text was updated successfully, but these errors were encountered:
what is the exact meaning of this annotation
[calculation]
?Documentation below says it means calculation is ready-made :
However do not understand how it is exactly working, notably in regards of these two main sets of concerns :
let' stay with example of
[calculation]
forFloatingAmount
question 1 : Given the various features of rate returns payout terms (e.g. averaging, compounding, 2021 overnights styles, discounting, etc.) plus possible combinations of these terms…
question 2: after first quick look I had across functional objects involved/composed together for eventually calculating the
FloatingAmount
and I could see lot of input are “external input” thus not being resolved from the Payout path values per se… that is to say there is no automation processing here because an externbecause there are gaps to manually fulfill, whereas should be resolving per functions, between Event model where agreements on terms is represented and related Process model based on “func” objects for the purpose of automating the execution of the Event model… as far as I can understand at this stage… if so, how to assess exactly where we stand in regards of target where ideally would have fully smart implementation i.e. “Trade -> Fixing -> “func” -> Calculation results” ?
The text was updated successfully, but these errors were encountered: