UML, associations and persistence of data

Question

Well, while studying UML (just started) I came across the following problem. I think it's something that has a very simple answer for someone with a medium knowledge of UML and OO.
So, suppose I want to model an Employee-Company class association. Each employee works for 1 company, and, of course, a Company has 1..* Employees. If I model this simple class association using a UML tool the following Java code is generated.
public class Employee {
    public Company company;
public class Company {
    public java.util.Collection employee = new java.util.TreeSet();
}Of course in a real scenario, the association between a Company and its Employees should be persistent, with Employees residing on a DB. I have seen a lot of such examples (i.e. School-Student, Gym-Customer.....).
What's the way to really implement such things?
Generally speaking how are class associations with a "more than 1" multiplicity at one of the ends of the relationship implemented?
Thanks in advance.

Answer 1

cleanzero wrote:
yawmark wrote:
cleanzero wrote:
Ok, so suppose that we all agree, without entering into specific details, that a DB is needed, in terms of UML how is this represented?In what, a class or sequence diagram? It isn't. The class (or object) that interacts with the database, however, could be.
~At class level. Is it, as I've done, a Employee * <-> 1 Company association?That's one way. It all depends on your problem. Sounds like that is correct for your case.
Your object model for the business process doesn't have to know or care whether or not objects persist. Get the classes, relationships, and sequences right first. Persistence can be added later.
%