Composition for Functional Depedencies
In a relational model, CC would be redundant, it's like saying that 1 = 1 * 1.
Using a real example, if A = person ID, B = person fingerprint, C = person name,
then you would say that "given a person ID and fingerprint, the name of a person is Bob, Bob is the name of the person".
Thus, I would argue that AB -> CC and AB -> C are equivalent, and the composition AB -> CC is not necessary.

given both A -> C and B -> C, then If you know did a search for "Bob" in the database, you would get both results for person ID's and person fingerprints. If fingerprints are stored together with person ID's, this means that your search result has one redundant entry for every result. Therefore it is much better design to only have the relation A -> C or B -> C to reduce the number of lookups. If A and B are in seperate entities, however, you might want both relations.

If you only specify AB -> C, you would not be able to use A -> C or B -> C, which are both true. Therefore you should not put this statement alone. However, if A -> B and B -> A, it might be valid, but usually inefficient. Now, to find AB given C (searching for all relations that match "Bob"), you need to lookup both person ID and person fingerprint, and match these two together (checking if A -> B or B -> A). It is faster to just check one attribute (look for only A or B, not both).