TypeFeaturing SysML
- class TypeFeaturing
Implementation of
TypeFeaturingdefined in the KerML specification.Specification:
A
TypeFeaturingis aFeaturingRelationshipin which thefeature_of_typeis thesourceand thefeaturing_typeis thetarget.For language description, see section 7.3.4.8 of the KerML specification. For more details on the model, see section 8.3.3.3.11 of the KerML specification.
Inheritance:
Members defined in
TypeFeaturing(7 members)RWhether this relationship can be used with chained features.
RAll subtypes of
TypeFeaturingaccording to the specification.RSysMLImplementation of
feature_of_typedefined in the KerML specification.RSyside specific accessor for manipulating the target of
feature_of_type.RSysMLImplementation of
featuring_typedefined in the KerML specification.RSyside specific accessor for manipulating the target of
featuring_type.RSysMLImplementation of
owning_feature_of_typedefined in the KerML specification.Members inherited from
Relationship(12 members)RConvenience method for sources[0].
RConvenience method for targets[0].
RWSysMLImplementation of
is_implieddefined in the KerML specification.RReturns
Trueif thisRelationshipis using implicit visibility.RSysMLImplementation of
owned_related_elementdefined in the KerML specification.RSysMLImplementation of
owning_related_elementdefined in the KerML specification.RSysMLImplementation of
related_elementdefined in the KerML specification.RSysMLImplementation of
sourcedefined in the KerML specification.RSysMLImplementation of
targetdefined in the KerML specification.RWThe visibility level of the related elements from this
Relationshiprelative to theowning_related_element.Reset visibility to its implicit value.
Non-throwing alternative to
visibilitysetter.Members inherited from
Element(25 members)RSysMLImplementation of
alias_idsdefined in the KerML specification.RThe owned
Commentsrelated byowned_relationships.RWSysMLImplementation of
declared_namedefined in the KerML specification.RWSysMLImplementation of
declared_short_namedefined in the KerML specification.RSysMLImplementation of
documentationdefined in the KerML specification.RWSysMLImplementation of
element_iddefined in the KerML specification.RSysMLImplementation of
is_implied_includeddefined in the KerML specification.RSysMLImplementation of
is_library_elementdefined in the KerML specification.RThe owned metadata related by
owned_relationships.RSysMLImplementation of
namedefined in the KerML specification.RSysMLImplementation of
owned_annotationdefined in the KerML specification.RSysMLImplementation of
owned_elementdefined in the KerML specification.RSysMLImplementation of
owned_relationshipdefined in the KerML specification.RSysMLImplementation of
ownerdefined in the KerML specification.RSysMLImplementation of
owning_membershipdefined in the KerML specification.RSysMLImplementation of
owning_namespacedefined in the KerML specification.RSysMLImplementation of
owning_relationshipdefined in the KerML specification.RReturn a unique description of the location of this
Elementin the containment structure rooted in a rootNamespace. In most cases the segments will be identical toQualifiedName.RSysMLImplementation of
qualified_namedefined in the KerML specification.RThe owner of this
Elementas the parent ofowning_membershiporowning_relationshipotherwise.RWThe state of semantic resolution for this
Element. Based on this, sema may skip elements to avoid duplicate work, e.g. when resolving elements in a group of related documents.RSysMLImplementation of
short_namedefined in the KerML specification.RSysMLImplementation of
textual_representationdefined in the KerML specification.Check if the qualified name of this
Elementmatches the provided segments of a qualified name.Members inherited from
AstNode(7 members)RThe source CST node of
selfif one exists.RThe
documentthat owns this node.RThe parent node of
self.Identity based hash of this node.
cast(self, *type: type[TNode]) -> TNode
Chainable equivalent to
isintance(self, type)Checked cast to
type.Attributes
- CHAINABLE: bool = False
Whether this relationship can be used with chained features.
Using this in, e.g.
append_chain, will raiseTypeError.
- STD: tuple[type[syside.TypeFeaturing], ...] = Ellipsis
All subtypes of
TypeFeaturingaccording to the specification.This is needed because the implementation does not use multiple inheritance like the standard metamodel. However, all would-be inherited attributes are implemented explicitly on classes in
TypeFeaturing.Std.When working with standard metamodel types, use:
if isinstance(element, TypeFeaturing.STD): ...
For type hints, instead use
TypeFeaturing.Std:Note that
TypeFeaturing.Stdis only defined duringTYPE_CHECKING, depending on the Python version used eitherfrom __future__ import annotationsordef function(...) -> "TypeFeaturing.Std"may be required to ensure that annotations are resolved lazily without an actual object present.
- property feature_of_type: syside.Feature | None
Implementation of
feature_of_typedefined in the KerML specification.Specification:
The
Featurethat is featured by thefeaturing_type. It is thesourceof theTypeFeaturing.See section 8.3.3.3.11 of the KerML specification for more details.
- property feature_of_type_target: syside.FeatureReference
Syside specific accessor for manipulating the target of
feature_of_type.
- property featuring_type: syside.Type | None
Implementation of
featuring_typedefined in the KerML specification.Specification:
The
Typethat features thefeature_of_type. It is thetargetof theTypeFeaturing.See section 8.3.3.3.11 of the KerML specification for more details.
- property featuring_type_target: syside.TypeReference
Syside specific accessor for manipulating the target of
featuring_type.
- property owning_feature_of_type: syside.Feature | None
Implementation of
owning_feature_of_typedefined in the KerML specification.Specification:
A
feature_of_typethat is also theowning_related_elementof thisTypeFeaturing.See section 8.3.3.3.11 of the KerML specification for more details.