Probably a bit off topic question, but it's something I'm really interested in getting to know from other people with different experience and backgrounds.
可能有点偏离主题问题,但这是我真正有兴趣从其他具有不同经验和背景的人那里了解的东西。
How do you keep track of your huge projects? Do you use subversion? EER-models? Do you write notes? Does all your faith lie in phpdoc? Which framework do you use, and which design pattern do you follow? A lot of questions, I know, and I don't expect you to answer ALL of them, just summarize whatever you want to emphasize the most.
你如何跟踪你的巨大项目?你使用颠覆吗? EER的模型?你写笔记吗?你的所有信仰都在于phpdoc吗?您使用哪个框架,以及您遵循哪种设计模式?我知道很多问题,而且我不希望你回答所有这些问题,只是总结一下你想要强调的内容。
Personally, I use subversion for source control, phpdoc, writing down personal notes for each model/controller etc and I'm almost always following the MVC-pattern.
就个人而言,我使用subversion进行源代码控制,phpdoc,为每个模型/控制器等写下个人笔记,我几乎总是遵循MVC模式。
Have a fantastic and automagic day! ;-)
有一个梦幻般的自动化日子! ;-)
3 个解决方案
#1
I would recommend on using the tools that work best for the people that you have, and the parts that are likely to be the most difficult to manage.
我建议使用最适合您的人的工具,以及可能最难管理的部件。
If you have a lot of requirements, use a tool which tracks requirements well.
如果您有很多要求,请使用能够很好地跟踪需求的工具。
If you have a lot of simple one-off projects, maybe simple project tracking works well.
如果你有很多简单的一次性项目,也许简单的项目跟踪效果很好。
#2
A great way to document your project (especially the high level stuff) is to have a wiki. The success of that obviously depends entirely on your teammates. If they hate writing prose then the whole idea is basically doomed from the start. But given the right people it can really pay off. A few wiki pages with a couple of diagrams can go a long way and oftentimes be way more expressive than any UML diagram and what-have-you (of course, the combination of both is even better :-) If you can get your testers and other people to join in, you're off to a good start. The more, the merrier.
记录您的项目(特别是高级别的东西)的一个好方法是拥有一个wiki。这一成功显然完全取决于你的队友。如果他们讨厌写散文,那么整个想法从一开始就基本上是注定的。但是如果有合适的人,它真的可以得到回报。一些带有几个图表的维基页面可以有很长的路要走,而且往往比任何UML图表都更具表现力,而且你有什么东西(当然,两者的组合更好:-)如果你能得到你的测试人员和其他人一起加入,你有一个良好的开端。越多越好。
One thing you forgot to mention in your post is a bug tracker. That is an absolute must-have, I am sure Joel has some good tips on which is the best software choice there ;)
您在帖子中忘记提及的一件事是错误跟踪器。这绝对是必须的,我相信Joel有一些很好的技巧,哪些是最好的软件选择;)
#3
You should a bug tracking software to record how each issue was resolve and tie it to your Subversion Repository so that you can see the issue that generated the check-in and the vice-versa. We use Fogbugz ourselves.
您应该使用错误跟踪软件来记录每个问题的解决方法,并将其与Subversion存储库联系起来,以便您可以看到生成签入的问题,反之亦然。我们自己使用Fogbugz。
#1
I would recommend on using the tools that work best for the people that you have, and the parts that are likely to be the most difficult to manage.
我建议使用最适合您的人的工具,以及可能最难管理的部件。
If you have a lot of requirements, use a tool which tracks requirements well.
如果您有很多要求,请使用能够很好地跟踪需求的工具。
If you have a lot of simple one-off projects, maybe simple project tracking works well.
如果你有很多简单的一次性项目,也许简单的项目跟踪效果很好。
#2
A great way to document your project (especially the high level stuff) is to have a wiki. The success of that obviously depends entirely on your teammates. If they hate writing prose then the whole idea is basically doomed from the start. But given the right people it can really pay off. A few wiki pages with a couple of diagrams can go a long way and oftentimes be way more expressive than any UML diagram and what-have-you (of course, the combination of both is even better :-) If you can get your testers and other people to join in, you're off to a good start. The more, the merrier.
记录您的项目(特别是高级别的东西)的一个好方法是拥有一个wiki。这一成功显然完全取决于你的队友。如果他们讨厌写散文,那么整个想法从一开始就基本上是注定的。但是如果有合适的人,它真的可以得到回报。一些带有几个图表的维基页面可以有很长的路要走,而且往往比任何UML图表都更具表现力,而且你有什么东西(当然,两者的组合更好:-)如果你能得到你的测试人员和其他人一起加入,你有一个良好的开端。越多越好。
One thing you forgot to mention in your post is a bug tracker. That is an absolute must-have, I am sure Joel has some good tips on which is the best software choice there ;)
您在帖子中忘记提及的一件事是错误跟踪器。这绝对是必须的,我相信Joel有一些很好的技巧,哪些是最好的软件选择;)
#3
You should a bug tracking software to record how each issue was resolve and tie it to your Subversion Repository so that you can see the issue that generated the check-in and the vice-versa. We use Fogbugz ourselves.
您应该使用错误跟踪软件来记录每个问题的解决方法,并将其与Subversion存储库联系起来,以便您可以看到生成签入的问题,反之亦然。我们自己使用Fogbugz。