fact finding (software engineering)

1. Fact finding Techniques
Fact finding is process of collection of data and information based on techniques which contain
sampling of existing documents, research, observation, questionnaires, interviews, prototyping
and joint requirements planning. System analyst uses suitable fact-finding techniques to develop
and implement the current existing system.
Fact-finding techniques
There are seven common fact-finding techniques
Sampling of existing documentation, forms and databases
Research and Site visits
Observation of the work environment
Questionnaires
Interviews
Prototyping
Joint requirements planning
Sampling of existing documentation,
forms and databases
The best way to analyse the existing system is to collect facts from existing documentation rather
than from human sources.
There are various kinds of documents to collect facts from existing documents. These include:
e-mails, customer complaints, suggestion box notes and reports.
Research and Site visits
Research and site visits, second technique, is the process of examining the problems which had
previously solved by other sources that can be either human or documents. To solve the
requirements of problem, the analyst visits to other organization that had previously experienced
for similar problems. In addition, the analyst can also find the information from database,
reference books, case studies and Internet.

2. Observation of the work environment
Another fact finding technique is observation. In this technique, system analyst participates in the
organization, studies the flow of documents, applies the existing system, and interacts with the
users. Observation can be a useful technique when the system analyst have user point of view.
Sampling technique called work sampling is useful for observation. By using this technique,
system analyst can know how employees spend their days.
Questionnaires
Questionnaires are also one of useful fact-finding technique to collect information from large
number of users. Users fill up the questions which are given by the system analyst and then give
the answers back to the system analyst. Qestionnaires can save time because system analyst
does not need to interview each of users and if the time of interview is short, questionnaires are
more useful. To fulfil the requirements of the system objective, system analyst should have the
ability to clearly define the design and frame of questionnaires.
Interviews
Interview is the most commonly used technique to collect information from the face-to-face
interviews. The purpose of interview is to find, verify, clarify facts, motivate end-users involved,
identify requirements and gather ideas and opinions. The role of interview includes interviewer
who is system analyst and interviewee who are system owner or user. Interviewing technique
needs good communication skills for interaction between system analyst and user.
Prototyping
Another fact-finding technique is known as prototyping which collects the requirement facts of the
system. Prototyping is sampling a small working model and it is more related to pre-design of the
information system. The implementation of prototyping can be developed in earlier stage of
system development life cycle when analyzing the facts. The process of prototyping facts in order
to specify the user’s requirements is also known as discovery prototyping.
Joint requirement planning
JRP is the structured group work meeting to identify, analyze problems and define the
requirements of system. JRP is becoming increasingly common in systems planning and
systems analysis to obtain group consensus on problems, objectives and requirements (Bentley
and Whitten; 2007). JRP can tabulate the facts efficiently in a short time and it can also replace
in the place of numerous and separate interviews. JRP contains different participants with each
specialized roles to perform structured meeting. JRP participants include sponsor, facilitator,
users and managers, scribes and IT staff. Sponsor is an individual in top management, who has
full authority to decide who will be participants, time and location of JRP session. The role of
facilitator is to lead JRP session, motivate participants, solve conflicts and meet the requirements

3. of meeting during the JRP session. Users in JRP session are responsible for rules and
requirement of business, prototype, and satisfactory decisions. And Managers are responsible
for projects, schedules and costs and training requirements. Scribes job is to record everything
discussed in the meeting. IT staff responsible for models and documentation concerning with
facts during the discussion.