Naming your components
When you create a component, you name it. The name you give a component should describe the services the component provides. It should also facilitate the maintainability of the system, because a component name can exist for a long time.
Early in the project, you should establish conventions for naming components. A popular convention calls for:
Application names that have three-letter prefixes that identify the project
Class names that are similar to the names of containing applications
Class names and application names must be unique within your image. Sometimes you might want to give a class the same name as its application. To avoid such name clashes, you could decide to suffix your application names with App.
Names are case sensitive. Applications and classes must start with an uppercase letter. Methods must start with a lowercase letter.
Last modified date: 01/29/2015