Code,Diagram and Model

yhwebus

于 2005-03-16 10:36:00 发布

阅读量1k

点赞数

分类专栏：软件过程

本文链接：https://blog.youkuaiyun.com/yhwebus/article/details/320786

版权

软件过程专栏收录该内容

10 篇文章

订阅专栏

"Always remember that the model is not the diagram. The diagram's purpose is to help communicate and explain the model. The code can serve as a repository of the details of the desgin" --- <<DDD>>

yhwebus

博客等级

码龄23年

63
原创

0
点赞

1
收藏

1
粉丝

关注

私信

分类专栏

BizTalk 13篇
分析架构 19篇
心得随笔 25篇
语言技术 6篇
软件过程 10篇

最新评论

Model confusion : Domain Model & E-R Model
chuck911: 受益匪浅~谢谢了！
一月杂记
Evan: "在业务逻辑层，一定不要产生对权限的倚赖性" ---- bs一下, 如果业务就是和权限相关,哪能?
OO Puzzle(2)
Evan: JavaEye上面的讨论 http://forum.javaeye.com/viewtopic.php?t=12428
Model confusion : Domain Model & E-R Model
Evan: 可见 UML表示的ER图和RUP里面最早分析出的领域模型是不一样的.虽然非常接近,但前者属于数据建模的范畴，后者属于对象建模的范畴.我想,前者易造成混淆,是不值得推荐的
Model confusion : Domain Model & E-R Model
Evan: Fragment of preface in <<Analysis Pattern>> ----------------- This is an object-oriented book, and I do not hesitate in proclaiming my belief that the object-oriented approach is the superior way to develop software. These models, however, are primarily conceptual models, and many data modelers have had a long tradition of using conceptual (or logical) models. Data modelers should find many of the patterns useful, particularly if they use more advanced semantic techniques. The object-oriented features of the models will reveal many of the differences between object-oriented and traditional approaches. I would encourage such readers to use this book in conjunction with an OO analysis book that stresses the conceptual side of modeling and the links between OO and semantic data modeling.