IC-Modeling with UML知识讲稿.ppt

* Passenger PurchaseSingleTicket PurchaseMultiCard NoChange extend Cancel extend include CollectMoney include include Relationships * Class Diagram Class diagrams represent the structure of the system. Class diagrams are used during requirements analysis to model problem domain concepts during system design to model subsystems and interfaces during object design to model classes. * A Class Diagram Enumeration getZones() Price getPrice(Zone) TariffSchedule * * Trip zone:Zone price:Price * Class A class represent a concept. A class encapsulates state (attributes) behavior (operations). Each attribute has a type. Each operation has a signature. The class name is the only mandatory information. * A Class zone2price getZones() getPrice() TariffSchedule Table zone2price Enumeration getZones() Price getPrice(Zone) TariffSchedule Name Attributes Operations Signature * Instance An instance represents a phenomenon. The name of an instance is underlined and can contain the class of the instance. The attributes are represented with their values. * An Instance zone2price = { {‘1’, .20},{‘2’, .40}, {‘3’, .60}} tariff_1974:TarifSchedule * Actor, Class, Instance Actor: An entity outside the system to be modeled, interacting with the system (“Pilot”) Class: An abstraction modeling an entity in the problem domain, inside the system to be modeled (“Cockpit”) Object: A specific instance of a class (“Joe, the inspector”). * Association Associations denote relationships between classes. The multiplicity of an association end denotes how many objects the source object can legitimately reference. * An Association Enumeration getZones() Price getPrice(Zone) TarifSchedule * pricezone TripLeg * * Associations 1-to-1 association 1-to-many association * draw() Polygon x:Integer y:Integer Point 1 Has-capital name:String Country name:String City 1 1 * Aggregation An aggregation is a special case of association denoting a “consists of” hierarchy. The aggregate is the parent class, the