Home | BA-Interview-Questions  | Jobs | Resumes  | BA-Dictionary | Books | Contact | Privacy Policy
Training & Tutorials:

*Roles and Responsibilities of a

 Business Analyst

*What is System Analyst

*What is SDLC and different

 Phases of it?

*What is usecase diagram?

 & its Importance.

*How to draw flowchart? And

 its uses?

*What is RUP? Explain in detail.

*What is UML explain in detail?

*Business Analyst Tutorials

*Business Analyst Interview


*Testing (QA) knowledge Required

 for BA

*Business Analyst Healthcare

 domain Tutorials

*Business Analyst Finance

 Domain Tutorials

*Rational Rose Tools Interview


*Diagrams for Business Analyst

*Resumes for Business Analyst

*Jobs for Business Analyst

*Interviews Tips



BA Interview Questions

*BA Interview questions set 1

*BA Interview questions set 2

*BA Interview questions set 3

*BA Interview questions set 4

*BA Interview questions set 5

*Business analyst Interview

 questions 6

*Business analyst Interview

 questions 7

*Business analyst Interview

 questions 8

*Resume writing tips for BA 9

*General business analyst interview

  questions 10

*Mortgage related interview questions

  for BA 11


Business Analyst Tutorials

*Responsibilities of a Business Analyst

*What is Business Analysis

*Sequence diagram Explained

*Class diagram explained

*RUP explained

*UML(unified modelling language)

*SDLC(systems development life cycle)

*Insurance knowledge for BA

*Health care knowledge for BA

*Finance banking knowledge for BA

*Role of a Business Analyst(high level)

*Use case diagram step by step

*Class Diagrams UML

*Responsibilities of BA

*What is RUP ?

*RUP in SDLC process


*Bug Life cycle

*BA Faq

*Business Users of the system

*Class diagrams

*CMM levels

*Collaboration diagram

*Data Mapping & Data modeling

*Data model in data base

*Deliverables in SDLC

*Tools used by BA

*Q-Gate (quality gate)

*RUP (rational unified processing)

*Sequence diagrams

*Deliverables in RUP

*UML (unified modeling language)

*Use case diagram

*Use case examples

*Use case template examples

*what are JAD sessions?

*What is GAP analysis ?

*What is User acceptance testing (

*Daily duties of a BA

*What is System analyst ?

*UML Tutorial Part 1

*UML Tutorial Part 2

*UML Tutorial Part 3

*UML Tutorial Part 4

*UML Tutorial Part 5

*UML Tutorial Part 6

*UML Tutorial Part 7

*UML Tutorial Part 8


Testing Knowledge

*Testing processes

*QTP recording flow

*Break points in qtp

*Split actions in qtp


*Check Points in QTP

*Integrated testing

*What is QTP ?

*Loadrunner step by step


Business Analyst Finance

*Business Analyst Finance domain

 Interview questions set 1

*What is Fixed rate Loan?

*What is home equity line of credit

  (HELOC) ?

*What is Loan to value ratio ?

*What is debt to income  ratio &

*What is lien Lien holder ?

*What are mutual funds ? Interview


*Trading of Stocks , what are stocks?

*New york Stock exchange

*What is NASDAQ ?

*Stock exchanges in USA

*Factors that will affect the change in

 price of STOCKS

*How to buy a STOCK ?

*What stocks are treated as equity

 while bonds as debt ?

*Some more Finance related interview

  questions for Business analyst

*Imp finance related interview

 questions for BA

*What is SWAP and types of swaps

*What are  Options & Bonds and types

Bonds in finance

*what are Options in finance

*what is a derivative and how it functions

*Who is a broker dealer

*Commercial bank in brokerage industry

*Who is a market maker?

*who is a specialist ?

*What are bond and types of bonds

*Steps for writing use case diagram

*What is SOX (Sarbanes Oxley act)

*CMM Capability maturity model


Business Analyst Health care :

*BA Health Care Claims

*SAS (statistical analysis system)

*Clinical Trials

*What are FACETS

*Health care fraud detection

*What is HIPAA

*Medicare Procedures and policies

*Health care Interview questions for BA


Share on Facebook





Functional vs Technical Requirements

Functional requirements VS Technical requirements

 Any system that has to be built by an organization/company starts just as documents. This requirements documents are the ones that speak out the customer minds. What is expected of the system? How is it going to be used? Who is going use it? What are the things that the system should support? What new “Out-of-the-box” features are expected now/in future? Well, you have all such questions answered by the customer in these documents.

 Not all requirements are going to be handled by the programmers and System Analysts alike. Not all requirements makes sense in the same way! Some requirements can just give you idea what is to be built as system- this is helpful for the programmers- Whilst, some others can give you the requirements as facts that have to be true- these may be just the ones that can alter the entire requirement and technology usages. Formally taken these are the ones that are respectively called as the Functional and Technical requirements.

 Functional requirements and uses:
These are the ones that say what is expected from a system. They are the ones that get transformed into the UMLs and the UseCases. What exactly is the system going to achieve. It can be stated in informal terms like “the system should get input A and give output Ax”. This is just a plain practical usage description from the customer. We can make out easily that there is no specification from customer as to how this should be done. All we are worried about in case of the functional requirements are the higher level system interaction and behaviour. They describe the system!

 Technical requirements and implications:

The technical requirements are giving the information to the developers as to what the system must adhere to. They are more often just facts that have to be true about the final system. Let us say for example “the system should handle 300 calls per second for over 8 hours”. Here we just are able to see what is expectation from customer. These are just guidelines that can have implications over on the developer’s way of developing a code. These are refinements that have to be considered when designing a system technically. Some software systems can come in with technical requirement as “program should run on the Java platform”. In such a case the system to be built is meant for java, so has to be built compatibly.

 Ideally, the technical requirements should give an insight as to what is being required basically from the client. More of the technical stuff just makes the requirement a constraint over the system. Most of the technical requirements can be converted to functional requirements by very good questioning. There are also some technical requirements that are put in to have a standard or to maintain a generality of operation. In such a case, the development should take in the requirement as one on which the other functional requirements are based. For a really successful development process identification of the correlation between the functional requirements and corresponding technical requirements/constraints is really important and that can happen when they are both stated and represented well to the team.