ITM 305 Lecture Notes - Abstract And Concrete, Class Diagram, Cash Machine
DepartmentInformation Technology Management
Course CodeITM 305
This preview shows half of the first page. to view the full 3 pages of the document.
Goal-to write on or more collections of data processing computer instructions (computer
programs)which, upon execution, would either support the realization or realize a human recognizable
function such as sending an email message, adisplaying a picture on a screen or withdrawing money
from an automatic teller machine.
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.
Objects,classes and attributes-
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)
Attribute: holds the object data. It has a name, type, and a value
Operation:something an object can do
Associations in UML:
-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.
Aggregation and composition-
-------it is a whole-part association
-the part may exist independently of the aggregate
-the part can be associated with other aggregates(student is part of two different languages)----
------it is a strong aggregation
-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-------
You're Reading a Preview
Unlock to view full version