The Business Readiness Assessment is a key activity conducted during the Implementation or Business Change Deployment stage of the project. Its primary purpose is to determine whether the target business areas, including the People, Organisation, and Processes, are sufficiently prepared to accept the business change and begin operating the new solution in the 'To Be' state. This involves checking factors such as whether staff have been trained, new processes are documented, communication has been effective, and necessary resources are in place. This assessment informs the 'Go/No Go' decision for the system's launch, ensuring a smooth transition to the new way of working.
(Reference: BCS Business Analysis Practice - Business Change Deployment, Business Readiness)

Functional and non-functional requirements sit within the detailed requirements area and describe what the solution must do and how well it must perform. Functional requirements define required behaviour, services, processing, calculations, or interactions. Non-functional requirements define qualities and constraints such as performance, security, usability, availability, and reliability. In a requirements hierarchy, these requirements are developed from broader business, general, and technical requirement categories. Option B is too narrow because it describes mainly non-functional requirements, not functional requirements. Option D is wrong because the highest level is the business need or business requirement. Option A refers to project principles, not solution requirements.
Therefore, functional and non-functional requirements are best described as an elaboration of General and Technical requirements.

Business analyst competencies are commonly grouped into personal qualities, business knowledge, and professional techniques. Personal qualities include communication, analytical thinking, facilitation, influencing, and relationship-building. Business knowledge covers understanding the organisation, industry, strategy, finance, processes, and business context. Professional techniques include modelling, requirements engineering, stakeholder analysis, investigation techniques, and business case development. IT skills may be useful for some business analysts, especially those working on digital or software-enabled change, but IT skills are not one of the three main competency groups. Treating IT skills as a core group would narrow the business analyst role too much, because business analysis is concerned with business change, not only technology delivery. Therefore, option D is not one of the three competency groups.

Traceability links requirements to other project artefacts. There are two main types: horizontal and vertical.
Horizontal traceability (Option A) links a requirement forward to its design, code, and test cases, and backward to its source (Option D), tracing its lifecycle from inception to delivery. Vertical traceability concerns tracing a requirement up or down the requirements hierarchy (C). This ensures that lower-level requirements (e.g., functional) are aligned with and fully support the higher-level business objectives, policies, and strategy. For example, it traces a solution requirement up to the business requirement it satisfies, validating that every low-level detail is necessary and justified by a high-level business need.
(Reference: BCS Requirements Engineering - Requirements Traceability)

Gap analysis is a structured process used to identify the differences between the current state (as-is) and the desired future state (to-be). The first step in this process involves understanding the current situation.
Key Steps in Gap Analysis:
* Assemble representations of the existing situation: This involves documenting the current state, including processes, systems, and capabilities.
* Compare representations of the existing and target situations: After understanding the current state, it is compared with the desired future state to identify gaps.
* Identify gaps to be addressed: Once gaps are identified, they are prioritized based on their impact and feasibility.
* Consider possible actions to address the gaps: Finally, potential solutions or actions are developed to bridge the identified gaps.
Evaluation of Each Option:
* A. Assemble representations of existing situation: Understanding the current state is the foundational step in gap analysis. Without this, there is no baseline for comparison. Conclusion: This is correct .
* B. Consider possible actions to address the gaps: This is a later step in the process, not the first.
Conclusion: This is not correct .
* C. Compare representations of the existing and target situations: Comparison occurs after the current state has been documented. Conclusion: This is not correct .
* D. Identify gaps to be addressed: Identifying gaps follows the documentation and comparison steps.
Conclusion: This is not correct .
Final Recommendation:
The first step in the gap analysis process is:
A). Assemble representations of existing situation.