Expert answer:Chapters 4 through 7
Solved by verified expert:Chapters 4 through 7:Review the Personal Trainer, Inc. case at the end of each chapter.Complete the Case Assignment questions in each chapter in an APA formatted document.Complete the following Questions:Chapter 4: 2-3Chapter 5: 3Chapter 6: N/AChapter 7: 1-3[post must be two to three substantive paragraphs (250+ words) and include at least two APA-formatted citation/reference, need an unique paper with zero plagarisam in APA format. Make sure the answers/Paper in MS word ][post must be two to three substantive paragraphs (250+ words) and include at least two APA-formatted citation/reference, need an unique paper with zero plagarisam in APA format. Make sure the answers/Paper in MS word ]http://160592857366.free.fr/joe/ebooks/ShareData/System%20Analysis%20and%20Design%209e%20-%20Shelly%20Cashman.pdf
chapter_04.pptx
chapter_05.pptx
chapter_06.pptx
chapter_07.pptx
chapter_08.pptx
chapter_03.pptx
Unformatted Attachment Preview
Systems Analysis and Design
9th Edition
Chapter 4
Requirements Modeling
Phase Description
• Systems analysis is the second of five phases
in the systems development life cycle (SDLC)
• Will use requirements modeling, data and
process modeling, and object modeling
techniques to represent the new system
• Will consider various development strategies
for the new system, and plan for the transition
to systems design tasks
2
Chapter Objectives
• Describe systems analysis phase activities
• Explain joint application development (JAD),
rapid application development (RAD), and
agile methods
• Use a functional decomposition diagram (FDD)
to model business functions and processes
3
Chapter Objectives
• Describe the Unified Modeling Language
(UML) and examples of UML diagrams
• List and describe system requirements,
including outputs, inputs, processes,
performance, and controls
• Explain the concept of scalability
4
Chapter Objectives
• Use fact-finding techniques, including
interviews, documentation review,
observation, questionnaires, sampling, and
research
• Define total cost of ownership (TCO)
• Conduct a successful interview
• Develop effective documentation methods to
use during systems development
5
Introduction
• This chapter describes requirements modeling
techniques and team-based methods that
systems analysts use to visualize and
document new systems
• The chapter then discusses system
requirements and fact-finding techniques,
which include interviewing, documentation
review, observation, surveys and
questionnaires, sampling, and research
6
Systems Analysis Phase Overview
• The overall objective of the systems analysis
phase is to understand the proposed project,
ensure that it will support business
requirements, and build a solid foundation for
system development
• You use models and other documentation
tools to visualize and describe the proposed
system
7
Systems Analysis Phase Overview
• Systems Analysis
Activities
– Requirements
modeling
•
•
•
•
•
Outputs
Inputs
Processes
Performance
Security
8
Systems Analysis Phase Overview
• Systems Analysis Activities
– Data and process modeling
– Object Modeling
– Development Strategies
• System requirements document
9
Systems Analysis Phase Overview
• Systems Analysis Skills
– Analytical skills
– Interpersonal skills
• Team-Oriented Methods and Techniques
– Joint application development (JAD)
– Rapid application development (RAD)
– Agile methods
10
Joint Application Development
• User Involvement
– Users have a vital stake in an information system
and they should participate fully
– Successful systems must be user-oriented, and
users need to be involved
– One popular strategy for user involvement is a JAD
team approach
11
Joint Application Development
• JAD Participants and Roles
12
Joint Application Development
• JAD Advantages and Disadvantages
– More expensive and can be cumbersome if the
group is too large relative to the size of the project
– Allows key users to participate effectively
– When properly used, JAD can result in a more
accurate statement of system requirements, a
better understanding of common goals, and a
stronger commitment to the success of the new
system
13
Rapid Application Development
• Is a team-based technique that speeds up
information systems development and
produces a functioning information system
• Relies heavily on prototyping and user
involvement
• Interactive process continues until the system
is completely developed and users are
satisfied
14
Rapid Application Development
• RAD Phases and Activities
15
Rapid Application Development
• RAD Objectives
– To cut development time and expense by involving
the users in every phase of systems development
– Successful RAD team must have IT resources,
skills, and management support
– Helps a development team design a system that
requires a highly interactive or complex user
interface
16
Rapid Application Development
• RAD Advantages and Disadvantages
– Systems can be developed more quickly with
significant cost savings
– RAD stresses the mechanics of the system itself
and does not emphasize the company’s strategic
business needs
– Might allow less time to develop quality,
consistency, and design standards
17
Agile Methods
• Attempt to develop a system incrementally
• Agilian modeling toolset includes support for
many modeling tools
• Some agile developers prefer not to use CASE
tools at all, and rely instead on whiteboard
displays and arrangements of movable sticky
notes
18
Agile Methods
• Scrum is a rugby term
• Pigs include the product owner, the facilitator,
and the development team; while the
chickens include users, other stakeholders,
and managers
• Scrum sessions have specific guidelines that
emphasize time blocks, interaction, and teambased activities that result in deliverable
software
19
Agile Methods
• Agile Method Advantages and Disadvantages
– Are very flexible and efficient in dealing with
change
– Frequent deliverables constantly validate the
project and reduce risk
– Team members need a high level of technical and
interpersonal skills
– May be subject to significant change in scope
20
Modeling Tools and Techniques
• Involves graphical methods and nontechnical
language that represent the system at various
stages of development
• Can use various tools
• Functional Decomposition Diagrams
– Functional decomposition diagram (FDD)
– Model business functions and show how they are
organized into lower-level processes
21
Modeling Tools and Techniques
• Business Process Modeling
– Business process model (BPM)
– Business process modeling notation (BPMN)
– Pool
– Swim lanes
22
Modeling Tools and Techniques
• Data Flow Diagrams
– Data flow diagram (DFD)
– show how the system stores, processes, and
transforms data
– Additional levels of information and detail are
depicted in other, related DFDs
23
Modeling Tools and Techniques
• Unified Modeling Language
– Widely used method of visualizing and
documenting software systems design
– Use case diagrams
• Actor
– Sequence diagrams
24
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 sorted by part number
25
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
26
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
27
System Requirements Checklist
• Performance
– The system must support 25 users online
simultaneously
– Response time must not exceed four seconds
28
System Requirements Checklist
• 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
29
Future Growth, Costs, and Benefits
• Scalability
– A scalable system offers a better return on the
initial investment
– To evaluate scalability, you need information
about projected future volume for all outputs,
inputs, and processes
30
Future Growth, Costs, and Benefits
• Total Cost of Ownership
– Total cost of ownership
(TCO) is especially
important if the
development team is
evaluating several
alternatives
– One problem is that cost
estimates tend to
understate indirect costs
– Rapid Economic
Justification (REJ)
31
Fact-Finding
• Fact-Finding Overview
– First, you must identify the information you need
– Develop 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
32
Fact-Finding
• The Zachman
Framework
– Zachman Framework for
Enterprise Architecture
– Helps managers and
users understand the
model and assures that
overall business goals
translate into successful
IT projects
33
Interviews
• 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
34
Interviews
• Step 3: Develop Interview Questions
– Creating a standard list of interview questions
helps to keep you on track and avoid unnecessary
tangents
– Avoid leading questions
– Open-ended questions
– Closed-ended questions
– Range-of-response questions
35
Interviews
• Step 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 hour
– Send a list of topics
– Ask the interviewee to have samples available
36
Interviews
• Step 5: Conduct the Interview
– 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
session and seek a confirmation
37
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
38
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
39
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
40
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
41
Other Fact-Finding Techniques
• Sampling
– Systematic sample
– Stratified sample
– Random sample
– Main objective of a sample is to ensure that it
represents the overall population accurately
42
Other Fact-Finding Techniques
• Research
– Can include the Internet,
IT magazines, and books
to obtain background
information, technical
material, and news
about industry trends
and developments
– Site visit
43
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
– Structured brainstorming
– Unstructured brainstorming
44
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 so related material
is located easily
45
Documentation
• Software Tools
– CASE Tools
– Productivity Software
• Word processing,
spreadsheets, database
management,
presentation graphics,
and collaborative
software programs
• Histogram
46
Documentation
• Software Tools
– Graphics modeling software
– Personal information managers
– Wireless communication devices
47
Preview of Logical Modeling
• 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 development methodologies, and no
universally accepted approach exists
48
Chapter Summary
• The systems analysis phase includes three
activities: requirements modeling, data and
process modeling, and consideration of
development strategies
• The main objective is to understand the
proposed project, ensure that it will support
business requirements, and build a solid
foundation for the systems design phase
49
Chapter Summary
• The fact-finding process includes interviewing,
document review, observation, questionnaires,
sampling, and research
• Systems analysts should carefully record and
document factual information as it is collected,
and various software tools can help an analyst
visualize and describe an information system
• Chapter 4 complete
50
Systems Analysis and Design
9th Edition
Chapter 5
Data and Process Modeling
Chapter Objectives
• Describe data and process modeling concepts
and tools, including data flow diagrams, a data
dictionary, and process descriptions
• Describe the symbols used in data flow
diagrams and explain the rules for their use
• Draw data flow diagrams in a sequence, from
general to specific
• Explain how to level and balance a set of data
flow diagrams
2
Chapter Objectives
• Describe how a data dictionary is used and
what it contains
• Use process description tools, including
structured English, decision tables, and
decision trees
• Describe the relationship between logical and
physical models
3
Introduction
• In Chapters 5 & 6, you will develop a logical
model of the proposed system and document
the system requirements
– Logical model shows what the system must do
– Physical model describes how the system will be
constructed
4
Overview of Data and Process
Modeling Tools
• Systems analysts use many graphical
techniques to describe an information system
• A data flow diagram (DFD) uses various
symbols to show how the system transforms
input data into useful information
5
Data Flow Diagrams
• A data flow diagram
(DFD) shows how data
moves through an
information system but
does not show program
logic or processing steps
• A set of DFDs provides a
logical model that
shows what the system
does, not how it does it
6
Data Flow Diagrams
• DFD Symbols
7
Data Flow Diagrams
• DFD Symbols
– Process symbol
• Receives input data and produces output that has a
different content, form, or both
• Contain the business logic, also called business rules
• Referred to as a black box
8
Data Flow Diagrams
• DFD Symbols
– Data flow symbol
• Represents one or
more data items
• The symbol for a data
flow is a line with a
single or double
arrowhead
• Spontaneous
generation
• Black hole
• Gray hole
9
Data Flow Diagrams
• DFD Symbols
– Data store symbol
• Represent data that
the system stores
• The physical
characteristics of a
data store are
unimportant because
you are concerned
only with a logical
model
10
Data Flow Diagrams
• DFD Symbols
– Entity Symbol
• Name of the entity
appears inside the
symbol
• Terminators
• Source
• Sink
11
Creating a Set of DFDs
• Create a graphical model of the information
system based on your fact-finding results
• First, you will review a set of guidelines for
drawing DFDs. Then you will learn how to
apply these guidelines and create a set of
DFDs using a three-step process
12
Creating a Set of DFDs
• Guidelines for Drawing DFDs
– Draw the context diagram so that it fits on one
page
– Use the name of the information system as the
process name in the context diagram
– Use unique names within each set of symbols
13
Creating a Set of DFDs
• Guidelines for Drawing DFDs
– Do not cross lines
– Provide a unique name and reference number for
each process
– Obtain as much user input and feedback as
possible
14
Creating a Set of DFDs
• Step 1: Draw a Context Diagram
15
Creating a Set of DFDs
• Step 2: Draw a Diagram 0 DFD
16
Creating a Set of DFDs
• Step 2: Draw a Diagram 0 DFD
– If same data flows in both directions, you can use
a double-headed arrow
– Diagram 0 is an exploded view of process 0
– Parent diagram
– Child diagram
– Functional primitive
17
Creating a Set of DFDs
• Step 3: Draw the LowerLevel Diagrams
– Must use leveling and
balancing techniques
– Leveling examples
• Uses a series of
increasingly detailed DFDs
to describe an
information system
• Exploding, partitioning, or
decomposing
18
Creating a Set of DFDs
• Step 3: Draw the LowerLevel Diagrams
– Balancing Examples
• Ensures that the input
and output data flows of
the parent DFD are
maintained on the child
DFD
19
Data Dictionary
• A data dictionary, or data repository, is a
central storehouse of information about the
system’s data
• An analyst uses the data dictionary to collect,
document, and organize specific facts about
the system
• Also defines and describes all data elements
and meaningful combinations of data
elements
20
Data Dictionary
• A data element, also called a data item or
field, is the smallest piece of data that has
meaning
• Data elements are combined into records, also
called data structures
• A record is a meaningful combination of
related data elements that is included in a
data flow or retained in a data store
21
Data Dictionary
• Using CASE Tools for Documentation
– The more complex the system, the more difficult it
is to maintain full and accurate documentation
– Modern CASE tools simplify the task
– A CASE repository ensures data consistency
– You will learn more about CASE tools in Part 2 of
the Systems Analyst’s Toolkit
22
Data Dictionary
• Documenting the Data
Elements
– You must document
every data element in
the data dictionary
– The objective is the
same: to provide clear,
comprehensive
information about the
data and processes that
make up the system
23
Data Dictionary
• Documenting the Data Elements
– The following attributes usually are recorded and
described
•
•
•
•
•
Data element name and label
Alias
Type and length
Default value
Acceptable values – Domain and validity rules
24
Data Dictionary
• Documenting the Data Elements
– The following attributes usually are recorded and
described
•
•
•
•
Source
Security
Responsible user(s)
Description and comments
25
Data Dictionary
• Documenting the Data Flows
– The typical attributes are as follows
•
•
•
•
•
•
•
Data flow name or label
Description
Alternate name(s)
Origin
Destination
Record
Volume and frequency
26
Data Dictionary
• Documenting the Data Stores
– Typical characteristics of a data store are
•
•
•
•
•
Data store name or label
Description
Alternate name(s)
Attributes
Volume and frequency
27
Data Dictionary
• Documenting the Processes
– Typical characteristics of a process
•
•
•
•
Process name or label
Description
Process number
Process description
28
Data Dictionary
• Documenting the Entities
– Typical characteristics of an entity include
•
•
•
•
•
Entity name
Description
Alternate name(s)
Input data flows
Output data flows
29
Data Dictionary
• Documenting the Records
– Typical characteristics of a record include
•
•
•
•
Record or data structure name
Definition or description
Alternate name(s)
Attributes
30
Data Dictionary
• Data Dictionary R …
Purchase answer to see full
attachment
How it works
- Paste your instructions in the instructions box. You can also attach an instructions file
- Select the writer category, deadline, education level and review the instructions
- Make a payment for the order to be assignment to a writer
- Download the paper after the writer uploads it
Will the writer plagiarize my essay?
You will get a plagiarism-free paper and you can get an originality report upon request.
Is this service safe?
All the personal information is confidential and we have 100% safe payment methods. We also guarantee good grades