Create an association between Lecture and Student. On the student end of the association, create an association end called "studentsAttending" having a multiplicity of 0..*. (I recommend you call that association end "attendingStudent" to be consistent with standards such as ISO 11179, BTW.)
You should probably give the other end of the association a name also, like "attendedLecture", with a multiplicity of 0..*.
Here's an example:
These association ends are properties, owned either by the class on the opposite side of the association or owned by the association. Here's some evidence of this from a UML 2 compliant tool:
When the max cardinality is > 1, the property typically gets a type that is some kind of collection in the technology. For an example in Java: List<Student> attendingStudent
. (Although in the technology layer, I prefer to pluralize such properties, which would make that List<Student> attendingStudents
.)
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…