Home › BCS BA Found. › Practice questions › Establishing the Requirements
BCS BA Found. · BCS · Establishing the Requirements · Bank updated 2026-11-04

BCS BA Found. practice questions: Establishing the Requirements

5 free questions from 17 on this area · answer and explanation for each · no sign-up

These 5 questions come from the Establishing the Requirements section of our BCS BA Found. bank (17 questions on this area, which carries 10% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.

Try 6 free BCS BA Foundation questions → All BCS BA Found. sample questions

Free: 6 questions in study mode, no card. All 17 Establishing the Requirements questions and the full BCS BA Found. bank: $15 one-time.

1/5 · Establishing the Requirements · easy
The requirements engineering framework referenced in the BCS Business Analysis syllabus describes a set of core activities, with requirements management running continuously alongside them. Which four activities make up that core sequence?
ADiscovery, Negotiation, Approval, Closure
BInvestigation, Prioritisation, Sign-off, Traceability
CElicitation, Analysis (and negotiation), Documentation, Validation
DElicitation, Design, Build, Test
Answer: C. The requirements engineering framework used in the BCS syllabus sets out elicitation, analysis and negotiation, documentation, and validation as the core activities, with requirements management operating continuously throughout the lifecycle to control change and maintain traceability. Source: the BCS Business Analysis Foundation syllabus v4.1 + 'Business Analysis, 4th Edition' (Paul & Cadle, BCS 2020) - Establishing the Requirements
2/5 · Establishing the Requirements
Within the requirements hierarchy, a 'technical' business requirement is best distinguished from a 'general' business requirement by the fact that it...
ACannot be assigned a 'Could Have' priority under MoSCoW, because that category is reserved for general business requirements in the requirements hierarchy
BStill expresses a business-level need, but already places a constraint on the type of technology, architecture or system approach that may be used
CDescribes what the finished software system must do at a detailed functional level, rather than expressing a need at the level of the business
DIs authored by the IT delivery team rather than being derived from business stakeholders, and sits at the level of the solution rather than the business
Answer: B. General business requirements state a business need without reference to any particular technology, whereas technical business requirements remain expressions of business need but already impose a technology-related constraint (for example, mandating integration with an existing platform), narrowing the range of acceptable solutions. Source: the BCS Business Analysis Foundation syllabus v4.1 + 'Business Analysis, 4th Edition' (Paul & Cadle, BCS 2020) - Establishing the Requirements
3/5 · Establishing the Requirements · hard
An organisation states: 'A customer's credit limit must not exceed £5,000 unless the increase is approved by a senior manager.' How is this business rule best classified?
AAn operative (behavioural) business rule, which constrains an action and can be overridden under a defined condition of authority
BA definitional (structural) business rule that simply defines a term or derives a calculated value, and cannot be overridden by any approval
CA functional requirement describing a feature that a software system must provide for users, such as a credit limit screen
DA non-functional requirement of the solution, such as a performance, availability or security quality attribute of the IT system
Answer: A. Business rules can be classified as definitional (fixed facts, definitions or derivations that cannot be violated) or operative/behavioural (rules that constrain actions but can, under specified conditions such as managerial approval, be overridden). The credit limit example constrains behaviour and permits an authorised exception, making it operative rather than definitional. Source: the BCS Business Analysis Foundation syllabus v4.1 + 'Business Analysis, 4th Edition' (Paul & Cadle, BCS 2020) - Establishing the Requirements
4/5 · Establishing the Requirements · easy
Future users of a proposed customer self-service portal cannot describe what they want the screens and navigation to look like when simply asked in interviews, but they are quick to say what they like or dislike when shown a sample screen. Which elicitation technique would BEST help the analyst draw out these requirements?
AA further round of structured one-to-one interviews using more detailed open questions
BPrototyping, building sample screens or a mock-up for users to react to and refine
CSpecial purpose records logging how long users currently spend on each self-service task
DAnalysis of documents from the current system, since it already has customer-facing screens
Answer: B. Prototyping is specifically well suited to situations where stakeholders find it difficult to articulate requirements in the abstract but can readily respond to something concrete, such as a mock-up of screens or navigation. This makes it a common choice for interface- and interaction-related requirements where users know what they want only when they see it. Interviews, document analysis and special purpose records each target different kinds of information and do not address this particular difficulty. Source: the BCS Business Analysis Foundation syllabus - Establishing the Requirements
5/5 · Establishing the Requirements
A business analyst is running a two-week timebox to produce a requirements document. Halfway through, it is clear that not all planned sections will be finished by the agreed end. The team has a prioritised list of what the timebox must deliver. What is the best course of action?
Areduce the set of deliverables and close the timebox on the agreed date
Bmove the end date so that every planned deliverable can be completed
Cstart the dependent timebox early so that the lost time is recovered
Dleave the timebox open until the missing items are finished, then review
Answer: A. Technique 75 states that if the agreed completion time may be missed, the deliverable set should be reduced in scope rather than letting the timebox overrun, because the philosophy is that scope slips but timing never. Prioritisation, such as MoSCoW, supports deciding what to drop. Source: Paul, Cadle, Turner (eds), Business Analysis Techniques, 2nd ed., BCS, Technique 75: Timeboxing, p. n/a Source: the BCS Business Analysis Foundation syllabus v4.1 + 'Business Analysis, 4th Edition' (Paul & Cadle, BCS 2020) - Investigating the Business Situation
Try 6 more free BCS BA Foundation questions → See the whole BCS BA Found. bank

Other BCS BA Found. areas

The same kind of free sample for every other section of the BCS BA Found. bank:

What is Business Analysis?12 qThe Competencies of a Business Analyst11 qThe Strategic Context for Business Analysis16 qThe Business Analysis Service Framework10 qInvestigating the Business Situation21 qAnalysing and Managing Stakeholders18 qImproving Business Services and Processes19 qDefining the Solution15 qMaking the Business Case12 qDocumenting and Modelling Requirements16 qValidating and Managing Requirements9 qDelivering the Requirements11 qDelivering the Business Solution12 q

Practise BCS BA Found. with instant feedback

6 free questions in study mode · no card · full BCS BA Found. bank with area filters and the error log: $15 one-time · no dumps, no ads.

Start BCS BA Foundation free →
Read next
BCS Foundation Certificate in Business Analysis vs ECBA: Which Entry-Level BA Certificate? BCS BA Foundation (40 questions, 60 min, £200) vs IIBA ECBA (50 questions, 75 min, $395). Format, cost and who each fits. Verified 19 Oct 2026.
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by BCS. BCS BA Found. and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official BCS materials (as of August 2026); always confirm current details with the vendor before booking.