ITM 305 Lecture Notes - Abstract And Concrete, Class Diagram, Cash Machine
Document Summary
Softwware design approach that relies on the conception of abstract programming entities called objects that are given the responsibility of realizing through collaborations the behaviour specified by the use case model. An object is a person, thing or an event. (john, square, johns graduation) We define a class as an abstract entity that represents a group of objects. (eyes nose, legs, for people) It has a name, type, and a value. Defines a structural relationship that captures the possibility of navigating from one object to the next and vice versa(both can establish communication) The multiplicity(the name sometimes) practically feasible to show. The part may exist independently of the aggregate. The part can be associated with other aggregates(student is part of two different languages)---- The part can be associated with one and only one aggregate(called composite in this case) The lifecycle of the part is dependant on thatof the composite. If the composite is destroyed the part will be destroyed-------