Monday, 20 November 2017

Elicitation Article

What is Elicitation?

Elicitation is the process of discovering the new business requirements and techniques which are readily not available and are not used in real-time. The elicitation process includes gathering the information depending on the requirements for any sort of paper work or study or research or etc.

When business analyst use Elicitation?

Business analysts (BA) are facing huge competition in their respective industries. To reach all the needs and goals Elicitation process is considered as the major aspect in various sectors.

Business Analysts are responsible for managing and reaching the project goals. To earn the required outcome, Business Analysts are considering the help of elicitation requirements which includes collecting information which are provided by stake holders, customers, Clients, users and through other feedback forms.

According to BABOK2.0 the stakeholders include customers/end users, suppliers, the project manager,quality analysis, regulators, project sponsors, operational support, domain subject matter experts, and implementation subject matter experts, and many others. 

BA is responsible to collect the exact information from Enterprise opportunities, restrictions,assumptions, and real-time data which are reflected by stakeholders. BA should also be part of resolving the conflicts between the requirements, and information providers.
In real-time Business Analysts uses various elicitation techniques in achieving the project goals to get the necessary success.

Different Types of Elicitation Techniques:

1. Brain storming
2. Document Analysis
3. Group Focusing
4. Interface Analysis
5. Interviews
6. Observation
7. Prototyping
8. Workshop requirements
9. Survey
10. Questionnaires
11. Reverse Engineering
12. Problem Tracking

Elicitation Preparation Process:

First step in Elicitation requirements is to understand the pro’s and con’s of the project, learning the do’s and don’ts of the stakeholder requirements, understanding the business needs of the provided project, gleaning the accurate comprehensive business needs,etc.

Then, business analysts ensure the safety and security of stakeholder requirements throughout the project duration. Then, analyst will recruit the appropriate stakeholder based on the business needs of the projects. After recruiting, the elicit requirements are documented and submitted to the respective  stakeholders.

How Elicitation Results are confirmed?

Ones all the elicitation method is completed along with business analysts, the elicit information is reviewed and documented. When document is finished, it is then shared with the respective stake holders to confirm the agreement.

This stage will be successful only when the data is grasped by BA accurately and has the best
communication between the Elicitation provider and receiver to avoid the conflicts and mislead of the

Tuesday, 31 October 2017

Business Analyst Article on Functional and non Functional Requirements

Functional and non Functional Requirements In Business Analyst?

Before we begin a project, we are always required to
document the requirements and classify them between
functional requirements and non-functional requirements.
This activity is beneficial whenever there is a future risk
or disagreements.

What are Functional requirements?

1. Functional requirements may be calculations,
technical details, data manipulation and processing
and other specific functionality that define what a
system is supposed to accomplish.

2. In simple terms, Functional requirements defines
what a system is supposed to do.

What is a function?

1. A function is described as a set of inputs, the
behavior, and outputs.

2. So, A function specifically involves external


3. It describes the action which completes the
work,that system is supposed to do.

4. Behavioral requirements describing all the cases
where the system uses the functional requirements
are captured in use cases.

5. This behavior may be expressed as services, tasks or
functions the system is required to perform.

Use Case?

1. A use case describes an interaction between an actor
and the system.

For example: Interaction between customer and Bank

Some of the more typical functional requirements

1. Business Rules

2. Transaction corrections, adjustments and

3. Administrative functions

4. Authentication

5. Authorization levels

6. Audit Tracking

7. External Interfaces

8. Certification Requirements

9. Reporting Requirements

10. Historical Data

11. Legal or Regulatory Requirements

Some typical non-functional requirements are:

1. Performance – for example Response Time,
Throughput, Utilization, Static Volumetric

2. Scalability

3. Capacity

4. Availability

5. Reliability

6. Recoverability

7. Maintainability

8. Serviceability

9. Security

10. Regulatory

11. Manageability

12. Environmental

13. Data Integrity

14. Usability

15. Interoperability

Tuesday, 5 September 2017

Interview questions for Business Analyst

Interview questions for Business Analyst.........

1Q: What is a flowchart and why it is important?
A:Flowchart shows complete flow of system through symbols and diagrams. It is important,
because it makes the system easy to understand for developers and all concerned people.

2Q:  Define Use Case Model?
A:Use case model shows sequence of events and stream of actions regarding any process
performed by an actor.

3Q:  What does UML stand for?
A:It stands for Unified Modeling Language.

4Q: Do you think Activity Diagram is important and how?
A:As the name implies, activity diagram is all about system activities. Main purpose of activity
diagram is to show various activities taking place in an organization in different departments.

5Q: Can you name the two types of diagrams heavily used in your field?
A:The two diagrams are Use Case Diagram and  Collaboration Diagram

6Q: Do you know what is meant by an alternate flow in a use case?
A:It is the alternative solution or activity in a use case that should be followed in case of any failure
in the system.

7Q: What are exceptions?
A:These are the unexpected situations or results in an application.

8Q: What are extends?
A:Extends are actions that must take place in a use case.

9Q: Name the two documents related to a use case?
AThe two documents are FRD (Functional Requirement Document) and SDD (System Design

10Q: What is the difference between Business Analyst and Business Analysis?
A:Business Analysis is the process performed by the Business Analyst.

want to do the training contact this number: +91 9441233734
visit this link :