This sounds very ambitious, but I'm sure it's possible. Unfortunately, I've forgotten a bit of System Analysis, but do adhere to many of its guiding principles for my own projects. In fact, I would say that most data-driven Web sites are excellent candidates for Systems Analysis and should be used always during Web planning for any project you plan on putting into production.
Straight from the wiki:
The development of a feasibility study, involving determining whether a project is economically, socially, technologically and organizationally feasible.
Conducting fact-finding measures, designed to ascertain the requirements of the system's end-users. These typically span interviews, questionnaires, or visual observations of work on the existing system.
Gauging how the end-users would operate the system (in terms of general experience in using computer hardware or software), what the system would be used for etc.
For the first point, I would analyze different technologies such as ASP.NET, Ruby on Rails and PHP. Each technology has its strengths and weaknesses. One key thing to keep in mind is if you plan on making your social network free, you may consider open source technologies over proprietary - as many servers and application frameworks for proprietary projects are costly. I would also consider Web startup and hosting fees. If you plan on getting a reseller account with Host Gator, then you would need to factor in monthly billing costs. If you plan to host your own servers, you may be amazed at the cost of doing so. For a truly stable system, you would need to put a lot of work and cash into managing your own Web servers.
For the second point, you could probably locate plenty of information on user requirements from similar sites - just check out forums for DIY social networks and see what people are having issues with in the Technical Support section. Obviously, looking into technology based articles and magazines would be a good place to search on end user expectations - or even just joining Facebook and Twitter - see what they are doing since people seem content.
For the third point, again you can consult your competition and see how the user interface works out. Is it easy to use? Is it difficult in some aspects? If you had to use their system for 8 hours a day at least 5 days a week, what would drive you mad and how would you do it better? And keep in mind logical work flow as well. Knowing your user base is important too. In some systems, you may be developing for other programmers. Using strong jargon may be fine, but for a social network you must remember that they aren't familiar with Web site data flow and terminology. So your controls should still make sense to a computer novice and still work securely (don't forget system security too!) and in an organized fashion.
Finally, remember that things happen. I recently created a back-end site for a client of mine. I though the system worked very well - and they were very pleased, but I just got an email today that they want the way order items are stored to work differently. This is why there's a maintenance aspect to the System Development Life Cycle - things change after you finish deploying. It could also be said that if I had communicated with my client's needs more closely, this could have been resolved. Fortunately, the change is relatively minor, and we do live in a real world where things don't always work as we expect. We just do our best :)
As I said earlier, Systems Analysis is a lot of work and should be. The point of it is to determine that what you are trying to accomplish is feasible and practical without committing to a long term project that could span years. And always remember that no plan is perfect. If there were perfect plans, we wouldn't need new systems :).
发布评论
评论（1）
这听起来非常雄心勃勃，但我确信这是可能的。不幸的是，我忘记了一些系统分析，但在我自己的项目中确实遵守了它的许多指导原则。事实上，我想说大多数数据驱动的网站都是系统分析的优秀候选者，并且应该在您计划投入生产的任何项目的 Web 规划期间始终使用。
直接来自 wiki：
研究，涉及确定是否
一个项目具有经济、社会、
在技术和组织上
可行的。
措施，旨在确定
系统的要求
最终用户。这些通常跨越
访谈、问卷调查或
对工作的视觉观察
现有系统。
最终用户将操作系统
（就一般经验而言
使用计算机硬件或
软件），系统是什么
对于
第一点，我会分析不同的技术，例如 ASP.NET、Ruby on Rails 和 PHP。每种技术都有其优点和缺点。要记住的一件关键事情是，如果您计划使您的社交网络免费，您可能会考虑开源技术而不是专有技术 - 因为专有项目的许多服务器和应用程序框架都很昂贵。我还会考虑网络启动和托管费用。如果您计划获得 Host Gator 的经销商帐户，那么您需要考虑每月的账单费用。如果您计划托管自己的服务器，您可能会对这样做的成本感到惊讶。对于一个真正稳定的系统，您需要投入大量的工作和金钱来管理您自己的 Web 服务器。
对于第二点，您可能可以从类似网站找到有关用户需求的大量信息 - 只需查看 DIY 社交网络论坛，并在技术支持部分查看人们遇到的问题。显然，研究基于技术的文章和杂志将是搜索最终用户期望的好地方 - 甚至只是加入 Facebook 和 Twitter - 看看他们在做什么，因为人们似乎很满意。
对于第三点，您可以再次咨询您的竞争对手，看看用户界面的效果如何。使用起来方便吗？在某些方面是不是很困难？如果您必须每天使用他们的系统 8 小时，至少每周使用 5 天，什么会让您发疯？您会如何做得更好？还要记住逻辑工作流程。了解您的用户群也很重要。在某些系统中，您可能正在为其他程序员进行开发。使用强烈的术语可能没问题，但对于社交网络，您必须记住他们不熟悉网站数据流和术语。因此，您的控件对于计算机新手来说仍然应该有意义，并且仍然可以安全地工作（也不要忘记系统安全性！）并且以有组织的方式。
最后，记住事情总会发生。我最近为我的一个客户创建了一个后端网站。我认为该系统运行良好 - 他们非常高兴，但我今天刚刚收到一封电子邮件，他们希望订单项目的存储方式以不同的方式工作。这就是系统开发生命周期中存在维护方面的原因 - 完成部署后事情会发生变化。也可以说，如果我更密切地与客户的需求沟通，这个问题本来是可以解决的。幸运的是，这种变化相对较小，而且我们确实生活在一个现实世界中，事情并不总是按照我们的预期进行。我们只是尽力而为:)
正如我之前所说，系统分析是一项繁重的工作，而且应该如此。重点是确定您想要完成的事情是可行且实用的，而无需致力于可能跨越数年的长期项目。永远记住，没有一个计划是完美的。如果有完美的计划，我们就不需要新系统了:)。
This sounds very ambitious, but I'm sure it's possible. Unfortunately, I've forgotten a bit of System Analysis, but do adhere to many of its guiding principles for my own projects. In fact, I would say that most data-driven Web sites are excellent candidates for Systems Analysis and should be used always during Web planning for any project you plan on putting into production.
Straight from the wiki:
study, involving determining whether
a project is economically, socially,
technologically and organizationally
feasible.
measures, designed to ascertain the
requirements of the system's
end-users. These typically span
interviews, questionnaires, or
visual observations of work on the
existing system.
end-users would operate the system
(in terms of general experience in
using computer hardware or
software), what the system would be
used for etc.
For the first point, I would analyze different technologies such as ASP.NET, Ruby on Rails and PHP. Each technology has its strengths and weaknesses. One key thing to keep in mind is if you plan on making your social network free, you may consider open source technologies over proprietary - as many servers and application frameworks for proprietary projects are costly. I would also consider Web startup and hosting fees. If you plan on getting a reseller account with Host Gator, then you would need to factor in monthly billing costs. If you plan to host your own servers, you may be amazed at the cost of doing so. For a truly stable system, you would need to put a lot of work and cash into managing your own Web servers.
For the second point, you could probably locate plenty of information on user requirements from similar sites - just check out forums for DIY social networks and see what people are having issues with in the Technical Support section. Obviously, looking into technology based articles and magazines would be a good place to search on end user expectations - or even just joining Facebook and Twitter - see what they are doing since people seem content.
For the third point, again you can consult your competition and see how the user interface works out. Is it easy to use? Is it difficult in some aspects? If you had to use their system for 8 hours a day at least 5 days a week, what would drive you mad and how would you do it better? And keep in mind logical work flow as well. Knowing your user base is important too. In some systems, you may be developing for other programmers. Using strong jargon may be fine, but for a social network you must remember that they aren't familiar with Web site data flow and terminology. So your controls should still make sense to a computer novice and still work securely (don't forget system security too!) and in an organized fashion.
Finally, remember that things happen. I recently created a back-end site for a client of mine. I though the system worked very well - and they were very pleased, but I just got an email today that they want the way order items are stored to work differently. This is why there's a maintenance aspect to the System Development Life Cycle - things change after you finish deploying. It could also be said that if I had communicated with my client's needs more closely, this could have been resolved. Fortunately, the change is relatively minor, and we do live in a real world where things don't always work as we expect. We just do our best :)
As I said earlier, Systems Analysis is a lot of work and should be. The point of it is to determine that what you are trying to accomplish is feasible and practical without committing to a long term project that could span years. And always remember that no plan is perfect. If there were perfect plans, we wouldn't need new systems :).