Babok Chapter 7 Solution Assessment And Validation

Front 1

You are working on a project to implement enterprise software. You convince the project manager and sponsor to also consider a custom solution, because you have heard of difficulties implementing the commercial software in, similar organizations. You study and rank each alternative. You are performing which task?
a. Compare solution alternatives.
b. Assess organizational readiness.
c. Assess proposed solution.
d. Evaluate solution performance.

Back 1

c. Assess proposed solution.

Hint 1

BABOK7.1 description: "Solution assessment may be performed on a single solution or to compare multiple proposed solutions."

Front 2

When performing the above task, you determine how closely which types of requirements match the proposed solution?
a. Business and non-functional.
b. Stakeholder and solution.
c. Functional, non-functional, and transition.
d. Business, functional, and non-functional.

Back 2

b. Stakeholder and solution.

Hint 2

The purpose of assessing proposed solutions would be to compare stakeholder and solution requirements. BABOK 7.1.2.

Front 3

In the above scenario, which technique would be most effective?
a. Vendor analysis.
b. Solution analysis.
c. Organizational analysis.
d. Decision analysis.

Back 3

d. Decision analysis.

Hint 3

BABOK 7.1.5. Decision Analysis (9.8): Decision analysis methods directly support the assessment and ranking of solution options.

Front 4

The purpose of the task allocate requirements is to:
a. Allocate requirements to implementation SME(s).
b. Allocate requirements to appropriate testers.
c. Allocate requirements to designers and/or developers.
d. Allocate requirements to solution components and releases.

Back 4

d. Allocate requirements to solution components and releases.

Hint 4

BABOK 7.2.1 Purpose.
Allocate stakeholder and solution requirements among solution components and releases in order to maximize the possible business value given the options and alternatives generated by the design team.

Front 5

Examples of solution components are:
a. Business analysis solution assessment plan.
b. Organizational structure.
c. Solution scope.
d. Solution assessment recommendation.

Back 5

b. Organizational structure.

Hint 5

BABOK 7.2.4.
Solution components may include:
Structure of the organization, including interactions between the organization, its customers, and its suppliers

Front 6

Which factors will be most helpful to consider during release planning?
a. Business analysis metrics, key performance indications.
b. Resource constraints, which components deliver the greatest benefit, the competence of the testers.
c. Project budget, schedules, ability of organization to absorb change.
d. Project budget, resource constraints, project manager preference.

Back 6

c. Project budget, schedules, ability of organization to absorb change.

Hint 6

BABOK 7.2.4.
There are many factors that will guide these decisions, such as the overall project budget, the need to implement a solution or parts of the solution by a certain date, resource constraints, training schedule and ability for the business to absorb changes within a defined timeframe.

Front 7

Part of assessing organizational readiness is cultural assessment. Which of the following is not part of cultural assessment:
a. Assess willingness of stakeholder groups to accept change.
b. Determine if stakeholders understand why the change is occurring.
c. Determine if stakeholders want the change to be successful.
d. Assess the attitudes of different cultures towards change.

Back 7

d. Assess the attitudes of different cultures towards change.

Hint 7

BABOK 7.3.4.1.
Determine whether stakeholder groups genuinely want the change to be successful. Assess the beliefs, attitudes and feelings common to key stakeholder groups and the willingness of those stakeholder groups to accept a change. Determine whether stakeholders understand the reasons that a new solution is being implemented, whether they view that solution as something that will be beneficial, and they understand the reasons why a new solution is required.

Front 8

Operational assessment means:
a. Evaluate whether stakeholders are prepared to make use of the solution.
b. Assess impact of business analysis to the organization.
c. Evaluate whether stakeholders are physically capable of operating the equipment.
d. Evaluate alternative solutions and recommend effect on operational aspects of the organization.

Back 8

a. Evaluate whether stakeholders are prepared to make use of the solution.

Hint 8

BABOK 7.3.4.2.
Determine whether the organization is able to take advantage of the capabilities provided by the new solution, and evaluate whether stakeholders are prepared to make use of the new solution. Determine if training has been performed, whether new policies and procedures have been defined, whether IT systems required to support it are in place, and whether the solution is capable of performing at a required level.

Front 9

Force field analysis is a technique to assess the organizational readiness. Force field analysis is a:
a. Conflict-resolution technique that allows for a designated stakeholder to "choose sides," when stakeholders disagree.
b. Technique related to the type of influence that makes use of coercion, and studies the affects of coercion on stakeholders resisting change.
c. Graphical method for depicting forces that support and oppose change.
d. Technique for analyzing the effect of change on teams who are geographically
dispersed.

Back 9

c. Graphical method for depicting forces that support and oppose change.

Hint 9

