Fact-Finding Techniques in System Analysis and Design

Topic: Interviews, Questionnaires, Observation, and Document Analysis

Example Project: Student Attendance Management System (SAMS)

Learning Objective: Understand how a system analyst collects reliable information from users and existing records before designing a new information system.

1. Introduction to Fact-Finding

Fact-finding is the systematic process of collecting information about an existing system, its users, business processes, problems, and requirements. It is an important activity in the System Analysis and Design (SAD) process.

Before developing a new system, an analyst must understand how the current system operates, what difficulties users experience, what information they need, and what improvements they expect.

For example, before developing a Student Attendance Management System, the analyst needs to understand how teachers record attendance, how attendance percentages are calculated, who can correct records, and how attendance reports are prepared.

1.1 Why Is Fact-Finding Necessary?

To understand the existing business process.
To identify problems and their causes.
To identify users and other stakeholders.
To collect functional and non-functional requirements.
To discover missing, duplicated, or unnecessary activities.
To verify assumptions before designing the system.
To reduce misunderstandings and costly changes during development.

1.2 Example: The Existing Attendance Process

Suppose a department records attendance using paper sheets or separate spreadsheets. Teachers calculate attendance percentages manually, and students contact teachers to check their records.

The analyst may investigate the following questions:

How does a teacher obtain the enrolled student list?
How is attendance recorded for each class?
How are absent and present students identified?
How are attendance percentages calculated?
Who approves attendance corrections?
How are reports prepared for academic management?

The answers provide the foundation for the requirements of the proposed system.

2. Four Major Fact-Finding Techniques

Technique	How It Works	Example in SAMS	Primary Benefit
Interview	Direct conversation with stakeholders.	Discuss attendance problems with teachers.	Detailed explanations and follow-up questions.
Questionnaire	A structured set of questions distributed to many people.	Ask 100 students about attendance-report access.	Collects comparable feedback from many respondents.
Observation	Watch a real process as it is performed.	Observe a teacher recording attendance.	Reveals actual practices and workflow problems.
Document Analysis	Examine existing forms, reports, rules, and records.	Review attendance sheets and report formats.	Identifies existing data fields, rules, and outputs.

3. Interview Technique

3.1 Definition

An interview is a fact-finding technique in which the system analyst asks questions directly to stakeholders to understand their needs, experiences, problems, and expectations.

Interviews may be conducted face-to-face or through an online meeting. They are especially useful when an analyst needs detailed information or wants to clarify an answer.

3.2 Types of Interviews

Type	Description	Example
Structured	Uses a predetermined list of questions.	Ask every teacher the same questions about attendance recording.
Unstructured	Uses a flexible conversation guided by the topic.	Discuss general difficulties with a department administrator.
Semi-structured	Uses prepared questions while allowing follow-up questions.	Ask standard questions and explore unexpected problems.

3.3 Interview Process

Step 1: Identify the interviewee.
Choose stakeholders who understand the process, such as teachers, academic administrators, or IT staff.

Step 2: Define the purpose.
Decide what information is needed from the interview.

Step 3: Prepare questions.
Write clear, neutral questions and arrange them in a logical order.

Step 4: Conduct the interview.
Explain the purpose, ask questions, listen carefully, and ask follow-up questions where necessary.

Step 5: Record the findings.
Document the answers, issues, proposed requirements, and unresolved questions.

Step 6: Confirm the findings.
Share a summary with the interviewee to correct misunderstandings.

3.4 Sample Interview for SAMS

Interviewee: Course Teacher

Purpose: Understand the existing attendance-recording process.

Note: The following is a sample interview guide, not a record of an actual interview.

Q1. How do you currently record attendance?
Possible finding: Attendance is recorded on paper or in a spreadsheet.

Q2. How do you obtain the student list for a course section?
Possible finding: The teacher uses an enrolment list provided by the department.

Q3. How do you calculate attendance percentages?
Possible finding: Percentages are calculated manually or by spreadsheet formulas.

Q4. What problems do you experience?
Possible finding: Preparing reports and checking old records takes time.

Q5. Should teachers be able to edit attendance after submission?
Possible finding: Corrections may require authorization and a record of the change.

Q6. What reports do you need?
Possible finding: Student-wise and course-wise attendance reports are required.

3.5 Advantages of Interviews

Provides detailed information.
Allows immediate clarification.
Helps discover unexpected problems.
Allows the analyst to explore stakeholder expectations.
Builds communication between users and the analyst.

