the modern systems analyst the modern systems analyst the
TRANSCRIPT
The Modern Systems Analyst
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Planning
Analysis
Design
Support
Problem to be solved
Problem analysis
and
Solution requirements
Acceptable
solution
Obsolete solution
Implemen- tation
Implemented
solution
Related problem to be solved
New solution
to same problemImplementation
error
to be fixed
The Modern Systems Analyst
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Chief Executive Officer (CEO)
or
Line of Business Chief Executive
VP of Information Services
or
Chief Information Officer (CIO)
Manager
Systems Development
Telecommunications
Administrator
Manager
End User Computing
Data
Administrator
Manager.
Computer Operations
Data
Analysts
Database
Analysts
Database
Administrators
Network
Managers
Network
Technicians
Network
AnalystsEnd User
Consultants
End User
Trainers
System
Programmers
Capacity
Analyst
Computer
Operators
Manager
Financial
Systems
Manager
Development
Center
Manager
Marketing
Systems
Manager
Manufacturing
Systems
Systems
Analysts
Application
Programmers
The Modern Systems Analyst
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Chief Executive Officer (CEO)
or
Line of Business Chief Executive
Chief Information Officer (CIO)
(for central information services)
Vice President
Finance
Vice President
Marketing
Vice President
Manufacturing
Manager
Financial
Information
Services
Manager
Financial
Information
Services
Manager
Financial
Information
Services
Network
Manager
Analyst/
Programmers
Team
Network
Manager
Analyst/
Programmers
Team
Network
Manager
Analyst/
Programmers
Team
Information
Strategy
Planning
Team
Information
Technology
Architecture
Team
Cross-Functional
Systems &
Applications
Development Teams
Information
Technology
Competency
Centers
Departmental
Computing
Coordination
Data
Administrator
Telecommuni-
cations
Administrator
Project
Managers
coordinate advise evaluate
Other
Technical
Specialists
Application
Technology
Specialists
Database
Specialists
Network
Specialists
indicates dynamic
assignments
to teams
as needed
The Modern Systems Analyst
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Systemsanalyst
Steering committee
User 1
User 2
User N
Management/ systemowner
Databaseadministrator
Interfacedesign expert
Networkadministrator
Applicationsprogrammers
Informationtechnology
vendors
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Information System Building Blocks
Transaction
Processing
System
Executive
Information
System
Management
Information
System
Decision
Support
System
Expert
System
Personal
Information
System
Office
Information
System
Business
Database
Expertise
Database
Business Data
Warehouse
Data
Data
Captured
data
Data
and
messages
Read-only
data
Data
snapshots
Read-only
data
Data
Rules
Data
Problem
Decision
support
information
Executive
inquiry
Executive
information
Any Manager
Any
Decision Maker
or
Executive
Information
need
Management
information
Any
Relevant
User
Problem
Solution
Any
User
Transaction
Data
Transaction
information
Communications
between users
and within groups
Any
User
Personal
data
Shared
data
Personal
Files &
Databases
Personal
data
Personal
information
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Information System Building BlocksINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
SYSTEM
BUILDERS
SYSTEM
DESIGNERS
SYSTEM
USERS
SYSTEM
OWNERS
Data
Technology
INFORMATION SYSTEM COMPONENTS
(the actual, technical implementation of the system)
INFORMATION SYSTEM DESIGN
(HOW the system will be implemented using technology)
INFORMATION SYSTEM REQUIREMENTS
(WHAT the system "is" and "must do" independent of technology)
INFORMATION SYSTEM SCOPE
(purpose and vision; goals and objectives; costs and benefits)
INFORMATION SYSTEM FOCUSES
Networking
TechnologyInterface
TechnologySoftware
Technology
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Information System Building BlocksINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
System
Builders'
views of
DATA
System
Designers'
views of
DATA
System
Users'
views of
DATA
System
Owners'
views of
DATA
DATA
FOCUS
Data
Technology
System
Builders'
views of
PROCESSES
System
Designers'
views of
PROCESSES
System
Users'
views of
PROCESSES
System
Owners'
views of
PROCESSES
PROCESS
FOCUS
System
Builders'
views of
INTERFACES
System
Designers'
views of
INTERFACES
System
Users'
views of
INTERFACES
System
Owners'
views of
INTERFACES
INTERFACE
FOCUS
System
Builders'
views of
GEOGRAPHY
System
Designers'
views of
GEOGRAPHY
System
Users'
view of
GEOGRAPHY
System
Owners'
views of
GEOGRAPHY
GEOGRAPHY
FOCUS
Networking
Technology
Interface
TechnologySoftware
Technology
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Information System Building BlocksINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
(facilitation)
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Database
Technology
FOCUS ON
SYSTEM
DATA
COBOL Program
Structure Chart
Data Flow Diagram
Decomposition Diagram
FOCUS ON
SYSTEM
PROCESSES
FOCUS ON
SYSTEM
INTERFACES
COBOL
Compiler
on
IBM 3090 MVS
Interface
TechnologyNetworking
Telchnology
FOCUS ON
SYSTEM
GEOGRAPHY
Marketing
Advertising
Orders
Sales
Cancellations Services
Check
credit
Validate
customer
Validate
products
Release
order
Customers
Orders
Products
order
custome
number
valid orde
order witho
valid
customer
credi
order with
valid produc
approved ord
quantity
in stock
approve
order
rejected ord
prices
picking
ticket
Order
Processing
Program
Process
an Order
Initiation
Routine
Shutdown
Routine
Get an
Order
Validate
an Order
File an
Order
Check
Customer
Credit
Check
Product
Data
Check
Credit
Data
Release
an
Order
Customers ProductsOrders
VALIDATE_AN_ORDE
REPEAT UNTIL NO_MORE_ORD
PERFORM CUSTOMER_VALI
REPEAT UNTIL NO_MORE_ORDER
PERFORM PRODUCT_VALID
END REPEAT
PERFORM CREDIT_CHE
IF CREDIT CHECK 'BAD' T
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
Information System Building BlocksINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
(facilitation)
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Database
Technology
Database Programs
Database Schema
Data Requirements
Business Subjects
FOCUS ON
SYSTEM
DATA
FOCUS ON
SYSTEM
PROCESSES
FOCUS ON
SYSTEM
INTERFACES
Software
Technology
Interface
TechnologyNetworking
Telchnology
FOCUS ON
SYSTEM
GEOGRAPHY
Customers order zero,
one, or more products.
Products may be ordered
by zero, one, or more
customers.
CUSTOME
customer_no [Alpha (10
customer_name [Alp
customer_rating [Alpha(
balance_due [Rea
PRODUC
product_no [Alpha(1
product_name [Alp
unit_of_measure [A
unit_price [Rea
quantity_available [In
ORDER
order_no [Alpha(12)
order_date [Date(mm
CUSTOMER.custom
ORDER_PROD
ORDER.order
PRODUCT.produ
quantity_ordered [In
CREATE TABLE CUSTO
(customer_no CHAR(10) NO
customer_name CHAR(32) NO
customer _rating CHAR(1) NO
balance_due DECIMA
CREATE INDEX cust_no_idx on CU
CREATE INDEX cust_rt_idx on CU
CUSTOMER
customer-no
customer-name
customer-rating
balance-due
PRODUCT
product-no
product-name
unit-of-measure
unit-price
quantity-availab
ORDER
order-no
order-date
products-ordered
quantities-ordered
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Information System Building BlocksINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
(facilitation)
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Database
Technology
Database Structures
Database Scehma
Data Requirements
Business Subjects
FOCUS ON
SYSTEM
DATA
Application Programs
Application Schema
Business Process
Reqts.
Business Functions
FOCUS ON
SYSTEM
PROCESSES
FOCUS ON
SYSTEM
INTERFACES
Software
(and Hardware)
Technology
Interface
TechnologyNetworking
Telchnology
FOCUS ON
SYSTEM
GEOGRAPHY
Marketing
Advertising
Orders
Sales
Cancellations Services
Order
Processing
Program
Process
an Order
Initiation
Routine
Shutdown
Routine
Get an
Order
Validate
an Order
File an
Order
Check
Customer
Credit
Check
Product
Data
Check
Credit
Data
Release
an
Order
Customers ProductsOrders
VALIDATE_AN_ORDE
REPEAT UNTIL NO_MORE_OR
PERFORM CUSTOMER_VAL
REPEAT UNTIL NO_MORE_ORDER
PERFORM PRODUCT_VALID
END REPEA
PERFORM CREDIT_CHE
IF CREDIT CHECK 'BAD' T
Check
credit
Validate
customer
Validate
products
Release
order
Customers
Orders
Products
order
custome
number
valid orde
order withou
valid
customer
credit
order with
valid product
approved orde
quantity
in stock
approved
order
rejected orde
prices
picking
ticket
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19987
Information System Building BlocksINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
(facilitation)
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Database
Technology
Database Structures
Database Scehma
Data Requirements
Business Subjects
FOCUS ON
SYSTEM
DATA
Application Programs
Application Schema
Business Process
Reqts.
Business Functions
FOCUS ON
SYSTEM
PROCESSES
Component Programs
Interface Schema
Input/Output Reqts.
System Context
FOCUS ON
SYSTEM
INTERFACES
Software
(and Hardware)
Technology
Interface
TechnologyNetworking
Telchnology
FOCUS ON
SYSTEM
GEOGRAPHY
Order
Management
System
Customer
Accounts
Receivable
Database
Warehouse
Bank
OrderPicking
Order
Credit
Credit
Voucher
Order Form
Help +
CustomerForm
Product
Lookup
Logon
New Customer
New Order
Order Accepted
Change
of
Address
First Order
Request Order Help
Order Help Complete
Request
Product
Lookup
Request Product Lookup Help
Product Lookup Help Complete
On Event Help.ButtonClick D
Change Focus HelpDialo
On Event OKButton Do
Begin
{proecdure}
End
On Event CancelButton Do
Firecracker Sales
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19988
Information System Building BlocksINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
(facilitation)
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Database
Technology
Database Structures
Database Scehma
Data Requirements
Business Subjects
FOCUS ON
SYSTEM
DATA
Application Programs
Application Schema
Business Process
Reqts.
Business Functions
FOCUS ON
SYSTEM
PROCESSES
Component Programs
Interface Schema
Input/Output Reqts.
System Context
FOCUS ON
SYSTEM
INTERFACES
Software
(and Hardware)
Technology
Interface
TechnologyNetworking
Telchnology
Network Programs
Network Schema
Communication Reqts.
Operating Locations
FOCUS ON
SYSTEM
GEOGRAPHY
EDI
Cust
St.
Louis
HQ
LA
Office
Indy
Ware-
house
NY
Office
West
Customers
East
Customers
Maintenance
Records
Products
Catalogorder
catalog
changes
ship
order
ship
ordership order
credit credit
service
St. Louis
Mainframe
Indy AIX Serve
NT Server LA
NT Server NY
Communication
Controller
PBX
Enternet LAN AIX/Lan
Manager
Ethernet LAN/NT
Ethernet LAN/NT
Client PC Client PC
Client PC Client PC
Create AccountType =
SalesClerk
Set OrderDir.Rights=full
Set CustomerDir.Rights=ful
Set ProductDir.Rights=read
Set OrderAppDir.Rights=cop
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19989
Information System Building BlocksINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
(facilitation)
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Database
Technology
Database Structures
any good DB course
Database Scehma
Chapter 12
Data Requirements
Chapters 5, 6
Business Subjects
Chapters 5, 6
FOCUS ON
SYSTEM
DATA
Application Programs
any good
programming course
Application Schema
Chapters 11, 16
Business Processes
Chapters 5, 7
Business Functions
Chapters 5, 7
FOCUS ON
SYSTEM
PROCESSES
Component Programs
any good
programming course
Interface Schema
Chapters 11, 13, 14, 15
Interface Requirements
Chapters 5, 13, 14
System Context
Chapters 5, 7
FOCUS ON
SYSTEM
INTERFACES
Software
(and Hardware)
Technology
Interface
TechnologyNetworking
Telchnology
Network Programs
any good data
communication course
Network Schema
Chapter 11
Communication Reqts.
Chapters 5, 8
Operating Locations
Chapters 5, 8
FOCUS ON
SYSTEM
GEOGRAPHY
CREATE TABLE CUSTOMER
(customer_no CHAR(10) NOT NULL
customer_name CHAR(32) NOT NULL
customer _rating CHAR(1) NOT NULL
balance_due DECIMAL(5,2)
CREATE INDEX cust_no_idx on CUSTOMER
CREATE INDEX cust_rt_idx on CUSTOMER
CUSTOMER
customer-nocustomer-name
customer-ratingbalance-due
PRODUCT
product-no
product-name
unit-of-measureunit-price
quantity-availabl
ORDER
order-no
order-date
products-orderedquantities-ordered
Order Form
Help +
Customer
Form
Product
Lookup
Logon
New Customer
New Order
Order Accepted
Changeof
Address
First Order
Request Order Help
Order Help Complete
RequestProductLookup
Request Product Lookup Help
Product Lookup Help Complete
On Event Help.ButtonClick Do
Change Focus HelpDialog
On Event OKButton Do
Begin
{proecdure}
End
On Event CancelButton Do
Create AccountType =
SalesClerk
Set OrderDir.Rights=full
Set CustomerDir.Rights=full
Set ProductDir.Rights=read
Set OrderAppDir.Rights=copy
Customers order zero,
one, or more products.
Products may be ordered
by zero, one, or more
customers.
Marketing
Advertising
Orders
Sales
Cancellations Services
Order
Management
System
Customer
Accounts
Receivable
Database
Warehouse
Bank
OrderPickingOrder
Credit
CreditVoucher
Check
credit
Validate
customer
Validate
products
Release
order
Customers
Orders
Products
order
customer
number
valid order
order without
valid
customer
credit
order with
valid products
approved order
quantity
in stock
approved
order
rejected order
prices
picking
ticket
Firecracker Sales
EDI
Cust
St.
Louis
HQ
LA
Office
Indy
Ware-
house
NY
Office
West
Customers
East
Customers
Maintenance
Records
Products
Catalogorder
catalog
changes
ship
order
ship
ordership order
credit credit
service
CUSTOMER
customer_no [Alpha (10)] IN
customer_name [Alpha(3
customer_rating [Alpha(1)] IN
balance_due [Real(5,
PRODUCT
product_no [Alpha(10)] IN
product_name [Alpha(3
unit_of_measure [Alpha(
unit_price [Real(3,2
quantity_available [Intege
ORDER
order_no [Alpha(12)] IND
order_date [Date(mmddy
CUSTOMER.customer_
ORDER_PRODUC
ORDER.order_n
PRODUCT.product_n
quantity_ordered [Intege
OrderProcessing
Program
Process
an Order
Initiation
Routine
Shutdown
Routine
Get an
Order
Validate
an Order
File an
Order
Check
CustomerCredit
Check
ProductData
Check
CreditData
Release
anOrder
Customers ProductsOrders
St. Louis
Mainframe
Indy AIX Server
NT Server LA
NT Server NY
Communications
Controller
PBX
Enternet LAN AIX/Lan
Manager
Ethernet LAN/NT
Ethernet LAN/NT
Client PC Client PC
Client PC Client PC
VALIDATE_AN_ORDER.
REPEAT UNTIL NO_MORE_ORDERS
PERFORM CUSTOMER_VALIDATIO
REPEAT UNTIL NO_MORE_ORDER
PERFORM PRODUCT_VALIDATI
END REPEAT.
PERFORM CREDIT_CHECK.
IF CREDIT CHECK 'BAD' THEN
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Information System DevelopmentINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Database
Technology
Database Structures
Database Scehma
Data Requirements
Business Subjects
FOCUS ON
SYSTEM
DATA
Application Programs
Application Schema
Business Processes
Business Functions
FOCUS ON
SYSTEM
PROCESSES
Component Programs
Interface Schema
Interface Requirements
System Context
FOCUS ON
SYSTEM
INTERFACES
Software
(and Hardware)
Technology
Interface
TechnologyNetworking
Telchnology
Network Programs
Network Schema
Communication Reqts.
Operating Locations
FOCUS ON
SYSTEM
GEOGRAPHY
SYSTEM
SUPPORT
SYSTEM
IMPLEMENTATION
SYSTEM
DESIGN
SYSTEM
ANALYSIS
SYSTEM
PLANNING
System
Development
CREATE TABLE CUSTOM
(customer_no CHAR(10) NOT N
customer_name CHAR(32) NOT
customer _rating CHAR(1) NOT N
balance_due DECIMAL(5
CREATE INDEX cust_no_idx on CUSTO
CREATE INDEX cust_rt_idx on CUSTO
CUSTOMER
customer-n
customer-nam
customer-ratin
balance-du
PRODUCT
product-no
product-nam
unit-of-measu
unit-price
quantity-availa
ORDER
order-no
order-date
products-order
quantities-order
Order Form
Help +
Customer
Form
Product
Lookup
Logon
New Custome
New Orde
Order Accepte
Change
of
Address
First Orde
Request Order He
Order Help Comple
Reques
Product
Lookup
Request Product Lookup He
Product Lookup Help Compl
On Event Help.ButtonClick Do
Change Focus HelpDialog
On Event OKButton Do
Begin
{proecdure}
End
On Event CancelButton Do
Create AccountType =
SalesClerk
Set OrderDir.Rights=full
Set CustomerDir.Rights=full
Set ProductDir.Rights=read
Set OrderAppDir.Rights=copy
Customers order zero,
one, or more products.
Products may be ordered
by zero, one, or more
customers.
Marketing
Advertising
Orders
Sales
Cancellations Services
Order
Management
System
Customer
Accounts
Receivable
Database
Warehouse
Bank
OrderPicking
Order
Credit
Credit
Voucher
Check
credit
Validate
customer
Validate
products
Release
order
Customers
Orders
Products
order
custome
number
valid orde
order witho
valid
customer
credi
order with
valid produc
approved ord
quantity
in stock
approve
order
rejected ord
prices
picking
ticket
Firecracker Sales
EDI
Cust
St.
Louis
HQ
LA
Office
Indy
Ware-
house
NY
Office
West
Customers
East
Customers
Maintenance
Records
Products
Catalogorder
catalog
changes
ship
order
ship
ordership order
credit credit
service
CUSTOME
customer_no [Alpha (10
customer_name [Alp
customer_rating [Alpha(
balance_due [Rea
PRODUC
product_no [Alpha(10
product_name [Alph
unit_of_measure [Al
unit_price [Real
quantity_available [In
ORDER
order_no [Alpha(12)]
order_date [Date(mm
CUSTOMER.custom
ORDER_PROD
ORDER.order
PRODUCT.produ
quantity_ordered [Int
Order
Processing
Program
Process
an Order
Initiation
Routine
Shutdown
Routine
Get an
Order
Validate
an Order
File an
Order
Check
CustomerCredit
Check
ProductData
Check
CreditData
Release
anOrder
Customers ProductsOrders
St. Louis
Mainframe
Indy AIX Serve
NT Server LA
NT Server NY
Communication
Controller
PBX
Enternet LAN AIX/Lan
Manager
Ethernet LAN/NT
Ethernet LAN/NT
Client PC Client PC
Client PC Client PC
VALIDATE_AN_ORDER.
REPEAT UNTIL NO_MORE_ORDER
PERFORM CUSTOMER_VALIDAT
REPEAT UNTIL NO_MORE_ORDER
PERFORM PRODUCT_VALIDAT
END REPEAT.
PERFORM CREDIT_CHECK
IF CREDIT CHECK 'BAD' THEN
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Information System Development
Systems
Planning
Systems
Analysis
Systems Design
Systems
Implementation
Systems
Support
Obsolete System
New 'business' problem or requirement
New 'technology'
alternative or requirementImplementation error
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Information System Development
REASON:
A
System
Development
Methodology
System
Users
System
Owners
Production
System
Database
Program
LibraryRepository
STARTSTART
System
Knowledge and
Documentation
Database
Structures
and actual
Business Data
Application Programs
FINISH
Planned
System
Initiative
Unplanned
System
Request
OR
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Information System Development
1
Survey
Phase
2
Study
Phase
3
Definition
Phase
4
Targeting Phase
6
Design Phase
7
Construction
Phase
5
Purchasing
Phase (if necessary)
8
Delivery
Phase
System
Users
System
Owners
Information Technology
Vendors
Unplanned System Problem
Planned
System Project
Project and System Scope
System
Objectives
Business
Requirements
Technology Requirements
Design
Requirements
Technology Integration
Requirements
Design
Specifications
Prototypes
Operational System
Business Requirements
Business Requirements
Request for
Proposals
Proposals
Production System
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
Information System Development
1
Survey and
plan the
project
2
Study and
analyze the
existing
system
3
Define
and priortize
the business
requirements
4
Target a
feasible
system
solution
6
Design and
integrate
the
target
system
7
Construct
and test
the target
system
5
Purchase
any new
hardware and
software
8
Install and
implement
the
production
system
System
Users
System
Owners
Information
Technology
Vendors
training, support, and feedback
demonstrations
and
feedback
ideas
and
opinions
ideas
and
opinions
requirements
and
rriorities
the business,
problems,
causes, and
effects
Unplanned System Request
Planned
System
Project
Project and
System Scope
System
Objectives
Business
Requirements
Technology
Requirements
Design
Requirements
Technology
Integration
Requirements
Design
Specifications
Prototypes
Functional
System
technology standards
technology
standards
system
proposal
problem statement
and
feasibility analysis
Business Requirements
Business
Requirements
Request
for
Proposals
Proposals
technical
support
installation
support
consulting
services
Production System
executive
leadership
Feasibility
Assessment
and
Project
Plan
technical
leadership
scope
technology proposal
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Information System DevelopmentINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Database
Technology
(and standards)
Database Structures
Database Scehma
Data Requirements
Business Subjects
FOCUS ON
SYSTEM
DATA
Application Programs
Application Schema
Business Processes
Business Functions
FOCUS ON
SYSTEM
PROCESSES
Component Programs
Interface Schema
Interface Requirements
System Context
FOCUS ON
SYSTEM
INTERFACES
Software
(and Hardware)
Technology
(and standards)
Interface
Technology
(and standards)
Networking
Telchnology
(and standards)
Network Programs
Network Schema
Communication Reqts.
Operating Locations
FOCUS ON
SYSTEM
GEOGRAPHY
On-Going Support
Maintenance
Continuous
Improvement
Construction Phase
Delivery Phase
Targeting Phase
Purchasing Phase
Design Phase
Study Phase
Definition Phase
Survey Phase
(and project
planning)
Methodology
CREATE TABLE CUSTOM
(customer_no CHAR(10) NOT N
customer_name CHAR(32) NOT
customer _rating CHAR(1) NOT N
balance_due DECIMAL(5
CREATE INDEX cust_no_idx on CUSTO
CREATE INDEX cust_rt_idx on CUSTO
CUSTOMER
customer-ncustomer-nam
customer-rati
balance-du
PRODUCTproduct-no
product-namunit-of-measu
unit-price
quantity-availa
ORDER
order-no
order-date
products-orderquantities-order
Order Form
Help +
Customer
Form
Product
Lookup
Logon
New Custome
New Orde
Order Accepte
Change
of
Address
First Orde
Request Order He
Order Help Comple
Reques
ProductLookup
Request Product Lookup H
Product Lookup Help Compl
On Event Help.ButtonClick Do
Change Focus HelpDialog
On Event OKButton Do
Begin
{proecdure}
End
On Event CancelButton Do
Create AccountType =
SalesClerk
Set OrderDir.Rights=full
Set CustomerDir.Rights=full
Set ProductDir.Rights=read
Set OrderAppDir.Rights=copy
Customers order zero,
one, or more products.
Products may be ordered
by zero, one, or more
customers.
Marketing
Advertising
Orders
Sales
Cancellations Services
Order
Management
System
Customer
Accounts
Receivable
Database
Warehouse
Bank
OrderPicking
Order
Credit
Credit
Voucher
Check
credit
Validate
customer
Validate
products
Release
order
Customers
Orders
Products
order
custome
number
valid orde
order witho
valid
customer
credi
order with
valid produc
approved ord
quantity
in stock
approve
order
rejected ord
prices
picking
ticket
Firecracker Sales
EDI
Cust
St.
Louis
HQ
LA
Office
Indy
Ware-
house
NY
Office
West
Customers
East
Customers
Maintenance
Records
Products
Catalogorder
catalog
changes
ship
order
ship
ordership order
credit credit
service
CUSTOME
customer_no [Alpha (10
customer_name [Alp
customer_rating [Alpha(1
balance_due [Rea
PRODUC
product_no [Alpha(10
product_name [Alph
unit_of_measure [Al
unit_price [Real
quantity_available [In
ORDER
order_no [Alpha(12)]
order_date [Date(mm
CUSTOMER.custom
ORDER_PROD
ORDER.order
PRODUCT.produ
quantity_ordered [Int
Order
Processing
Program
Process
an Order
Initiation
Routine
Shutdown
Routine
Get an
Order
Validate
an Order
File an
Order
Check
Customer
Credit
Check
Product
Data
Check
Credit
Data
Release
an
Order
Customers Products Orders
St. Louis
Mainframe
Indy AIX Serve
NT Server LA
NT Server NY
Communication
Controller
PBX
Enternet LAN AIX/Lan
Manager
Ethernet LAN/NT
Ethernet LAN/NT
Client PC Client PC
Client PC Client PC
VALIDATE_AN_ORDER.
REPEAT UNTIL NO_MORE_ORDER
PERFORM CUSTOMER_VALIDAT
REPEAT UNTIL NO_MORE_ORDER
PERFORM PRODUCT_VALIDAT
END REPEAT.
PERFORM CREDIT_CHECK
IF CREDIT CHECK 'BAD' THEN
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19987
Information System Development
ID Task Name
1 Survey Phase
2 Study Phase
3 Definition Phase
4 Targeting Phase
5 Design Phase
6 Purchasing Phase
7 Construction Phase
8 Implementation Phase
9
10 Fact Finding
11 Documentation
12 Presentation
13 Estimation
14 Measurement
15 Feasibility Analysis
16 Project management
17 Process management
18
19
20
21
22
23
24
25
26
12/31 1/7 1/14 1/21 1/28 2/4 2/11 2/18 2/25 3/3 3/10 3/17 3/24 3/31 4/7 4/14 4/21 4/28 5/5 5/12 5/19
January February March April May
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19988
Information System Development
1
The
Survey
Phase
2
The
Study
Phase3
The
Definition
Phase
4
The
Targeting
Phase
5
The
Design
Phase
7
The
Construction
Phase6
The
Purchasing
Phase
8
The
Implementa-
tion
Phase
Program
LibraryDatabase
Repository
project and
system scope
system objectives
business
requirements
design and technology
requirements
design
specificationstechnology
integration requirements
functional system
specifications
production system
specifications
purchased
software
prototypes
and functional
software
production software
test data
actual business dataPrepared by Kevin C. Dittman for
Systems Analysis & Design Methods 4edby J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 1998
9
Information System Development
Computer-aided systems engineering (CASE)
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199810
Information System Development
CENTRAL
REPOSITORY
Local
Repository
(on a LAN
Server)Security and
Version
Control
Inquiry and
Reporting
Tools
Data
Sharing
Tools
House-
keeping
Tools
Graphics
Tools
Decision
Support
Tools
Quality
Management
Tools
Design
Generators
Code
GeneratorsDocument
Tools
INPUTS: models,
descriptions
and prototypes
OUTPUTS: reports,
problems, and
analyses
imported and
exported
knowledgecheck-out/
check in knowledge
Repository Server
CASE Tool
Facilities (on a workstation)
Description
Tools
Prototyping
Toolslinks links
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Systems Analysis
1
Survey and
plan the
project
2
Study and
analyze the
existing
system
3
Define
and priortize
the business
requirements
Project and
System Scope
System
Improvement
Objectives
Business
Requirements
Business
Requirementsto the design phase
to the configuration phase
Repository
Documentation
Documentation
Documentation
SYSTEM ANALYSIS
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Systems Analysis
Club
Member
Club
Member
Warehouse
Accounts
Orders
Process
Automatic
Orders
Process
Bonus
Orders
Process
Member
Orders
Member order response
Credit rating and limit
Credit rating
and limitCredit
rating
and
limit
Order to be
filledOrder to be filled
Revised automatic orderExisting order details
Bonus
Order
Order
to be
filled
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Systems Analysis
Member Agreeementis enrolled under;
applies to
Club
established by;
established
Member
Order
Product Promotionsponsors;
is sponsored byis featured in;
features
generates;
generated by
sells;
is sold on
placed by;
places
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Systems AnalysisINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Existing
Databases
and
Technology
Business Subjects
d t
FOCUS ON
SYSTEM
DATA
Business Functions
FOCUS ON
SYSTEM
PROCESSES
System Context
th t
FOCUS ON
SYSTEM
INTERFACES
Existing
Applications
and Technology
Existing
Interfaces
and
Technology
Existing
Networks
and
Technology
Operating Locations
hi
FOCUS ON
SYSTEM
GEOGRAPHY
Survey Phase
(establish scope
and project plan)
FAST
Methodology
Customers order zero,
one, or more products.
Products may be ordered
by zero, one, or more
customers.
Marketing
Advertising
Orders
Sales
Cancellations Services
Order
Management
System
Customer
Accounts
Receivable
Database
Warehouse
Bank
OrderPicking
Order
Credit
Credit
Voucher
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
Systems Analysis
1.1
Survey
problems
and
opportunities
1.2
Negotiate
project
scope
1.3
Plan
the
project
Repository
1.4
Present
the
project
System
Owners
System
Owners
and Users
Request
for
system
services
Request
for
system
services
problem
survey
statement
Problem survey
statement
scope
statement
Request
for
system
services
Problem
statement
Scope
statement
Project
plan
Problem statement
Scope statement
Project plan
System
Management
Project templates
and
Project standards
Project
charter
Project charter
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Systems Analysis
FORM ISS-100-RFSS (Last r evised December , 1996)
SoundStage Entertainment ClubInformation System ServicesPhone: 494-0666 Fax: 494-0999Internet: http://www.soundstage.comIntranet: http://www.soundtstage.com/iss
DATE OF REQUEST SERVICE REQUESTED FOR DEPARTMENT(S)
January 10, 1997 Member Services, Warehouse, Shipping
SUBMITTED BY (key user contact) EXECUTIVE SPONSOR (funding authority)Name Sarah Hartman Name Galen Kirkhoff
Title Business Analyst, Member Services Title Vice President, Member Services
Office B035 Office G242
Phone 494-0867 Phone 494-1242
TYPE OF SERVICE REQUESTED:Information Strategy Planning Existing Application EnhancementBusiness Process Analysis and Redesign Existing Application Maintenance (problem fix)New Application Development Not SureOther (please specify _______________________________________________________________________
BRIEF STATEMENT OF PROBLEM, OPPORTUNITY, OR DIRECTIVE (attach additional documentation as necessary)
The information strategy planning group has targeted member services, marketing, and order fulfillment (inclusive ofshipping) for business process redesign and integrated application development. Currently serviced by separateinformation systems, these areas are not well integrated to maximize efficient order services to our members. Thecurrent systems are not adaptable to our rapidly changing products and services. In some cases, separate systemsexist for similar products and services. Some of these systems were inherited through mergers that expanded ourproducts and services. There also exist several marketing opportunities to increase our presence to our members.One example includes Internet commerce services. Finally, the automatic identification system being developed forthe warehouse must fully interoperate with member services.
BRIEF STATEMENT OF EXPECTED SOLUTIONWe envision completely new and streamlined business processes that minimize the response time to member ordersfor products and services. An order shall not be considered fulfilled until it has been received by the member. Thenew system should provide for expanded club and member flexibility and adaptability of basic business products andservices.
We envision a system that extends to the desktop computers of both employees and members, with appropriateshared services provided across the network, consistent with the ISS distributed architecture. This is consistent withstrategic plans to retire the AS/400 central computer and replace it with servers.
ACTION (ISS Office Use Only)
Feasibility assessment approved Assigned to Sandra Shepherd
Feasibility assessment waived Approved Budget $ _450,000___________
Start Date __ASAP________ Deadline ___ASAP________
Request delayed Backlogged until date: ______________
Request rejected Reason: ________________________________________________
Authorized Signatures:
_____________________________________ _______________________________________Chair, ISS Executive Steering Body Project Executive Sponsor
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19987
Systems Analysis
PROBLEM STATEMENTS
PROJECT: Member Services Information System PROJECT MANAGER: Sandra Shepherd
CREATED BY: Sandra Shepherd LAST UPDATED BY: Robert Martinez
DATE CREATED: January 15, 1997 DATE LAST UPDATED: January 17, 1997
Brief Statements of Problem, Opportunity, or Directive Urgency Visibility Annual
Benefits
Priority
or Rank
Proposed Solution
1. Order response time as measured from time of order receipt to time of customer delivery
has increased to 15 an average of 15 days
ASAP High $175,000 2 New development
2. The recent acquisitions of Private Screenings Video Club and GameScreen will further
stress the throughput requirements for the current system.
6 months Med 75,000 2 New development
3. Currently, three different order entry systems service the audio, video, and game divisions.
Each system is designed to interface with a different warehousing system; therefore, the
intent to merge inventory into a single warehouse house been delayed.
6 months Med 515,000 2 New development
4. There is a general lack of access to management and decision-making information. This
will become exasperated by the acquisition of two additional order processing systems
(from Private Screenings and GameScreen).
12 months Low 15,000 3 after new system is
developed, provide users
with easy-to-learn and -
use reporting tools.
5. There currently exists data inconsistencies in the member and order files. 3 months High 35,000 1 Quick fix; then new
development
6. The Private Screenings and GameScreen file systems are incompatible with the
SoundStage equivalents. Business data problems include data inconsistencies and lack of
input edit controls.
6 months Med unknown 2 New development.
Additional quantification
of benefit might increase
urgency.
7. There is an opportunity to open order systems to the Internet, but security and control is
an issue.
12 months Low unknown 4 Future version of newly
developed system
8. The current order entry system is incompatible with the forthcoming automatic
identification (bar coding) system being developed for the warejhouse
3 months High 65,000 1 Quick fix; then new
development
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19988
Systems Analysis
Project Feasibility Assessment Report
I. Executive summary (1 page)
A. Summary of recommendation
B. Brief statement of anticipated benefits
C. Brief explanation of report contents
II. Background information (1-2 pages)
A. Brief description of project request
B. Brief explanation of the summary phase activities
III. Findings (2-3 pages)
A. Problems and analysis (optional: reference problem statement matrix)
B. Opportunities and analysis (optional: reference problem statement matrix)
C. Directives and implications
IV. Detailed recommendation
A. Narrative recommendation (1 page)
1. Immediate fixes
2. Quick fixes
3. Enhancements
4. New systems development
B. Project Plan
1. Initial project objectives
2. Initial master project plan (phase level)
3. Detailed plan for the study or definition phase
V. Appendices
A. Request for System Services
B. Problem Statements Matrix
C. (other documents as appropriate)
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19989
Systems AnalysisINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Existing
Databases
and
Technology
Database Structures
Database Scehma
Data Problems
and Opportunities
data capture
data access
data reliability
info accuracy
info timeliness
Business Subjects
FOCUS ON
SYSTEM
DATA
Application Programs
Application Schema
Process Problems
and Opportunities
throughput
response time
cost and value
efficiency
service
Business Functions
FOCUS ON
SYSTEM
PROCESSES
Component Programs
Interface Schema
Interface Problems
and Opportunities
control
service
integration
interoperability
service
System Context
FOCUS ON
SYSTEM
INTERFACES
Existing
Applications
and
Technology
Existing
Interfaces
and
Technlogy
Existing
Networks
and
Technology
Network Programs
Network Schema
Geographic Problems
and Opportunities
service
cost and value
response time
accessibility
security
Operating Locations
FOCUS ON
SYSTEM
GEOGRAPHY
Study Phase
(establish
system
improvement
objectives)
Survey Phase
(establish scope
and project plan)
FAST
Methodology
Customers order zero,
one, or more products.
Products may be ordered
by zero, one, or more
customers.
Marketing
Advertising
Orders
Sales
Cancellations Services
Order
Managemen
System
Customer
Accounts
Receivable
Database
Warehouse
Bank
OrderPicking
Order
Credi
Credit
Vouche
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199810
Systems Analysis
2.1
Model
the
current
system
2.3
Analyze
problems
and
opportunities
2.4
Establish
system
improvement
objectives
Repository
1.4
Present
the
project
System
Owners
Approval
to
continue
project
scope
statement
problem statement
cause/effect
analysis
System
models
System
improvement
objectives and
constraints
All prior
deliverables
and
revised
project plan
Detailed
Study
Findingssystem
models
2.2
Analyze
the
business
processes
Process models
Process anaysis
models
Process
analysis data
Cause/effect
analysis
2.5
Modify
project
scope and
plan
System
models
cause/effect
analysis
system
improvement
objectives
and constraints
Project
plan
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199811
Systems Analysis
Page 1 of 5
PROBLEMS, OPPORTUNITIES, OBJECTIVES AND CONSTRAINTS MATRIX
Project: Member Services Information System Project Manager: Sandra Shepherd
Created by: Robert Martinez Last Updated by: Robert Martinez
Date Created: January 21, 1997 Date Last Updated: January 31, 1997
CAUSE AND EFFECT ANALYSIS SYSTEM IMPROVEMENT OBJECTIVES
Problem or Opportunity Causes and Effects System Objective System Constraint
1. Order response time is unaccept-
able.
1. Throughput has increased while
number of order clerks was down-
sized. Time to process a single or-
der has remained relatively con-
stant.
2. System is too keyboard dependent.
Many of the same values are keyed
for most orders. Net result is (with
the current system) each order
takes longer to process than is
ideal.
3. Data editing is performed by the
AS/400. As that computer has ap-
proached its capacity, order edit re-
sponses have slowed. Because or-
der clerks are trying to work faster
to keep up with the volume, the
number of errors have increased.
4. Warehouse picking tickets for or-
ders were never designed to maxi-
mize the efficiency of order fillers.
As warehouse operations grew, or-
der filling delays were inevitable.
1. Decrease the time required to proc-
ess a single order by 30%.
2. Eliminate keyboard data entry for
as much as 50% of all orders.
3. For remaining orders, reduce as
many keystrokes as possible by re-
placing keystrokes with point-and-
click objects on the computer dis-
play screen.
4. Move data editing from a shared
computer to the desktop.
5. Replace existing picking tickets
with a paperless communication
system between member services
and the warehouse.
1. There will be no increase in the
order processing workforce.
2. Any system developed must be
compatible with the existing Win-
dows 95 desktop standard.
3. New system must be compatible
with the already approved auto-
matic identification system (for bar
coding).
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199812
Systems AnalysisAnalysis of the Current ___________ System
I. Executive summary (approximately 2 pages)
A. Summary of recommendation
B. Summary of problems, opportunities, and directives
C. Brief statement of system improvement objectives
D. Brief explanation of report contents
II. Background information (approximately 2 pages)
A. List of interviews and facilitated group meetings conducted
B. List of other sources of information that were exploited
C. Description of analytical techniques used
III. Overview of the current system (approximately 5 pages)
A. Strategic implications (if the project is part of, or impacts an existing information
systems strategic plan)
B. Models of the current system
1. Interface model (showing project scope)
2. Data model (showing project scope)
3. Geographic models (showing project scope)
4. Process model (showing functional decomposition only)
IV. Analysis of the Current System (approximately 5-10 pages)
A. Performance problems, opportunities, and cause/effect analysis
B. Information problems, opportunities, and cause/effect analysis
C. Economic problems, opportunities, and cause/effect analysis
D. Control problems, opportunities, and cause/effect analysis
E. Efficiency problems, opportunities, and cause/effect analysis
F. Service problems, opportunities, and cause/effect analysis
V. Detailed recommendations (approximately 5-10 pages)
A. System improvement objectives and priorities
B. Constraints
C. Project Plan
1. Scope reassessment and refinement
2. Revised master plan
3. Detailed plan for the definition phase
VI. Appendices
A. Any detailed system models
B. (other documents as appropriate)
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199813
Systems AnalysisINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Existing
Databases
and
Technology
Data Requirements
data models
Business Subjects
FOCUS ON
SYSTEM
DATA
Business Processes
process models
Business Functions
FOCUS ON
SYSTEM
PROCESSES
Interface
Requirements
interface models
System Context
FOCUS ON
SYSTEM
INTERFACES
Existing
Applications
and
Technology
Existing
Interfaces
and
Technology
Existing
Networks
and
Technology
Communication Reqts.
distribution models
Operating Locations
FOCUS ON
SYSTEM
GEOGRAPHY
Definition Phase
(establish and
prioritize
business system
requirements)
Study Phase
(establish
system
improvement
objectives)
Survey Phase
(establish scope
and project plan)
FAST
Methodology
CUSTOMER
customer-no
customer-name
customer-rating
balance-due
PRODUCT
product-no
product-name
unit-of-measure
unit-price
quantity-availab
ORDER
order-no
order-date
products-ordered
quantities-ordere
Customers order zero,
one, or more products.
Products may be ordered
by zero, one, or more
customers.
Marketing
Advertising
Orders
Sales
Cancellations Services
Order
Management
System
Customer
Accounts
Receivable
Database
Warehouse
Bank
OrderPicking
Order
Credit
Credit
Voucher
Check
credit
Validate
customer
Validate
products
Release
order
Customers
Orders
Products
order
custome
number
valid orde
order withou
valid
customer
credi
order with
valid product
approved orde
quantity
in stock
approve
order
rejected orde
prices
picking
ticket
Firecracker Sales
EDI
Cust
St.
Louis
HQ
LA
Office
Indy
Ware-
house
NY
Office
West
Customers
East
Customers
Maintenance
Records
Products
Catalogorder
catalog
changes
ship
order
ship
ordership order
credit credit
service
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199814
Systems Analysis
3.1
Outline
Business
Requirements
3.2
Model
business
system
requirements
3.3
Build
discovery
prototypes
Repository
3.5
Modify
project
plan
and
scope
System
Owners
Approval
to
continue
project
system
improvement
objectives
requirements
statement outline
system models
Discovery prototypes
Requirements
statement
outline
All prior
deliverables
Revised
scope
and
planrequirements
statement
outline
3.4
Prioritize
Business
Requirements
System
models
Discovery
prototypes
Business
requirements'
priorities
System
models
Business
requirements
outline
Revised
plan
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199815
Systems Analysis
The
Member
Services
Information
System
Current
Member
Accounts
Warehouse
Prospective
Member
Past
Member
Marketing
Division
Member
Services
Division
Resubscription
Order
Subscription Order
Member Order
Member Promotion
Referral Order
Picking Order
Unanticipated Backorder
PRODUCT SHIPMENT
Sales
Reports
and
Analyses
New Monthly
Promotion
Subscription
Plan
Membership
Reports and
Analyses
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Data Modeling
CUSTOMER
Customer Number (PK)
Customer Name
Shipping Address
Billing Address
Balance Due
ORDER
Order Number (PK)
Order Date
Order Total Cost
Customer Number (FK)
INVENTORY PRODUCT
Product Number (PK)
Product Name
Product Unit of Measure
Product Unit Price
ORDERED PRODUCT
Ordered Product ID (PK)
. Order Number (FK)
. Product Number (FK)
Quantity Ordered
Unit Price at Time of Order
has placed
sold
sold as
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Data Modeling
STUDENT CURRICULUMis enrolled inis being studied by
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Data Modeling
Cardinality
Interpretation
Minimum
Instances
Maximum
Instances
Graphic Notation
Exactly one 1 1
Zero or one 0 1
One or more 1 many ( > 1 )
Zero, one, or more 0 many ( > 1 )
More than one > 1 > 1
Figure 5.3
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Data Modeling
COURSE
Course Id (Primary Key)
. Subject Abbreviation
. Course Number
Course Title
Course Credit
is a prerequisite for
has as a prerequisite
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
Data Modeling
COURSE
Course ID (Primary Key)
. Subject Abbreviation
. Course Number
Course Title
Credit
INSTRUCTOR
Instructor ID Code (Primary
Key)
Instructor Name
. Last Name
. First Name
. Middle Initial
ROOM
Classroom ID
. Building Abbreviation
. Room Number
Number of Seats
SCHEDULED CLASS
Scheduled Class ID (Primary Key)
. Course ID
. Instructor ID
. Room ID
Division Number
Days of Week
Start Time
End Time
meets asis assigned to
is assigned to
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Data Modeling
CURRICULUM
Program of Study Code (Primary Key)
Title of Program
Type of Degree Awarded (Subsetting Criteria 1)
Department Number (Foreign Key)
DEPARTMENT
Department Number (Primary Key)
Department Name offers is offered by
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19987
Data Modeling STUDENT
Student Number (Primary Key 1)
Name (Alternate Key 1)
. Last Name
. First Name
. Middle Initial
Address
. Street Address
. City
. State or Province
. Country
. Postal Code
Phone Number
. Area Code
. Exchange Number
. Number Within Exchange
Date of Birth
Gender (Subsetting Criteria 1)
Race (Subsetting Criteria 2)
Grade Point Average
FIGURE(a)
CURRICULUM
Program of Study Code (Primary Key)
Title of Program
Type of Degree Awarded (Subsetting Criteria 1)
applies to is enrolled in
STUDENT
Student Number (Primary Key 1)
Name (Alternate Key 1)
. Last Name
. First Name
. Middle Initial
Address
. Street Address
. City
. State or Province
. Country
. Postal Code
Phone Number
. Area Code
. Exchange Number
. Number Within Exchange
Date of Birth
Gender (Subsetting Criteria 1)
Race (Subsetting Criteria 2)
Grade Point Average
CURRICULUM
Program of Study Code (Primary Key)
Title of Program
Type of Degree Awarded (Subsetting Criteria 1)
has declared
is being studied by
FIGURE (b)
MAJOR
Major ID (Primary Key)
. Student Number (Foreign Key)
. Program of Study Code (Foriegn Key)
Date Enrolled
Current Candidate for Degree?
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19988
Data Modeling PERSON
Personal ID Number (Primary Key)
Name
. Last Name
. First Name
. Middle Initial
Gender (Subsetting Criteria 1)
Race (Subsetting Criteria 2)
Marital Status (Subsetting Criteria 3)
STUDENT
Personal ID Number = Student Number (Primary
Key)
all attributes from PERSON
EMPLOYEE
Personal ID Number = Social Security Number (Primary
Key)
all attributes from PERSON plus
Pension Plan Code
Life Insurance Plan Code
Medical Insurance Plan Code
Vacation Days Accumulated
Sick Days Acculumlated
ADDRESS
is ais a
can be
contacted
at
PROSPECT
all attributes from PERSON and STUDENT plus
First Contact Date
Last Contact Date
Has Visited Campus?
ALUMNUS
all attributes from PERSON and STUDENT plus
Member of Alumni Association?
Job in Field of Study?
Last Known Salary
FORMER STUDENT
all attributes from PERSON and STUDENT plus
Reason for Withdrawal
Plans to Return?
CURRENT STUDENT
all attributes from PERSON and STUDENT plus
Number of Credits Earned
Grade Point Average
Encumberance Status
Financial Aid Eligibility Status
is a
is a
could be a
could be a
CONTRACTis bound by
AWARDED
DEGREEhas earned
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19989
Data ModelingINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Existing
Databases
and
Technology
Data Requirements
d d l
Business Subjects
i i d d fi i i
FOCUS ON
SYSTEM
DATA
FOCUS ON
SYSTEM
PROCESSES
FOCUS ON
SYSTEM
INTERFACES
Existing
Applications
and
Technology
Existing
Interfaces
and
Technology
Existing
Networks
and
Technology
FOCUS ON
SYSTEM
GEOGRAPHY
Definition Phase
(establish and
prioritize
business system
requirements)
Study Phase
(establish
system
improvement
objectives)
Survey Phase
(establish scope
and project plan)
FAST
Methodology
CUSTOMER
customer-ncustomer-nam
customer-rati
balance-du
PRODUCTproduct-no
product-namunit-of-measu
unit-price
quantity-availa
ORDER
order-no
order-date
products-orderquantities-order
Customers order zero,
one, or more products.
Products may be ordered
by zero, one, or more
customers.
Reverse
Engineering
(optional)
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199810
Data Modeling
MEMBER ORDER
Comment
PRODUCT
Comment
MEMBER
Comment
PROMOTION
Comment
AGREEMENT
Comment
CLUB
Comment
responds to
is featured in
places
establishessponsors
belongs to
sells binds
generates
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199811
Data Modeling
PRODUCT ON ORDER
Key Data
Order-Number [PK1] [FK]
Member-Number [PK2] [FK]
Product-Number [PK3] [FK]
Universal-Product-Code [PK4] [FK]
PROMOTION
Key Data
Product-Number [PK2] [FK]Club-Name [PK1] [FK]Universal-Product-Code [PK3] [FK]
PRODUCT
Key Data
Product-Number [PK1]Universal-Product-Code [PK2]
MEMBER ORDER
Key Data
Order-Number [PK1]Member-Number [PK2] [FK]
AGREEMENT
Key Data
Club-Name [PK2] [FK]Agreement-Number [PK1]
CLUB MEMBERSHIP
Key Data
Member-Number [PK2] [FK]
Club-Name [PK3] [FK]
MEMBER
Key Data
Member-Number [PK1]
CLUB
Key Data
Club-Name [PK1]
sold as
sells
enrolls in
sponsors
binds
responds to
is featured in
places
establishessponsors
generates
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199812
Data Modeling
PRODUCT ON AN ORDER
Key Data
Order-Number [PK1] [FK]
Product-Number [PK2] [FK]
Universal-Product-Code [PK3] [FK]
CLUB MEMBERSHIP
Key Data
Club-Name [PK1] [FK]
Member-Number [PK2] [FK]
Agreement-Number [PK3] [FK]
TITLE
Key Data
Product-Number [PK1] [FK]
Universal-Product-Code [PK2] [FK]
MERCHANDISE
Key Data
Product-Number [PK1] [FK]
Universal-Product-Code [PK2] [FK]
VIDEO TITLE
Key Data
Product-Number [PK1] [FK]
Universal-Product-Code [PK2] [FK]
GAME TITLE
Key Data
Product-Number [PK1] [FK]
Universal-Product-Code [PK2] [FK]
AUDIO TITLE
Key Data
Product-Number [PK1] [FK]
Universal-Product-Code [PK2] [FK]
PRODUCT
Key Data
Product-Number [PK1]
Universal-Product-Code [PK2]
AGREEMENT
Key Data
Club-Name [PK2] [FK]
Agreement-Number [PK1]
MEMBER
Key Data
Member-Number [PK1]
MEMBER ORDER
Key Data
Order-Number [PK1]
PROMOTION
Key Data
Club-Name [PK1] [FK]CLUB
Key Data
Club-Name [PK1]
generates
sold as
sells
responds to
placed
sponsors
sponsors
binds
establishes
enrolls in
generates
is a
is a
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199813
Data Modeling
MEMBER
Key Data
Member-Number [PK1]
Non-Key Data
Member-Name
. Last-Name
. First-Name
. Middle-Initial
Member-Status
Member-Street-Address
Member-Post-Office-Box
Member-City
Member-State
Member-Zip-Code
Member-Daytime-Phone-Number
. Area-Code
. Phone-Number
. Extension ()
Member-Date-of-Last-Order
Member-Balance
Member-Credit-Card-Type
Member-Credit-Card-Number
Member-Credit-Card-Expire-Date
Member-Bonus-Balance
MEMBER ORDER
Key Data
Order-Number [PK1]
Non-Key Data
Order-Creation-Date
Order-Fill-Date
Shipping-Address-Name
Shipping-Street-Address
Shipping-City
Shipping-State
Shipping-Zip
Shipping-Instructions
Order-Sub-Total
Order-Sales-Tax
Order-Shipping-Method
Order-Shipping-&-Handling-Cost
Order-Status
Order-Prepaid-Amount
Order-Prepayment-Method
Member-Number [FK]
Club-Name [FK]
Promotion-Number
VIDEO TITLE
Key Data
Product-Number [PK1] [FK]
Universal-Product-Code [PK2] [FK]
Non-Key Data
Producer
Director
Video-Category
Video-Sub-Category
Closed-Captioned
Language
Running-Time
Video-Media-Type
Video-Encoding
Screen-Aspect
MPA-Rating-Code
GAME TITLE
Key Data
Product-Number [PK1] [FK]
Universal-Product-Code [PK2] [FK]
Non-Key Data
Manufacturer
Game-Category
Game-Sub-Category
Game-Platform
Game-Media-Type
Number-of-Players
Parent-Advisory-Code
PRODUCT
Key Data
Product-Number [PK1]
Universal-Product-Code [PK2]
Non-Key Data
Product-Quantity-in-Stock
Product-Type
Manf-Suggested-Price
Club-Default-Price
Special-Price
Units-Sold-Month-to-Date
Units-Sold-Year-to-Date
Units-Sold-Lifetime
PRODUCT ON AN ORDER
Key Data
Order-Number [PK1] [FK]
Product-Number [PK2] [FK]
Universal-Product-Code [PK3] [FK]
Non-Key Data
Quantity-Ordered
Quantity-Shipped
Quantity-Backordered
Purchase-Unit-Price
Credits-Earned
AUDIO TITLE
Key Data
Product-Number [PK1] [FK]
Universal-Product-Code [PK2] [FK]
Non-Key Data
Artist
Audio-Category
Audio-Sub-Category
Number-of-Units-in-Package
Audio-Media-Code
Content-Advisory-Code
TITLE
Key Data
Product-Number [PK1] [FK]
Universal-Product-Code [PK2] [FK]
Non-Key Data
Title-of-Work
Title-Cover
Catalog-Description
Copyright-Date
Entertainment-Category
Credit-Value
PROMOTION
Key Data
Club-Name [PK1] [FK]
Non-Key Data
Promotion-Number
Promotion-Release-Date
Promotion-Status
Promotion-Type
Automatic-Fill-Delay
Product-Number [FK]
Universal-Product-Code [FK]
MERCHANDISE
Key Data
Product-Number [PK1] [FK]
Universal-Product-Code [PK2] [FK]
Non-Key Data
Merchandise-Name
Merchandise-Description
Merchadise-Type
Unit-of-Measure
CLUB MEMBERSHIP
Key Data
Club-Name [PK1] [FK]
Member-Number [PK2] [FK]
Agreement-Number [PK3] [FK]
Non-Key Data
Date-Enrolled
Expiration-Date
Number-of-Credits-Required
Number-of-Credits-Earned
AGREEMENT
Key Data
Club-Name [PK2] [FK]
Agreement-Number [PK1]
Non-Key Data
Agreement-Active-Date
Agreement-Expire-Date
Fulfillment-Period
Required-Number-of-Credits
CLUB
Key Data
Club-Name [PK1]
Non-Key Data
Club-Description
Club-Charter-Date
sold as
sells
responds to
placed
sponsors
sponsors
binds
establishes
enrolls in
generates
generates
is a
is a
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Process ModelingINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Database
Technology
FOCUS ON
SYSTEM
DATA
Business Processe
D t Fl Di
Business Functions
D iti Di
FOCUS ON
SYSTEM
PROCESSES
System Context
C t t Di
FOCUS ON
SYSTEM
INTERFACES
Software
(and Hardware)
Technology
Interface
Technology Networking
Telchnology
FOCUS ON
SYSTEM
GEOGRAPHY
Study Phase
(establish
system
improvement
objectives)
Definition Phase
(establish and
prioritize
business system
requirements)
Survey Phase
(establish scope
and project plan)
FAST
Methodology
Marketing
Advertising
Orders
Sales
Cancellations Services
Order
Managemen
System
Customer
Accounts
Receivable
Database
Warehouse
Bank
OrderPicking
Order
Credi
Credit
Vouche
Check
credit
Validate
customer
Validate
products
Release
order
Customer
Orders
Products
order
custome
numbe
valid ord
order witho
valid
customer
cred
order with
valid produc
approved ord
quantity
in stock
approve
order
rejected ord
prices
picking
ticket
Reverse
Engineering
(optional)
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Process Modeling
Reconcile
Account
Balances
Pay
a
Bill
Withdraw
Funds from
an Account
Deposit Funds
into an
Account
Bank
Creditor
Employer
Other
Income
Source
Bank
Monthly Account
Statements
Account
Transactions
Bank Accounts
Account
Transactions
Bill
Payment
Monthly
Statement
Account
Balance
Transaction
Prior Monthly
Statement
New or Modified
Monthly Statement
Modified
Balance
Pay
Reimbursement
Withdraw or transfer
Deposit
Payment
Modified Balance
Current
Balance
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Process Modeling
The System's Environment
(constantly changing)
The
System
Process
input output
Feeback and
Control Loop
input
inputoutput
output
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Process ModelingSystem Concepts for Process
Modeling
Process name
Process name
(the Gane & Sarson shape;
used throughout this book)
(the DeMarco & Yourdon shape)
Process name
(the SSADM & IDEF0 shape)Prepared by Kevin C. Dittman for
Systems Analysis & Design Methods 4edby J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 1998
5
Process Modeling
0
The System
1
A Function of the System
1.1
Activity of the Function
Task 1.1.3
1.2
Another Activity of the Function
Task 1.1.1 Task 1.1.2
Task 1.2.2
Task 1.2.1
2
Another Function of the System
2.1
Activity of this Function
Task 2.1.1
Task 2.1.3 Task 2.1.4
Task 2.1.2
2.2
Another Activity of this Function
Task 2.2.1
Task 2.2.3
Task 2.2.2
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Process Modeling0
The System
1
A Function
2
Another
Function
1.1
Activity of the
Function
1.2
Another Activity
of the Function
Task 1.2.2
Task 2.1.1Task 1.1.1
Task 1.1.2
Task 1.1.3
Task 1.2.1
2.2
Another Activity
of this Function
2.1
Acivity of this
Function
Task 2.1.2
Task 2.1.3
Task 2.1.4
Task 2.2.1
Task 2.2.2
Task 2.2.3
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19987
Process Modeling
3.1.2
Create a new
member account
3.1.1
Generate an
employee bank
statement
3.1.3
Freeze member
account number
Accounts
Receivable
Department
Employee
Member Accounts Employees
Existing account
New account status
Employee
status
Frozen account notification
Employee address
Bank statement
Membership
application
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19988
Process Modeling
Telephone
Service
Provider
Pay
phone
bill
Itemized
calls
and
invoice
Itemized calls
Invoice
Correct use of the
packet concept
Incorrect
use of the
packet
concept
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19989
Process Modeling
(b) More Detailed DFD
(a) General-Level DFD
Process
orderCustomer ...OrderAccepted
Order
Process
recurring
order
Process
standard
order
Process
rush
order
Customer
Process
employee
order
yOrder
Standing
Order
Recurring
Order
Rush
Order
Employee
Order
...
...
...
...
Accepted
Standing
Order
Accepted
Recurring
Order
Accepted
Rush
Order
Accepted
Employee
Order
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199810
Process Modeling
Orders
Process
Order
Cencel
Order
Change
Order
Address
Summarize
Unfilled
Orders
OrderCancelled Order
Change of Address Summary of Orders
New
Order
Address
Unfilled
Order
l
New
Order
Order
to be
Deleted
2
1
2
2
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199811
Process Modeling
B1 B2 B1 B1
B1 B1
B1 B1
DS1 DS2 DS1
a process is
needed to
exchange data
flows between
boundaries
a process is
needed to
update (or
use) a data
store
a process is
needed to
present data
from a data
store
a process is
needed to
move data
from one data
store to
another
DS2
DS1
DS1 DS1
DS1
Illegal
data
flows
Corrected
data
flows
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199812
Process Modeling
Process
data flow A
data flow B
data flow C
converging
data flow
A + B + C
data flow D
data flow E
data flow F
converging
data flow
D or E or F
diverging
data flow
U + V + W
diverging
data flow
X or Y or Z
data flow U
data flow V
data flow W
data flow X
data flow Y
data flow Z
1 1
2 2
data flow H
data flow J
data flow R
data flow T
3 3data flow I data flow S
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199813
Process ModelingSystem Concepts for Process
Modeling
External Agents
The term external means “external to the system being analyzed or
designed.”
An external agent is represented by a square on the data flow
diagram.
The Yourdon/Demarco equivalent is a rectangle
External agents on a logical data flow diagram may include people,
business units, other internal systems with which your system must
interact, and external organizations.
Gane & SarsonExternal Agent
Shape
DeMarco/Yourdon External Agent
Shape
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199814
Process ModelingSystem Concepts for Process
Modeling
Data Stores
Most information systems capture data for later use.
The data is kept in a data store.
A data store is an ``inventory’’ of data. Synonyms include file
and database (although those terms are too implementation-
oriented for essential process modeling).
A data store is represented by the open-end box.
If data flows are data in motion, think of data stores as data at rest.
Data stores should describe ``things’’ about which the business
wants to store data.
Gane & SarsonData Store Shape
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199815
Process Modeling
The
System
Event 1 Event 5 Event n
Function 1 Function n
. . .Event 1 Event 2 Event 3 Event 4 Event 5 Event n-2 Event n-1 Event n
. . .Function 2
The
System
. . .. . .
1
2
4
3
Event-Response List
event 1 response
event 2 response
response
event 3 response
response
response
event 4 response
...
5
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199816
Process Modeling
Event 1
Event 3
Event 4
Event n-2
Event n-1
Event 2
Event n
Event 5
2.2
2.1
2.4
2.3
6
7
. . . . . .
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199817
Process Modeling
PotentialMember
D AccountsReceivableData BaseClub
Member
MarketingDepartment
MemberServices
Warehouse
PastMember
P
MemberServicesSystem
Other Order
Member Order Response
New Member Subscription
Club Promotion
Subscription Renewal
Membership Reports
Member Reports
Sales and Promotions Reports
Subscription Program
New Monthly Promotion
Order to be Filled
MemberCredit Status
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199818
Process Modeling
GenerateMembership
Reports
Process
MembershipTransactions
GenerateOrder
Reports
PromotionsSubsystem
Process
PromotionTransactions
GeneratePromotion
Reports
OrdersSubsystem
MembershipSubsystem
Process
OrderTransactions
Member ServicesSystem
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199819
Process Modeling
Generate
Membership
Reports
Process
Membership
Transactions
Generate
Order
Reports
Generate
Promotion
Reports
Process
Promotion
Transactions
Promotions
Subsystem
Orders
Subsystem
Generate
Membership
List
Process
Order
Transactions
Membership
Subsystem
Generate
Agreemt
Compliance
Rpt
Member Services
System
Generate
Inactive
Member
Report
Process
New
Member
Subscription
Generate
Member
Activity
Report
Process
Subscription
Cancel
Process
Referral
Subscription
Respond to
Member
Inquiry
Move
Member to
a New Club
Process
Member
Cancellation
Process
Name /
Address
Change
Cancel
Inactive
Members
Change
Member
Agreement
Page
3
Page
3
Page
2
Page
2
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199820
Process Modeling
P
ProcessChange ofAddress
Member
D Members
Event DiagramEvent: Member changes name or address
Change of Address
Update to Name/AddressName/Address Change Confirm
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199821
Process Modeling
P
ProcessMember Order
Response
Member Warehouse
D AccountsReceivable DB
D Memberships
D Agreements
D Products
D Orders
D Members
Event DiagramEvent: Member responds to promotional order.
Update to Membership Credits
Member Address
Update: Order Changes
Update to Order Status
Original Dated Order
Update to Agreement Stats
Product Availability
Credit Rating and Limits
Backorder Picking Ticket
Member Order Response
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199822
Process Modeling
P
AutomaticallyFill Dated Order Warehouse
D Members
D Memberships
D Agreements
D Products
D AccountsReceivable DB
D Orders
Event DiagramEvent: Deadline for member to reposnd to dated order has passed.
Product Availability
Update to Agreement StatsMember Address
Update toMembership
Credits
Picking Ticket
Credit Ratingand Limits
Update: Order Changes
Update to Order Status
Original Dated Order
Deadline to Fill Dated Order
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199823
Process Modeling
P
Credit MemberPurchase
P
Release Orderto Warehouse
P
CalculateOrder Total
Cost
P
CheckMember Credit
P
CalculateExtended
Cost
P
Check ProductAvailability
P
CheckOrderedProductValidity
P
ValidateMember
Warehouse
Member
D Members
D Agreements
D Memberships
D Orders
D AccountsReceivable DB
D Ordered Products
D Products
D Orders
D Members
Elementary Processes forProcess Member Order Response
R. Martinezas of March 6, 1997
Member Address Updated Activity Record
Update to Agreement Stats
Update to Membership Credits
Fillable Ordered Product
Update to Order Status
Fillable Order
Picking Ticket
Credit Rating and Limits
Pre-Payment Request
Total Order Price
Ordered Product Extended Price
Product Price
Available Productand Quantity
Update Ordered Product Status
Inventory Commitment
Product Availability
Valid Product
Update Order Product
Product ID
Backorder
Invalid Product ID
Update: Order Changes
Original Dated Order
Member Demographics
Updated Member DemographicsInvalid Member ID
Member OrderResponse
Payment Method and Amount
OrderedProductQuantity
Ordered Product ID
Member ID and Address
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Object Modeling(Customer)
customer number = 412209
last name = Bentley
first name = Lonnie
home phone = 317-463-9593
street = 2625 Darwin
Drive
city = West Lafayette
state = Indiana
zipcode = 47906
etc.
(a)
(Book)
ISBN = 0256101329
type = textbook
title = Systems Analysis & Design Methods
copyright = 1996
(b)
(Book)
ISBN = 0256102219
type = workbook
title = Projects and Cases to Accompany
SADM
copyright = 1996
Person Class
(supertype)
Student Class
(subtype)
Teacher Class
(subtype)
Student A Student B Student C Teacher A Teacher B
(c)
Open
Close
ISBN
type
title
copyright
Book
(d)Prepared by Kevin C. Dittman for
Systems Analysis & Design Methods 4edby J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 1998
2
Object Modeling
walk
jump
talk
sleep
eat
etc.
last name
first name
birthdate
gender
Person
enroll
display GPA
GPA
classification
Student
lecture
rank
Teacher
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Object Modeling
Class name
Class name
Class name
Class name
Class name
1
+
n, m
means one and only one
means zero or more
means zero or one
one or more
means minimum of n and
maximum of m (ie. 1,7)
(b)
MultiplicityNotation
Meaning ofNotation
Customer OrderPlaces
(a)
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Object Modeling
Book
CoverTable of
Contents Chapter Index
Page
Paragraph
Word
1
+
1
+
1
+
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
Object Modeling
Customeradd order
modify order
delete order
display status
etc.
order number
order date
order status
etc.
Order
display order status
of order 23161
MESSAGEREQUEST
(containing name of request behavior
and attribute needed by ORDER)
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Object Modeling
Warehouse
Member Services
System
Club Member
Marketing
Department
Potential
Member
Subscription Offer
New Subscription
New MembershipPlan & Subscrition
Offer
Sales & PromotionReports
Order To Be Filled
Club Promtion
Promotion Order
Member Services
Context Model
New Monthly orSeasonal Promotion
Past Member
Subscrition
Renewal Offer
SubscritionRenewal
Member CreditStatus
Accounts
Receivable
Data Base
Regular Order
Member Services
Department
MembershipReports
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19987
Object Modeling
ACTOR USE CASE
Club Member initiates Submit Promotion Order
Submit Regular Order
Potential Member initiates Submit New Subscription
Past Member initiates Submit Subscription Renewal
Member Services Department initiates Request Membership Rpts.
Marketing Department initiates Create New Monthly Promotion
Create New Seasonal Promotion
Create New Subscription Program
Request Promotion Rpts.
Request Sales Rpts.
Member Services System initiates Send New Subscription Offer
Send Club Promotion
Send Subscription Renewal Offer
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19988
Object Modeling
Member
Services
Department
Marketing
Department
Member
Services
System
Past
Member
Potential
Member
Club
Member
Create New
Seasonal Promotion
Request Promotion
Rpts.
Request
Membership Rpts.
Request Sales Rpts.
Create New
Subscription
Program
Create New
Monthly Promotion
Submit New
Subscription
Send New
Subscription Offer
Submit
Subscription
Renewal
Send Subscription
Renewal Offer
Submit Promotion
Order
Send Club
Promotion
Submit Regular
Order
Member Services SystemUse Case Model
PromotionsSubsystem
OrdersSubsystem
MembershipSubsystem
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19989
Object ModelingUSE CASE
Author:__L. Bentley_ Date:__10/01/96_
USE CASE NAME: Submit Promotion Order
ACTOR: Club Member
DESCRIPTION: Describes the process when a club member submits a club promotion order to either
indicate the products they are interested in ordering or declining to order during
this promotion.
NORMAL
COURSE:
1. This use case is initiated when the club member submits the promotion order to
be processed.
2. The club member’s personal information such as address is validated against
what is currently recorded in member services.
3. The promotion order is verified to see if product is being ordered.
4. The club member’s credit status is checked with Accounts Receivable to make
sure no payments are outstanding.
5. For each product being ordered, validate the product number.
6. For each product being ordered, check the availability in inventory and record
the ordered product information which include “quantify being ordered” and
give each ordered product a status of “open”.
7. Create a Picking Ticket for the promotion order containing all ordered
products which have a status “open”.
8. Route the Picking Ticket to the Warehouse.
PRE-CONDITION: Use case Send Club Motion has been processed.
POST-CONDITION: Promotion order has been recorded and the Picking Ticket has been routed to the
Warehouse.
ASSUMPTIONS:
A
B
C
D
E
F
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199810
Object Modeling
Create New
Seasonal Promotion
Send Club
Promotion
Request Promotion
Rpts.
Create New
Monthly Promotion
Submit Promotion
Order
Send New
Subscription Offer
Send Subscription
Renewal Offer
Submit New
Subscription
Request
Membership Rpts.
Subscription
Renewal
Create New
Subscription
Program
Request Sales
Rpts.
Submit Regular
OrderOR
Member Services SystemUse Case Dependency Diagram
depends on
depends on
depends on
depends on
depends on
depends on
depends on
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199811
Object Modeling
POTENTIAL OBJECT
LIST
Club Member
Potential Member
Past Member
Member Services Department
Marketing Department
Member Services System
Member Address
Promotion order
Product
Product Inventory
Order Quantity
Ordered Product
Credit Status
Payments
Ordered Product Status
Picking Ticket
Warehouse
Member Telephone Number
Selection Of Month
Transaction
Accounts Receivable
Promotion Order Status
Order Error Report
Member Services Clerk
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199812
Object Modeling
POTENTIAL OBJECT
LIST
REASON
Club Member Type of “MEMBER”
Potential Member Type of “MEMBER”
Past Member Type of “MEMBER”
Member Services Department Not relevant for current project
Marketing Department Not relevant for current project
Member Services System Not relevant for current project
Member Address Attribute of “MEMBER”
Promotion order Result of an event named “PROMOTION”
Type of “MEMBER ORDER”
Product “PRODUCT”
Product Inventory Attribute of “PRODUCT”
Order Quantity Attribute of “MEMBER ORDER”
Ordered Product “PRODUCT ON ORDER”
Credit Status Attribute of “MEMBER”
Payment Out of Scope
Ordered Product Status Attribute of “PRODUCT ON ORDER”
Picking Ticket Potential interface item
Warehouse Not relevant for current project
Member Telephone Number Attribute of “MEMBER”
Selection Of Month Type of “TITLE”
Transaction Not relevant for current project
Accounts Receivable Not relevant for current project
Promotion Order Status Attribute of “MEMBER ORDER”
Order Error Report Potential interface item
Member Services Clerk Not relevant for current project
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199813
Object Modeling
PROPOSED OBJECT
LIST
MEMBER
MEMBER ORDER
PRODUCT
PRODUCT ON ORDER
TITLE
PROMOTION
PLUS
MERCHANDISE
AUDIO TITLE
VIDEO TITLE
GAME TITLE
CLUB
CLUB MEMBERSHIP
AGREEMENT
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199814
Object Modeling
PRODUCT ON ORDER
CLUB MEMBERSHIP
AUDIO TITLE VIDEO TITLE GAME TITLE
MEMBER ORDER MEMBER
MERCHANDISE
PRODUCT
TITLE AGREEMENTCLUBPROMOTION
MEMBER SERVICES INFORMATION SYSTEMHIGH LEVEL OBJECT MODEL
is a
is a
generates sponsors
sponsors
1+
establishes
binds
1+
enrolls in
placed
sold as
1+
sells