Definition of the technique. BABOK 7.3.5.2.
Force field analysis is a graphical method for depicting the forces that support and oppose a change. It involves identifying the forces that support and oppose a change, depicting them on opposite sides of a line, and then estimating the strength of each force in order to assess which set of forces are stronger. Once this analysis is complete, the next step is to look for ways to strengthen the forces that support the desired outcome or generate new forces.

Front 10

Transition requirements are:
a. Unlike other requirements because they are no longer relevant after implementation.
b. Also known as implementation requirements because they defme the implementation needs.
c. Also known as solution requirements because they de:fme how the solution will be designed, built, tested, and implemented.
d. Unlike other requirements because they remain relevant after implementation.

Back 10

a. Unlike other requirements because they are no longer relevant after implementation.

Hint 10

They're used for things like running parallel systems and are no longer relevant once the solution is fully implemented. BABOK 7.4.2.

Front 11

What tasks are part of Solution Assessment and Validation?

Back 11

Assess Proposed Solution
Allocate Requirements
Assess Organizational Readiness
Define Transition Requirements
Validate Solution
Evaluate Solution Performance

Hint 11

Mnemonic PART VP
What "Part" does a BAplay in allocating requirements?

Front 12

Which is NOT an element of conducting a Vendor Assessment
a. Terms and Conditions
b. Contacts with Company and Established Relationships
c. Product Reputation and Market Position
d. Licensing and Pricing Models

Back 12

b. Contacts with Company and Established Relationships

Hint 12

BABOK 9.34

Front 13

How do constraints play a role in assesing the proposed solution?
a. Require customization to solutions
b. Limit available options
c. They don't play a role
d. They increase the cost

Back 13

b. Limit available options

Hint 13

BABOK 7.1.3
Assumptions may lead to certain solutions being favored, while constraints may limit available solution options.

Front 14

Transition requirements ________?
a. Will not be needed once transition is complete
b. Limit available options
c. Don't play a role
d. Increase the cost

Back 14

a. Will not be needed once transition is complete

Hint 14

BABOK 7.4.2 Transition requirements also have a different lifespan from other types of requirements, as they remain relevant only during the transition period between solutions.

BABOK 7.4.7 Transition requirements describe capabilities that must be developed in order for an organization to successfully transition between solutions.

Front 15

What should NOT be considered when evaluating the proposed solution?
a. Licensing
b. Product reputation
c. Price only
d. Experience

Back 15

c. Price only

Hint 15

BABOK 7.6.4 Evaluate Solution Performance Elements

Front 16

You are assisting business stakeholders to assemble their requirements into release packages. They have asked for a customer to be able to search for products and place an order in release 1.

Which of the following would you recommend to also include in Release 1?
a. Return goods
b. Create backup
c. Print delivery advice
d. Repeat order

Back 16

c. Print delivery advice

Hint 16

There are many factors that will guide these decisions, such as the overall project budget, the need to implement a solution or parts of the solution by a certain date, resource constraints, training schedule and ability for the business to absorb changes within a defined timeframe.

Alternative flows can be separated from the base use case and included in an extension to be moved into a later release.

Front 17

A segment or part of a solution, including technology and nontechnology portions.
a. Allocate
b. Data Conversion
c. Solution Components
d. Data Flow

Back 17

c. Solution Components

Hint 17

BABOK 7.2.4
-Solution components may include:
-Business policies and business rules
-Business processes to be performed and managed
-People who operate and maintain the solution, including their job functions and responsibilities
-Software applications and application components used in the solution.
-Structure of the organization, including interactions between the organization, its customers, and its suppliers

Front 18

Assigning of stakeholder and solution requirements to solution components, such as releases. It traces a requirement through implementation.
a. Allocate
b. Data Conversion
c. Solution Components
d. Data Flow

Back 18

a. Allocate

Hint 18

BABOK 7.2.2 Requirements allocation is the process of assigning stakeholder and solution requirements to solution components and to releases.

Front 19

Requirements for temporary capabilities in order to transition from an existing to a new solution.
a. Business Requirements
.b Stakeholder Requirements
c. Transition Requirements
d. Non-functional requirements

Back 19

c. Transition Requirements

Hint 19

BABOK 7.4.2 Transition requirements also have a different lifespan from other types of requirements, as they remain relevant only during the transition period between solutions.

BABOK 7.4.7 Transition requirements describe capabilities that must be developed in order for an organization to successfully transition between solutions.

Front 20

A flaw in a deliverable that either lessens its quality, or causes it to vary from its preferred characteristics.
a. Scope Creep
b. Bug
c. Gold Plating
d. Defect

Back 20

d. Defect

Hint 20

Glossary: A deficiency in a product or service that reduces its quality or varies from a desired attribute, state, or functionality.