728x90
would like to know how I can represent complex typedef like the following in UML:
class Foo {
protected:
typedef std::pair<uint64_t, Bar> BarPair;
typedef std::set<BarPair> BarPairSet;
std::map<uint32_t, BarPairSet> m_indexedBarPairSet
};
Bar is not part of Foo.
There is no direct way to represent your typedefs, of course it is possible to have for instance the class BarPair with a dependency to the template class pair but there is no standard way to support the binding.
In case it is not for instance typedef std::pair BarPair but BarPair : public std::pair {} we have
So what about to extend UML with the stereotype typedef to have something like that :
or to stereotype the realization with typedef-bind and to use the stereotype typedef for BarPair and BarPairSet
'Architecture' 카테고리의 다른 글
Pattern: Saga (5) | 2024.09.27 |
---|---|
Pagination in the REST API (0) | 2024.09.24 |
Class Diagram | Unified Modeling Language (UML) (1) | 2024.09.23 |
Pagination 101: why it matters and how to do it right in your API (0) | 2024.08.22 |