3.6 Limitations of Interviews

Can be time-consuming when many people are involved.
Answers may be influenced by personal opinions or memory.
Some interviewees may not describe their actual practices accurately.
Findings need to be documented and validated carefully.

4. Questionnaire Technique

4.1 Definition

A questionnaire is a structured set of written questions used to collect information from a group of respondents. It may be distributed using online forms, email, printed sheets, or other approved channels.

Questionnaires are useful when the analyst needs comparable information from many people within a limited period.

4.2 Types of Questionnaire Questions

Question Type	Description	Example
Closed-ended	Respondents select from predefined answers.	Do you currently check attendance online? Yes / No.
Multiple-choice	Respondents choose one or more options.	Which report do you need? Student-wise / Course-wise / Both.
Rating scale	Respondents rate an opinion or experience.	Rate the difficulty of manual attendance recording from 1 to 5.
Open-ended	Respondents answer in their own words.	What improvement would you suggest for attendance management?

4.3 Sample Questionnaire for SAMS

Target respondents: Students

Purpose: Identify student needs for an attendance management system.

The questions below are examples. Responses should be collected before drawing conclusions about actual users.

Q1. How do you currently check your attendance?

Ask the course teacher.
Check a displayed attendance sheet.
Use an existing online system.
Other.

Q2. How frequently do you need to check your attendance?

Every week.
Several times during a semester.
Only before examinations.
Other.

Q3. Which information should the system display?

Present and absent sessions.
Total classes conducted.
Attendance percentage.
Course-wise attendance summary.
All of the above.

Q4. How useful would online attendance information be?

1 — Not useful.
2 — Slightly useful.
3 — Moderately useful.
4 — Very useful.
5 — Extremely useful.

Q5. What concerns would you have about an online attendance system?

Answer: __________________________________________

Q6. What additional features would you suggest?

Answer: __________________________________________

4.4 Questionnaire Design Guidelines

Use simple and unambiguous language.
Ask one clear question at a time.
Avoid leading questions that encourage a particular answer.
Provide relevant answer options.
Include an appropriate option such as “Other” where needed.
Keep the questionnaire reasonably short.
Test it with a small group before wider distribution.
Explain the purpose and handle respondents' information appropriately.

4.5 Advantages of Questionnaires

Can collect information from many respondents.
Responses can be compared and summarized.
Online questionnaires are relatively easy to distribute.
Respondents can answer at a convenient time.
Rating-scale responses can help identify patterns.

4.6 Limitations of Questionnaires

Response rates may be low.
Respondents may misunderstand a question.
Open-ended answers may be difficult to analyze.
The analyst cannot always ask immediate follow-up questions.
A poorly designed questionnaire may produce misleading results.

5. Observation Technique

5.1 Definition

Observation is a fact-finding technique in which the analyst watches users perform their normal tasks to understand the actual workflow, tools, decisions, and difficulties involved.

People may describe a process differently from how they actually perform it. Observation helps the analyst identify such differences.

5.2 Types of Observation

Type	Description	Example
Direct observation	The analyst watches the process as it occurs.	Observe a teacher taking attendance in class.
Participant observation	The observer participates in some parts of the activity when appropriate.	Assist with a controlled demonstration of an attendance workflow.
Structured observation	The analyst uses a checklist of specific actions or events.	Record the steps and time needed to prepare a report.
Unstructured observation	The analyst records general behavior and issues without a rigid checklist.	Explore how staff handle unexpected attendance corrections.

5.3 Observation Example: Taking Attendance

Suppose the analyst observes a teacher taking attendance for a class of 50 students. The analyst records the workflow and notes where delays or errors may occur.

Observed Activity	Potential Issue	Possible System Requirement
Teacher finds the correct student list.	Lists may be stored in different locations.	Display the enrolled list by course and section.
Teacher marks each student.	Manual marking may take time.	Provide a simple attendance-entry interface.
Teacher calculates attendance totals.	Manual calculation may introduce errors.	Calculate attendance percentages automatically.
Teacher checks earlier records.	Historical records may be difficult to retrieve.	Provide searchable attendance history.
Teacher corrects a mistaken entry.	The correction may not be documented.	Provide authorized corrections with audit history.

5.4 Sample Observation Checklist

