The class name needs to tell you what it does or holds. CurrentCallObject doesn't tell me anything. What call? Instead of generic "call", use what calls it or what it holds. And object isn't needed as it will be an object once instantiated.

I'll refer you AGAIN to Framework Design Guidelines http://www.barnesandnoble.com/w/framework-design-guidelines-krzysztof-cwalina/1100835446?ean=9780321545619 where all this is explained. They're online too http://msdn.microsoft.com/en-us/library/ms229042.aspx. Even though it refers to "framework" there is good advice for application developers




>Hi everybody,
>
>I am wondering what principles do you use when naming classes (and their methods / properties)? Do you know a good article on this topic?
>
>Say, right now I am thinking of how to name a class. My colleague suggested to use 'CurrentCallObject' for the class name, but I am not sure I like it. On the other hand, I don't have a better idea.
>
>This class is going to be instantiated on each invoke call (this call comes from C++ application) and will hold attributes related to the call.
>
>Thanks in advance.