第一个网站项目如何指定网站 UI 和网站时的互操作性和易于集成性后端是否由单独的开发人员开发？
我想使用 Elance.com 寻找开发人员为我创建一个网站。
我决定将开发分为两个部分：
UI 和后端，每个都由单独的开发人员开发。
后端使用的技术将是Spring MVC、Java、iBatis、MySQL/Derby/H2。
前端使用的技术将是JSTL
是否有任何模式可以对这样的项目进行分区？
如何指定项目以便 UI &后端能够互操作并且易于集成吗？
谢谢
I would like to use Elance.com to find a developer to create a website for me.
I have decided to split the development into two components:
the UI and the back-end, with each being developed by separate developers.
The technologies to be used for the back-end will be Spring MVC, Java, iBatis, MySQL/Derby/H2.
The technologies to be used for the front-end will be JSTL
Are there any patterns for partitioning a project like this?
How do I specify the project so that UI & backend will interoperate and be easy to integrate?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
别把它分开。你说：
无论您认为您正在创建的新网站有多独特，其中已经有一些网站了。您需要关心的不仅是网站的创建，还包括您将如何推广服务以及您可能通过服务添加的网站之外的任何附加价值。
如果这个项目和你想象的一样好，其他人无论如何都会克隆它 - 如果他们有经验，那么他们的成本将比你选择的任何“随机”团队少得多......他们会这样做，没有来源。它超越了网站，是整个服务以及业务带来的一切。
诗。找到一个好的团队，将项目分解为可以在一切完成之前发布到生产的功能部分......一个好的团队应该帮助您构建它，以便您每周（或每两周）看到进展。
Don't split it. You said:
It doesn't matter how unique you think that new site you are creating is, there are already some of those out there. Its not only the creation of the site that you need to be concerned with, but also how you will promote the service and any additional value that's beyond the site that you might add with your service.
If the project is as good as you think it is, other people will clone it anyway - and if they are experienced it will cost them a lot less than any 'random' team u pick ... they will do so, without the source. Its beyond the site, is the whole service and everything that comes with the business.
Ps. find a good team, break the project into functional pieces that can be published to production before everything is complete ... a good team should help u structuring it so u see progress weekly (or bi-weekly).
当不同的开发人员在同一个项目上一起工作以进行交互和通信时，这已经够困难的了。当您似乎没有足够的经验来独自维持项目时，我不确定为什么您会希望通过拆分开发来使项目变得更加困难。尽管将开发一分为二以提高效率听起来很诱人，但我认为风险要高得多，并且最终可能会花费更长的时间，除非您运气好并找到真正优秀的开发人员。
我建议你集中精力寻找一个能够同时完成后端和前端的后端开发人员。您可能想查看后端开发人员是否认识可以分包该项目部分的前端开发人员。至少，如果他们以前合作过，那么你们的沟通问题可能会减少。最好看看您是否能找到一家能够承担整个项目的小型软件开发商店。
从某种意义上说，我会把这比作一个家居装修项目。如果您有足够的经验并且知道如何自己完成这项工作，但没有时间，您可以担任自己的总承包商并协调分包商的工作。如果没有，那么您最好找到一个可以运行该项目的优秀总承包商（软件开发商店）。如果没有，那么至少您会想为工作中最困难的部分找到最好的承包商，并让该人负责整个项目，这样您就只需与一个人打交道。
It's hard enough when you have different developers working together on the same project to interface and communicate. I'm not sure why you would want to make your project harder by splitting the development, when you seemingly don't have enough experience to hold the project together on your own. Even though it sounds tempting to split the development in two to gain some efficiency, I think the risk is significantly higher and it may ultimately make it take longer unless you luck out and find really excellent developers.
I suggest that you concentrate on find a developer for the backend who may be able complete both the back end and front end. You might want to see if the backend developer knows any frontend developers who could subcontract that portion of the project. At the very least if they have worked together previously you may have less communication issues. Even better see if you can find a small software development shop that may be able to take on the whole project.
In some sense I would liken this to a home improvement project. If you have enough experience and know how to do the job yourself, but don't have the time, you could work as your own general contractor and coordinate the work of the subcontractors. If not, then you're probably better off finding a good general contractor (software dev shop) who can run the project. If not, then at least you'd want to find the best contractor for the hardest part of the work and put that person in charge of the whole project so you only have to deal with one person.