9/25/2020

MODELING TOOLS AND TECHNIQUES

CHAPTER 03-02
Data flow diagram (DFD)
SYSTEMS ANALYSIS AND DESIGN
Show how the system
stores, processes, and
REQUIREMENTS MODELING [2] transforms data
Additional levels of
information and detail
are depicted in other,
related DFDs
2

MODELING TOOLS AND TECHNIQUES SYSTEM REQUIREMENTS CHECKLIST

Unified Modeling Language Outputs

Widely used method of The Web site must report online volume statistics
visualizing & documenting every four hours, and hourly during peak periods
software systems design
The inventory system must produce a daily report
Use case diagrams showing the part number, description, quantity on
– Actor hand, quantity allocated, quantity available, and unit
cost of all sorted by part number
Sequence diagrams
3 4
 9/25/2020

SYSTEM REQUIREMENTS CHECKLIST 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
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

5 6

SYSTEM REQUIREMENTS CHECKLIST SYSTEM REQUIREMENTS CHECKLIST

Performance
The system must support 25 users online
simultaneously
Response time must not exceed four seconds
Controls
The system must provide logon 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

7 8
 9/25/2020

FUTURE GROWTH, COSTS, AND BENEFITS FUTURE GROWTH, COSTS, AND BENEFITS

Scalability • Total Cost of Ownership

– Total cost of ownership
A scalable system offers a better return on the (TCO) is especially
initial investment important if the
development team is
To evaluate scalability, you need information about
evaluating several
projected future volume for all outputs, inputs, and alternatives
processes – One problem is that cost
estimates tend to
understate indirect costs
9 – Rapid Economic 10

Justification (REJ)

FACT-FINDING FACT-FINDING

Fact-Finding Overview The Zachman Framework

First, you must identify the information you need Zachman Framework for
Enterprise Architecture
Develop a fact-finding plan
Helps managers and
Who, What, Where, When, How, and Why? users understand the
Difference between asking what is being done model and assures that
and what could or should be done overall business goals
translate into successful
IT projects
11 12
 9/25/2020

INTERVIEWS INTERVIEWS

Step 1: Determine the People Step 3: Develop Interview Questions

to Interview ₋ Creating a standard list of interview questions
₋ Informal structures helps to keep you on track and avoid unnecessary
tangents
Step 2: Establish Objectives
for the Interview ₋ Avoid leading questions

₋ Determine the general areas ₋ Open-ended questions

to be discussed ₋ Closed-ended questions
₋ List the facts you want to 13 ₋ Range-of-response questions 14

gather

INTERVIEWS INTERVIEWS

Step 4: Prepare for the Interview Step 5: Conduct 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 hour
₋ Send a list of topics
₋ Ask the interviewee to have samples available
15
₋ Develop a specific plan for the meeting
₋ Begin by introducing yourself, describing the
project, and explaining your interview objectives
₋ Engaged listening
₋ Allow the person enough time to think about the
question
₋ After an interview, you should summarize the 16

session and seek a confirmation

 9/25/2020

INTERVIEWS INTERVIEWS

Step 6: Document the Interview Step 7: Evaluate 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 17
₋ 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
18

additions or corrections

OTHER FACT-FINDING TECHNIQUES OTHER FACT-FINDING TECHNIQUES

• Document Review Questionnaires and

Surveys
• Observation
When designing a
– Seeing the system in action questionnaire, the most
gives you additional important rule of all is to
perspective and a better make sure that your
understanding of the system questions collect the right
procedures data in a form that you can
use to further your fact-
– Plan your observations in finding
advance 19
Fill-in form
20

– Hawthorne Effect
 9/25/2020

OTHER FACT-FINDING TECHNIQUES OTHER FACT-FINDING TECHNIQUES

Sampling Research
Systematic sample Can include the
Internet, IT magazines,
Stratified sample
and books to obtain
Random sample background
Main objective of a sample is to ensure that it information, technical
represents the overall population accurately material, and news
about industry trends
and developments
21 22

Site visit

OTHER FACT-FINDING TECHNIQUES DOCUMENTATION

Interviews versus Questionnaires The Need for Recording the Facts

Interview is more familiar and personal Record information as soon as you obtain it
Questionnaire gives many people the opportunity Use the simplest recording method
to provide input and suggestions Record your findings in such a way that they can be
Brainstorming understood by someone else
Structured brainstorming Organize your documentation so related material is
Unstructured brainstorming located easily
23 24
 9/25/2020

DOCUMENTATION DOCUMENTATION

Software Tools Software Tools

CASE Tools Graphics modeling software
Productivity Software Personal information managers
Word processing, Wireless communication devices
spreadsheets, database
management,
presentation graphics,
and collaborative
software programs
25 26

Histogram

PREVIEW OF LOGICAL MODELING Q &A

At the conclusion of requirements modeling, systems
developers should have a clear understanding of
business processes and system requirements
The next step is to construct a logical model of the
system
IT professionals have differing views about systems THANK YOU
development methodologies, and no universally
accepted approach exists

27 28