Do you understand what it takes to be a business analyst? Could you pass this quiz? A business analyst is an individual who evaluates an organization or place of business and records its processes, or systems, reviewing the business model and its merging with technology. Business analysts help businesses by improving the way they conduct themselves. If you want to See moretest your abilities as a potential business analyst, this is the quiz for you.
Requirements, solution, solution performance metrics
Solution scope, stakeholder concerns, business analysis performance metrics
Enterprise architecture, assumptions and constraints, and interview results.
Solution options, business case, stakeholder concerns
Rate this question:
Interviews and Reverse Engineering.
Requirements workshop and prototyping
Interface analysis and focus group.
Interviews and prototyping
Rate this question:
Determine architectural gaps.
Determine the organizational impacts.
Determine the business process gaps.
Determine the solution approach.
Rate this question:
Modifiable, testable, correct, feasible, complete, cohesive.
Unambiguous, verified, standardized, sponsored, solution based.
Correct, diagrammed, textually represented, modifiable, testable.
Testable, verified, validated, defined, modifiable, consistent.
Rate this question:
Review class diagrams with the Subject Matter Experts (SMEs) in a requirements workshop as a way to translate information requirements.
Include a textual description to use with the logical data model as the best way to visualize and describe information requirements.
Use the Entity/Relationship Diagram to show how entities relate to other entities for the Project Sponsor.
Identify all objects uncovered during requirements elicitation as an independent 'class'.
Rate this question:
Cardinality and relationship.
Optional vs. mandatory and which entity/class it belongs to.
Cardinality and constraints/domains.
Occurrences and which entity/class it belongs to.
Rate this question:
The organizational preference for Agile analysis versus structured analysis.
The ability of the BA to use pre-defined questions versus discussing topics of interest in an open-ended format.
A structured interview will be used when there is more time for the requirements team to complete a deliverable.
A structured interview represents a higher level of understanding of the BA regarding the business domain than an unstructured interview
Rate this question:
Allocate requirements (task) and release planning (element).
Define solution scope (task) and implementation approach (element).
Determine solution approach (task) and implementation approach (element).
Determine solution approach (task) and release planning (element).
Rate this question:
Organizational readiness assessment, transition requirements, stakeholder concerns.
Allocated requirements, transition requirements, validated solution scope
Assessment of proposed solution, allocated requirements, and identified defects/mitigating actions,
Assessment of proposed solution, assumptions and constraints, and allocated requirements.
Rate this question:
Formal documentation.
Informal documentation.
Presentation.
Models.
Rate this question:
Stakeholder impact analysis.
Cultural assessment.
Operational assessment.
Technical assessment.
Rate this question:
Effectiveness of Julie's decision-making abilities.
Effectiveness of Julie's problem-solving abilities.
Stakeholders include the BA in the decision making process.
Effectiveness of Julie's creative thinking abilities.
Rate this question:
It is complete and contains all the needed elements.
It is missing who the problem affects.
It is missing the impact of the problem.
It is missing what a successful solution would produce.
Rate this question:
Are shown by an actor connected by a line with an arrowhead.
Can be connected to a use case by dotted line.
Cannot be shown on a use case diagram.
Is indicated with a time actor to trigger the use case.
Rate this question:
Vendor assessment, decision analysis, and key performance indicators.
Vendor assessment, key performance indicators, and acceptance/evaluation criteria definition.
Decision analysis, structured walkthrough, and functional decomposition.
Decision analysis, acceptance/evaluation criteria, and vendor assessment.
Rate this question:
Decision Analysis.
Systems Thinking.
Problem Solving.
Learning.
Rate this question:
Solution approach.
Recommendation on feasibility of solution.
Market surveys, analytic hierarchy process, and benchmarking results.
Benchmarking results and feasibility recommendation.
Rate this question:
SWOT analysis.
Customer survey.
Data modeling.
Fishbone diagrams.
Rate this question:
Brainstorming session.
Impact analysis.
Focus group.
Inspection.
Rate this question:
An assumption.
A constraint.
A risk.
An issue.
Rate this question:
Feasibility analysis (technique) and define business case (task).
Alternatives Generation (technique) and determine solution approach (task).
Current Capability Analysis (technique) and assess capability gaps (task).
Feasibility analysis (technique) and determine solution approach (task).
Rate this question:
Jeff apparently did not understand who was supposed to approve his requirements. A structured walkthrough would have helped.
Jeff apparently did not understand the roles he needed to have in place in order to conduct a requirements review. Conduct Stakeholder Analysis would have helped.
Jeff waited too long to seek the sponsor's approval. A RACI matrix would have helped.
Jeff failed to adequately analyze and categorize his stakeholders, particularly who was authorized to approve requirements. Acceptance and Evaluation Criteria Definition would have helped.
Rate this question:
Conduct requirements elicitation activity.
Communicate requirements.
Validate requirements.
Manage solution scope and requirements.
Rate this question:
Decision analysis.
Problem analysis.
Solution scope analysis.
Root cause analysis.
Rate this question:
A statement of the project objective.
A statement of the business objective.
The definition of the required change to the organizational systems or capabilities.
A definition of why the change is required.
Rate this question:
Assess Solution Scope.
Assess Proposed Solution.
Assess Organizational Readiness.
Assess Solution Capabilities.
Rate this question:
Map the current processes in all the divisions and eliminate redundancy.
Simplify manual processes by increasing the complexity of system interfaces.
Recommend a new process to Increase consistency of behavior
Improve access to information
Rate this question:
Activity Diagrams.
Prototyping
Entity Relationship Diagrams.
Use Cases.
Rate this question:
The company likes Marc better. He has a proven track record
Julianne did not present an RFP - she presented an RFQ.
Julianne should not have used yes/no close-ended questions. She should have used open-ended questions.
Julianne let the company RFP form limit her ability to gather information about the vendor.
Rate this question:
Verify solution (task). Identified defects, solution verification assessment, and transition requirements (outputs).
Validate solution (tasks). Identified defects, mitigating actions, and solution validation assessment (outputs).
Define transition requirements (task). Transition requirements (output).
Validate requirements (task). Requirements [validated] (output).
Rate this question:
Requirements are always allocated to a specific release.
Requirements must be allocated by components of the Enterprise Architreectu
Requirements can be allocated by job function, organizational units or releases.
Requirements are allocated as they are verified by stakeholders.
Rate this question:
Context scope diagram.
Requirements workshop.
Structured walkthrough
Brainstorming.
Rate this question:
Uncover gaps in the data to ensure that the changes in the regulation are accommodated in the software and that appropriate alternative solutions can be explored, affected stakeholders can be consulted, and the solution approaches can be evaluated.
Uncover gaps in the business process to ensure that changes in the regulation are accommodated in both the application and the business process and that appropriate alternative solutions can be explored, affected stakeholders can be consulted, and .the solution approaches can be evaluated
Help understand the business need so that appropriate alternative solutions can be explored, affected stakeholders can be consulted, and .the solution approaches can be evaluated
Help the compliance officer to enforce the new regulation, as well as for audit purposes to encourage compliance with the regulation.
Rate this question:
Structured walkthrough.
Requirements documentation
Request for information (RFI).
Request for proposal (RFP).
Rate this question:
To determine whether and how each option can provide an expected business benefit to meet the business need.
To build the foundation of a work breakdown structure.
To describe the justification for the project in terms of the value added to the business.
To conceptualize and design the recommended solution in enough detail to build a Business Case, conduct an initial risk assessment and propose a new project for portfolio management.
Rate this question:
Document your elicitation results and organize them into requirements.
Send meeting notes out to all attendees and update the requirements management plan.
Document the results from the workshop and validate that the requirements match the stakeholder's understanding of the problem and needs.
Confirm your elicitation results and communicate as appropriate
Rate this question:
Current capability analysis and benchmarking.
Define solution scope and alternative generation.
SWOT analysis and problem and vision statement.
Scope modeling and implementation analysis.
Rate this question:
Determine solution approach, define solution scope, and define assumptions and constraints
Define solution scope, verify requirements, and prioritize requirements.
Plan business analysis approach, prepare for elicitation, and determine solution approach.
Define solution scope, verify requirements, and conduct stakeholder analysis.
The scope of the solution and the business need.
A business case and the business need.
The required capabilities and the business need.
The scope of the solution and organizational process assets.
Industry knowledge
Personal organization
Specialized application
Problem-solving
Rate this question:
Define solution scope, and do a risk assessment and risk analysis.
Determine solution approach, conduct alternative generation, and do document analysis.
Define the problem or vision statement, document dependencies, and do interface analysis
Assess capability gaps, conduct current capability analysis, and do document analysis
Communicate requirements.
Define technical requirements.
Ensuring that the project plan includes time for testing.
Provide a summary of brainstorming activities that have been documented
Rate this question:
Formal inspections
Comparing against quality standards
Facilitating a workshop among key SMEs to ensure requirements are correct.
Repairing defects.
Rate this question:
Organization's usability standards.
Prioritized, approved business requirements.
Transition requirements
Alternate solutions.
Rate this question:
Business and non-functional.
Stakeholder and solution.
Functional, non-functional, and transition.
Business, functional, and non-functional.
Rate this question:
Eliciting of requirements did not include the project sponsor.
Stated requirements must reflect actual business requirements as opposed to describing solutions.
Enterprise architecture is too complex for the solution to be realized.
The enterprise culture just isn't ready for a formal business analysis approach. An organizational assessment should be conducted
Rate this question:
Time consuming
Cannot produce innovative solutions.
Lack of staff expertise
Contractual obligations may present a problem.
Rate this question:
Document the data characteristics which will become the columns or fields in a database.
Document the business concepts that will be the basis for Use Cases that involve data.
Document the business objects that will contain data characteristics.
Be used mainly for database design, because entities or classes do not belong in requirements documentation.
Rate this question:
Quiz Review Timeline (Updated): Mar 22, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.