1 Essential Object-Oriented Design(3)

consists of set of objects that interacts through a set of messages or method invocations. Throughout a system's lifetime objects gets created and garbage collected, thus a system is very dynamic in both its behaviour and con guration. Even with small or m

gramming languages and conceptual programming 6]. The model in Figure 1 can be applied to describe conventional object-oriented technology. A class describes a concept exempli ed by a set of phenomena described by a set of objects. A class can be composed of (references to) other class descriptions, and classes can be parts of generalization hierarchies.3.1 Basic Model

component types can be related in generalization hierarchies. following mechanisms and situations: object creation, object deletion, and method invocation (message sending). Events are classi ed by event types. An event type describes the participating component roles. Event types can be part of generalization and aggregation hierarchies. In this way a single event can be an abstraction over a large number of method invocations or object creations. When choosing the events and the components for the description of a system it is important that the selections support each other. I.e. that the events makes sense on the chosen components, and vice versa. The chosen components and events are the common abstract basis for the description of the system architecture.

Events An event is an abstraction over the

搜索“diyifanwen.net”或“第一范文网”即可找到本站免费阅读全部范文。收藏本站方便下次阅读，第一范文网，提供最新人文社科1 Essential Object-Oriented Design(3)全文阅读和word下载服务。