A little late here, but throwing tables together is database design. Not good design, but it's design.
Doing a design well means looking at the things Jeff has mentioned. I'd mention that database modeling would include looking at the problem and then deciding which entities or objects are required and how they might be broken into separate tables. The design would involve breaking those down to the actual columns, fields, indexes, etc.