CBAF-001 Certified Business Analyst - Foundation Questions and Answers

The Internal Rate of Return.

The Time to Payback.

The Net Present Value.

The Return on Investment.

Requirements elicitation.

Requirements analysis.

Requirements management.

Requirements documentation.

It reduces speed and productivity of the project.

It is time-consuming to arrange and organize.

It focuses on a narrow view of the area under investigation.

It obtains buy-in and acceptance for the project.

Ignore.

Watch.

Keep on side.

Keep informed.

Human Resources (HR).

Procurement.

Information Technology (IT).

Marketing and Sales.

Cow.

Cat.

Dog.

Goat.

Fear.

Self-esteem.

Anger.

Shock.

Workshops.

Interviewing.

Ethnographic study.

Prototyping.

Questionnaires.

Ethnographic study.

Shadowing.

Activity sampling.

A business analysis process model.

A systems development lifecycle.

A concerns-based adoption model.

A soft systems methodology.

Culture.

Process.

Norms.

Intuition.

To ensure that the requirement supports business objectives.

To ensure that the requirement is intelligently expressed.

To ensure that the requirement is well formed.

To ensure that the requirement is graphically modelled.

Regulators.

Competitors.

Testers.

Employees.

The rich picture.

The 'to be' process model.

The business activity model.

The use case diagram.

Management Qualities.

Business Knowledge.

IT Skills.

Project Skills.

When suitably sized rooms are available.

When all stakeholders are agreed on the way forward.

When a geographically dispersed set of users’ needs to be consulted.

When time and budget are constrained.

The project pays back in year 4 of the project.

The project does not pay back within the four year period.

The project pays back in year 2 of the project.

The project pays back in year 3 of the project.

Requirements validation.

Requirements verification.

Requirements testing.

Requirements traceability.

Quantifying costs and benefits.

Defining the needs of the business.

Implementing business changes.

Specifying IT system requirements.

As general requirements.

As technical requirements.

As functional requirements.

As non-functional requirements.

The statements declaring what the business is in and what it intends to achieve.

The approach the organization intends to take to achieve its declared mission.

The goals against which the organization's achievements can be measured.

The detailed means by which an agreed business strategy will be implemented.

Financial feasibility.

Business feasibility.

Technical feasibility.

Operational feasibility.

Those with high power/influence and no interest in the project.

Those with high power/influence and some interest in the project.

Those with some power/influence and high interest in the project.

Those with some power/influence and some interest in the project.

As an intangible cost.

As a tangible benefit.

As a tangible cost.

an intangible benefit.

Scenario Analysis.

Questionnaires.

Document Analysis.

Interviewing.

The Owner.

The Customer.

The Weltanschauung or world-view.

The Actor.

Assign resources.

Resource.

Project Manager.

Project.

Scenario analysis.

Protocol analysis.

Shadowing.

Activity sampling.

The BAM is concerned with who carries out the activities.

The BAM is concerned with where activities are carried out.

There will be one BAM for each business perspective.

The BAM is an AS-IS model of the real world.

Develop the coaching skills of selected staff members.

Establish clear benefits for s elected, powerful stakeholders.

Retain the previous system and its associated processes.

Ensure that improved staff performance is not rewarded.

It consists of two requirements which should be separately defined.

It contains the word "should" which must not be used in a requirement.

It should be specific about the user it refers to.

It should not contain the word "system" in the requirement.

Change management should be considered right from the start of the project.

Change management should first be considered in the design stage of the project.

The management of change is the sole responsibility of the project manager.

Social and cultural factors have little influence on the success of implementing changes.

Forces for and against business change.

Forces in the competitive environment.

The financial strength of the company.

The power of external suppliers.

Book.

Librarian.

Borrowing Limit.

Borrow book.

An intangible cost.

A tangible benefit.

An intangible benefit.

A tangible cost.

Opponent.

Neutral.

Critic.

Blocker.

Skills, values, communities of practice.

Job descriptions, tasks, targets.

Culture, norms, historical data.

Style guides, procedures, processes.

Workshops.

Prototyping.

Scenario analysis.

Shadowing.

MOSCOW.

SMART.

OSCAR.

MOST.

Plan.

Analysis.

Feasibility Study.

Strategic Vision.

The person who documented the risk in the risk register.

The person who identified the risk in the initial requirements analysis.

The person responsible for defining the probability of the risk.

The person best placed to take the necessary counter-measures to the risk.

Mess finding.

Data finding.

Problem finding.

Idea finding.

A study which uses prototype graphical screens to demonstrate a user requirement.

A study of users in their workplace undertaking representative simulated scenarios.

A study where the analyst spends an extended period of time in the target environment.

A study which ensures that the needs of a wide range of ethnic groups are considered.

Explicit or implicit management statements.

Statutory and internal policies.

Constraints and operational guidance.

Negotiable and non-negotiable limitations.

Shadowing.

Prototyping.

Special purpose records.

Activity sampling.