UML component diagram - interfaces and relationships
posted 7 years ago
Would it be ok to not define interfaces and relationships for all components in a component diagram? May be only for those components which serve more than function? Or would you advise me to remove all lollipops and sockets and keep regular associations like aggregation composition or realization and generalization?
I understand that this is more of a UML question but I would like to get an opinion from a 'SCEA assignment submission point of view'