The CDL must be able to express hard constraints on the required security/performance

[marklaw]

From D2.1 (Companion)

ID	R-T4.1-2
Section	WP4: Modelling Environment Requirements
Type	FUNCTIONAL_SUITABILITY
User Story	As a QoS Engineer/Software Designer I want to express hard constraints on security and performance of serverless functions, microservices and data pipelines using the CDL.
Requirement	The CDL must be able to express hard constraints on the required security/performance.
Extended Description	Security conditions include constraints on the encryption / access control of personal data. One example of a performance constraint is that the expected latency should be low.
Priority	Must have
Affected Tools	CDL
Means of Verification	A check that the CDL can express a set of required hard constraints for a set of different use cases.
Dependency

[marklaw]

@gcasale I slightly modified the extended description. It originally said that we should guarantee low-latency. I'm not sure this is actually possible, as in a real system things could easily go wrong, increasing latency. I have changed it to say "the expected latency should be low". I think we should be able to define expected latency of a series of calls if we are given the expected latency for each component (and each connection between components).

[gcasale]

Accepted. This is implicit, perfomance measures by default are always mean values.