Coupling Criteria
A coupling criterion describes an architecturally significant requirement why two nanoentities should or should not be owned by the same service. These criteria define the semantic model on which the Service Cutter is built on.
- CC-1 Identity and Lifecycle Commonality
- CC-2 Semantic Proximity
- CC-3 Shared Owner
- CC-4 Structural Volatility
- CC-5 Latency
- CC-6 Consistency Criticality
- CC-7 Availability Criticality
- CC-8 Content Volatility
- CC-9 Consistency Constraint
- CC-10 Mutability (not implemented)
- CC-11 Storage Similarity
- CC-12 Predefined Service Constraint
- CC-13 Network Traffic Similarity (not implemented)
- CC-14 Security Contextuality
- CC-15 Security Criticality
- CC-16 Security Constraint