In the top diagram, the arrows indicate an association. This means that a Customer can have many Orders, and an Order can have one Customer. Since there is an arrowhead at each end, it means that the relationship is "bi-directional" meaning that each class has a reference to the other (each class "knows about" the other).
The corresponding classes might look like this:
public class Order
{
public Customer Customer {get;set;}
// Other order properties
}
public class Customer
{
public List<Order> Orders {get;set;}
// Other Customer properties
}
In the second diagram, the filled diamond represents "Composition." This is a more specific type of a relationship. Composition is usually compared to "aggregation," which would be an open diamond.
With the filled diamond (composition), it means that an Order has a "strong life-cycle" dependency on the Customer class. A common way of understanding Composition is saying that one class "owns" another. In this case, you would say that the Order "owns" the Customer, which doesn't really make sense, so I think it might be a bad example. Really, it's the Customer that should own the Order, so I think the filled diamond should be on the other side of the relationship.