UML基本架构建模--类的通用建模技术(一).docVIP

UML基本架构建模--类的通用建模技术(一).doc

  1. 1、本文档共5页,可阅读全部内容。
  2. 2、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
  5. 5、该文档为VIP文档,如果想要下载,成为VIP会员后,下载免费。
  6. 6、成为VIP后,下载本文档将扣除1次下载权益。下载后,不支持退款、换文档。如有疑问请联系我们
  7. 7、成为VIP后,您将拥有八大权益,权益包括:VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
  8. 8、VIP文档为合作方或网友上传,每下载1次, 网站将根据用户上传文档的质量评分、类型等,对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档
查看更多
UML基本架构建模--类的通用建模技术(一).doc

Modeling the Vocabulary of a System 为系统的词汇表建模 You’ll use classes most commonly to model abstractions that are drawn from the problem you are trying to solve or from the technology you are using to implement a solution to that problem. Each of these abstractions is a part of the vocabulary of your system, meaning that, together, they represent the things that are important to users and to implementers. 你可以使用最常用的类为抽象建模,这些抽象来自你正在尝试解决的问题或是使用实现一个解决这个问题的技术.这些抽象的每一个都是系统词汇的一部分.同时这意味着,它们代表的是那些对用户和实施者很重要的事情. For users, most abstractions are not that hard to identify because, typically, they are drawn from the things that users already use to describe their system. Techniques such as CRC cards and use case-based analysis are excellent ways to help users find these abstractions. For implementers, these abstractions are typically just the things in the technology that are parts of the solution. 对用户来说,大多数的抽象事物并不难识别,因为,通常它们来自用户在描述它们的系统时已经使用过的事物.像CRC卡技巧和基于用例分析的技巧都是帮助用户寻找这些抽象事物的很好的方法.对于实施者来说,这些抽象事物,通常仅是技巧的一部分. To model the vocabulary of a system, 为构建系统的词汇表模型,需要做的事有: Identify those things that users or implementers use to describe the problem or solution. Use CRC cards and use case-based analysis to help find these abstractions. 识别那些用户和实施者使用描述问题和答案的事物.使用CRC卡和基于用例分析来帮助寻找这些抽象. For each abstraction, identify a set of responsibilities. Make sure that each class is crisply defined and that there is a good balance of responsibilities among all your classes. 为每个抽象标识一组职责.确保每个类清晰地被定义,这能很好的平衡你所有类之间的职责. Provide the attributes and operations that are needed to carry out these responsibilities for each class. 为每个需要执行这些职责的类提供属性和操作. Figure 4-9 shows a set of classes drawn from a retail system, including Customer, Order, and Product. This figure includes a few other related abstractions drawn from the vocabulary of the problem, such as Shipment(used to track orders), Invoice(used to bill orders), and Warehouse(where products are located prior to shipment). There is also one solution-related abstract

文档评论(0)

aiwendang + 关注
实名认证
文档贡献者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档