fact-finding fact-finding overview first, you must identify the information you need develop a...
TRANSCRIPT
Fact-FindingFact-Finding Overview
First, you must identify the information you need
Develop a fact-finding planWho, What, Where, When, How, and Why?
Difference between asking what is being done and what could or should be done
1
System Analysis and Design System Planning
Avicenna2
Preliminary Investigation OverviewPreliminary investigation used
to study the system request and recommend specific action
Analyst through interacting with managers and users gathers facts about the problem or opportunity, project scope and constraints, project benefits, and estimated development time and costs
The product of the preliminary investigation is a report to management
System Analysis and Design System Planning
Avicenna3
Preliminary Investigation OverviewPreliminary investigationInteraction with Managers and Users
Let people know about the investigation and explain your role
Employee attitudes and reactions are important and must be considered
Be careful in your use of the word problemQuestion users about additional capability they
would like to have
System Analysis and Design System Planning
Avicenna4
Preliminary Investigation Overview
Planning the Preliminary InvestigationDuring a preliminary
investigation, a systems analyst typically follows a series of steps
The exact procedure depends on the nature of the request, the size of the project, and the degree of urgency
System Analysis and Design System Planning
Avicenna5
Preliminary Investigation Overview
Step 1: Understand the Problem or OpportunityDetermine which departments, users, and
business processes are involvedSystem request in general does not revel the
underlying problem, but only symptom A popular technique for investigating causes
and effects is called a fishbone diagram
System Analysis and Design System Planning
Avicenna6
Preliminary Investigation Overview
Step 1: Understand the Problem or Opportunity
fishbone diagram An analysis tool that
represents the possible causes of a problem
First states the problem as main bone
Sub-bones represent possible causes of the problem
In each sub-bone analyst identifies possible causes, draws them as horizontal sub-bones
System Analysis and Design System Planning
Avicenna7
Preliminary Investigation Overview
Step 2: Define the Project Scope and ConstraintsProject scope Project creepConstraint
System Analysis and Design System Planning
Avicenna8
Preliminary Investigation Overview
Step 2: Define the Project Scope and Constraints
Determining the project scope means defining the specific boundaries, or extent, of the project
Define project scope by creating a list with sections called must do, should do, could do, and won’t do
Projects with very general scope called project creep
A constraint is a requirement or condition that the system must satisfy or an outcome that the system must achieve
System constraints also define project scope
System Analysis and Design System Planning
Avicenna9
Preliminary Investigation Overview Step 2: Define the Project Scope and Constraints When examining constraints, analyst should identify their
characteristicsPresent versus future Internal versus externalMandatory versus desirableRegardless of the type, all constraints should be identified as
early as possible to avoid future problems and surprises
Fact-FindingThe Zachman
FrameworkZachman
Framework for Enterprise Architecture
Helps managers and users understand the model and assures that overall business goals translate into successful IT projects
10
InterviewsStep 1: Determine
the People to InterviewInformal structures
Step 2: Establish Objectives for the InterviewDetermine the
general areas to be discussed
List the facts you want to gather
11
InterviewsStep 3: Develop Interview Questions
Creating a standard list of interview questions helps to keep you on track and avoid unnecessary tangents
Avoid leading questionsOpen-ended questionsClosed-ended questionsRange-of-response questions
12
InterviewsStep 4: Prepare for the Interview
Careful preparation is essential because an interview is an important meeting and not just a casual chat
Limit the interview to no more than one hourSend a list of topicsAsk the interviewee to have samples
available
13
InterviewsStep 5: Conduct the Interview
Develop a specific plan for the meetingBegin by introducing yourself, describing the
project, and explaining your interview objectives
Engaged listeningAllow the person enough time to think about
the questionAfter an interview, you should summarize
the session and seek a confirmation
14
Interviews• Step 6: Document the Interview– Note taking should be kept to a minimum– After conducting the interview, you must
record the information quickly– After the interview, send memo to the
interviewee expressing your appreciation– Note date, time, location, purpose of the
interview, and the main points you discussed so the interviewee has a written summary and can offer additions or corrections
15
InterviewsStep 7: Evaluate the Interview
In addition to recording the facts obtained in an interview, try to identify any possible biases
Unsuccessful InterviewsNo matter how well you prepare for
interviews, some are not successful
16
Other Fact-Finding Techniques• Document Review• Observation– Seeing the system in
action gives you additional perspective and a better understanding of the system procedures
– Plan your observations in advance
– Hawthorne Effect
17
Other Fact-Finding Techniques
Questionnaires and SurveysWhen designing a
questionnaire, the most important rule of all is to make sure that your questions collect the right data in a form that you can use to further your fact-finding
Fill-in form18
Other Fact-Finding TechniquesSampling
Systematic sampleStratified sampleRandom sampleMain objective of a sample is to ensure that it
represents the overall population accurately
19
Other Fact-Finding TechniquesResearch
Can include the Internet, IT magazines, and books to obtain background information, technical material, and news about industry trends and developments
Site visit
20
System Analysis and Design System Planning
Avicenna21
Preliminary Investigation OverviewStep 4: Evaluate Feasibility
Evaluate the project’s operational, technical, economic, and schedule feasibility
System Analysis and Design System Planning
Avicenna22
Preliminary Investigation Overview
Step 5: Estimate Project Development Time and CostWhat information must you obtain, and how
will you gather and analyze the information?What sources of information will you use, and
what difficulties will you encounter in obtaining information?
System Analysis and Design System Planning
Avicenna23
Preliminary Investigation Overview
Step 5: Estimate Project Development Time and CostWill you conduct interviews? How many
people will you interview, and how much time will you need to meet with the people and summarize their responses?
Will you conduct a survey? Who will be involved? How much time will it take people to complete it? How much time will it take to prepare it and tabulate the results?
System Analysis and Design System Planning
Avicenna24
Preliminary Investigation Overview
Step 5: Estimate Project Development Time and CostHow much will it cost to analyze the
information gathered and to prepare a report with findings and recommendations?
You should provide an estimate for the overall project, so managers can understand the full cost impact and timetable
System Analysis and Design System Planning
Avicenna25
Preliminary Investigation Overview
Step 6: Present Results and Recommendations to ManagementThe final task in the preliminary investigation
is to prepare a report to managementThe format of the preliminary investigation
report varies from one company to anotherThe report includes an evaluation of system
request, an estimate of costs and benefits, and your recommendation
System Analysis and Design System Planning
Avicenna26
Preliminary Investigation Overview
Step 6: Present Results and Recommendations to Management
Introduction It contains a brief description of the system, the name of
the person or group who performed the investigation, and the name of the person or group who initiated the investigation
Systems request summary It describes the basis of the system request
Findings It contains the results of the preliminary investigation
Recommendations Recommendations for further action, with specific reasons
and justification
System Analysis and Design System Planning
Avicenna27
Preliminary Investigation Overview
Step 6: Present Results and Recommendations to Management
Project Roles Lists the people who will participate in the project, and
describes each person’s roleTime & cost estimates
This section describes the cost of acquiring and installing the system, and the total cost of ownership during the system’s useful life
Expected benefits Anticipated tangible and intangible benefits and a timetable
that shows when they are to occur Appendix
It included in the report for supporting information