GIS设计6面向对象与设计.ppt

(2). 用活动图来说明具体的工作流程。 例2：用活动图对操作建模的例子：用活动图描述类Line的操作intersection的算法。 * COM interfaces Developing with COM means developing using interfaces. All communication between COM components happens via the components’ interfaces. Interfaces are standardized by COM rules, so it does not matter what language is used to create a class. Interfaces help a class evolve over time because new interfaces can be added. However, once an interface is added, it can never be removed. The actual implementation can be altered (e.g., an algorithm can be updated without breaking any third party developer code), but the interface is permanent. Why interfaces? Some object-oriented programming languages use only classes and objects without interfaces. Problems can arise when a class needs to be updated and code changes. As the class and its code evolve, client code could become obsolete, and any client code using the class (instantiating it and using its properties and methods) may be caused to fail. For example, imagine a car dealer installing the latest stereo in your car. The new stereo has an AM/FM radio and a CD player. But what if you own cassettes, not CDs? Programming with interfaces would allow the dealer to install the new CD interface without changing or removing the cassette interface. Interfaces solve this problem of evolving code. Once written, code for an interface never changes; therefore, client code is less likely to break. The client code can assume an interface will never change. If the class needs to be reprogrammed, new interfaces are created. The class evolves without causing headaches for the existing client code. When a new interface comes out, the class stays the same, but the client can interact with the class through the newest interface. * In building a visual model of a system, many different diagrams are needed to represent different views of the system. The UML provides a rich notation for visualizing our models. This includes the following key diagrams: Use-Case