Scribd
Upload
39 views

BSD Lecture 7 - Systems Analysis

This document discusses systems analysis and design techniques used in requirements modeling. It describes identifying system requirements through fact-finding methods like interviews, documentation review, observation, and surveys. Systems analysts use requirement models and documentation tools to visualize and describe proposed systems based on outputs, inputs, processes, performance, security, and other requirements. The goal of systems analysis is to understand new projects and ensure they meet business needs before development.

Uploaded by

Angel Kitty Labor
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
39 views

BSD Lecture 7 - Systems Analysis

This document discusses systems analysis and design techniques used in requirements modeling. It describes identifying system requirements through fact-finding methods like interviews, documentation review, observation, and surveys. Systems analysts use requirement models and documentation tools to visualize and describe proposed systems based on outputs, inputs, processes, performance, security, and other requirements. The goal of systems analysis is to understand new projects and ensure they meet business needs before development.

Uploaded by

Angel Kitty Labor
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 23

Business Information Systems

Analysis and Design (BSD)


Lecture # 7
INTRODUCTION TO
SYSTEMS ANALYSIS & DESIGN
6. Systems Analysis and Design
Objectives
List and describe system requirements, including
outputs, inputs, processes, performance, and controls
Explain the importance of scalability in system design
Use fact-finding techniques, including interviews,
documentation review, observation, questionnaires,
sampling, and research
Introduction
This chapter describes requirements modeling
techniques and team-based methods that systems
analysts use to visualize and document new systems
Discusses system requirements and fact-finding
techniques, which include interviewing,
documentation review, observation, surveys and
questionnaires, sampling, and research
Systems Analysis Phase Overview
The overall objective is to understand the proposed
project, ensure that it will support business
requirements, and build a solid foundation for system
development
You use a models and other documentation tools to
visualize and describe the proposed system
Systems Analysis Phase Overview
Systems Analysis Activities
Requirements modeling
 Outputs
 Inputs
 Processes

 Performance
 Security

Data and process modeling


Development Strategies
System requirements document
System Requirements Checklist
System requirement
Five general categories
Outputs
Inputs
Processes
Performance
Controls
System Requirements Checklist
Outputs
The Web site must report online volume statistics
every four hours, and hourly during peak periods
The inventory system must produce a daily report
showing the part number, description, quantity on
hand, quantity allocated, quantity available, and unit
cost of all parts — sorted by part number
System Requirements Checklist
Inputs
Manufacturing employees must swipe their ID cards
into online data collection terminals that record labor
costs and calculate production efficiency
The department head must enter overtime hours on a
separate screen
System Requirements Checklist
Processes
The student records system must calculate the GPA at
the end of each semester
As the final step in year-end processing, the payroll
system must update employee salaries, bonuses, and
benefits and produce tax data required by the IRS
System Requirements Checklist
Performance
The system must support 25 users online simultaneously
Response time must not exceed four seconds
Controls
The system must provide log-on security at the
operating system level and at the application level
An employee record must be added, changed, or deleted
only by a member of the human resources department
Fact-Finding
Fact-Finding Overview
The first step is to identify the information you need
Start with a fact-finding plan
Who, What, Where, When, How, and Why?
Difference between asking what is being done and what
could or should be done
Interviews
Systems analysts spend a great deal of time talking
with people
Much of that time is spent conducting interviews
Interview
Step 1: Determine the People to Interview
Informal structures
Step 2: Establish Objectives for the Interview
Determine the general areas to be discussed
List the facts you want to gather
Step 3: Develop Interview Questions
Creating a standard list of interview questions helps to
keep you on track and avoid unnecessary irrelevant
points.
Interviews
Step 4: Prepare for the Interview
Careful preparation is essential because interview is an
important meeting and not just a casual chat
Limit the interview to no more than one hour
Send a list of topics
Ask the interviewee to have samples available
Interviews
Step 5: Conduct the Interview
Develop a specific plan for the meeting
Begin by introducing yourself, describing the project,
and explaining interview objectives
Use engaged listening
Allow the person enough time to think about the
question
Summarize main points
After interview, summarize the session and seek a
confirmation
Interviews
Step 6: Document the Interview
During the interview, note taking should be kept to a
minimum
After the interview, record the information quickly
After the interview, send memo expressing appreciation,
including the main points discussed so the interviewee
has a written summary and can offer additions or
corrections
Interviews
Step 7: Evaluate the Interview
In addition to recording the facts obtained in an
interview, try to identify any possible biases
Unsuccessful Interviews
No matter how well you prepare for interviews, some are
not successful
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
Other Fact-Finding Techniques
Questionnaires and Surveys
When 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 form
Sampling
Main objective of a sample is to ensure that it represents
the overall population accurately
Other Fact-Finding Techniques
Research
Newsgroups
Site visit
Other Fact-Finding Techniques
Interviews versus Questionnaires
Interview is more familiar and personal
Questionnaire gives many people the opportunity to
provide input and suggestions
Brainstorming
Documentation
The Need for Recording the Facts
Record information as soon as you obtain it
Use the simplest recording method
Record your findings in such a way that they can be
understood by someone else
Organize your documentation
Preview of Data and Process Modeling
At the conclusion of requirements modeling, systems
developers should have clear understanding of
business processes and system requirements
The next step is to model the logical design of the
system

You might also like