学习如何分析项目 [英] Learning how to analyse a project

问题描述

我刚接触到为我公司的一位客户(SMB)分析项目的工作.我是.Net开发人员(5年)，几乎没有分析软件的经验(学校提供的UML).

I've just stumbled into the job of analysing a project for one of my company's clients (an SMB). I am a .Net developer (5 years) with little experience in analysing software (UML from school).

我们刚刚完成了与用户的两个星期的交谈，并获得了很多不错的要求.显然，我们已经过滤掉了最重要的要求，不得不将一大堆标记为超出范围".

We've just finished two weeks of talking with the users and got a nice big list of requirements. Obviously we've filtered out the most important requirements and had to mark a bunch as 'out of scope'.

我刚刚开始制作一些用例，但是觉得我没有足够的专业知识来完成整个项目.我想知道是否有人实现了从开发人员到分析师的飞跃，这是怎么回事.另外，一些很好的资源来分析项目也很不错.

I have just started making some usecases, but feel I don't have the required expertise to bring this entire project to a good end. I'd like to know if someone has made the leap from developer to analyst and what goes with it. Also some good resources on analysing a project would be nice.

谢谢.

推荐答案

似乎没有其他人对此表示欢迎.

Nobody else seems to be taking a whack at this so I will.

我必须首先给您提供一些不受欢迎的消息-做一个好的分析师就像做一个好的开发人员-并非每个人都能做到.我认识许多人，他们擅长编写复杂的Windows应用程序代码，而对找出用户想要的内容，缩小要求范围并提出设计毫无用处.因此，如果遇到困难，请不要感到难过.

I have to first give you some unwelcome news - being a good analyst is like being a good developer - not everyone can do it. I've known lots of people that were great at writing complicated Windows application code that were useless at finding out what the user wanted, narrowing down those requirements, and coming up with a design. So don't feel bad if you find it hard going.

这带给我第二点-您不能分开分析和 设计，特别是对于现代OO系统，这两者是一个连续体的一部分.因此，您必须为此做好准备.

Which brings me to a second point - you can't separate analysis and design, particularly for modern OO systems, the two are part of a continuum. So you have to be prepared for that.

我的第三点不是太拘泥于UML.这是一个很好的工具，可以向其他人解释您的想法(前提是他们也知道UML)，但是对于进行实际设计却是一个相当烂的工具.例如，与UML使用的那些火柴人绘图相反，用例可以轻松地保存在文本文件中.我使用UML而不是UML来显示对象，组件和关系，这些对象，组件和关系通常在纸上和白板上进行草绘.

My third point is not to get too wedded to UML. It is a good tool for explaining your ideas to others (provided they know UML too) but a fairly rotten tool for doing the actual design. For example, use cases can just as easily be maintained in a text file as opposed to those stick-man drawings that UML uses. Instead of UML, I use simple block diagrams to show objects, components and relationships, normally sketched on paper and on a whiteboard.

我的最后一点是，A& D不是一个人的活动.找别人 涉及到您可以反弹想法.如果您可以找一位经验丰富的分析师/设计师为您提供一天左右的帮助，那就更好了.

My last point is that A&D is not a one-man activity. Get someone else involved that you can bounce ideas off. If you can get an experienced analyst/designer to help you for a day or so, so much the better.

希望是有用的，而不是太消极！

Hope that was useful, and not too negative!

这篇关于学习如何分析项目的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！