Gathering software requirements for begining business analysts搜集的软件需求为开端业务分析员
Posted on March 8, 2007 at 9:21 am发布于2007年3月8日,在上午09时21分
Working as a Business Analyst for the last 4 years has taught me a few things about gathering user and software requirements that I thought I would share!工作作为一个商业分析员在过去四年已经使我领悟到一些东西收集用户和软件要求,我以为我也有同感! There are a couple of things you need to do and keep in mind when you are trying to design a system or application for a particular set of users:有几件事你需要做的,并要记住,当你正试图设计一个系统或应用,为特定的用户:
1. 1 。 What the user ask for may not be exactly what they want!什么用户要求可能不正是他们要什么! They may ask you to do X, Y, and Z because that’ll make things a lot easier, but if you just go ahead and do that blindly, you will more than likely find that later on the users will complain and say that it’s not working in the best possible way or the way it “should”.他们会问:你这样做的X , Y和Z ,因为这样可以使事情变得容易得多,但如果你去做好了,做盲目,你会超过可能发觉后,对使用者会抱怨,并说这'不能为工作在尽可能最好的方式或途径,它"应该" 。 In order to figure out what the users REALLY need, you must sit down with them and WATCH while they work.为了推算出用户真正需要的,你必须坐下来与他们观看,而他们的工作。 Meetings are great and they will try to remember how they do things (50% of the stuff they will not remember they do) and give you some warped view of their work.会议是伟大的,他们会尽量记住他们是如何做到的事情( 50 %的东西,他们不会记得,他们这样做) ,并给你一些歪鉴于他们的工作。 Not that they do this on purpose, but once you go sit down and see how people work, you’ll find there are tons of small little, but importants steps that they didn’t think were worth mentioning!不说,他们这样做目的的,但一旦你去坐下来看看人们如何工作,你会发现有吨小一点,但importants步骤,他们不相信人,值得一提! Once you see the flow with your own eyes, then sit down with everyone and have a meeting about what they want and WHY.一旦你看到流与自己的眼睛,然后坐下来与大家有一个会议,对他们要什么,以及为什么。
2. 2 。 Always ask WHY people are doing things the way they are…usually you’ll find that some problems can just be solved by telling someone to do it another way!总是问,为什么人们正在做的事情,他们的手段…通常,你会发现一些问题,就可以得到解决,告诉别人去做另一种方式! Someone else told Person X to do it this way and so now they just keep doing it that way even though the process may have changed!别人告诉人X到这样做,所以现在他们仅仅会不断地做这样说的,即使过程可能有变了! People don’t like to change, even if it’s good for them!人们不喜欢改变,即使是对他们有好处! When you start asking why, people will begin to actually think about it and may figure out for themselves that they are wasting time or doing it in a complicated way that’s not necessary.当你开始问为什么,人们将开始真正去想它,并可能出来为自己说,他们是在浪费时间,或者是在一个复杂的方法,这是没有必要的。
3. 3 。 Always try to get a general view first!一向致力争取总的看第一! People will immediately begin to tell you about this problem with this particular feature or this step in the process, etc, etc, but you want to first get a clear understanding of the entire process from a higher level.人们将立即开始告诉你关于这个问题,这个特殊功能或这一步,在这个过程中,等,等,但你要首先搞清楚建设的整个过程中,从更高层次发展。 If you get right into the details, you’ll end up making software or a process that might be overly complicated!如果你得到的权利,有关详情,你将最终使软件或过程可能过于复杂! It’s amazing how many times I’ve looked at processes and determined that the entire step can be eliminated!!!它的惊人多少次,我已经看过进程,并确定整个步骤可以消除! Always try to get the BIG PERSPECTIVE!一直致力争取的大视野!
4. 4 。 Make sure to document everything, so people don’t think you are wasting time.一定要以文件的一切,所以人们不认为你是在浪费时间。 If you’re spending a lot of time with the people who actually do the work (which you should), then make sure you write everything down because you don’t want your boss to think you’re not getting anything done!如果您花了很多的时间与人究竟是谁做的工作(你应该) ,然后确保你的一切写下来,因为你不喜欢你的老板认为你得不到任何事情! It’ll also be easier to convince others that your solution is the best solution if you have lots of supporting evidence on paper.它也会比较容易说服别人认为你的解决方案是最好的解决办法,如果您有大量的证据支持在纸面上。
5. 5 。 Get sign off from all the top people, plus the users!得到签署过的所有高层人士,再加上用户! If management wants it one way and users want it another way, those issues need to be resolved quickly and jointly!如果管理层希望它的一个方法和使用者想要它另一种方式,这些问题必须尽快解决,并共同! Don’t ever say you’ll do one thing before making sure it’s ok with the boss.不要说你会做一件事,然后才作出肯定的好与老板。 Otherwise you’ll have to backtrack on your promise and people will get annoyed!否则你就会有走回头路,对你的承诺和人民将获得恼火!
6. 6 。 Lastly, but MOST IMPORTANTLY, TEST TEST TEST!!!最后,但最重要的,测试测试测试! Write out test scripts and test cycles.写出来的测试脚本和测试周期。 Don’t have to do anything fancy, use Excel to write it out.不须做任何花式,用Excel写出来。 One column for the particular feature or function you are testing, one column for the expected outcome, one column for the inputs and one column for the expected outputs.一栏为特定功能或功能是要测试,其中一个栏目,为预期的结果,一栏为投入和一栏中,为预期的产出。 You should always have expected inputs and outputs.你应该总是有预期的投入和产出。 And try to use varied data sets, small sets, large sets, and sets you know will cause errors (but hope to catch).并尝试用不同的数据集,小集,大集,并规定了,你知道会产生失误(但希望能借此引起) 。
Hope this helps!希望这有助于!
If you enjoyed this post, make sure you 如果你喜欢这个职位,请务必 subscribe to my RSS feed 订阅我的RSS馈送 ! !
» Filed Under »提起下 IT Job Stuff它的工作内容
Related Posts相关职位
- Reasons to work for a small company if you’re in IT理工作,为一家小公司,如果你想要它
- How to ask for a raise in the IT/Computer field!如何要求加薪,在资讯科技/电脑领域!
- A few more things about how to ask for aa raise in IT!数更多的事情,如何要求机管局提高,在它!
- Using the Principles of Dale Carnegie to Create a Great Blog!使用原则戴尔卡内基创造一个伟大的博客!
- Learn the physics behind everyday life and how things work学习物理背后的日常生活,以及如何工作的事
























