如何在UML类图中指定类属性到数据库表列的映射？

Great question! When you're stuck with an unchangeable database model but need to explicitly show how your class attributes map to specific table columns in UML, stereotypes are absolutely a valid and widely used approach—but there are a couple of other structured options depending on your project's scale and needs. Let's break them down:

1. Stereotypes + Tagged Values (The Standard UML Approach) #

This is the most idiomatic way to represent this kind of mapping. Here's how to implement it:

• Define a custom stereotype like <<persistTo>> to flag attributes that have a direct database column mapping.
• Pair it with a tagged value (a key-value property in UML) to specify the exact table and column. For example:
  • For a class attribute fullName, apply the <<persistTo>> stereotype, then add a tagged value like column: users.user_full_name.
• You can even visualize this directly on the UML diagram: place the stereotype above the attribute, and list the tagged value in brackets next to it (e.g., fullName: String <<persistTo>> {column: users.user_full_name}).

This approach is UML-compliant, easy for other developers to understand, and works with most UML modeling tools.

2. Custom UML Profile (For Team-Wide Consistency) #

If this mapping pattern is going to be used across your entire project or team, creating a custom UML Profile is a step up. A Profile lets you formalize your persistence rules:

• Define a Profile with dedicated stereotypes like <<DBEntity>> for classes tied to database tables, and <<DBColumn>> for attributes mapped to columns.
• Add required tagged values to these stereotypes (e.g., tableName for <<DBEntity>>, columnName for <<DBColumn>>).
• This way, every team member uses the same standardized notation, reducing ambiguity and making diagrams more consistent.

3. Inline Documentation (Quick, Low-Overhead Option) #

For small projects or one-off mappings where formal UML notation feels overkill, you can simply add clear documentation to the attribute's notes section. For example:

fullName: String
Persists directly to the users.user_full_name column in the existing database

While this isn't as structured as stereotypes, it's straightforward and requires no setup in your modeling tool.

Final Recommendation #

If you need a UML-standard, maintainable solution, go with stereotypes + tagged values—it balances clarity and formality. For larger teams or long-term projects, invest in a custom UML Profile to enforce consistency. The inline docs are great for quick, ad-hoc cases.

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