OCL implementation of UML operation "Classifier::directlyUsedInterfaces()"
On page 177 of the UML 2.5.1 specification under section 9.9.47 "Operations" for Classifier, we have the following operation definitions:
directlyRealizedInterfaces() : Interface [0..*]
The Interfaces directly realized by this Classifier
body: (clientDependency->select(
oclIsKindOf(Realization)
and supplier->forAll(oclIsKindOf(Interface))))->
collect(supplier.oclAsType(Interface))->asSet()
This is fairly straightforward to implement, for example in C++, since there is a property clentDependency defined for NamedElement which is one of the base classes for Classifier.
However, the next operation is problematic:
directlyUsedInterfaces() : Interface [0..*]
The Interfaces directly used by this Classifier
body: (supplierDependency->select(
oclIsKindOf(Usage)
and client->forAll(oclIsKindOf(Interface))))->
collect(client.oclAsType(Interface))->asSet()
The problem is that there is no property supplierDependency in NamedElement. Perhaps there used to be one and it was removed? I came across this reference WRT supplierDependency: https://www.site.uottawa.ca/~tcl/gradtheses/mnojoumian/ThesisFiles/FinalSpec/UML/7.3.33.html
I suppose this could be implemented similar to the NamedElement::clientDependency() body:
body: Dependency.allInstances()->select(d | d.client->includes(self))
using supplier instead of client?
There actually is a property supplierDependency defined on NamedElement as you can see in the UML specification
This is also present in the xmi file for version 2.5. This is an image of the resulting model in EA after importing the xmi file.
- Copying virtual base class results in losing shared_ptr owned object
- How does C++23 happens before apply to std::memory_order_seq_cst?
- Are repeated declarations of a template with a type-template-parameter defaulted to a closure type a violation of ODR?
- Modifying a global variable in a constexpr function in C++17
- Which part of the C++ standard forbids destroying an object twice?
- Does the C++ standard forbid reusing storage without destroying?
- Is it well defined to cast generic function pointers to specifc signatures with void* params pointing to different types
- Why is a double semicolon a SyntaxError in Python?
- Can atomic loads be merged in the C++ memory model?
- Which sort of UB do I have here, deleting array of operator new[]?
- Is shifting 0 to the left considered undefined behavior in C?
- asctime - day of month zero or space padded?
- How to determine whether the following switch block is exhaustive?
- Definite matching in Java pattern matching
- Implicitly changing the active union member between two members of the same primitive type
- C++ Aliasing a type with the same name
- Does calling a dependent function that has not been yet declared at the point of template definition cause the program to be IFNDR?
- Does C++11 allow dollar signs in identifiers?
- What are the prohibitions against certain kinds of aliasing through unions?
- Does calling non-const mem. fun. on const object via non-const ref obtained via const_cast invoke UB only if the fun actually modifies the object?
- Common initial sequence with nested struct
- Is there a way to assert something about an argument to a consteval function, with a meaningful error message on failure
- C++14 constexpr function requirements on cppreference
- Error when binding a constexpr reference to variable of different type
- Is there inlinable function for pow2?
- Can & (address-of-operator) ever return nullptr?
- C++17 Are non-static POD class members initialized with curly braces {} set to 0?
- Why can’t I use a unary operator in a chained assignment, but only in separate assignment statements?
- Changing active member in a union with copying using std::construct_at
- Can std::ranges::enumerate enumerate any possible valid C++ array?