What you should know to become a Business Analyst ?(part 02)

Thumsi Herath
4 min readMar 20, 2020

--

This is a collection of common interview questions that most of the interviewees might ask during a BA interview. If your target is to open up your career path as a Business Analyst this series might help you.

11) Describe the types of requirements briefly.

  • Functional Requirements — The functionality that the solution must offer, what it must do, the capability it must offer.
  • Non functional Requirements — Description of how or in what way the solution must function, the quality standard.
  • General Requirements — The business goals, policy, compliance and other strategic needs of the solution.
  • Technical Requirements — Specifics that come from a business perspective that are constraints or design imperatives.

12) What is a U M L Diagram?

A UML diagram is a diagram based on the UML (Unified Modeling Language) with the purpose of visually representing a system along with its main actors, roles, actions, artifacts or classes, in order to better understand, alter, maintain, or document information about the system.

13) Give Examples for UML Diagrams.

UML diagrams can be categorized into 2 sections as

  • Structural Diagrams
  • Behavioral Diagrams

Examples for Structural Diagrams —

  • Class Diagrams
Example 01 Class Diagram
  • Object Diagrams
  • Composite Structure Diagrams
  • Package Diagrams
  • Profile Diagrams
  • Deployment Diagrams

Examples for Behavioral Diagrams —

  • Use Case Diagrams
Example 01 Use Case Diagram
  • Activity Diagrams
  • Sequence Diagrams
Example 02 Sequence Diagram
  • State Machine Diagrams
State Transition Diagram
  • Communication Diagrams

14) What is a user story?

A user story is the smallest unit of work in an agile framework.It is an informal, natural language description of one or more features of a software system.Generally a story is written by the product owner, product manager, or program manager and submitted for review.

15) What is a project deliverable?

Project deliverable is a set of measurable goods and services that are delivered to the end customer at the completion of a project. It is the outcome of the project.deliverable could be a report, a document, a software product, a server upgrade or any other building block of an overall project.

16) Explain the business analysis process flow.

  1. Information gathering
    2. Identify the key stakeholders
    3. Identify the business objective
    4. Determine the available options
    5. Scope definition
    6. Define the delivery plan
    7. Define the requirements for a project
    8. Implementation and evaluation

17) What is the difference between verification and validation?

Verification —

  • Checks the details of the requirements with stakeholders .
  • Ensures that stakeholder needs are correctly interpreted.
  • Focuses on functionality, details and local consequence.

Validation —

  • Checks that combined requirements meet business goals.
  • Ensures that decision makers understand the future state.
  • Focuses on outcomes, solutions and their suitability.

The terms Verification & Validation can be confusing and are often misused Verification: truth and integrity check Validation: value and acceptance check.

18)What is Pareto Analysis?

Pareto Analysis which is also known as 80/20 rule is a decision-making technique. It is a useful technique for defect resolution and quality control. As per this analysis rule, 20 % causes create 80 % effects in a system, which is why it is named as 80/20 rule.

19) Name different types of Agile methodologies?

  • Scrum
  • Lean software development and Extreme Programming (XP)
  • Feature-driven development (FDD)
  • Crystal Methodology
  • DSDM (Dynamic Software Development Method)

20) When should you use waterfall methodology instead of scrum?

Many Initial Product Requirements & Strict Regulatory Requirements: ✅ Waterfall

Few Initial Product & Regulatory Requirements: ✅ Agile

Strict Processes in Place: ✅ Waterfall

Lenient Processes in Place: ✅ Agile

Low Product Owner Involvement: ✅ Waterfall

High Product Owner Involvement: ✅ Agile

Enhancement to an Existing Product: ✅ Waterfall

Greenfield Product: ✅ Agile

Fixed & Firm Timeline: ✅ Waterfall

Short, Flexible Timeline: ✅ Agile

Fixed, Inflexible Budget: ✅ Waterfall

Budget With Wiggle Room: ✅ Agile

If the requirement is simple and specific, we should go for Waterfall model instead of Scrum.

Additional Information :

--

--

No responses yet