Pattern asymmetricOneToOne

SVG plug-in required to display this diagram

Description This pattern implements an asymmetric One-to-one relationship where the relationship asset becomes a subordinate of one of the entities in the relationship.
Default Namespace
Namespace Prefixes {none}
Scope Definitions {none}
Default Type System {none}
Type System Prefixes {none}
Default Constraint Language {none}
Constraint Language Prefixes {none}
Default Operation Vocabulary {none}
Operation Vocabulary Prefixes {none}
Design Patterns {none}
Included Models {none}

Pattern Info

Category generic/relationship
Keywords relationship
Alias names {none}
Purpose The purpose of this pattern is to establish an asymmetric relationship between a single entity of type A and a single entity of type B.
Motivation One-to-one relationships occur quite often in real world scenarios, for example the relationship between hsuband and wife in western societies.
Applicability This design pattern should be applied for binary one-to-one relationships. It should not be applied to one-to-many relationships or many-to-many relationships. It is also not suitable for ternary, or even higher n-ary relationships, or for composite/part situations.

This pattern implements the given one-to-many relationship as a separate asset. An arc with the cardinality constraint [1..1] points from the single entity A to the relationship asset, and an arc with the cardinality of [1..1] points from the relationship asset to the entity type B.

Advantages: This pattern can be used in situations where the entities are located in different containers (L2S) without the risk of creating orphan assets.

Disadvantages: The hierarchy between relationships and entities is not visualized well.

Known Applications Examples are: Relationship between husband and wife. Relationship between car and carholder.
Related Patterns
Use the composite pattern when dealing with aggregations.
Use the oneToOne pattern in containerless models or when both entities are located in the same container.
Use the asymmetricOneToMany relationship if the relationship relates an asset of type A to several assets of type B.
Level 2 Structures Entity1
Assets Entity2
Annotations {none}
Errors {none}
Warnings {none}
Infos {none}
Status Pattern contains 0 errors, 0 warnings, and 0 infos

Graphics Index