BCS PC-BA-FBA-20 Exam Dumps

A mission statement defines the organization's purpose and primary objectives, often focusing on what the organization does and how it operates in the present. In contrast, a vision statement outlines the long-term aspirations of the organization---what it aims to become in the future. The mission provided---'To meet or undercut all our competitors' prices'---is focused on price competitiveness, which is a tactical approach rather than a strategic aspiration.

Let's analyze each option:

A . To offer the best value office fitting service: While this aligns somewhat with the mission, it is more of a value proposition or operational goal rather than a visionary statement. It lacks the aspirational and long-term focus that defines a vision.

B . To reduce the cost of office fitting by 5%: This is a specific, measurable objective, but it is too narrow and tactical to qualify as a vision. Visions are broader and not tied to specific metrics.

C . To increase the company's market share: Increasing market share is a strategic goal, but it is still an intermediate step toward achieving something greater. It does not capture the overarching ambition of the company.

D . To be the premier office fitting company: This option reflects a long-term aspiration and aligns with the characteristics of a vision statement. It expresses the desire to achieve leadership and excellence in the industry, which is consistent with the mission of being competitive on price while aiming for a higher status.

According to the BCS Business Analysis Framework , a vision statement should inspire and guide the organization toward its ultimate goal. Therefore, D is the most appropriate choice.

Prototyping is a technique used to create a working model of a system or product to validate requirements and gather feedback. Let's evaluate each statement to determine which are false :

Evaluation of Each Statement:

A . Suitable for waterfall requirements elicitation: Prototyping is generally not suitable for traditional waterfall methodologies because waterfall follows a linear, sequential approach where requirements are defined upfront before development begins. Prototyping, on the other hand, involves iterative feedback loops, which are more aligned with Agile methodologies. Conclusion: This statement is false .

B . Allows an analyst to confirm their understanding of requirements: Prototyping enables analysts to validate their understanding of requirements by creating a tangible representation of the system for stakeholders to review and provide feedback. Conclusion: This statement is true .

C . Only suitable for Agile project environments: While prototyping is commonly used in Agile environments due to its iterative nature, it is not limited to Agile. Prototyping can also be used in hybrid or iterative waterfall projects to clarify requirements and reduce ambiguity. Conclusion: This statement is false .

D . Enables the elicitation of usability requirements: Prototyping is particularly effective for gathering usability requirements because it allows stakeholders to interact with a mock-up or early version of the system, providing insights into user experience and interface design. Conclusion: This statement is true .

A T-shaped professional is a concept used to describe individuals who possess a combination of broad and deep skills. Let's evaluate each option to determine which best describes this concept:

Key Characteristics of a T-Shaped Professional:

Vertical Line (Deep Expertise): Represents specialized knowledge or expertise in one specific area.

Horizontal Line (Broad Skills): Represents a wide range of general skills or knowledge across multiple disciplines, enabling collaboration and adaptability.

Evaluation of Each Option:

A . T stands for Talented: While 'talented' may describe the individual, the 'T' specifically refers to the shape that visually represents their skill profile (broad and deep). Conclusion: This is not correct .

B . T-shaped professional has a deep level of skills in many areas: A T-shaped professional does not have deep expertise in many areas; they have deep expertise in one area and broad skills across others. Conclusion: This is not correct .

C . The crossbar of the T-shape represents having a good level of skills across many areas, and deep level of skills in a specialism: This accurately describes the T-shaped professional: the horizontal bar represents broad skills, and the vertical bar represents deep expertise in a specific area. Conclusion: This is correct .

D . A T-Shaped professional possesses a deep understanding in a given area and leads a team of people in other areas: While leadership may be a trait of some T-shaped professionals, it is not a defining characteristic of the concept. Conclusion: This is not correct .

The Waterfall methodology is a linear approach where requirements are defined upfront, and changes are difficult to accommodate once the project begins. Agile methodology , on the other hand, emphasizes flexibility and adaptability to changing requirements.

Key Considerations:

Inherent Uncertainty in Cost: While cost uncertainty exists in both methodologies, Agile does not specifically address this drawback of Waterfall.

Inflexibility to Changing Requirements: Waterfall's rigid structure makes it difficult to incorporate changes once the project starts. Agile addresses this by allowing iterative development and continuous feedback.

Capturing All Requirements Upfront: Agile does not aim to capture all requirements upfront; instead, it embraces evolving requirements throughout the project.

Stakeholder Agreement on Scope Before Work Begins: Agile encourages ongoing collaboration with stakeholders rather than requiring scope agreement upfront.

Evaluation of Each Option:

A . The agile methodology addresses the inherent uncertainty in cost associated with waterfall: Agile does not specifically address cost uncertainty. Conclusion: This is not correct .

B . Agile development addresses the inflexibility of waterfall as it pertains to changing requirements: This is the primary drawback of Waterfall that Agile addresses through its iterative and flexible approach. Conclusion: This is correct .

C . The agile methodology captures all requirements at the start of a project to reduce risks typically experienced in waterfall: Agile does not capture all requirements upfront; it embraces evolving requirements. Conclusion: This is not correct .

D . Agile development requires stakeholders to agree to the scope of the project before the work begins, reducing uncertainty in the design: Agile does not require upfront scope agreement; it promotes adaptive planning. Conclusion: This is not correct .

Final Recommendation:

The drawback of Waterfall addressed in Agile is: B . Agile development addresses the inflexibility of waterfall as it pertains to changing requirements.

Change control is a critical aspect of requirements management in business analysis. It ensures that changes to requirements are systematically evaluated, approved, and implemented without negatively impacting the project.

Key Considerations:

Change Control Definition: Change control is a formal process used to manage modifications to requirements, ensuring that changes are necessary, feasible, and aligned with project goals.

Preventing Changes: Change control does not prevent changes but ensures they are managed appropriately.

Tracing Requirements: Tracing requirements involves tracking their origin and impact, which is separate from managing changes.

Evaluation of Each Option:

A . A process to control version numbering: Version numbering is a documentation practice, not the purpose of change control. Conclusion: This is not correct .

B . A process to manage changes to requirements: This accurately describes change control as a structured approach to handling modifications to requirements. Conclusion: This is correct .

C . A process to ensure that changes cannot be made: Change control does not block changes but ensures they are managed effectively. Conclusion: This is not correct .

D . A process to trace requirements: Tracing requirements is a related but distinct activity focused on linking requirements to their source and impact. Conclusion: This is not correct .