As a QoS Engineer/Software Designer I want to express soft constraints on security and performance of serverless functions, microservices and data pipelines using the CDL.
Requirement
The CDL should be able to express soft constraints on the required security/performance.
Extended Description
For example, there may be a hard constraint on the maximum (expected) latency, but a soft constraint expressing that even if the (expected) latency is within the required level, the lowest possible (expected) latency is preferred. The soft constraints should be weighted and prioritised, in order to allow us to reason about trade-offs (e.g. in some cases, soft constraints on latency may be less important than soft constraints on security).
Priority
Should have
Affected Tools
CDL
Means of Verification
A check that the CDL can express a set of required soft constraints for a set of different use cases.
From D2.1 (Companion)