Question: I have never understood what is the ideal way to name a project, package, class. I do it in a random way which doesn't look professional at all. I know the class name should start with a capital alphabet. But what I don't really have trouble with is finding the names that are suitable and look professional. lets consider this example. If I am writing a program for fibonacci series i give names like this:

```
project name = fibonacci_project
package name = org.fib.code1
class name = Code1

```

Doesn't look neat right? How would you do it ?

Answer: 
There are some tips about naming:

1. As you said *classname* have the capitalization of first letter of every word, eg. `LongClassName`
2. Sun always preferred long names that explain clearly the meaning of the class (think about `DefaultTableModel`). `Code1` is definetely not right, maybe `FibonacciCalc` or something that contains `Fibonacci` would fit better.
3. Preprend `Abstract` if it's an abstract class
4. Append `Impl` if it's an implementation of a particular interface
5. Package names should start with org, com, it, etc (usually it was the backward URL of project repository or the nick of the coder)
6. You should split your packages according to functionality, your example is really simple so there is not a way to do it.

Think about something more complex in which you have:

```
org.package.gui
org.package.core
org.package.extensions

```
Examples:

Project name - FibonacciSeriesProducer  

Package name - com.lazywithclass.utils, com.lazywithclass.entryPoint  

Class name - FibonacciLogic.java, FibonacciPrinter.java  

This is how I would have done it, maybe during development this will change a bit, the really important convention is naming convention for class names, see if this steps are of some help:

1. identifiy objects that you will need to solve the problem
2. Knowing what one class' purpose will be name it accordingly
3. Keep an eye on your class names, mantain them meaningful through the development

See [here](http://java.sun.com/docs/codeconv/html/CodeConventions.doc8.html) for some examples.