Những câu hỏi phỏng vấn "Closed-Ended (Kiến Thức Chuyên Môn)" dành cho Business Analyst

Ở phần 01: Những câu hỏi phỏng vấn “open-ended (cảm tính)” dành cho Business AnalystBAC đã cùng các bạn tìm hiểu về nhóm các câu hỏi cảm tính (là loại câu hỏi được hỏi dựa trên cảm tính của người hỏi: dựa vào thực tế dự án, và kinh nghiệm của người hỏi, và câu trả lời cũng dựa trên khả năng xử lý tình huống và giải quyết), được tổng hợp bằng tiếng Anh.

Để hỗ trợ bạn giải đáp những vấn đề này và tiếp thêm tự tin cho các bạn, BAC đã tổng hợp và biên soạn các câu hỏi mà bạn có thể sẽ gặp khi phỏng vấn vị trí BA. BAC phân loại các câu hỏi thành hai nhóm: 
  • Nhóm câu hỏi cảm tính: là loại câu hỏi được hỏi dựa trên cảm tính của người hỏi: dựa vào thực tế dự án, và kinh nghiệm của người hỏi, và câu trả lời cũng dựa trên khả năng xử lý tình huống và giải quyết. 
  • Và nhóm câu hỏi có câu hỏi kiến thức chuyên môn có đáp án: Là nhóm câu hỏi có đáp án rõ ràng, đúng sai dựa trên lý thuyết và kiến thức. 

