在Android对话框后创建另一个对话框(Creating another dialog after dialog Android)

 类名称如InvoiceReader，PriceCalculator，MessageBuilder，ArticleReader，InvoiceReader实际上并不是动词名称。 他们真的是“名词名词”的名字。 见代理名词 
 
 动词类的名字将类似于验证，操作，管理等。显然，这些更好地用作方法，并且作为类名称将是相当尴尬的。 
 
 “名词代理名词”类名称的最大问题在于它们对于该类什么是实际的（例如UserManager，DataProcessor等）可以给出很少的意义。 因此，他们更有可能blo肿，失去内在的凝聚力。 （见单一责任原则 ）。 
 
 因此，具有IInvoiceReader和IArticleReader接口的WebService类可能是更清晰和更有意义的OO设计。 
 
 这给你一个简单的，明显的名词类名“WebService”，以及“名词代理名词”接口名称，清楚地宣告WebService类可以为呼叫者做什么。 
 
 您可能还可以通过前缀另一个名词（例如PaymentWebService）为实际类赋予更多意义。 
 
 然而，界面总是比单一的类名更好地描述该类可以为呼叫者做什么。 随着课程越来越复杂，新界面也可以添加有意义的名称。 

Class names like InvoiceReader, PriceCalculator, MessageBuilder, ArticleReader, InvoiceReader are not actually verb names. They are really "noun agent-noun" class names. See agent nouns.
 
A verb class name would be something like Validate, Operate, Manage etc. Obviously these are better used as methods and would be quite awkward as class names.
 
The biggest problem with "noun agent-noun" class names is that they can give very little meaning as to what the class actually does (eg UserManager, DataProcessor etc). As a result they are more likely to be bloated and to lose internal cohesion. (See Single Responsibility Principle).
 
Therefore the WebService class with the IInvoiceReader and IArticleReader interfaces is probably the clearer and more meaningful OO design.
 
This gives you the simple, obvious noun class name "WebService", along with "noun agent-noun" interface names that clearly advertise what the WebService class can do for callers.
 
You could probably also give more meaning to the actual class by prefixing another noun, for example PaymentWebService. 
 
However the interfaces are always better than a single class-name at describing more specifically what the class can do for callers. As the class grows more complex, new interfaces can also be added with meaningful names.