BA TERMS Flashcards
Glossary of terms
This is a list of key terms and definitions that boosts understanding across teams involved in the project.
RACI chart
RACI stands for responsible, accountable, consulted, and informed. It’s a matrix that delineates who is responsible for what in the context of the business analysis effort.
Responsible: A person who performs an activity or does the work.
Accountable: A person who is ultimately accountable for the outcome
Consulted: A person who needs to provide feedback or contribute to the activity.
Informed: A person who needs to know of a decision or action.
Interview and elicitation records
These documents capture important information from stakeholders.
Stakeholder analysis
This document identifies:
Who you should talk with to understand the business problem
Who can help flesh out the requirements
The individuals who can give you a range of perspectives
User stories
A user story describes the functionality that a business system should provide so that it can be developed. It is often called a ticket or work item. The format is “As a…. I want to… So that I can…”
Use cases
A use case identifies, defines, and organizes the system requirements from the perspective of a user.
Business analysis plan
This plan lists all the business analysis activities that will take place throughout the project.
Current state analysis
If the current business process or domain is not well understood, the BA analyzes and documents the current state before scoping a project to improve upon it. (ex. as-is diagram)
Scope statement specification
This is the most fundamental deliverable on any project. It is a clear definition of what needs to be achieved and the work that must be done to deliver the project or product.
Functional requirements specification (FRS)
This is the business requirements that are defined from an end user or business perspective. It will specify the expected outcomes.
System requirements specification (SRS)
This document details how the complete system should function and enumerates hardware, software, and functional and behavioral requirements of the system.
Gap analysis document
This document describes the gaps between the current processes and the intended processes.
Change request logs
This document is a log of all the change requests in the project including date of request, requester, and any other key information.
Wireframes and other visual documentation
This document contains renderings of the user interface, often in the form of low-fidelity wireframes.
Test plans, test cases, or user acceptance test plans
These documents describe the test plans and detailed test cases that the team will use to validate the functional requirements.
