Topic: 忽然间我感到了一点困惑:设计与实践(框架)

  Print this page

1.忽然间我感到了一点困惑:设计与实践(框架) Copy to clipboard
Posted by: worldcreatxr
Posted on: 2004-07-14 07:35

忽然间我感到了一点困惑:设计与实践(框架)
如何才能进行正确地设计,使得设计不倚赖于框架,但实施的时候又能用上框架?
也许我说的还不太清楚,我不知应怎么问,请大家多多指教,谢谢

2.Re:忽然间我感到了一点困惑:设计与实践(框架) [Re: worldcreatxr] Copy to clipboard
Posted by: heaven
Posted on: 2004-07-14 11:46

我的理解:你说的设计也许是指业务分析(business analysis),它当然不应该考虑框架。

3.Re:忽然间我感到了一点困惑:设计与实践(框架) [Re: worldcreatxr] Copy to clipboard
Posted by: spi_cn
Posted on: 2004-07-14 19:28

个人理解:信息系统的建设包括两个大过程,一个是需求分析阶段的“分”过程,即将系统黑盒子分解成“过程 + 数据(sa)”或者“对象(oo)”,该阶段oo特别适合,类似于庖丁解牛;另一个是设计阶段的“合”过程,即将前一阶段的“过程+数据”或者“对象”与应用环境(j2ee或.net)结合起来,该阶段适合采用框架、模式,类似于建筑工程中的采用模具来成模。

4.Re:忽然间我感到了一点困惑:设计与实践(框架) [Re: worldcreatxr] Copy to clipboard
Posted by: yolaiyoqu
Posted on: 2004-09-23 10:10

设计分为两个阶段,概要设计和详细设计,概要设计当然最好不考虑框架,详细设计是不能不考虑框架的--个人之见

5.Re:忽然间我感到了一点困惑:设计与实践(框架) [Re: worldcreatxr] Copy to clipboard
Posted by: LuckyReport
Posted on: 2004-09-23 15:09

你的定义比较奇怪
你说的框架是不是象STRUTS之类的东东?
我认为这东西在你实践的时候自然会考虑到,在总体设计时,不会去过多考虑

6.Re:忽然间我感到了一点困惑:设计与实践(框架) [Re: worldcreatxr] Copy to clipboard
Posted by: floater
Posted on: 2004-09-23 22:24

This is a very good question.

The short answer is, nobody knows.

If I tell you something is right, something else is wrong. You can pick it up quickly. For example, most of jdk APIs are in this categories. It's black and white, easy to make a judgement. However, design is not as easy as this, it's kind of grey. This is where we need/build up experience. We want to make our designs as much independent of any concrete tools as possible, but we still have to build it based on something concrete. So the question is where to draw the line between these two. MDA is on the way to solve this problem, but still no there yet. This is a very hard problem because almost every design is different and thus it's hard to see the common patterns. Every design is an abstraction of something in the real world, solving this problem requires another abstraction of those design, so there are two levels of abstractions.

In my practice, I pay special attention and efforts on drawing the line between design and implementation, both at the design level and implementation level, since I found, there are some issues which exist between design and implementation levels but disappear at the design level(Lewis Ship, the tapestry guy, once noticed this too in his weblog, others noticed this much earlier).

MDA is a good starting point for this question, but is far from solving it. Experience still dominates this grey area, although there are certain rules we can follow in certain specific areas.

my 2cents


   Powered by Jute Powerful Forum® Version Jute 1.5.6 Ent
Copyright © 2002-2021 Cjsdn Team. All Righits Reserved. 闽ICP备05005120号-1
客服电话 18559299278    客服信箱 714923@qq.com    客服QQ 714923