从数据库设计首先通过对用户界面或水能捞到过来呢？ [英] Design from the database first through to UI or t'other way round?

问题描述

你总是在启动或规划一个新项目时，它偏向数据库架构的思维还是你走另一条路，并开始设计UI然后向下移动堆栈？

Do you always lean towards thinking of db schema when starting or planning a new project it or do you go the other way and start designing UI then moving down the stack?

或者你有开发不同的方式？

Or do you have a different way of developing?

不是一个真正的敏捷/瀑布/规格/故事质疑只是一个让个人/专业或其它项目时，人民路瘦肉上的手柄。

Not really an agile/waterfall/specs/stories question just a way of getting a handle on which way people lean when working on projects personal/professional or otherwise.

我已经决定了，无论是过去的最佳途径，并在UI第一阵营我目前但可以而且将改变！

I have decided that both are the best ways in the past and am currently in the UI first camp but that can and will change!

干杯
约翰·

推荐答案

我两者都做。我通常绘制出一个原型的屏幕将是什么样子，然后尝试开发从一个数据模型。而不是直接去一个数据库我觉得这作品很多与我，我也不会想到的，否则UI，我可以看到（在数据库或字段）属性需要更好的。从那里我可以开发模型和来回反弹，直到满足双方的要求的需求，然后我担心数据库模式。通常情况下，虽然模型本身将定义架构我，这样的照顾。

I do both. I typically draw out a prototype of what the screen will look like and then try to develop a data model from that. Instead of going directly to a database I find that this works a lot better as with my UI I can see the need for properties (or fields in a db) that I wouldn't have thought of otherwise. From there I then develop the model and bounce back and forth till the both suit the needs of the requirement and then I worry about database schemas. Typically though the model itself will define the schema for me so that's taken care of.

这篇关于从数据库设计首先通过对用户界面或水能捞到过来呢？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！