I like your workflow. It should lead to a decent result.
A few ideas here:
Let the designers know and understand your presentation model. What pages there are, what information and control elements will they have, what is the role of each of them, what is the purpose of the page and what message should it communicate to the user. If you let the designers work alone then they will design something to reflect their vision of the project and not your design. You'll end up redoing everything or trying to adapt one part to the other.
Users will only see and understand design. They know nothing of implementation. If they see a button they will think the feature is there. if you plan to go agile while cooperating with the users during development, hide out elements that are not implemented yet. Feed them results one step at a time.
If you can have users nearby do screen design together with them in iterations. There is not much work for designers yet, when you are basically deciding on the layout. All those colourful effects and polished buttons should be done after the layout is stable. Otherwise it will be a waste of the designers work.
I really like the model of extreme programming. When dealing with new products user requirements can quickly change over time and this is a proven method which keeps the design "up to date".
Have the users write up functions that they want for the application. And have the designers agree upon a general layout.
Write up a general wire-frame that both you and the user agree upon, I like to do this in smart draw or some sort of rapid gui development platform. (no functionality at this point).
Write the code for the GUI based upon the wire-frame and write sequence diagrams and class diagrams.
Based upon these design start to fill in the functionality behind the GUI
Release betas throughout the process of adding functionality to select users who can help guide future development
The benefit of this design is that at any point in time you can re-work the GUI and incorporate new functionality. The idea is to have a general plan at the beginning that can be adapted as user requirements change.
发布评论
评论（2）
我喜欢你的工作流程。它应该会带来不错的结果。
这里有一些想法：
让设计师了解并理解您的演示模型。有哪些页面，它们有哪些信息和控制元素，每个页面的作用是什么，页面的目的是什么以及它应该向用户传达什么消息。如果你让设计师单独工作，那么他们会设计一些东西来反映他们对项目的愿景，而不是你的设计。您最终将重做所有事情或尝试使一个部分适应另一部分。
用户只会看到并理解设计。他们对实施一无所知。如果他们看到一个按钮，他们会认为该功能就在那里。如果您计划在开发过程中与用户合作的同时变得敏捷，请隐藏尚未实现的元素。一次一步地向他们提供结果。
如果你能让附近的用户在迭代中与他们一起进行屏幕设计。当你基本上决定布局时，设计师还没有太多工作要做。所有这些色彩缤纷的效果和抛光的按钮都应该在布局稳定后完成。否则就浪费了设计师的工作。
I like your workflow. It should lead to a decent result.
A few ideas here:
Let the designers know and understand your presentation model. What pages there are, what information and control elements will they have, what is the role of each of them, what is the purpose of the page and what message should it communicate to the user. If you let the designers work alone then they will design something to reflect their vision of the project and not your design. You'll end up redoing everything or trying to adapt one part to the other.
Users will only see and understand design. They know nothing of implementation. If they see a button they will think the feature is there. if you plan to go agile while cooperating with the users during development, hide out elements that are not implemented yet. Feed them results one step at a time.
If you can have users nearby do screen design together with them in iterations. There is not much work for designers yet, when you are basically deciding on the layout. All those colourful effects and polished buttons should be done after the layout is stable. Otherwise it will be a waste of the designers work.
我真的很喜欢极限编程的模型。在处理新产品时，用户需求可能会随着时间的推移而快速变化，这是一种行之有效的方法，可以使设计保持“最新”。
，以选择可以帮助指导未来开发的用户。这种设计的好处是，您可以在任何时间点重新设计 GUI，并且合并新功能。这个想法是在一开始就有一个总体计划，可以随着用户需求的变化进行调整。
I really like the model of extreme programming. When dealing with new products user requirements can quickly change over time and this is a proven method which keeps the design "up to date".
The benefit of this design is that at any point in time you can re-work the GUI and incorporate new functionality. The idea is to have a general plan at the beginning that can be adapted as user requirements change.