先从数据库设计到 UI 还是其他方式? [英] Design from the database first through to UI or t'other way round?

问题描述

在开始或规划一个新项目时，您是否总是倾向于考虑 db schema，还是走另一条路，开始设计 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.

这篇关于先从数据库设计到 UI 还是其他方式?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！