Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I want to know what it would be if I had a Ticket that holds one TicketType but a ticket type can be part of many Tickets.
Would the relationship be an Aggregation, where the open diamond is at the Ticket class, or is it an association where the arrow is pointing to the TicketType?
My first thought was “Who cares?” You’re trying to express a relationship between two objects for yourself or other developers. You can’t even articulate the difference; what are the chances that others will be able to do it?
The association with open diamond says the Ticket owns a TicketType, but the type isn’t deleted if the Ticket goes away.
I’m not sure what additional information this provides over and above the simple arrow for association.
I think it’s important not to be too hung up on these things. Don’t get too carried away with UML.