Tiếp tục chuỗi bài viết về kỹ năng phỏng vấn dành cho Business Analyst, ở bài này, các bạn hãy cùng BAC “vượt qua” nhóm câu hỏi có câu hỏi kiến thức chuyên môn có đáp án (tức nhóm câu hỏi có đáp án rõ ràng, đúng sai dựa trên lý thuyết và kiến thức, được tổng hợp bằng tiếng Anh nhé! (BAC sẽ tổng hợp bằng cả ngôn ngữ tiếng Anh và tiếng Việt, nhằm phục vụ theo đúng từng nhu cầu tìm kiếm của các bạn BAs.)

Question 1: “Who is a business analyst?” 

Answer: “A business analyst works as a bridge between different stakeholders in an organization. He connects with the different stakeholders of an organization to clarify and finalize the requirements, helps the project team in project planning, designing and finally validating the developed components. He is the person who possesses adequate domain knowledge and can sort the business needs amongst the stakeholders who belong to different domains.”

Question 2: “Name some of the documents that a business analyst uses to handle?”

Answer: “Following are some of the common documents that a business analyst use to handle:

  • Project vision document

  • Use cases

  • Requirement Management Plan

  • User stories

  • Requirement Traceability Matrix (RTM)

  • Business Requirement Document

  • System Requirement Specification (SRS)/ System Requirement Document (SRD)

  • Test case

  • Functional Requirement Specification (FRS)/ Functional Specification Document (FSD)”

Tham khảo các loại tài liệu ở đây

Question 3: “What is SRS what are its key elements?”

Answer: “A System Requirements Specification (SRS) or a Software Requirements Specification is a document or set of documents that describe the features of a system or software application. It includes a variety of elements that define the intended functionality required by the stakeholders and customers to satisfy the end-users.

In addition to that, an SRS provides a high-level idea of the system and its behavior, the main supported business processes, the assumptions, and the key performance parameters for the system. The key elements of an SRS are:

  • Scope of Work

  • Functional Requirements

  • Non-Functional Requirements

  • Dependencie

  • Data Model

  • Assumptions

  • Constraints

  • Acceptance Criteria”

Question 4: “What is a requirement?”

Answer: “A requirement is a targeted solution to achieve specific business goals or objectives. It is an input to various stages of SDLC. This is a basis of a project which must be validated by the stakeholders and business users before implementation. Besides that, every requirement needs to be properly documented for future reference purposes.”

Question 5: “What is a use case?”
Answer: “A use case is a diagrammatic representation of a system that describes how a user uses a system to accomplish a goal. It is an integral part of software engineering and software modeling techniques that defines the targeted features and the resolution of any possible errors which a user may encounter.”
 
Question 6: “What are the steps that you need to follow to design a use case?”
Answer: The steps in designing use cases are:
  • Identify the users of the system

  • Creating a user profile for each category of users. This includes all roles that the users may play and are relevant to the system.

  • Identify essential goals associated with each role. Also, identifying the significant roles.

  • Creating use cases for every goal associated with a use case template. This also includes maintaining the same abstraction level for the entire use case. Higher-level use case steps are considered as goals for the lower level.

  • Structuring the use cases

  • Reviewing and validating the users”

Question 7: “What is a scope creep?”
Answer: Scope creep, or requirement creep is a term that relates to the uncontrolled changes or deviation in the project’s scope within the same resource range for example within the same schedule and budget of the project. It’s an indication of poor project management and a viable risk to a project. Some of the possible causes of scope creep are:
  • Poor communication between the project’s stakeholders

  • Improper documentation of the project’s requirements

Scope creep could be avoided by:

  • Clear documentation about the project scope

  • Following proper change management

  • Prior intimation about the effects of the changes to the associated parties

  • Proper documentation of the new requirements in the project log

  • Refrain from Gold Plating which means adding extra features to the existing functionalities.”

Question 8: “What is BRD? How is it different from SRS?”

Answer: A Business Requirements Document (BRD) is a formal contract between the customer and the organization for a product.

The difference between BRD and SRS are as follows:

  • BRD:

    • It is a high-level functional specification of the software;
    • It is a formal document to describe the requirement provided by the client (written, verbal);
    • The Business Analyst creates it after their direct interaction with the clients;
    • It is derived based on the requirements and client interaction.
  • SRS:
    • It is a high level functional and technical specification of the software;
    • It describes the functional and non-functional requirements of the software to be developed;
    • The System Architect creates it as it needs technical expertise. Though sometimes Bas too can create it;
    • It is derived from the BRS.”
Question 9: “What is Gap Analysis?”
Answer: Gap Analysis is a technique to analyze the gap between the existing system and functionalities, and the targeted system. Here gap means the amount of task or change that may be required to get the intended result. It’s a performance level comparison between the present and the proposed functionalities.”
 
Question 10: “What is requirement prioritization? What are the different techniques used for it?”
Answer: Requirements prioritization is the process to allocate requirements based on the business urgency to different phases, schedules, costs, etc.

There are various techniques that are used for requirements prioritization:

  • MoSCoW Technique

  • Requirements Ranking Method

  • 100-dollar method

  • Kano Analysis & More

  • Five Whys”

 
Question 11: “What is the required elicitation technique?”
Answer: Requirement elicitation is the process of requirement gathering from stakeholders, users, and customers by conducting meetings, questionnaires, interviews, brainstorming prototyping, sessions, etc.”
 
Question 12: “What is the fundamental difference between a requirement and need in a business analysis perspective?”
Answer: Needs are high-level definitions of the future goals of a business. Whereas, Requirements are the representation of the detailed description of that business needs.”
 
Question 13: “What are non functional requirements and how do you capture them?”
Answer: Non-functional requirements represent the performance level characteristics like how fast it can respond, how smooth is a user interface, security, etc. of the application under development (AUD).”
 
Question 14: “What are the skills that a business analyst must possess?”
Answer: We can broadly categorize the skills of a business analyst into three types:
  • Fundamental skills

  • Technical skills

  • Business Analysis skills”

Question 15: “How will you define a good quality requirement as business analyst?”
Answer: We can measure the quality of a requirement using the SMART rule. As per this rule, a good quality requirement should be:
  • Specific: The requirement should be specific and could be documented properly

  • Measurable: Different parameters can measure the success criteria of the requirement

  • Attainable: The requirement should be feasible within the scope of the given resources

  • Relevant: The requirement must be in line with the project’s business case

  • Timely: The requirement should be communicated early in the project lifecycle”

Question 16: “Which documents are used to capture non-functional requirements?”
Answer: There are two documents that are used to capture non-functional requirements, and they are:
  • SDD (System Design Document)

  • FRD (Functional Requirement Document)”

Question 17: “What is an alternate flow in a use case diagram?” 

Answer: It is an alternative solution or activity in a use case that should be followed in case of any failure in the system.”
 

Question 18: “Define Personas?”
Answer: Personas represent User-Centered Design methodologies. To enable an application capable of performing on a demographic basis, fictional characters are conceptualized by the business analysts and based on their possible demographic-specific behavior scenarios are created during design.”
 
Question 19: “What is an activity diagram and what are the important elements of it?”
Answer: An activity diagram is a visual representation of the workflow of a business use case. This diagram shows various activities that take place in an organization in different departments like HR, Sales, Accounts, etc. The activity diagram highlights the differences in the departments.

The important elements in the Activity diagram are initial nodes, activities, control flows, decisions, a fork, guard conditions, join and end nodes.”

 
Question 20: “What is UML modeling?”

Answer: UML stands for Unified Modelling Language. It is a standard that the industry uses for documenting, constructing and visualizing various components of a system. This modeling standard is primarily used for software development. However, it is also used for describing job roles, organizational functions, and business processes. Some of the important diagrams that BAs use as part of UML are the class diagram, state diagrams and use cases.”

 
 

Question 21: “What are the best practices to follow while writing a use case?”
Answer: Some of the best practices to write a use case are as follows:
  • To become a valid use case, the use case must provide some value back to the actor or stakeholder.

  • The functional and non-functional requirements must be captured appropriately in the use case.

  • The use case must have one or more alternate flow along with the main flow.

  • The use case should only describe what the system does and not how it is done which means it will not describe the design. It will act as a black box from the viewpoint of an actor.

  • The use case should not have any, i.e. it should be stand alone.”

Question 22: “What is the difference between exception flow and alternate flow?”
Answer: Alternate flows are the alternative actions that can be performed apart from the main flow and can be considered as an optional flow.

Exception flow is the path traversed in case of any exception or error.”

 
Question 23: “Do you think a business analyst should be involved in testing?”
Answer: Yes. Because a business analyst understands the overall system requirements and challenges associated with it very well. Hence, he can be instrumental during the testing phase to run it appropriately and resolve any system-related query.”
 
Question 24: “What does INVEST stand for?”
Answer: INVEST stands for –
  • Independent

  • Negotiable

  • Valuable

  • Estimable

  • Sized Appropriately

  • Testable”

Question 25: “What is Pareto Analysis?”
Answer: Pareto Analysis which is also known as the 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.”

 

Question 26: “What is BPMN and what are its basic elements?”
Answer: BPMN is the Business Process Model and Notation. It is a graphical representation of business processes.

There are five basic elements of BPMN, and they are –

  • Flow Objects

  • Data

  • Connecting Objects

  • Swimlanes

  • Artifacts”

Question 27: “What is Kano analysis?”
Answer: Kano Analysis is used to analyze a system regarding its requirements to identify its impact on customers’ satisfaction.”

 
Question 28: “What are the different types of actors you know in use case diagrams?”
Answer: There are mainly two types of actors that can be depicted in a Use case-
  • Primary actors – It starts the process

  • Secondary actors – It assists the primary actor

Moreover, we can categorized actors into four types :

  • Human

  • System

  • Hardware

  • Timer”

Question 29: “What are the different types of gaps that a business analyst can encounter during gap  analysis ?”
Answer: There are mainly four types of the gap –
  • Performance Gap – The difference between expected performance and the actual performance

  • Product/Market Gap – The gap between budgeted sales and actual sales is termed as the product/market gap

  • Profit Gap – The variance between a targeted and actual profit of the company.

  • Manpower Gap – The gap between the required number and quality of workforce and actual strength in the organization”

Question 30: “What is Benchmarking?”
Answer: Benchmarking is about measuring the performance of an organization to compete in the industry. In this process, a company may measure its policies, performance, rules and other measures.”
 

 
Question 31: “How do you decide that as a business analyst you have gathered all the requirements??”
Answer: We can conclude that all the requirements are gathered only when –
  • It is validated and approved by the business users.

  • The requirements are appropriately aligned with the project’s business requirements.

  • The requirements can be implemented with the available resources.

  • All the key business stakeholders are aligned with the elicited requirements.”

Question 32: “How do you perform requirement gathering?”
Answer: The requirement gathering process is generally divided into multiple steps which are agnostic to the SDLC cycle. Each step involves:
  • Specific tasks to perform

  • Principles to follow

  • Documents to produce

The steps are as follows:

  • Step 1: Gather Background Information – This may include collecting background information about the project, analyzing any potential risk associated with the project. Techniques like PESTLE analysis, Porter’s Five forces framework could be used for this purpose.

  • Step 2: Identify Stakeholders – They are the decision-makers of a project and approvers for requirements and priorities. Stakeholders may range from project owners to senior managers, end-users, and even competitors.

  • Step 3: Discover Business Objectives – This is to understand the business needs of the project before going deep into the project. SWOT analysis, Benchmarking, analyzing business objectives SMART and listing business objectives are some of the techniques used for this purpose.

  • Step 4: Evaluate Options – This is to identify the options to achieve business objectives. Impact analysis, Risk analysis, Cost-benefit analysis are some of the methods which are used for this purpose.

  • Step 5: Scope Definition – A scope is a project development goal that is set based on the business objectives. A scope definition document is used to detail the goals for each phase of a project.

  • Step 6: Business Analyst Delivery Plan – Based on the project scope, stakeholders’ availability and project methodology a document called business analyst is created at this step. The document provides information on deliverables with their timeline.

  • Step 7: Define Project Requirements – In this step, two types of documents are used – Functional requirement document and Non-functional requirement document. Based on the development methodology to be used in the project the business analyst needs to clarify the requirements with the stakeholders by interviewing them on the requirements and get the sign-off on the same.

  • Step 8: Support Implementation through SDLC – This is the technical implementation step of the requirements where a business analyst gets involved with different teams. This includes coordinating with the development team and testing team to ensure requirements are implemented as expected and appropriately tested against all the possible business scenarios. They also need to handle the change request which may arise from the stakeholders at a later point in time.

  • Step 9: Evaluate Value Added By Project – This is the continuous evaluation of the project to evaluate whether the business objectives implementation correctly meets the business needs outcome and timeline.”

 

Question 33: “Why it is necessary for a business analyst to get involved during the implementation of requirements ?”
Answer: Gaining domain knowledge and providing an analytical solution are the two major criteria of a business analyst. Hence, during the actual implementation of a requirement or use case a business analyst can help to resolve many business strategies related problems that may arise during the implementation stage. On the contrary, they can learn from the problems which may help them to provide the solution in similar scenarios and also help to gain their domain knowledge.”

 
Question 34: “What are the problems that a business analyst may face?”
Answer: From the initiation to post-implementation of a project, a business analyst may face the following problems –

  • Employees related issues

  • Technology-related problems

  • Access related

  • Business policies related issues

  • Business model errors”

Question 35: “Explain the requirement elicitation strategy”
Answer: Requirement elicitation is the process to collect all the requirements related to a system from the end-users, customers, and stakeholders. As per the BABOK guide, there are nine methods that can be used as part of the requirement elicitation process, and these are:
  • Brainstorming

  • Interviews

  • Observation

  • Document Analysis

  • Focus Groups

  • Requirements Workshops

  • Interface Analysis

  • Survey or Questionnaire

  • Prototyping”

 
Question 36: “What is Business Model Analysis?”
Answer: Business Model Analysis is a technique to analyze whether a business is viable and valuable regarding social, economic and other perspectives. The business model analysis provides the foundation for any required business model change and innovation for an organization.”

 

Question 37: “Do you think the role of a Business Analyst is a need for a project?”
Answer: Yes, because the role of a Business analyst is extremely beneficial from the kick-off to the implementation of a project. Here are the top 4 reasons:
  • During the project kick-off session, there are high possibilities that some technical queries come up from stakeholders and clients. As we don’t involve the technical project team during this phase and immediate answering is essential, a business analyst may play a pivotal role to answer those queries.

  • The next phase after the kick-off session essentially involves some gap analysis, business process analysis, documentation, SOW review, project scheduling, and of course preparing requirement specification documents.

  • During the development and testing phase, a business analyst can play a significant role to resolve any requirement-related queries from the project teams. Besides that, he can validate whether the requirements are correctly implemented and tested considering different functional and non-functional scenarios.

  • In a waterfall model, new requirements or modifications of requirements can be asked from stakeholders considering changing business needs. In this case business analyst is the person who can handle this change request with proper validation and analysis.”

 

Question 38: “What is the difference between Business analysis and Business analytics?”
Answer: The key difference between Business analysis and Business analytics is the first one is more functions and process-related whereas the second one is data-related.

Business analysis – recognizes business needs and determines the solutions to those problems. Tools and techniques like SWOT, PESTLE, CATWOE, MOST, FIVE WHY, etc. are used for business analysis.

Business analytics – handles data and analyzes data to get insights into a business. Finally, it generates reports. Mainly four types of business analytics are used, and they are – descriptive analytics, decisive analytics, prescriptive analytics, and predictive analytics Tools and technologies like Big data, BI is used for this purpose.”

 
Question 39: “What is process design?”
Answer: Process design is a way that helps a business to analyze the challenges in business and to find an effective solution for those. Through Process, design workflows are created to get the best possible outcome in the shortest time.”

 

Question 40: “What are the effective skills to solve any problems as a business analyst?”
Answer: They include
  • Leadership skill

  • Excellent communication skill

  • Problem analysis skill

  • Technical knowledge

  • Domain knowledge”

 
 
Question 41: “What is the Agile Manifesto?”
Answer: Agile Manifesto is a software guide about the Agile development principles which ensure iterative solutions.”
 

Question 42: “What are the essential qualities of an Agile BA ?”
Answer: An Agile BA must be able to:
  • The BA has expected to work to collaborate with product owners and developers to elicit requirements. The BA also must work to develop real functional requirements.

  • The BA must-do requirement elicitation in an iterative way

  • The BA must make requirement specifications, data models and business rules as much lightweight as possible.

  • The BA must be technically sound so that he can understand how the components of the system interact with each other. Besides that, he must understand the agile terminologies as he acts as the middleman between the customer and the project team.

  • The BA must concentrate on the just-enough requirement and test criteria to meet the just-in-time delivery goal of an agile project.”

 

Question 43: “When should you use the Waterfall model instead of Scrum?”
Answer: If the requirement is simple and specific, we should go for the Waterfall model instead of Scrum.”

 
Question 44: “What are the four key phases of business development?”
Answer: The four key phases of business development:

  • Forming

  • Storming

  • Norming

  • Performing”

Question 45: “What do you know about Kanban?”
Answer: Kanban is a tool that helps the agile team visually guide and manage the work as it progresses through the process. Besides, it works as a scheduling system in Agile just-in-time production. The Kanban board is used to describe the current development status.”

 
Question 46: “Mention about some of the most important agile metrics?”
Answer: The following are some important agile Matrices

  • Velocity – This is used to track the progress of a project

  • The sprint burndown matric – This helps to track the work done with the sprint.

  • The priority of the work

  • Work category allocation – This metric helps to get an idea about the priority of the work and work category allocation.

  • The cumulative flow diagram – the uniform flow of work can be checked through this diagram of cumulative flow. Here the x-axis represents time and the y-axis stands for the number of efforts.

  • Defect removal awareness – This helps to produce quality products.

  • Business value delivered – This is used to estimate the work efficiency of the team. It associates 100 points for measurement.

  • Time coverage – It estimates the amount of time invested in coding during testing. It is the ratio of the number of lines of code called by the test suite to the number of relative lines of codes.

  • Defect resolution time – This is the turnaround time for detecting and fixing bugs. There processes involved for this purpose are:

  1. bug fixing

  2. eliminating the bug

  3. Scheduling a fix

  4. Defect fixation

  5. Handover of the resolution report”

Question 47: “Explain the term ‘increment’?”
Answer: Increment refers to the sum of all the product backlog items completed in a sprint. The new increment value also includes the increment of the previous sprints.”

 
Question 48: “What are the different types of Agile methodologies?”
Answer: Some of the well-known agile methodologies are:

  • Scrum

  • Lean software development and Extreme Programming (XP)

  • Feature-driven development (FDD)

  • Crystal Methodology

  • DSDM (Dynamic Software Development Method)”

Question 49: “Is there any difference between incremental and iterative development?”
Answer: Yes. In an iterative development software development happens without any interruption. Here the software development cycles which typically consist of sprint and release are repeated till the final product is obtained. Whereas, in an incremental model, software development follows the product design, implementation, and testing incrementally until the product is finished. Hence, it involves development and maintenance.”
 

Question 50: “Difference between extreme programming and scrum?”
Answer: Scrum and extreme programming both follow iterations which are known as sprints. However, the sprints in a Scrum process last up to two weeks to one month long whereas in an extreme programming (XP) team the iteration lasts for one or two weeks. Extreme programming is more flexible than Scrum as Scrum does not allow any change during iterations.

Though we have categorized the above business analyst interview questions based on the experience levels, however, it could be a mix and match for any career level depending on the organization and their requirement.”

 
Question 51: “What are the industry and professional standards followed by business analysts?”
Answer: Industry standards that have been set for the BAs to follow are OOAD principles and Unified Modeling Language (UML). This is a common language used by business analysts all around the world to draft the functional requirements.”
 

Question 52: “Who uses the output produced by business analysts?”
Answer: The output will be used by both IT and non-IT people, as IT people use this document as key for the building of the application and non-IT people use those documents where they can see the prototype of their application.”
 
Question 53: “Why are excellent communication skills essential for a Business Analysyt?”
Answer: A BA is one who sits with the client and understands it, then tells the IT people what needs to be done hence BA needs to have excellent communication skills.”

 
Question 54: “What is the difference between a Data Model and an Entity Relationship Diagram?”
Answer: A data model is a model which shows how data is stored and used for e.g. a normal database. It has 3 main parts:

  • Structural part: how data is structured.

  • Integrity part: rules governing structure.

  • Manipulation part: operators used to select, update, query data, e.g. select, update, delete commands in SQL.”

Question 55: “What is the educational qualification required for a Business Analyst ?”
Answer: There is no specific qualification for a business analyst. Well, if you are a management graduate it is an added advantage since they have better communication skills. One important thing a BA needs to have is domain knowledge or business knowledge. Unless he/ she understands the client’s business process thoroughly they cannot draft the requirements properly.”

 

Question 56: “What is UML? Mention the components of UML?”
Answer: Answer: The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modeling and other non-software systems. The UML represents a collection of best engineering practices that have proven successful in the modeling of large and complex systems. UML uses many concepts from many sources.

  • For Structure: Actor, Attribute, Class, Component, Interface, Object, Package.

  • For Behavior: Activity, Event, Message, Method, Operation, State, use case.

  • For Relationships: Aggregation, Association, Composition, Depends, Generalization (or Inheritance).

  • Other Concepts: Stereotype. It qualifies the symbol it is attached to.”

Question 57: “Mention some of the important points a Business Analyst must take care of while preparing a business plan?”
Answer: While creating a business document, make sure you start from small problems. Don’t jump to big problems the right way. Keep the Business sponsors and IT folks in the loop. Make sure your document clearly states Exceptions, Assumptions, and Limitations. Sometimes you need to keep in mind the legal issues. The business document should be well written for usability and for future projects.”

 
Question 58: “Why are Business Analysts vital in an organization?”
Answer: This position is important because a BA is a people’s person when it comes to the users and an IT person when it comes to the developers. He can communicate with the users in jargon that they are comfortable with and is able to understand them in order to collect solid business requirements. Simultaneously he can effectively communicate these requirements and support them with documentation for a developer’s benefit.”

 
Question 59: “What are the quality procedures followed normally by a Business Analyst?”
Answer: For quality, there is no specific mark, of course, Six Sigma and ITIL (Information Technology Infrastructure Library – United kingdom) are certain quality standards establishing organizations and methods. But As normal, the following should be followed: The quality of communication while gathering requirements should be excellent and outstanding. Sometimes users are just looking for functionality in the system and they are not even able to say what exactly will be their dream functionality that will be most convenient to them. In that case, BA should explore them and figure out the exactly demanded requirements.”

 
Question 60: “How is requirement analysis done by Business Analysts?”
Answer: The requirement session is usually done through the JAD session. Business Folks and Major sponsors are always there along with some technical folks. The business analyst then goes through each requirement and asks for feedback. If Business Sponsors and Technical Folks think that all the requirements are according to the business and won’t be a barrier to the existing system. They get the official signoff on the Business Requirement document. IT manager and Business manager both do the sign-off on that business requirement document.”
 

 

Question 61: “Mention the difference between Business Process Improvement and Business Process Reengineering?”
Answer: Business Process Improvement implies changing a step sub-step or any part of the process i.e. process is not completely changed. In Business Process Reengineering, we actually study the business and find out what is the best way I can carry out the process and change the whole way the process runs (business process redesign).”
 

Question 62: “What are the problems that Business Analysts could face during gathering business requirements?”
Answer: The availability of the people (e.g. managers, supervisors, and the end-users) the BA wants to talk with for gathering business requirements. These people have regular daily works to do and their time to spend in the gathering is sometimes hard to schedule and for this reason, gathering business requirements is delayed.”
 
Question 63: “What is the relationship between use case and test case?”
Answer: A use case is written from a “user” perspective describing the interaction of a piece of software between the user and the software. These are written in common language typically from the business or user point of view and in enough detail for the developer to create a piece of software. Typically written in an MS Word type tool. Use cases capture the functional requirements of the system. It describes the expected interaction the user will experience, in detail. The audience is the business, for signoff, and technology for development.”

 

Bài viết này BAC tổng hợp các câu hỏi phỏng vấn BA – nhóm câu hỏi có câu hỏi kiến thức chuyên môn có đáp án (có đáp án rõ ràng, đúng sai dựa trên lý thuyết và kiến thức). Bạn có thể tham khảo và chuẩn bị thật tốt cho buổi phỏng vấn của mình. Ngoài ra, các kiến thức chuyên môn này, bạn có thể tìm hiểu, hoặc chuẩn chỉnh thêm bằng cách tham gia khoá học Phân tích Nghiệp vụ Phần mềm cơ bản của BAC. Các nội dung chính trong khoá học sẽ giúp bạn xây dựng một nền tảng kiến thức vững chắc, kỹ năng cốt lõi, và nhiều lợi ích khác nữa, hoặc tham gia học cách phỏng vấn trực tiếp cùng chuyên gia qua chương trình BA-Interview
 
Cuối lời, BAC chúc các bạn sẽ thành công và hẹn gặp lại ở các bài viết khác trên BAC’s Blog! Ngoài ra, bạn có thể tham khảo các bài viết khác, liên quan đến kỹ năng phỏng vấn BA như:

Nguồn tham khảo:

Nhu cầu đào tạo doanh nghiệp

BAC là đơn vị đào tạo BA đầu tiên tại Việt Nam. Đối tác chính thức của IIBA quốc tế. Ngoài các khóa học public, BAC còn có các khóa học in house dành riêng cho từng doanh nghiệp. Chương trình được thiết kế riêng theo yêu cầu của doanh nghiệp, giúp doanh nghiệp giải quyết những khó khăn và tư vấn phát triển.
 
 

CÁC KHOÁ HỌC BUSINESS ANALYST BACs.VN DÀNH CHO BẠN

Khoá học Online:

Khoá học Offline:

Tại Tp.HCM:

Tại Hà Nội:

Tham khảo lịch khai giảng TẤT CẢ các khóa học mới nhất

Ban biên tập nội dung – BAC

 

Previous Post
Next Post