Software development teams create all kinds of software for all forms of industries. So the software could be vastly different between companies, but all companies have the identical goal in your mind: develop quality software punctually, on budget, which meets the customer's real needs.
When the scope of an project may be defined, the next phase is for your business analyst to get together complete requirements. This can be a most significant part of a business analyst.
The company analyst (BA) is responsible for determining finding certain requirements. Usually they've got subject matter experts (SMEs) and/or users of the software to collect requirements from.
The BA can be in charge of defining the approach they will use for gathering what's needed. They could have a meeting in the conference room with everyone present, they might do a blend of in-person through business call, or they will often do several smaller sessions if people are in several locations/time zones.
The BA must obtain detailed and finished requirements. Here's one particular vague requirement: "Need a chance to take payments".
Instance of an even more detailed requirement: "Need to be able to take payments via Master Card, Visa, an atm card, and checks".
In the above example, there'd be more requirements that could spin from that one, but by identifying greater detailed initial requirement, it may help the BA to know what other things to ask in connection with accepting payments.
The BA is also accountable for prioritizing requirements. Some companies use similar to "Must Have, Nice to Have, Optional" while others might use a numbering priority like 1-3 with 1 meaning must have on and on down after that.
It is advisable to try this prioritizing step given it sometimes is needed when thinking about scope from the project. When projects have to be completed by an unique date (as most do), sometimes the scope of the project has to change in order to fulfill that date. It will help to understand which requirements are most critical vs. lowest when the project team is determining what is held off for any later release rather than gonna production inside initial release.
Eliciting requirements is an essential task a company analyst has on a project. What's needed will probably be employed by the expansion team to build the program and when you don't have clear and concise requirements, the program will likely be missing functionality or contain incorrect functionality, and won't meet the expectations or needs of one's business partners.
Author Resource:
My technical background is in technology and culture specializing in computer software. You can learn more about my latest blog entries at my site.
![[Valid RSS feed]](http://www.look4articles.com/images/icon_Rss.png "XML Feed For RSS"){kind=icon}
Category Rss Feed
Print This Article
Add To Favorites
![[Valid RSS feed]](http://www.look4articles.com/images/rss.jpg "XML Feed For RSS")