blocks|key|975082|text|您不应该在图表中包含getter和setter，直到它们做了一些特殊的事情:空值检查等等。但这是一个糟糕设计的标志，所以一般的答案是“不，你不应该这样做”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|975083|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You should not include getters and setters in your diagram until they do something special: null checking and so on. But it is a sign of bad design, so general answer is "No, you should not".

blocks|key|759552|text|UML是一种相当非正式的符号，最好是首先设置您将在项目或组织中使用的规则。例如，通常会隐藏getter和setter，但有时显示所有细节也很重要。规则可以是这样的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|759553|如果您的属性是使用一个私有变量和一对具有相同可见性的getter和setter实现的，那么您只需创建一个具有该可见性的属性。|759554|如果您的属性是使用私有变量实现的，但getter和setter具有不同的可见性，例如公共getter和受保护的setter，则建议在模型中显示getter和setter。|759555|所以儿子。|759556|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

UML is a rather informal notation, the best would be to first set the rules you going to use at your project or organization. 
For instance, it is usual to hide getters and setters, but sometimes it is important to show all details. A rule could be such as:

if your property is implemented with a private variable and a pair of getters and setters with the same visibility, you just create a property with this visibility.

if your property is implemented with a private variable, but the getter and setter has distinct visibilities, such as a public getter and a protected setter, it would be advisable to show the getter and setter in the model.

and so son...

blocks|key|975189|text|通过创建您自己的«get/set»和«get»构造型来对这些私有属性进行分类，使相关属性的getter/setter约定显式可能是有用的。请看我对Shortcut+for+denoting+or+implying+getters+and+setters+in+UML+class+diagrams的回答。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|975190|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/28139621/shortcut-for-denoting-or-implying-getters-and-setters-in-uml-class-diagrams/28141950#28141950^0|21|23|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

It may be useful to make the getter/setter convention explicit for the properties concerned by creating your own «get/set» and «get» stereotypes to be used for categorizing these private properties. See my answer to <a href="https://stackoverflow.com/questions/28139621/shortcut-for-denoting-or-implying-getters-and-setters-in-uml-class-diagrams/28141950#28141950">Shortcut for denoting or implying getters and setters in UML class diagrams</a>.

I am required to draw a class diagram for my JSF application for a project documentation. So I have lots of classes as managed beans, with many attributes therefore many getters and setters. 

When I draw the class diagram should I also include the getters &amp; setters in the diagram or can I simply leave them?

Should I include getters & setters in class diagram?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我需要为项目文档的JSF应用程序绘制一个类图。因此，我有许多类作为托管bean，具有许多属性，因此有许多getter和setter。当我绘制类图时，我是否也应该在图中包括getter和setter，或者我可以简单地离开它们？

问我应该在类图中包含getters和setter吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我应该在类图中包含getters和setter吗？EN