Choose Business Analyst as your career !

why to join as BA ?

Because getting selected as BA would be an upgrade for me. skills required to be a BA are both technical as well as non technical, I think a overall developed mind is necessary to become a BA which i possess. BA requires both understanding customer requirements and converting this information to technical work flow. understanding client requirements is a tricky task that's why it is very important to conform the small points because sometimes client may not able to express what he exactly wants. Biggest challenge of a BA is to convert client requirements( problem) into a workable solution. this task is or should be supported by the development manager as well as testing manager. to present a good workable solution, BA needs to spearhead discussion to understand client problem and clearly define them in terms of requirements, cost, delivery schedule and services offered.

To understand client a BA must consider-

1) client background
2) his nature of work
3) problem areas and exact problem
4) process through which problem is occurring
5) willingness to change - that is how much client is ready to change the process or adjust solution in the current work flow
6) nature of solution that is - looking for temporary or permanent solution
7) allotment a knowledgeable resource to support solution providing team

While providing solution BA must consider -

1) which platform
2) model of development necessary to adopt
3) technology to be used

Who can become BA ?

A business analyst is a person who carries out a set of tasks through acquired knowledge and derives techniques which are required to provide business solutions. The person must be conversant with the IT field since the solution will most likely include a computer system development component especially in this day and age. A business analyst is a person whose job involves the analysis of the client’s needs. Their job is to pin point problems and find solutions for them. If you are creative and are looking for a challenging job, business analysis may be the job for you.

why should you be selected as BA?
- Excellent Client Management skills
- Team Player, Strong communication and negotiation skills
- Requirement Gathering using Requirement Workshops, JAD sessions, UML diagrams
- Creating deliverable like Software Requirements Specs, Process flows, mockups, Use Cases

Software Testing

software testing is not a new thing now a days, every company big or small is considering
the s.t.team as a crucial team to whole project success. the probability that companies not
using s.t. is minimal but the real point is that does s.t. is contributing to success of any project. the fact of the matter is that s.t. is not just a formality to complete but the a full different approach with which the software is seen. using and implementing s.t. is one great task to do which require a approach called creative destruction. creative destruction is looking at the software from the point of view of breaking it. this approach immensely helps in finding defects in software and further improve it. s.t. is also a rational approach with which the user requirements are seen. a user requirement is functional and non functional in nature i.e. requirements of customer are fulfilled the way he wanted is the functional requirement. And non-functional requirement means with the functionality customer wanted from the software additional to functional requirements a software should comply to standards and policies of the customer as well as maker of the software. non functional

includes performance, user friendliness, security, compatibility of the software.

why software has bugs?

It is imperative question that when a good development team is given a software to build around the customer requirement, why do bugs appear in the first place. every programmer does his part very well and most of the time will provide a functioning code, still this well functioning code can have bugs. why? and How? the answer is simple: he has provided a functioning code but not according to requirements of the customer. In our daily life we come across many softwares and thus many software bugs. Actually bug is not a technical word and a tester should not say a incorrect result or operation as bug, the actual word is DEFECT. there are many things that cause a software to have a bug. these are( this list is not exhaustive)

1) when the the requirements provided by the customer are unclear/ambiguous.
2) as complexity of software increases, no of bugs also increases. so complexity is main issue to tackle. we should not lessen the complexity of any software but we should focus on making excellent testing for such software.