BlogJava 联系 聚合 管理  

Blog Stats

随笔分类

随笔档案

文章档案


orange

今天在msn上跟chuanbo讨论component design,说到component和class有什么具体的区别。现在找到了一篇讲组件设计的小文章:

http://www.agilemodeling.com/artifacts/componentDiagram.htm

开头的那段话对上面那个问题尤其有用吧:

Component diagrams are particularly useful with larger teams.  Your initial architectural modeling efforts during cycle 0 should focus on identifying the initial architectural landscape for your system.  UML component diagrams are great for doing this as they enable you to model the high-level software components, and more importantly the interfaces to those components.  Once the interfaces are defined, and agreed to by your team, it makes it much easier to organize the development effort between subteams. You will discover the need to evolve the interfaces to reflect new requirements or changes to your design as your project progresses, changes that need to be negotiated between the subteams and then implemented appropriately.
posted on 2006-06-23 16:01 Ruth Cao 阅读(416) 评论(2)  编辑  收藏

评论

# re: UML 2 Component Diagrams 2006-06-23 23:07 Rain Liu
辛苦了,小曹。也辛苦了我,:(,最不喜欢看英文了。  回复  更多评论
  

# re: UML 2 Component Diagrams 2006-06-24 09:08 绿色使者、绿色心情
不喜欢也得看啊,IT最新资讯都是E文的啦
赫赫,应该比6级阅读要容易的
上面也就是组件设计是high-level的,目的是不同子项目的协调,也就是边界是项目间通用的组件,内部的就是使用类来协作了,不知这样理解是否正确?  回复  更多评论
  


只有注册用户登录后才能发表评论。


网站导航: