Business Analysis Flashcards
- Introduction: sets the stage, sets the pace, and establishes the overall purpose.
- Body: where the questions are asked and the answers are given.
- Close: provides a graceful termination to the particular session.
- Follow-Up: the information is consolidated and confirmed with the participants.
Elicitation Activities
A question that allows the respondents to
answer in any way they desire.
Open-Ended Question
A question that calls for a response from a limited list of answer choices. Types include forced choice, limited choice, and confirmation.
Closed-Ended Question
A question that requires an answer regarding the subject at hand; namely, the problem domain or the proposed solutions.
Contextual Question
A question that may be asked in any
situation. They’re also used as lead-ins to obtain information to define the solution.
Context-Free Question
A technique that provides a direct way of viewing people in their environment to see how they perform their jobs or tasks and carry out processes. It is particularly helpful for detailed processes when people who use the product have difficulty or are reluctant to articulate their requirements.
Observation
Models that structure and organize the features, functions, and boundaries of the business domain being analyzed.
Scope Models
(Goal Model and Business
Objective Model, Ecosystem Map, Context Diagram, Feature Model and Use Case Diagram)
Models that describe business processes and ways in which stakeholders interact with these processes.
Process Models
(Process flow, Use Case, User Story)
Models of concept and behaviors that define or constrain aspects of a business in order to enforce established business policies.
Rule Models
(Business rules catalog, Decision Tree, Decision Table)
Models that document the data used in a process or system and its life cycle.
Data Models
(Entity relationship diagram, Data flow diagram, data dictionary, state table, state diagram)
Models that assist in understanding specific systems and their relationships within a solution.
Interface Models
(Report table, System interface table, User interface flow, Wireframes, Display-Action-Response)
Non functional requirements are the criteria that define how a system should behave, rather than what it is supposed to do.
Unlike functional requirements, which describe specific system functions, non functional requirements define aspects like performance, security, usability, reliability, and scalability.
Functional vs. Nonfunctional Requirements
A persona in business analysis is a fictional character that represents a business’s target customers or users. Personas are based on research from interviews with real stakeholders, such as employees and service users. They group people with similar behaviors and service needs together. Personas can include many different types of personal and professional details about an individual, such as:
Age
Geographic location
Education level
Socioeconomic status
Goals and dreams for their personal or professional life
Challenges, frustrations, and fears
Persona
Validate Requirements process ensures all requirements accurately reflect the intent of the stakeholder.
It is usually performed via requirements walkthrough or concept of CONTINUAL CONFIRMATION
Requirements validation is the process of ensuring that all requirements accurately reflect the intent of the stakeholder and that each requirement aligns to one or more business requirements.
Validation is concerned about ensuring that the requirements solve the problem.
VALIDATE requirements
Verify Requirements process reviews
the requirements for errors and quality criteria.
It is usually performed via peer review or inspection.
Requirements verification is the process of reviewing requirements and models to ensure they meet quality standards.
Verification is the process of reviewing the requirements for errors and quality. Verification may occur before or after validation.
VERIFY requirements
