How does an analyst investigate the current system and gather facts?
The fact-finding techniques used during investigation: interviews, questionnaires, observation and inspection of documents, with the advantages and disadvantages of each.
A CCEA A-Level Digital Technology answer on the fact-finding techniques used during system investigation: interviews, questionnaires, observation and document inspection, with the advantages, disadvantages and suitability of each.
Reviewed by: AI editorial process; not yet individually human-reviewed
Have a quick question? Jump to the Q&A page
Jump to a section
What this dot point is asking
CCEA wants you to describe the fact-finding techniques an analyst uses during investigation, interviews, questionnaires, observation and document inspection, and to weigh the advantages and disadvantages of each so you can recommend the right technique for a situation. Fact-finding is how the requirements specification is built.
The fact-finding techniques
- Interviews. One-to-one questioning of staff. Rich, detailed information with the chance to follow up unclear answers, but time-consuming, so only a few people can be interviewed, and the interviewer may bias the answers.
- Questionnaires. Written questions sent to many people. Reach a large number quickly and cheaply, and closed questions are easy to analyse, but the information is shallow, there is no follow-up, and response rates can be low.
- Observation. Watching staff at work. Shows what people actually do rather than what they say, but people may behave differently when watched (the Hawthorne effect), and it only captures the period observed.
- Document inspection. Examining existing forms, reports and records. Reveals the real data, formats and rules in use, but documents may be out of date or incomplete.
Choosing the right technique
The choice follows the need. To understand a manager's priorities, interview; to survey hundreds of customers, use a questionnaire; to see how a process really runs, observe; to size and format existing data, inspect documents. Because no single technique is complete, a good investigation triangulates: for example, observe a process, then interview the operator to explain what was seen, then inspect the documents the process produces.
Why fact-finding quality matters
The requirements specification is only as good as the facts behind it. Poor fact-finding (for example interviewing one person and assuming they speak for everyone) produces missed or wrong requirements, which propagate into a flawed design and a system that does not fit. Combining techniques and checking findings against each other is what makes the requirements trustworthy.
Try this
Q1. State the fact-finding technique best suited to gathering shallow information from a large number of people. [1 mark]
- Cue. A questionnaire.
Q2. Give one advantage and one disadvantage of observation as a fact-finding technique. [2 marks]
- Cue. Advantage: it shows what staff actually do, including informal workarounds. Disadvantage: people may behave differently when watched (the Hawthorne effect), and it only captures the observed period.
Q3. Explain why an analyst usually combines several fact-finding techniques. [2 marks]
- Cue. No single technique gives depth, breadth, real behaviour and factual data at once, so combining them lets the strengths of one cover the weaknesses of another and allows findings to be cross-checked.
Exam-style practice questions
Practice questions written in the style of CCEA exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.
CCEA AS 16 marksDescribe two fact-finding techniques an analyst could use, giving one advantage and one disadvantage of each.Show worked answer →
Choose two distinct techniques and give a balanced advantage and disadvantage for each.
Interviews: the analyst questions staff directly. Advantage: rich, detailed information and the chance to follow up unclear answers. Disadvantage: time-consuming and costly, so only a few people can be interviewed, and the interviewer may bias answers.
Questionnaires: a set of written questions sent to many people. Advantage: reach a large number of respondents quickly and cheaply, with answers easy to analyse if closed questions are used. Disadvantage: shallow, with no chance to follow up, and response rates can be low.
Other valid pairs include observation (shows what staff actually do, but they may behave differently when watched, the Hawthorne effect) and document inspection (reveals real data and rules, but documents may be out of date).
Markers award marks for each technique described with a valid advantage and disadvantage. A list of techniques with no advantages or disadvantages caps the mark.
CCEA AS 14 marksAn analyst needs to find out the exact volume and format of data currently processed by a department. Recommend a fact-finding technique and justify your choice.Show worked answer →
Recommend inspection of existing documents and records (with observation as support) and justify it against the need for exact, factual data.
Existing documents and records (such as order forms, reports and files) show the real data the department handles, its format, and the rules applied, which is exactly what is needed to size and format the new system. Observation can confirm how the documents are actually used in practice. Interviews and questionnaires would give people's recollections, which are less reliable for exact volumes and formats than the documents themselves.
Markers reward the recommendation and a justification linked to the need for precise, factual data on volume and format, and credit the rejection of interview or questionnaire as less reliable for this specific purpose.
Related dot points
- The stages of the systems development life cycle, the activities carried out in each stage and the documented outputs each stage hands on to the next.
A CCEA A-Level Digital Technology answer on the systems development life cycle: its stages from feasibility through analysis, design, implementation, testing and maintenance, the activities in each, and the documents each stage produces.
- The purpose and types of feasibility (technical, economic, legal, operational and schedule), fact-finding techniques for requirements gathering, and functional and non-functional requirements.
A CCEA A-Level Digital Technology answer on the feasibility study (technical, economic, legal, operational and schedule), fact-finding techniques for gathering requirements, and the difference between functional and non-functional requirements.
- Designing the inputs, outputs, processing, data storage and user interface of a system, and the design tools used: data flow diagrams, system flowcharts, entity relationship diagrams and the data dictionary.
A CCEA A-Level Digital Technology answer on the design stage: specifying inputs, outputs, processing, data storage and the user interface, and the design tools used including data flow diagrams, system flowcharts, entity relationship diagrams and the data dictionary.
- The waterfall, iterative or incremental and agile or rapid application development methodologies, their characteristics, advantages, disadvantages and the situations that suit each.
A CCEA A-Level Digital Technology answer comparing the waterfall, iterative or incremental and agile or rapid application development methodologies, their characteristics, strengths, weaknesses and the projects that suit each approach.
- The purpose and contents of technical documentation and user documentation, and the audience each serves during development, use and maintenance.
A CCEA A-Level Digital Technology answer on system documentation: the purpose, contents and audience of technical documentation and user documentation, and why each matters during development, use and maintenance.
Sources & how we know this
- CCEA GCE Digital Technology specification — CCEA (2016)