Added idea for new design (not UI).
Added License.
Fixed new line.
Added a TODO.
Added notice for Derby.
Modified design.
Ignores log files.
Fixed tables.
Added an idea.
Added TODO and formatted source.
Added idea about a new dictionary.
Decided how to develop. Beware! So many red lines in Eclipse!
Moved dictionary files to one directory.
Fresh commit

I know this is a very bad practice to do many things in 1 commit. I read an
article about commits, and I will be careful and try to get used to following
a good habit. However, there were too many things that has been changed before
I read that article, so this commit is a mess.
Here is a list of things that has been changed in this commit.
* Add UML diagram
* Modify .gitignore to ignore Apache Derby dir, autosave file from Dia
* Add classes according to the UML diagram
* Add Tester that currently tests the Records class
Change variables regarding connection to database constant

Driver, protocol, and the database file name will not change throughout the
execution of the program. Thus, it is safer to make these private constants.
Change visibility of Statement variable

This variable is often used in the child classes, for example, when executing
a query. Therefore, it was considered better to make this protected, allowing
access only from child classes instead of adding a getter method. However,
adding a getter method is a possibility as further development is done.
Fix bug where tables are not recognized as existing even when they do

The cause of this was because hard coded lower-case names were used for creating tables,
but Derby automatically converted the table names to upper-case. Solutions to
this bug were to use upper-case table names and make sure that the table name
is upper-case by converting them intentionally in the constructor.
Add getter method for variable tableName

Considering the possibility of tableName being modifiable in the future,
a better choice was to use getter instead of making tableName a public variable.
Add abstract methods to the parent class

These 4 methods are used to execute the basic four SQL commands using proper
classes. It might be a better choice not to make these abstract and implement the
four methods in the Database class.
Add method that formats a String specefically for INSERT SQL command

Due to the fact that the INSERT command needs the format (columnNames, ...)
VALUES (val, ...) it was considered better to split the formatting part to a
different method instead of clattering the insert method with the formatting.