Q: Questions regarding Change Sets I am using Change Sets for the first time. In the past I have deployed with Eclipse. 
Right now, I am attempting to deploy an entire object. I would like to deploy everything involved with the object (fields ; page layouts ; validation rules ; field updates ; workflows ; email alerts etc...)
So, I add this Custom Object to my Change Set (we'll call it "ObjectX_c") but then when I press "View/Add Dependencies" I get a huge list of components which includes components whose Parent Object is not ObjectX_c. At first I thought these were possibly components which referred to ObjectX or that it referred to in some way, but that doesn't appear to be the case. 
So, is it up to me to fish through that list and pick only the components which have ObjectX as its Parent Object ?
Thank you very much for your help.

A: Yes, the Dependencies displayed sometimes cast a wider net than you'd like but are generally good for catching out stuff you may have missed.
You will need to pick the fields, layouts etc and make sure that you have a deploy-able change set.
If you realise that you've missed out stuff after deploying to the destination, you can clone the change set and add stuff to it and redeploy.
It is a bit manual so works best for discrete things rather than large scale deployments.

A: Change sets are great, primarily because they're way easier to deal with than Eclipse or ANT.  That said, building them can be like pulling teeth, and the dependency analyzer doesn't do much to narrow things down and may not really answer the true question of "what's related to this object".
When you're doing larger deployments, i.e. a whole object and all of it's related stuff, Eclipse and ANT will start to become preferred.  As an example, the following package.xml will get you all the object details, fields, record types, field sets, buttons, list views for a particular object.  For an object with a non-trivial amount of these building a change set (which requires choosing each individual field, record type, button, and list view) makes watching paint dry seem like a reasonable occupational choice.
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>YourObject__c</members>
        <name>CustomObject</name>
    </types>
    <version>29.0</version>
</Package>

