开始开发大型网站的最佳方式是什么?

发布于 11-19 09:26 字数 1459 浏览 3 评论 0原文

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

西瑶2024-11-26 09:26:45

您的问题非常广泛,所以这里有一个同样广泛的答案。

与任何其他项目一样,无论大小:

  1. 弄清楚您的需求
  2. 将这些需求转换为功能的小规范
  3. 设计,实现并一一测试它们

一些额外的建议:

  • 我建议使用功能的“垂直切片”而不是比构建水平层。换句话说,不要构建一个 GUI,然后构建一个中间层,然后构建一个数据库层,并希望它们全部融合在一起。相反,一次构建一项功能,同时合并所有这些水平层的必要部分。

  • 使您实现的功能块尽可能小。做出许多渐进的改变并把它做好,比试图在一项改变中吞下超出你所能咀嚼的东西,然后把它搞得一团糟更好。

  • 首先构建基础,然后再完善它们。换句话说,在实现一个能歌善舞的 AJAX 支持的超级 GUI 之前,先使用基本控件获得核心功能。

  • 对出色的变更控制持迂腐态度。这确实值得费心。

Your question is very broad, so here's an equally-broad answer.

As with any other project, big or small:

  1. Figure out your requirements
  2. Transform those requirements into small specifications of functionality
  3. Design, Implement and Test them one by one

A few extra recommendations:

  • I recommend working with "vertical slices" of functionality rather than building horizontal layers. In other words, don't build a GUI, then a middle tier, then a database tier, and hope they all mesh together. Rather, build a piece of functionality at a time, incorporating the necessary bits of all of those horizontal tiers as you go.

  • Make the lumps of functionality you implement as small as you can. Better to make many incremental changes and get it right than try to bite off more than you can chew in one change, and make a hash of it.

  • Build the basics first, and then embellish them later. In other words, get the core functionality right using basic controls before you implement an all-singing, all-dancing AJAX-powered super-GUI.

  • Be pedantic about excellent change control. It really is worth the bother.

遮了一弯2024-11-26 09:26:45

我建议您首先写下使您的网站正常运行的主要要求,然后将主要要求分解为更小的部分,以及实现要求所需的条件。您还应该写下您认为完成每项要求需要多长时间。例如,可用性是一个主要要求。接下来将可用性分解为更小的方面,例如信息如何在您的网站上排列,您可以进一步分解。比估计您认为解决每个小方面的问题所需的时间,以及您为使网站可用而花费的总时间。在写下所有主要需求功能并估计每个功能的时间后。按照您希望首先完成的顺序排列它们。您应该将它们分为几个阶段,例如第 1 阶段创建您的网站,在该阶段下您将包括诸如托管服务类型、可用性等主要要求,第 2 阶段营销您的网站或让世界走出去,以及第 3 阶段维护您网站的。完成所有这些后,您可以开始为您的网站制作模型,然后转向 JavaScript 脚本和服务器端内容。希望我能帮上一点忙。确保将所有东西都视为对象,以及您需要为该对象提供哪些东西才能使其发挥作用。

I would Recommend you start by writing down major requirement that will make your site functional and from there on break does major requirements down to smaller pieces and what it will take to achieve does requirements. You should also write down how long you think it will take for you to complete each requirement. For example Usability is a major requirement. next break down usability into smaller aspect such as how is information arrange on your site, and you can break down that even more. than estimate the amount of time you think it will take for you to figure things out for each small aspect and than that will be your total time that will be spend on making your site usable. After you have written down all your major requirement function and estimated the time for each. arrange them in order that you want completed first. you should split them into phases like for example phase 1 creating you site and under that phase you would include such major requirement such as type of hosting service,usability and so, phase 2 marketing your site or getting the world out there and phase 3 maintenance of your site. after all that is done you can begin working on the mock-up for your site, and move to JavaScript scripting and server side stuff. Hope i helped a little.Make sure to think of everything as objects and what things do u need to give that object in order for it to function.

把时间冻结2024-11-26 09:26:45

设计是软件开发中最重要的步骤,项目越大,好的详细设计就越能帮助您并节省您的时间。尝试对网站的未来发展、主要功能是什么以及它们将如何工作有一个扎实的了解。预见这些事情很重要,这样你就可以提前看到一切是否有意义并且能够紧密地结合在一起。这样,您就不会遇到问题,也不会浪费大量时间编写无法解决问题的代码。最好在设计时而不是在代码时解决这些问题。获取您的项目的功能列表并写下您计划如何实施它们。至于从代码的何处开始,从一些基本的数据层功能开始,例如打开/关闭数据库连接、创建用户和用户权限,然后一次一页。

Design is the most important step in software development, and the bigger the project, the more good detailed design is going to help you and save you time. Try to get a solid idea of how the site is going to be and what the main features are and how they are going to work. It is important to foresee these things so that you can see ahead of time if everything is going to make sense and function together cohesively. That way you don't run into problems down the line and possibly waste lots of time coding something that isn't going to work out. Its best to get the kinks out in design time rather that in code time. Get a features list for your project and write out how you plan on implementing them. As far as where to start in code, start with some basic data layer functions, like opening/closing database connections, creating users and user privileges, and then take it one page at a time.

冰之心2024-11-26 09:26:45

我将首先回顾一下本次会议的会议:

http://www.waterfall2006.com/

I would get started by reviewing the sessions from this conference:

http://www.waterfall2006.com/

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文