Hi quest ,  welcome  |  sign in  |  registered now  |  need help ?

The role of business intelligence in gathering requirements

Written By anfaku01 on Monday, June 13, 2011 | 4:03 AM

Software development teams to create all types of software for all types of industry. Thus software can vary widely between companies, but all companies have the same objective: to develop quality software on time, on budget, and that meets the real needs of the customer.

After you have defined the scope of the project, the next step is for a business analytics needs to collect full. This is the most important task for business intelligence.

Business analyst (BA) is responsible for determining where to find the requirements. Usually they will have subject matter experts (SMEs) and/or users of the software to collect claims.

BA is also responsible for defining the approach they use to capture requirements. They can have a meeting in a Conference Hall with all present, they can do in person and at the Conference, or they can do some small sessions if the people are in different locations, time zones.

BA should be detailed and complete requirements. Here is an example of a vague requirement: you need the ability to accept payments.

An example of a more detailed requirements: "should the ability to accept payments via Master Card, Visa, debit cards and checks.

In the example above would still be more requirements that would spin on that one, but by identifying more specific initial requirement, he helps Ba know what other questions to ask relating to the payment reception.

BA is also responsible for prioritizing requirements. Some companies use something like "Must be nice to advanced, and others may use the priority number as must have 1-3 with 1 point and going down from there.

It is important to take this step to set priorities because it sometimes comes into play when considering project. When projects must be completed by a certain date (as most do), sometimes the scope of the project you want to change in order to meet that date. It helps to know what the requirements are the most important and least important when a team project is the definition of what could be held for later instead of having to go into production in the initial release.

Security requirements is most important to the business analyst is to draft. Requirements will be used by developers to create software and if you do not have a clear and concise claims software will contain incorrect functionality or feature and would not be in line with expectations or needs of your business partners.

Therese Bennett
Analyst coach
1-866-968-6657
http://www.theanalystcoach.NET/
Go to my site, Subscribe to my free newsletter with great tips for IT and get a report of "The Top 10 success Secrets from his intelligence, value 19.95.


View the original article here

0 comments:

Post a Comment