UML类图中是否存在GOF23类图里pseudocode annotation的对应元素？

Great question! I’ve wrestled with this exact discrepancy before—since the GOF’s Design Patterns book is such a cornerstone, its diagram conventions often feel like "canon," even pre-dating formal UML standards.

First, let’s clarify: UML doesn’t have a direct, native element that perfectly matches the pseudocode annotations used in the GOF book’s class diagrams. The reason for this is simple: the GOF book was published in 1994, three years before UML 1.0 was formally standardized. The authors used their own diagramming shorthand to convey implementation details via pseudocode, which wasn’t yet codified into UML’s specification.

That said, there are several UML-compliant ways to replicate the same functionality (adding pseudocode context to class elements):

• UML Notes (Comments)
  This is the closest and most straightforward replacement. UML Notes are represented as a rectangle with a folded corner, and they can be attached to any class, method, attribute, or even the entire diagram. You can paste the exact pseudocode from the GOF annotation directly into a Note and link it to the relevant element. Most UML tools (like Visual Paradigm, StarUML, or even draw.io) support this, and it serves the exact same purpose: adding human-readable implementation context to the structural diagram.

• Stereotypes with Constraints
  If you prefer a more structured approach, you can define a custom <<pseudocode>> stereotype and attach it to the class or operation that needs annotation. Then, use a UML Constraint (a text string enclosed in braces) to hold the pseudocode itself. This is more formal than a Note, but it’s useful if you’re building a standardized modeling library for your team.

• Inline Operation Descriptions
  Many UML tools let you add extended descriptions to operations (methods) beyond their signature. You can paste pseudocode directly into this description field, tying the code snippet directly to the method without needing a separate Note element. This keeps the diagram cleaner while still preserving the implementation context.

In short: while there’s no 1-to-1 UML equivalent for the GOF’s pseudocode annotation style, UML Notes are the most practical and direct way to replicate its intent.

内容的提问来源于stack exchange，提问作者Rui