Professional Documents
Culture Documents
Lec7 & 8 - System Planning
Lec7 & 8 - System Planning
Requirements Gathering
Technical
feasibility
study:
determines
the
organizations ability to build and integrate the proposed
system
PLANNING 3: Develop
the Project Plan
Developing
is
9-5
requirements
gathering
What techniques are available for
gathering
information
requirements?
about
Fact Gathering
Techniques
Interviews
Questionnaires
Observation
Document / Procedure Analysis
JAD
Prototyping
Fact-Gathering Techniques
A. Fact Gathering Through Interviews
B. Fact Gathering Through
Questionnaires
Interviews
Interview - a fact-finding technique whereby the
systems analysts collect information from
individuals through face-to-face interaction.
Find facts
Verify facts
Clarify facts
Generate enthusiasm
Get the end-user involved
Identify requirements
Solicit ideas and opinions
10
Interviews
Types of samples
13
Interviews
Conducting the Interview--practical
tips
Interviews
Post Interview
Consider asking for more time if
necessary
Confirm major points identified with
interviewee
Look for Gaps and New Questions
Type up notes within 24 hours
(preferably immediately after the
interview is over
Questionnaires
Questionnaire a special-purpose document
What types of
information
do you use to make
decisions?
Questionnaires
A questionnaire is similar to a very
structured interview
Many of the same guidelines apply
Choosing respondents
Should
Questionnaires
Document/Procedure
Analysis
Great starting point
Gets analyst quickly up to speed with user jargon
Can create preliminary models, e.g. DFDs
Document/Procedure
Analysis
Four types of useful documents
Written work procedures
Describes
Joint Application
Design
Joint Application Design (JAD)
Brings together key users,
Joint Application
Design
Participants
Session Leader
Users
Managers
Sponsor
Systems Analysts
Scribe
IS Staff
Joint Application
Design
Supporting JAD with GSS
Group support systems (GSS) can be used
type
their
answers
into
the
computer
All members of the group see what other
Joint Requirements
Planning
Joint requirements planning (JRP) a process whereby highly
structured group meetings are conducted for the purpose of analyzing
problems and defining requirements.
JRP is a subset of a more comprehensive joint application development
overhead projectors
Needed computer equipment
2. Selecting the participants
28
Discovery Prototyping
Discovery
ultimate system
29
Prototyping
Quickly converts requirements to working version of
system
and users
Tools are readily available to build prototype
Prototyping
Drawbacks
Tendency to avoid formal documentation
Difficult to adapt to more general user audience
Sharing data with other systems is often not
considered
Systems Development Life Cycle (SDLC) checks