《软件工程翻译题--实施uml九项注意》由会员分享，可在线阅读，更多相关《软件工程翻译题--实施uml九项注意（8页珍藏版）》请在金锄头文库上搜索。
1、实施 UML 九项注意In the last quarter of 1997, I taught object-oriented analysis and design with UML to a wide range of developers working on various projects. The projects spanned application domains including retail shelf space management, pharmaceutical clinical trials, cellular telephony, and more. Imp
2、lementation languages included Visual Basic, C+, Java, DB2, and others. This article discusses several aspects of how well the UML notation, along with my companys use case-driven Unified Object Modeling process (also based on the methods of Booch, Jacobson, and Rumbaugh), met the demands of a diver
3、se set of projects. It provides practical guidance for tailoring your use of UML for various projects. 1997 年的最后一个季度，我在教一些来自不同项目的开发者使用 UML 作面向对象分析与实际。这些项目涉及许多应用领域包括零售货架空间管理，临床药物实验，移动电话等。开发语言包括 Visual Basic, C+, Java, DB2 还有其他。通过我们公司的用例驱动统一对象建模过程（是建立在 Booch, Jacobson, and Rumbaugh 方法的基础之上的）来从几个方面介绍UM
4、L 符号如何更好得满足不同项目的需求。为如何使用 UML 提供了实际的指导。The UML notation is big (maybe too big) and is flexible enough to aclearcase/ target=_blank ccommodate the needs of a very wide range of projects. To succeed with UML, you must streamline how you use it. Different projects will need different pieces. Which speci
5、fic elements of the UML notation you need for your project will depend on its nature (client/server with a mainframe RDBMS vs. real-time embedded, for example) and on the implementation language you will be using. Some detailed C+ design constructs are not needed if youre building in Java or Smallta
6、lk, and you may want to avoid too much use of generalization or inheritance if youre building in Visual Basic. Sometimes, the sheer volume of modeling constructs can be overwhelming, especially to those students who are new to object-oriented analysis and design. However, the good news is that you c
7、an model almost anything using UML. There are plenty of modeling constructs to go around. UML 的符号比较多（可能太多）而且足够灵活能适应大范围项目的需求。为了成功使用UML，在使用的过程中必须流程化。不同的项目需要不同的内容。项目中使用 UML 符号的哪些具体元素取决于项目的本质（使用关系数据库客户端/服务器端或实时嵌入式）及要使用的开发语言。使用 JAVA 或 Smalltalk 时一些详细的 C+设计组件将不会被使用；如果使用 VB，你可能想避免使用更多的泛化和继承。有时，纯粹的建模组件可能太庞大
8、了，尤其对那些刚开始接触面向对象分析和设计的学生来说。但是，好消息是几乎任何事情都可以使用 UML 来建模来实现。有很多建模组件可供使用。You Still Need a Process 过程仍然需要UML itself is only a notation; to build effective models, you still need a modeling process. There are many modeling approaches you can use with UML; the modeling language itself does not prescribe th
9、e process. My company has been successful teaching a slightly modified version of the Objectory process (derived from Ivar Jacobsons Object-Oriented Software Engineering: A Use Case Driven Approach, Addison-Wesley, 1992) that we developed as a synthesis of Booch/Rumbaugh/Jacobson several years prior
10、 to the advent of UML. Our approach places slightly more emphasis on identifying high-level static models (domain models) up front, in parallel with use cases. We then refine the static model iteratively and incrementally refine as we explore the use cases and dynamic models. UML 本身仅仅是一种符号，为了创建有效的模型
11、，仍然需要一个建模过程。使用 UML 有很多种建模方法；建模语言本身并不描述过程。在 UML 产生的几年前，我们一直把作了微小变化的 Objectory 过程（从 Ivar Jacobson 的 面向对象软件工程：一个用例驱动方法 而来，Addison-Wesley, 1992）作为 Booch/Rumbaugh/Jacobson 的综合来授课，并取得了成功。我们的方法将重点放在了区分更高层次的静态模型（域模型） ，同时也产生用例。然后我们精炼出静态模型，在开发用例和动态模型时反复精练。Whether you prefer using Objectory, Object Modeling Te
12、chnique, our ICONIX Unified Object Modeling process, or some other approach, its important to understand that UML is not a process, and that it is critically important to get your project team on the same page process-wise before undertaking a modeling effort. Once again, the size and bulk of UML (a
13、nd the overwhelming weight of documentation on notation as opposed to process) can make it easy to slip into analysis paralysis. Focusing the team on an understandable process that is supported by the UML notation can generally get the modeling effort underway. 或者你更倾向于使用 Objectory，对象模型方法，我们的 ICONIX
14、统一对象模型过程，或其他一些方法。在从事建模工作之前，理解 UML 不是一个过程是重要的。让项目组处于同一个开发阶段尤其重要。让项目组对 UML 有统一的理解使建模成功的保证。UML 的规模（文档符号的庞大相对于过程而言）很容易陷入“分析麻痹” 。关注项目组通过 UML 符号对过程的统一理解，能让建模更容易。Legacy Methods Are Important 过去的方法依然重要Many of my students ask whether developing an understanding of Booch, Jacobson, and Rumbaughs legacy method
15、s is still important. My answer is an emphatic yes. Just as knowing the symbols used for electronic circuit design doesnt eliminate the need to know circuit theory, understanding the notational aspects of UML doesnt eliminate the need to understand object modeling theory. Since UML represents the sy
16、nthesis of the works of Jacobson, Booch, and Rumbaugh, the original legacy methods are a rich source of this information. 我的大部分学生会问我理解 Booch, Jacobson, and Rumbaugh 过去的方法是否仍然很重要。我的答案是非常重要。就像知道电流设计并没有排除知道电路理论一样，虽然 UML 符号而不排除理解对象建模理论的必要性。自从 UML 代表了 Jacobson, Booch, and Rumbaugh三人方法的综合，但早期的方法是信息的来源。Keep It Simple 保持简单 Getting a project team to make effective use of UML is tricky. Team members will have varied experience with object-oriented analysis and design and UML. A