Observation Item	Finding / Notes
Process observed	Recording student attendance
Person performing the task	[Teacher role or approved identifier]
Tools used	[Paper sheet, spreadsheet, or existing application]
Sequence of activities	[Record each step in order]
Time required	[Record actual measured time]
Problems observed	[Document factual observations]
Potential improvement	[Describe possible improvement for validation]

5.5 Advantages of Observation

Reveals the actual working process.
Identifies unnecessary steps and delays.
Helps discover exceptions and workarounds.
Provides context for information gathered through interviews.
Can help establish baseline task times.

5.6 Limitations of Observation

People may change their behavior when being observed.
Observation may require considerable time.
Some activities occur too rarely to observe during a short visit.
The observer may misinterpret the reason for an action.
Privacy and permission must be considered before observing real work.

6. Document Analysis Technique

6.1 Definition

Document analysis is the examination of existing documents, forms, spreadsheets, reports, policies, manuals, and records to understand the current system and identify information requirements.

Documents can reveal what data is collected, how it is organized, what rules apply, and what outputs users expect.

6.2 Documents for the SAMS Project

Document	Information to Identify	Potential Requirement
Attendance Sheet	Student identifiers, dates, attendance marks.	Store attendance by student and class session.
Student Enrolment List	Student ID, name, course, section.	Display the correct enrolled student list.
Course Offering List	Course, term, section, assigned teacher.	Maintain course and teacher assignments.
Attendance Summary	Sessions held, attendance totals, percentages.	Generate attendance statistics and reports.
Academic Attendance Policy	Calculation rules, thresholds, exceptions.	Apply approved attendance rules.
Correction Request Form	Reason for correction, approval, date.	Support controlled and traceable corrections.

6.3 Document Analysis Process

Step 1: Identify relevant documents.
Request only the documents needed to understand the attendance process.

Step 2: Check the source and version.
Determine whether each document is current, approved, and relevant.

Step 3: Identify data fields.
Record identifiers, dates, statuses, calculations, and relationships.

Step 4: Identify business rules.
Extract documented rules and distinguish official policy from informal practice.

Step 5: Compare documents.
Look for inconsistent field names, duplicated information, and conflicting rules.

Step 6: Validate findings.
Ask the responsible stakeholders to confirm interpretations and resolve conflicts.

6.4 Example: Analyzing an Attendance Sheet

Suppose an existing attendance sheet contains the following fields:

Student ID	Student Name	Course Code	Class Date	Status
2026-001	Example Student A	CSE-301	2026-10-01	Present
2026-002	Example Student B	CSE-301	2026-10-01	Absent
2026-003	Example Student C	CSE-301	2026-10-01	Present

From this sample, the analyst can identify potential data entities such as Student, Course Offering, Class Session, and Attendance.

The analyst should also investigate whether the course code alone uniquely identifies a course offering. If courses repeat across terms or sections, the database may need a separate course-offering identifier.

6.5 Advantages of Document Analysis

Provides evidence of existing data structures and reports.
Helps identify mandatory fields and data relationships.
Can reveal official policies and business rules.
Allows analysis without interrupting normal work.
Helps compare written procedures with actual practices.

6.6 Limitations of Document Analysis

Documents may be outdated or incomplete.
Written procedures may differ from actual practice.
Some business rules may not be documented.
Different departments may use inconsistent formats.
Access to confidential records may be restricted.

7. Comparison of the Four Techniques

Criteria	Interview	Questionnaire	Observation	Document Analysis
Direct interaction	High	Low	Varies	Usually low
Suitable for large groups	Less suitable	Highly suitable	Less suitable	Depends on documents
Detailed explanations	High	Limited to questions	Behavior-focused	Depends on content
Shows actual behavior	Indirectly	Indirectly	Directly	Usually indirectly
Identifies data fields	Sometimes	Sometimes	Sometimes	Very useful
Common limitation	Time required	Low response rate	Observer effect	Outdated documents

8. Combining Fact-Finding Techniques

A reliable system analyst should not depend on a single technique. Combining techniques helps verify information from different sources. This process is commonly called triangulation.

8.1 Combined Example for SAMS

Interview: A teacher explains that attendance reporting takes too much time.

Questionnaire: A wider group of teachers is asked whether report preparation is a common problem.

Observation: The analyst measures the actual steps and time required to prepare a report.

Document Analysis: Existing reports are examined to identify the required columns, calculations, and filters.

After comparing these findings, the analyst may propose the requirement:

Proposed Requirement: The system shall generate an attendance report for an authorized course and date range, displaying student identifiers, attendance totals, and attendance percentages.

The requirement should then be reviewed with stakeholders and checked for completeness, clarity, and feasibility.

9. From Fact-Finding to System Requirements

Fact-finding is not complete when information has merely been collected. The analyst must organize the findings and convert them into clear, testable requirements.

Finding	Analysis	Proposed Requirement	Possible Test
Teachers maintain separate attendance sheets.	Records may be difficult to consolidate.	The system shall maintain attendance records in a centralized database.	Verify records can be retrieved through the application.
Attendance percentages are calculated manually.	Manual calculations may introduce errors.	The system shall calculate attendance percentages using the approved formula.	Compare system results against known test cases.
Historical reports take time to prepare.	Users need searchable historical data.	The system shall generate reports using approved filters.	Check results for a selected course and date range.
Attendance corrections are not consistently recorded.	Changes may be difficult to audit.	The system shall record authorized changes with user and timestamp information.	Review the audit history after a test correction.

10. Sample Fact-Finding Plan

The following plan is an example for a student project. Actual participants, dates, and findings should be recorded during the investigation.

Activity	Target / Source	Output
Prepare interview questions	Teachers and academic administrators	Interview guide
Conduct interviews	Selected stakeholders	Interview notes and findings
Distribute questionnaire	Selected student or teacher respondents	Response dataset and summary
Observe attendance workflow	Approved classroom or administrative process	Workflow notes and measured timings
Analyze documents	Attendance sheets, course lists, policies	Data fields and documented rules
Validate findings	Relevant stakeholders	Confirmed requirements and open issues

11. Common Mistakes to Avoid

Assuming that one person's opinion represents every user.
Asking leading or ambiguous interview questions.
Using a questionnaire without testing its clarity.
Observing a process without recording evidence.
Assuming every old document reflects the current policy.
Confusing stakeholder suggestions with approved requirements.
Failing to protect confidential information during fact-finding.
Writing requirements that cannot be verified through testing.
Claiming that interviews or observations occurred when they did not.

12. Student Exercises

Exercise 1: Identify the Technique

Choose the most appropriate primary technique for each situation.

Question 1: A teacher explains why attendance reports take too long.

Answer: Interview. It allows the analyst to ask follow-up questions and understand the reasons behind the problem.

Question 2: The analyst wants feedback from 200 students.

Answer: Questionnaire. It can collect comparable information from a large group.

Question 3: The analyst watches a teacher record attendance.

Answer: Observation. It reveals the actual workflow and possible delays.

Question 4: The analyst reviews an official attendance policy.

Answer: Document analysis. It helps identify documented business rules and institutional requirements.

Exercise 2: Develop an Interview Guide

Prepare ten interview questions for an academic administrator. Your questions should cover student records, course sections, attendance corrections, report generation, and access permissions.

Exercise 3: Design a Questionnaire

Prepare a questionnaire containing at least:

Three closed-ended questions.
Two multiple-choice questions.
One rating-scale question.
Two open-ended questions.

Exercise 4: Prepare an Observation Checklist

Design a checklist for observing a teacher recording attendance for a class of 40–50 students. Include the sequence of activities, tools used, errors, and actual time taken.

Exercise 5: Analyze a Document

Create a sample attendance sheet and identify its fields, possible data entities, validation rules, and potential database relationships.

Exercise 6: Write Requirements

Using the findings from the previous exercises, write five functional requirements and three non-functional requirements for the Student Attendance Management System.

13. Review Questions

What is fact-finding in System Analysis and Design?
Why is fact-finding necessary before software development?
What is the difference between structured and unstructured interviews?
When is a questionnaire more suitable than an interview?
How can observation reveal problems that interviews may miss?
What information can be obtained from document analysis?
What is triangulation, and why is it useful?
How can the analyst validate information collected from stakeholders?
Why must proposed requirements be measurable and testable?
What privacy considerations apply during fact-finding?

14. Conclusion

Fact-finding is a fundamental activity in System Analysis and Design. Interviews provide detailed explanations, questionnaires collect structured feedback from many respondents, observation reveals actual work practices, and document analysis identifies existing data structures and formal rules.

For the Student Attendance Management System, using all four techniques can help the analyst understand the existing attendance process and develop requirements that are more accurate, complete, and useful.

The final goal is not simply to collect information, but to transform validated findings into clear requirements that can guide system design, implementation, and testing.