Systems Design and Constructionpibul2.psru.ac.th/~thep/student/SA/CHAPTER 9-18 Slides...Prepared by...
Transcript of Systems Design and Constructionpibul2.psru.ac.th/~thep/student/SA/CHAPTER 9-18 Slides...Prepared by...
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Systems Design and Construction
Configuration
Phase
Procurement
Phase
Design
&
Integration
Phase
Repository
SYSTEMS DESIGN
Technology
Requirements
Design
Requirements
Technology
Integration
Requirements
to the
construction
phase
Documentation
Documentation
Documentation
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Systems Design and Construction1.2
Approve
applicant
1.2.2
Determine
acceptance
1.2.1
Get past
member account
standing
1.2.3
Record
reviewed
application
1.2.3.1
Reject
applicant
1.2.3.2
Accept
applicant
Past Member
Rejected
applicationsMembers
Rejected
application
Rejected
application
New
member
details
New
member
details
Subscriber's
name
Standing and
time account
closed
Standing and
time account
closed
Standing and
time account
closed
Standing and
time account
closed
Acceptance
decision
Acceptance
decision
Reviewed
application
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Systems Design and ConstructionINFORMATION SYSTEMS FRAMEWORK
SYSTEM
ANALYSTS
SYSTEM BUILDERS
(components)
SYSTEM DESIGNERS
(specification)
SYSTEM USERS
(requirements)
SYSTEM OWNERS
(scope)
Database
Technology
(and standards)
Data Requirements
Business Subjects
FOCUS ON SYSTEM
DATA
Business Processes
Business Functions
FOCUS ON SYSTEM
PROCESSES
Interface Requirements
System Context
FOCUS ON SYSTEM
INTERFACES
Software
(and Hardware)
Technology
(and standards)
Interface
Technology
(and standards)
Networking
Telchnology
(and standards)
Communication Reqts.
Operating Locations
FOCUS ON SYSTEM
GEOGRAPHY
Definition Phase
Study Phase
REASON
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
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
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
approved
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
Survey Phase
Configuration
Phase
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Systems Design and Construction
1
Define
Candidate
Solutions
2
Analyze
Feasibility of
Alternative
Solutions
3
Recommend
A System
Solution
Repository
CONFIGURATION PHASE
System
Owners
Approval
to
continue
project Various
Outside
Sources
H/W & S/W
Costs
and
References
H/W & S/W
Specifications
Candidate
Solutions
Business
Reqmts
Outline
&
Approved
Tech.
Architecture
Candidate
Solutions
Feasibility
Analysis
System
ProposalChanges
to
Proposed
Design
Proj. Plan,
Size Estimates,
Candidate
Solutions,
& Feasibility
Analysis
to the procurement phase
to the design and integration phase
Technology
Requirements
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
Systems Design and ConstructionCharacteristics Candidate 1 Candidate 2 Candidate 3 Candidate ...
Portion of System Computerized
Brief description of that portion of thesystem that would be computerized inthis candidate.
COTS package PlatinumPlus from EntertainmentSoftware Solutions would bepurchased and customized tosatisfy Member Servicesrequired functionality.
Member Services andwarehouse operations inrelation to order fulfillment.
Same as candidate 2.
Benefits
Brief description of the business benefitsthat would be realized for thiscandidate.
This solution can beimplemented quicklybecause its a purchasedsolution.
Fully supports user requiredbusiness processes forSoundstage Inc. Plus moreefficient interaction withmember accounts.
Same as candidate 2.
Servers and Workstations
A description of the servers andworkstations needed to support thiscandidate.
Technically architecturedictates Pentium pro, MSWindows NT class serversand Pentium, MS WindowsNT 4.0 workstations(clients).
Same as candidate 1. Same as candidate 1.
Software Tools Needed
Software tools needed to design andbuild the candidate (e. g., databasemanagement system, emulators,operating systems, languages, etc.). Notgenerally applicable if applicationssoftware packages are to be purchased.
MS Visual C++ and MSACCESS for customizationof package to provide reportwriting and integration.
MS Visual Basic 5.0System Architect 3.1Internet Explorer
MS Visual Basic 5.0System Architect 3.1Internet Explorer
Application Software
A description of the software to bepurchased, built, accessed, or somecombination of these techniques.
Package Solution Custom Solution Same as candidate 2.
Method of Data Processing
Generally some combination of: on-line,batch, deferred batch, remote batch, andreal-time.
Client/Server Same as candidate 1. Same as candidate 1.
Output Devices and Implications
A description of output devices thatwould be used, special outputrequirements, (e.g. network, preprintedforms, etc.), and output considerations(e.g., timing constraints).
(2) HP4MV departmentLaser printers(2) HP5SI LAN laserprinters
(2) HP4MV departmentLaser printers(2) HP5SI LAN laserprinters(1) PRINTRONIX bar-codeprinter (includes software &drivers)
Web pages must be designedto VGA resolution. Allinternal screens will bedesigned for SVGAresolution.
Same as candidate 2.
Input Devices and Implications
A description of Input methods to beused, input devices (e.g., keyboard,mouse, etc.), special input requirements,(e.g. new or revised forms from whichdata would be input), and inputconsiderations (e.g., timing of actualinputs).
Keyboard & mouse Apple “Quick Take” digitalcamera and software(15) PSC Quickscan laserbar-code scanners(1) - HP Scanjet 4C FlatbedScannerKeyboard & mouse
Same as candidate 2.
Storage Devices and Implications
Brief description of what data would bestored, what data would be accessedfrom existing stores, what storage mediawould be used, how much storagecapacity would be needed, and howdata would be organized.
MS SQL Server DBMS with100GB arrayed capability.
Same as candidate 1. Same as candidate 1.
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Systems Design and Construction
Feasibility Criteria Wt. Candidate 1 Candidate 2 Candidate 3 Candidate ..
Operational Feasibility
Functionality. A description of to whatdegree the candidate would benefit theorganization and how well the systemwould work.
Political. A description of how wellreceived this solution would be fromboth user management, user, andorganization perspective.
30% Only supports MemberServices requirements andcurrent business processeswould have to be modified totake advantage of softwarefunctionality
Score: 60
Fully supports user requiredfunctionality.
Score: 100
Same as candidate 2.
Score: 100
Technical Feasibility
Technology. An assessment of thematurity, availability (or ability toacquire), and desirability of thecomputer technology needed to supportthis candidate.
Expertise. An assessment to thetechnical expertise needed to develop,operate, and maintain the candidatesystem.
30% Current production release ofPlatinum Plus package isversion 1.0 and has only beenon the market for 6 weeks.Maturity of product is a riskand company charges anadditional monthly fee fortechnical support.
Required to hire or train C++expertise to performmodifications for integrationrequirements.
Score: 50
Although current technicalstaff has only Powerbuilderexperience, the senioranalysts who saw the MSVisual Basic demonstrationand presentation, has agreedthe transition will be simpleand finding experienced VBprogrammers will be easierthan finding Powerbuilderprogrammers and at a muchcheaper cost.
MS Visual Basic 5.0 is amature technology based onversion number.
Score: 95
Although current technicalstaff is comfortable withPowerbuilder, management isconcerned with recentacquisition of Powerbuilderby Sybase Inc.MS SQL Server is a currentcompany standard andcompetes with SYBASE inthe Client/Server DBMSmarket. Because of this wehave no guarantee futureversions of Powerbuilderwill “play well” with ourcurrent version SQL Server.
Score: 60
Economic Feasibility
Cost to develop:
Payback period (discounted):
Net present value:
Detailed calculations:
30%
Approximately $350,000.
Approximately 4.5 years.
Approximately $210,000.
See Attachment A.
Score: 60
Approximately $418,040.
Approximately 3.5 years.
Approximately $306,748.
See Attachment A.
Score: 85
Approximately $400,000.
Approximately 3.3 years.
Approximately $325,500.
See Attachment A.
Score: 90
Schedule Feasibility
An assessment of how long the solutionwill take to design and implement.
10% Less than 3 months.
Score: 95
9-12 months
Score: 80
9 months
Score: 85
Ranking 100% 60.5 92 83.5
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19987
Systems Design and ConstructionINFORMATION SYSTEMS FRAMEWORK
SYSTEM
ANALYSTS
SYSTEM BUILDERS
(components)
SYSTEM DESIGNERS
(specification)
SYSTEM USERS
(requirements)
SYSTEM OWNERS
(scope)
Database
Technology
(and standards)
Database Schema
Data Requirements
Business Subjects
FOCUS ON SYSTEM
DATA
Application Schema
Business Processes
Business Functions
FOCUS ON SYSTEM
PROCESSES
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 Schema
Communication Reqts.
Operating Locations
FOCUS ON SYSTEM
GEOGRAPHY
Procurement
Phase
Definition Phase
Study Phase
REASON
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
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
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
approved
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
Order Form
Help +
Customer
Form
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
CUSTOME
customer_no [Alpha (10)]
customer_name [Alph
customer_rating [Alpha(1)
balance_due [Real
PRODUC
product_no [Alpha(10)
product_name [Alph
unit_of_measure [Alp
unit_price [Real(
quantity_available [Inte
ORDER
order_no [Alpha(12)] I
order_date [Date(mmd
CUSTOMER.custom
ORDER_PRODU
ORDER.order_
PRODUCT.produc
quantity_ordered [Inte
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
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
Survey Phase
Configuration
Phase
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19988
Systems Design and Construction
Research
Technical
Criteria
&
Options
Validate
Vendor
Claims
&
Performance
Evaluate
and
Rank
Vendor
Proposals
Repository
Establish
Integration
Requirements
System
Owners
Design
Approval
Solicit
Proposals
(or quotes)
Award
Contract
&
Debrief
Vendors
Potential
Vendors,
Options &
Tech. Criteria
H/W & S/W
Requirements
Potential
Vendors,
Options, &
Tech. Criteria
RFP or RFQ
and Selection
CriteriaVendor
RFP
or
RFQ
Proposal
and/or
Quotation
Validation
Criteria
Validated
Proposals
Evaluation
Criteria
H/W & S/W
Recommendations
Not Validate Proposals
H/W & S/W
Specifications
Vendor
Contract & Order
or
Debrief of Proposal
H/W & S/W
Specs
Integration
Requirements
H/W & S/W
Recommendation
H/W & S/W
Approval
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19989
Systems Design and ConstructionINFORMATION SYSTEMS FRAMEWORK
SYSTEM
ANALYSTS
SYSTEM BUILDERS
(components)
SYSTEM DESIGNERS
(specification)
SYSTEM USERS
(requirements)
SYSTEM OWNERS
(scope)
Database
Technology
(and standards)
Database Schema
Data Requirements
Business Subjects
FOCUS ON SYSTEM
DATA
Application Schema
Business Processes
Business Functions
FOCUS ON SYSTEM
PROCESSES
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 Schema
Communication Reqts.
Operating Locations
FOCUS ON SYSTEM
GEOGRAPHY
Procurement
Phase
and
Design &
Integration Phase
Definition Phase
Study Phase
REASON
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
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
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
approved
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
Order Form
Help +
Customer
Form
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
CUSTOME
customer_no [Alpha (10)]
customer_name [Alph
customer_rating [Alpha(1)
balance_due [Real
PRODUC
product_no [Alpha(10)
product_name [Alph
unit_of_measure [Alp
unit_price [Real(
quantity_available [Inte
ORDER
order_no [Alpha(12)]
order_date [Date(mmd
CUSTOMER.custom
ORDER_PRODU
ORDER.order_
PRODUCT.produc
quantity_ordered [Inte
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
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
Survey Phase
Configuration
Phase
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199810
Systems Design and Construction
Analyze
and
Distribute
Data
Design
Database(s)Design
Computer
Outputs
and
Inputs
Repository
Present
and
Review
Design
System
Owners
Approval
to
continue
project
Finished
Design
Units
Technical
Design
Statement
Analyze
and
Distribute
Processes
Design
On-line
User
Interfaces
Data
Models
Normalized
Distributed
Data Models
and
Revised
Prodess
ModelsData Model,
Target Solution,
& Process
Models
Distributed
Process
Models
Database
Design Units
Database
Design Specs
I/O
Design
Reqmts.
I/O
Design
Specs
Interface
Design
Reqmts.
Interface
Design Specs
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Application Architecture & Process Design
INFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
INFORMATION
TECHNOLOGY
ARCHITECTURE
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirements)
SYSTEM
OWNERS
(scope)
Database
Architecture
Database Scehma
Data Requirements
Business Subjects
FOCUS ON
SYSTEM
DATA
Application Schema
Business Processes
Business Functions
FOCUS ON
SYSTEM
PROCESSES
Interface Schema
Interface Requirements
System Context
FOCUS ON
SYSTEM
INTERFACES
Processor and
Software Architecture
Interface
Architecture Networking
Architecture
Network Schema
Communication Reqts.
Operating Locations
FOCUS ON
SYSTEM
GEOGRAPHY
Architecture Project
or
Configuration
Implementation
Phase
(deliver the new
system into
operation)
Design/Constructio
n Phases
(design and develop
the system solution)
Definition Phase
(establish and
prioritize business
system requirements)
Study Phase
(establish system
improvement
objectives)
Survey Phase
(establish scope
and project plan)
System
Development
CUSTOME
customer-n
customer-nam
customer-rati
balance-du
PRODUCT
product-n
product-nam
unit-of-measu
unit-price
quantity-avail
ORDER
order-no
order-date
products-order
quantities-orde
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
Produc
Lookup
Request Product Lookup H
Product Lookup Help Comp
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
Check
credit
Validate
customer
Validate
products
Release
order
Customer
Orders
Products
order
custome
numbe
valid ord
order witho
valid
customer
credi
order with
valid produc
approved ord
quantity
in stock
approve
order
rejected ord
price
picking
ticket
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 (1
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
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
St. Louis
Mainframe
Indy AIX Serv
NT Server LA
NT Server N
Communicatio
Controller
PBX
Enternet LAN AIX/Lan
Manager
Ethernet LAN/NT
Ethernet LAN/NT
Client PC Client PC
Client PC Client PC
Firecracker Sales
Database
Decisions
Process
Decisions
Interface
DecisionsNetwork
Decisions
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Application Architecture & Process Design
What is the
client and
operating
system?
Where are
user/syste
m interface
instruction
s
executed?
Where is
the
business
logic
instruction
s
executed?
Where are
database
commands
executed?
The clients are either dumb
(non-programmable) terminals, or
PCs (any OS) that are emulating
dumb terminals using software.
Any system interfaces are either
executed on the server or across
the network on another server.
The user interface (usually
non-graphical) is stored and
executed on the server.
All business logic is programmed
to execute on the server.
Resulting data files may be
transferred to another server
across the network.
All data is stored on the server and
all file and database access and
update commands and instructions
are executed on the server
computer.
Centralized
Computing
The clients are personal
computers or workstations
(sometimes called fat clients)
running Windows 9x, Windows NT,
OS/2, or Macintosh OS.
Any system interfaces are either
executed on the server or across
the network on another server.
All business logic is programmed
to execute on the server.
Resulting data files may be
transferred to another server
across the network.
All data is stored on the server and
all file and database access and
update commands and instructions
are executed on the server
computer.
Distributed Presentation
Computing
The clients are personal
computers or workstations
(sometimes called fat clients)
running Windows 9x, Windows NT,
OS/2, or Macintosh OS.
Any system interfaces are either
executed on the server or across
the network on another server.
The user interface (usually
graphical) is stored and executed
on the client.
All business logic is programmed
to execute on the client using a
PC-based programming language.
All data is stored on the server and
all file and database access and
update commands and instructions
are executed on the server
computer.
A database server is usually
microprocessor-based (e.g., UNIX
or Windows/NT Server) but could
still be a mainframe or
minicomputer.
Distributed Database
Computing
The clients are personal
computers or workstations
(sometimes called fat clients)
running Windows 9x, Windows NT,
OS/2, or Macintosh OS.
Any system interfaces are either
executed on the server or across
the network on another server.
The user interface (usually
graphical) is stored and executed
on the client.
Some business logic may be
programmed to execute on the
client.
Most business logic is programmed
to execute on the server.
Typically. data and business logic
(and possibly other services) are
on separate servers (same OS's as
in previous column).
Distributed Data/Logic
Computing
In addition to fat clients (see
previous column), some clients
may be network computers (also
called NCs or thin clients) that only
execute downloaded programs
User interfaces may be stored and
executed on the client, or
downloaded from the Internet or
intranet for execution on the client.
System interfaces are managed
from the Internet or intranet.
Appropriate business logic may be
downloaded from Inter/intranet
server to execute on the client.
Appropriate business logic is
programmed to execute on the
server.
All data is stored on the server
(possibly multiple servers) and all
file and database access and
update commands and instructions
are executed on the server
computers.
Utilizes data and/or file servers as
in previous two columns, but adds
one or more Internet and intranet
servers.
Internet/Intranet
Computing
What is the
server and
operating
system?
The server is usually a
minicomputer or mainframe,
possibly networked to other
minicomputers or mainframes.
The server is usually a
minicomputer (e.g., OS/400 OS) or
mainframe computer (e.g. MVS,
VM, or UNIX OS).
Wide
Area
Network
Wide
Area
Network
Local
Area
Network
Wide
Area
Network
Local
Area
Network
The user interface (usually
graphical) is stored and executed
on the client.
All data is stored on the server
(possibly multiple servers) and all
file and database access and
update commands and instructions
are executed on the server
computers.
Local
Area
Network
Intranet
or
InternetLocal or
Wide Area
Network
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Application Architecture & Process Design
Data and DB
process on server
All business logic on
the mainframe server
All data on the
mainframe server
Business logic on
application server
User Interface
on the PC Client
Network
Logic & user
interface on PC
Network
Data on DB process
on Server
User interface
on the PC client
Network Network
Some logic on
Intranet ServerData on database
server
Internal user
interface on PC
Network
Secure intranet
provides access
to data, logic,
and interfaces
Distributed Presentation
Distributed Data (2-tier)
Distributed Data & Logic (3-tier)
Internet and Intranet
Some logic on
Internet Server
External user
PC client
Internet Connection
provides access to
interfaces and
some logic
Secure Gateway
to protect applications
and data
Connection
to outside
world
Secure
connection
to database
server
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Application Architecture & Process Design
Account Register
(Quicken File)
Bank
Reconcile account
balances
(Quicken)
Verify balances
and transactions
(You)
Monthly
Statement
(Printed Form)
Beginning and Ending Balance
(Windows Dialog Box)
Cleared
Transactions
(Window Checkboxes)
Reconciliation Report
(Window and/or Printed Report)
Transactions
and
Balances
(Read)
Revised Transactions
(Create, Delete, Update)
Cleared Transactions
(Update)
Creditor
Plan payment of
the bill
(You)
Bill
(Paper Invoice)
Bill
(Electronic Invoice)
Transaction
(Create, Delete, or Update)
Pay a bill
Time to pay a billTransaction Due
(Read)
Schedule a
payment
(Quicken)
Memorized and Scheduled
Transactions
(Quicken File)
Memorized or Scheduled Transaction
(Create, Delete, or Update)
Reusuable
Transaction
Details
(Read)
Paid Transaction
(Update)
Check
(Printed)
Check
(Hand)
Check
(Electronic
Fund Transfer)
Make a deposit or
withdrawal at the
bank
(You)
Record deposit or
withdrawal
Make a
withdrawal
(ATM)
ATM Receipt
(ATM printout)
Teller Receipt
(Printout Form)
Transaction
(Create,
Update)
You
Deposit Slip
(Form)
Withdrawal
(verbal)
You
Customer PIN (bank card)
and
Withdrawal Info (keypad)
Direct
Deposit
Reminder
(read)
This diagram
is intentionally
incomplete and
oversimplified
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
Application Architecture & Process Design
Modeling Application Architecture & Information System Processes
Physical Data Flow Diagrams
Physical Processes:
Process names use the action verb + object clause convention,
however, the name is preceded or followed by an
implementation method. The format is:
• implementation method : action verb + object clause
• action verb + object clause : implementation method
If a logical process is to be implemented partially by people and
partially by software, it must be split into separate physical
processes and appropriate data flows must be added between
the physical processes.
• The name of a physical process to be performed by people, not
software, should indicate who will perform that process.
ID# (opt)
action verb + object
clause
implementation
method
ID# (opt)
implementation
method : action
verb + object
clause
ID# (opt)
action verb +
object clause
(implementation
method)
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Application Architecture & Process Design
Modeling Application Architecture & Information System Processes
Physical Data Flow Diagrams
Physical Data Stores:
Each data store on the logical DFD now represents a data entity
on a normalized entity relationship diagram.
Most physical data stores represent a single file or a single
database or table in the database. Additional physical data
stores may be added to represent temporary files or batches
necessitated by physical processes.
The name of a physical data store uses the following format:
• file or database implementation method : file, database, or table
name
• file, database, or table name : file or database implementation
method
database name
(implementation
method)
implementation
method:
database name
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Database Design
Information
SystemFile File
Information
System
Information
System
Database
(consolidated &
integrated data
from files)
File
File
Information
System
Information
System
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Database DesignINFORMATION 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 Programs
Database Schema
Data Requirements
Business Subjects
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
Implementation
Phase
(translate technical
design into code)
Design Phase
(translate business
requirements into a
technical design)
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-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
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(10
product_name [Alp
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
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
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Database Design
A legacy
file-based
information
system
(built
in-house)
File
FileInformation
System
(built
in-house)
Information
System
(built
in-house)
Operational
Database
File
File
Information System
(built in-house)
A legacy
file-based
information
system
(purchased)
File
File
File
Information
System
(purchased)
Operational
Database
Data
Warehouse
End-User
Tools
End-User
ApplicationsPersonal
DB
Work-Group
Database
Users and Programmers
Users and Programmers
Users and Programmers
Users and Programmers
Users
End-User Work Group
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Database Design
Database Management System (DBMS)
Data
Definition
Language
DDL
Data
Manipulation
Language
DML
Proprietary Data
Manipulation
Language and/or
Report Writers
Host-based
Transaction
Processing
Monitor
(optional)
Internal TP Monitor
(opt)
Stored Data Metadata
Programmers
End Users
Systems Analysts and/or
Database Designers
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
Database Design
sells sold onOrdered Product
Customer Order Productplaces
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Database DesignCustomers TableCustomer Number Customer Name Customer
Balance
…
10112 Luck Star 1455.77
10113 Pemrose 12.14
10114 Hartman 0.00
10117 K-Jack Industries - 20.00
Orders
TableOrder
Number
Customer Number
(foreign key)
…
A633 10112
A634 10114
A635 10112
Ordered Products TableOrder
Number
(foreign
key)
Product Number
(foreign key)
Quantity
Ordered
…
A633 77F02 1
A633 77B12 500
A634 77B13 100
A634 77F01 5
A635 77B12 300
A635 77B15 15
Products TableProduct Number Product Description Quantity
in Stock
…
77B12 Widget 8000
77B13 Widget 0
77B15 Widget 52
77F01 Gadget 20
77F02 Gadget 2
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19987
Database DesignMEMBER ORDER ------------------Key Data--------------------- Order-Number (PK) ----------------Non-Key Data----------------- Order-Creation-Date Order-Automatic-Fill-Date Member Number (FK1)
Member-Name
Member-Address
Shipping-Address Shipping Instructions Club-Name (FK2) Promotion-Number (FK2)
0 { Ordered-Product-Description } n
0 { Ordered-Product-Title } n
1 { Quantity-Ordered } n
1 { Purchased-Unit-Price } n
1 { Extended-Price } n
Order-Sub-Total-Cost Order-Sales-Tax Ship-Via-Method Shipping-Charge Order-Status Prepaid-Amount Method-of-Payment
PRODUCT ------------Key Data---------------- Product-Number (PK1) Universal-Product-Code (PK2) --------Non-Key Data------------- Quantity-in-Stock Product-Type Suggested-Retail-Price Club-Default-Unit-Price Current-Special-Unit-Price Current-Month-Units-Sold Current-Year-Units-Sold Total-Lifetime-Units-Sold
sold
MERCHANDISE -------------Key Data--------------- Product-Number (PK1) Universal-Product-Code (PK1) ---------Non-Key Data------------ Merchandise-Name Merchandise-Description Merchandise-Size Merchasnise-Color Unit-of-Measure
TITLE --------------Key Data-------------- Product-Number (PK1) Universal-Product-Code (PK2) ----------Non-Key Data----------- Title-of-Work Title-Cover Catalog-Description Copyright-Date Entertainment-Category Credit-Value
AUDIO TITLE -------------Key Data--------------- Product-Number (PK1) Universal-Product-Code (PK1) ---------Non-Key Data------------ Artist Audio-CategoryAudio-Sub-CategoryNumber-of-Units-in-Package Audio-Media-Code Content-Advisory-Code
VIDEO TITLE -------------Key Data--------------- Product-Number (PK1) Universal-Product-Code (PK1) ---------Non-Key Data------------ Producer Director Video-CategoryVideo-Sub-CategoryClosed-Captioned Language Running-Time Video-media-Type Video-Encoding Screen-Aspect MPA-Rating-Code
GAME TITLE -------------Key Data--------------- Product-Number (PK1) Universal-Product-Code (PK1) ---------Non-Key Data------------ Manufacturer Game-Category Game-Sub-Category Game-Platform Game-Media-Type Number-of-Players Parent-Advisory-Code
is a
is a
MEMBER ---------------------Key Data---------------------- Member-Number (PK1) ------------------Non-Key Data------------------- Member-Name Member-Status Member-Street-Address Member-Daytime-Phone-Number Date-of-Last-Order Member-Balance-Due Member-Bonus-Balance-Available Member-Credit-Card-Information
1 { Club-Name } n
1 { Agreement-Number } n
1 { Taste Code } n
1 { Media Preference } n
1 { Date-Enrolled } n
1 { Expiration-Date } n
1 { Number-of-Credits-Required } n
1 { Number of Credits-Earned } n
placed
CLUB ------------------Key Data---------------------- Club-Name (PK) --------------Non-Key Data-------------------- Club-Description Club-Charter-Date
1 { Agreement-Number } n
1 { Agreement-Active-Date } n
1 { Agreement-Expiration-Date } n
1 { Obligation-Period } n
1 { Required-Number-of-Credits } n
1 { Bonus-Credits-After-Obligation } n
PROMOTION ---------Key Data------------- Club-Name (PK1) Promotion-Number (PK1) -------Non-Key Data-------- Product-Number (FK1) Promotion-Release-Date Promotion-Status Promotion-Type Automatic-Fill-Delay
enrolls in
sponsors
generates
features
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19988
Database Design
MEMBER ORDER (unnormalized) ------------------KeyData--------------------- Order-Number (PK) ---------------Non-Key Data----------------- Order-Creation-Date Order-Automatic-Fill-Date Member Number (FK1)
Member-Name
Member-Address
Shipping-Address Shipping Instructions Club-Name (FK2) Promotion-Number (FK2)
0 { Ordered-Product-Description } n
0 { Ordered-Product-Title } n
1 { Quantity-Ordered } n
1 { Purchased-Unit-Price } n
1 { Extended-Price } n
Order-Sub-Total-Cost Order-Sales-Tax Ship-Via-Method Shipping-Charge Order-Status Prepaid-Amount Method-of-Payment
PRODUCT (1NF) ------------Key Data---------------- Product-Number (PK1) Universal-Product-Code (PK2) --------Non-Key Data------------- Quantity-in-Stock Product-Type Suggested-Retail-Price Club-Default-Unit-Price Current-Special-Unit-Price Current-Month-Units-Sold Current-Year-Units-Sold Total-Lifetime-Units-Sold
MEMBER ORDERED PRODUCT (1NF) ---------------Key Data------------------ Member-Number (PK1) (FK) Product-Number (PK1) (FK) -------------Non-Key Data------------- Ordered-Product-Description Ordered-Product-Title Quantity-Ordered Purchased-Unit-Price Extended-Price
CORRECTION
sold as
MEMBER ORDER (1NF) ------------------Key Data--------------------- Order-Number (PK) ----------------Non-Key Data----------------- Order-Creation-Date Order-Automatic-Fill-Date Member Number (FK1) Member-Name Member-Address Shipping-Address Shipping Instructions Club-Name (FK2) Order-Sub-Total-Cost Order-Sales-Tax Ship-Via-Method Shipping-Charge Order-Status Prepaid-Amount
sells
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19989
Database Design
CLUB (unnormalized) ------------------Key Data---------------------- Club-Name (PK) --------------Non-Key Data-------------------- Club-Description Club-Charter-Date
1 { Agreement-Number } n
1 { Agreement-Active-Date } n
1 { Agreement-Expiration-Date } n
1 { Obligation-Period } n
1 { Required-Number-of-Credits } n
1 { Bonus-Credits-After-Obligation } n
CLUB (1NF) ------------------Key Data---------------------- Club-Name (PK) --------------Non-Key Data-------------------- Club-Description Club-Charter-Date
CORRECTION
AGREEMENT (1NF) ----------Key Data----------------- Club-Name (PK1) (FK) Agreement-Number (PK1) --------Non-Key Data------------- Agreement-Active-Date Agreement-Expiration-Date Obligation-Period Required-Number-of-Credits Bonus-Credits-After-Obligation
establishes
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199810
Database Design
MEMBER (unnormalized) ---------------------Key Data---------------------- Member-Number (PK1) ------------------Non-Key Data------------------- Member-Name Member-Status Member-Address Member-Daytime-Phone-Number Date-of-Last-Order Member-Balance-Due Member-Bonus-Balance-Available Member-Credit-Card-Information
1 { Club-Name } n
1 { Agreement-Number } n
1 { Taste Code } n
1 { Media Preference } n
1 { Date-Enrolled } n
1 { Expiration-Date } n
1 { Number-of-Credits-Required } n
1 { Number of Credits-Earned } n
MEMBER (1NF) ---------------------Key Data---------------------- Member-Number (PK1) ------------------Non-Key Data------------------- Member-Name Member-Status Member-Street-Address Member-Daytime-Phone-Number Date-of-Last-Order Member-Balance-Due Member-Bonus-Balance-Available Member-Credit-Card-Information
CLUB MEMBERSHIP (1NF) -------------Key Data-------------- Member-Number (PK1) (FK) Club-Name (PK1) (FK) Agreement-Number (PK1) (FK) ---------Non-Key Data----------- Taste Code Media Preference Date-Enrolled Expiration-Date Number-of-Credits-Required Number of Credits-Earned
CLUB (1NF) ------------------Key Data---------------------- Club-Name (PK) --------------Non-Key Data-------------------- Club-Description Club-Charter-Date
AGREEMENT (1NF) ----------Key Data----------------- Club-Name (PK1) (FK) Agreement-Number (PK1) --------Non-Key Data------------- Agreement-Active-Date Agreement-Expiration-Date Obligation-Period Required-Number-of-Credits Bonus-Credits-After-Obligation
enrolls in
binds
establishes
sponsors
CORRECTION
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199811
Database Design
PRODUCT (2NF) ------------Key Data---------------- Product-Number (PK1) Universal-Product-Code (PK2) --------Non-Key Data------------- Quantity-in-Stock Product-Type Suggested-Retail-Price Club-Default-Unit-Price Current-Special-Unit-Price Current-Month-Units-Sold Current-Year-Units-Sold Total-Lifetime-Units-Sold
MEMBER ORDERED PRODUCT (1NF) ---------------Key Data------------------ Member-Number (PK1) (FK) Product-Number (PK1) (FK) -------------Non-Key Data-------------
Ordered-Product-Description
Ordered-Product-Title
Quantity-Ordered Purchased-Unit-Price Extended-Price
MEMBER ORDERED PRODUCT (2NF) ---------------Key Data------------------ Member-Number (PK1) (FK) Product-Number (PK1) (FK) -------------Non-Key Data------------- Quantity-Ordered Purchased-Unit-Price Extended-Price
MERCHANDISE (2NF) -------------Key Data--------------- Product-Number (PK1) Universal-Product-Code (PK1) ---------Non-Key Data------------ Merchandise-Name
Merchandise-Description
Merchandise-Size Merchasnise-Color Unit-of-Measure
TITLE (2NF) --------------Key Data-------------- Product-Number (PK1) Universal-Product-Code (PK2) ----------Non-Key Data----------- Title-of-Work
Title-Cover Catalog-Description Copyright-Date Entertainment-Category Credit-Value
is a
sold as
CORRECTION
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199812
Database Design
MEMBER ORDERED PRODUCT (2NF) ---------------Key Data------------------ Member-Number (PK1) (FK) Product-Number (PK1) (FK) -------------Non-Key Data------------- Quantity-Ordered Purchased-Unit-Price Extended-Price
MEMBER ORDERED PRODUCT (3NF) ---------------Key Data------------------ Member-Number (PK1) (FK) Product-Number (PK1) (FK) -------------Non-Key Data------------- Quantity-Ordered Purchased-Unit-Price Extended-Price
CORRECTION
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199813
Database DesignMEMBER (3NF) ---------------------Key Data---------------------- Member-Number (PK1) ------------------Non-Key Data-------------------
Member-Name
Member-Status Member-Street-Address
Member-Daytime-Phone-Number Date-of-Last-Order Member-Balance-Due Member-Bonus-Balance-Available Member-Credit-Card-Information
MEMBER ORDER (2NF) ------------------Key Data--------------------- Order-Number (PK) ----------------Non-Key Data----------------- Order-Creation-Date Order-Automatic-Fill-Date Member Number (FK1)
Member-Name
Member-Address
Shipping-Address Shipping Instructions Club-Name (FK2) Order-Sub-Total-Cost Order-Sales-Tax Ship-Via-Method Shipping-Charge Order-Status Prepaid-Amount
MEMBER ORDER (3NF) ------------------Key Data--------------------- Order-Number (PK) ----------------Non-Key Data----------------- Order-Creation-Date Order-Automatic-Fill-Date Member Number (FK1) Member-Name Member-Address Shipping-Address Shipping Instructions Club-Name (FK2) Order-Sub-Total-Cost Order-Sales-Tax Ship-Via-Method Shipping-Charge Order-Status Prepaid-Amount
CORRECTION
placed
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Input Design and Prototyping
xxxxx
xxxxxxxxxx xx-xx-xx xxxx
xxxx xxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxx xxxxxxxxxxxxxxx xx x.xx xxx.xx next linexxxx xxxxxxxxxxxxxxx xx x.xx xxx.xx next linexxxx xxxxxxxxxxxxxxx xx x.xx xxx.xx next linexxxx xxxxxxxxxxxxxxx xx x.xx xxx.xx next linexxxx xxxxxxxxxxxxxxx xx x.xx xxx.xx next linexxxx xxxxxxxxxxxxxxx xx x.xx xxx.xx stop
xxxxxxxxxx xxxxxxxxxx xxxxxxxxxx
xxxxx xxxxxxxxxx xx.xxx xx.xxx stopxx-xxx-xxx
Good
Bad
(a)
(b)
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Input Design and Prototyping
MODULUS 11
The following procedure is used to assign a check digit to a key field:
STEP 1: Determine the size of the key field in digits.
2 4 1 3 5 = 5 digits
STEP 2: Number each digit location from right or left beginning with the number “2.”
2 4 1 3 5
6 5 4 3 2
STEP 3: Multiply each digit in the key field by its assigned location number.
2 X 6 = 12
4 X 5 = 20
1 X 4 = 4
3 X 3 = 9
5 X 2 = 10
STEP 4: Sum the products from step 3.
12 + 20 + 4 + 9 + 10 = 55
STEP 5: Divide the sum from step 4 by 11.
55/11 = 5 Remainder 0
STEP 6: If the remainder is less than 10, append the remainder digit to the key field. If
the remainder is equal to 10, append the character “X” to the key field.
2 4 1 3 5 0
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Input Design and Prototyping
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Input Design and Prototyping
1 4
2
3
5
6
7
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
Input Design and Prototyping
2
5
1 3
4
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Input Design and Prototyping
(a)(b)
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19987
Input Design and Prototyping
(a) (b)
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19988
Input Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Output Design and PrototypingSoundStage Entertainment ClubFax 317-494-0999
The following number must appear on all related correspondence,
shipping papers, and invoices:
P.O. NUMBER: 712812
To: Ship To:SoundStage Entertainment Club SoundStage Entertainment Club2625 Darwin Drive Shipping/Receiving StationIndianapolis, IN 45213 Building A
2630 Darwin DriveIndianapolis, IN 45213
P.O. DATE REQUISITIONER SHIP VIA F.O.B. POINT TERMS
5-3-96 ldb ups N30
QTY DESCRIPTION UNIT PRICE TOTAL
10000 Powder - VHS 19.99 199,900.00
5000 Now and Then - VHS 15.95 79,750.00
2500 Pulp Fiction Soundtrack - CD 7.99 19,975.00
450 U2 on Tour - T-shirt 3.49 1,570.50
Subtotal 301,195.50
Tax 15,059.77
Total 316,255.27
1. Please send two copies of your invoice.
2. Enter this order in accordance with the prices, terms, delivery method, andspecifications listed above.
3. Please notify us immediately if you are unable to ship as specified.
Madge Worthy 5-4-96Authorized by Date
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Output Design and Prototyping
Invoice No. 301231
Name Carlina Smith Date 7/21/97
Address 3019 Duroc Drive Order No. 346910
City Little Rock State AR ZIP 42653Phone 502-430-4545 Payment Amt
Detach and return top portion with payment
Qty Description Unit Price TOTAL
1 Star Wars - Empire Strikes Back VHS $19.99 $19.991 Eric Clapton Unplugged CD $13.99 $13.99
1 Alladin VHS $17.95 $17.95
SubTotal $51.93
Shipping & Handling $7.00 Cash Taxes $2.95
Check
Credit Card TOTAL $61.88
Name
CC # Office Use OnlyExpires
RETURN TOP PORTION WITH PAYMENT
SoundStageEntertainment Club2630 Darwin Drive - Bldg B
Indianapolis, IN 45213
INVOICE
Payment Details
Customer
Please return top portion invoice with payment. Make checks payable to:
SoundStage Entertainment Club.
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Output Design and Prototyping
Page 1
SOUNDSTAGE ENTERTAINMENT CLUB
Products Ordered on 6-31-1996
PO Number Product Number Product Type Quantity In Stock Quantity On Order
112312 102774 Merchandise 273 450
202653 Title 75 325
393752 Title 251 125
112313 109833 Merchandise 0 200
111340 Title 46 150
231045 Title 225 1,500
253967 Title 332 850
112314 287904 Title 0 2,000
699034 Merchandise 0 300
836785 Merchandise 35 175
984523 Title 213 250
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Output Design and Prototyping
Page 1
SOUNDSTAGE ENTERTAINMENT CLUB
Product Sales Summary as of 7-2-1996
Product Type Product Category Current Month’s Unit Sales Current Year Unit Sales
Merchandise Clothing 784 4,312
Media Accessory 541 2,079
Total:
Title Audio 3,815 20,175
Game Title 1,247 5,671
Video Title 2,136 9,032
Total:
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
Output Design and Prototyping
Page 1
SOUNDSTAGE ENTERTAINMENT CLUB
Delinquent Member Accounts as of 7-9-1996
(90 Days Overdue)
Number Name Area Code Phone Extension Balance Due
137842 Joe Dunn 317 490-0012 111 29.43
142314 Bob Fischer 501 282-7996 43.97
157723 Mary Slatter 218 993-9091 56.99
209438 Harold Martin 823 231-8355 33.17
237121 Kevin Ditmano 655 219-0988 99.23
384563 Rick Carlina 501 454-6311 11.23
421134 Barb Kitts 393 789-5412 231 23.66
476688 Kenny Bum 443 234-8845 123.77
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Output Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19987
Output Design and Prototyping
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19988
Output Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19989
Output Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199810
Output Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199811
Output Design and Prototyping
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199812
Output Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199813
Output Design and Prototyping
5
4
2
1
3
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199814
Output Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199815
Output Design and Prototyping
2
31
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
User Interface Design and Prototyping
Menu Bar
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
User Interface Design and Prototyping
Pull-down Menu
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
User Interface Design and Prototyping
Dialogue Box
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
User Interface Design and Prototyping
Cascading Menu
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
User Interface Design and Prototyping
Cascading Menu
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
User Interface Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19987
User Interface Design and Prototyping
Iconic Menu
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19988
User Interface Design and Prototyping
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19989
User Interface Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199810
User Interface Design and Prototyping
Question
Answer
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199811
User Interface Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199812
User Interface Design and Prototyping
1
1
1
2
2 2
3
4
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199813
User Interface Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199814
User Interface Design and Prototyping
1
3
2
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199815
User Interface Design and Prototyping
1
2
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199816
User Interface Design and Prototyping
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199817
User Interface Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199818
User Interface Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199819
User Interface Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199820
User Interface Design and Prototyping
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199821
User Interface Design and Prototyping
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Software DesignINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
(facilitation)
SYSTEM
BUILDERS
(com ponents)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirem ents)
SYSTEM
OW NERS
(scope)
FOCUS ON
SYSTEM
DATA
Application Schema
Chapters 11, 16
Business Processes
Chapters 5, 7
FOCUS ON
SYSTEM
PROCESSES
FOCUS ON
SYSTEM
INTERFACES
Software
(and Hardware)
Technology
Interface
Technology
FOCUS ON
SYSTEM
GEOGRAPHY
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
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
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Software Design
MODULEB
MODULEA
LIBRARYMODULE
A
MODULEG
MODULEF
MODULEE
MODULED
MODULEC
SYSTEMMODULE
DATA A
DATA A DATA B
DATA B
DATA C
DATA B
FLAG BFLAG B
FLAG A
DATA B
AND C/DDATA D
1
23
4
5 6
7
6
5
4
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Software Design
BOUNDARYA
BOUNDARYB
BOUNDARYB
BOUNDARYA
P
NEWPROCESS
B
P
NEWPROCESS
A
P
PROCESS A
P
PROCESS B
P
PROCESS B(DO NOTEXPAND)
P
PROCESS A(DO NOTEXPAND)
P
PROCESSWITH MANY
INPUTS &OUTPUTS
D DATA STORE B
D DATA STORE A
D DATA STORE B
D DATA STORE C
D DATA STORE C
D DATA STORE A
EXPANDED (ORREPLACED BY)
DATA B
DATA A
DATA B
DATA C
SUM OF DATA AAND DATA C
SCREENEDDATA B
FINAL TOTALSOF DATA A & C
RELEASED DATA D
REVISED XYZ STATUS
REVISED XYZ STATUS
RELEASED DATA D
FINAL TOTALSOF DATA A & C
SCREENEDDATA B
SUM OF DATA AAND DATA C
DATA C
DATA A
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Software Design
P
PROCESS X
P
PROCESS X
P
DELETED DETAILS
P
READA DETAILS
P
UPDATEC DETAILS
BOUNDARYA
BOUNDARYA
P
ADDNEW B
DETAILS
D DATA STORE A
D DATA STORE A
D DATA STORE D
D DATA STORE B
D DATA STORE D
D DATA STORE C
D DATA STORE C
D DATA STORE B
B DETAILS
B DETAILS
DELETED D DETAILS
UPDATED C DETAILS
NEW B DETAILS
C DETAILS TOBE UPDATED
D DETAILSTO BE DELETED
NEW B DETAILSTO BE ADDED
A DETAILS FORPROCESSING
A DETAILS
DELETED D DETAILS
UPDATED C DETAILS
NEW B DETAILS
A DETAILS
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
Software Design
P
OUTPUTFUNCTION
C
P
INPUTFUNCTION
B
P
INPUTFUNCTION
D
P
OUTPUTFUNCTION
A
P
INPUTFUNCTION
C
P
OUTPUTFUNCTION
B
P
TRANSFORMFUNCTION
A
P
TRANSFORMFUNCTION B
P
INPUTFUNCTION
A
BOUNDARYB
BOUNDARYA
D DATA STORE D
D DATA STORE B
D DATA STORE E
M
L
K
J
I
H
G
F
E
D
C
B
A
Afferent
CentralTransform
Efferent
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Software Design
P
OUTPUTFUNCTION
C
P
TRANSFORMFUNCTION
A
P
TRANSFORMFUNCTION B
P
INPUTFUNCTION
B
P
INPUTFUNCTION
D
P
OUTPUTFUNCTION
A
P
INPUTFUNCTION
C
P
OUTPUTFUNCTION
B
P
INPUTFUNCTION
A
BOUNDARYB
BOUNDARYA
D DATA STORE D
D DATA STORE B
D DATA STORE E
M
L
K
J
I
H
G
F
E
D
C
B
A
START FOR
TRACING
INPUT B
START FOR
TRACING
INPUT D
START FOR
TRACING
INPUT A
FINISH POINTS
FOR TRACING
INPUTS A & B
FINISH POINT
FOR TRACING
INPUT D
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19987
Software Design
INPUTFUNCTION
A
INPUTFUNCTION
D
INPUTFUNCTION
B
INPUTFUNCTION
C
BOSS
GF
E
C
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19988
Software Design
TRANSFORMFUNCTION
A
TRANSFORMFUNCTION
B
INPUTFUNCTION
A
INPUTFUNCTION
D
INPUTFUNCTION
B
INPUTFUNCTION
C
BOSS
CENTRALTRANSFORMCONTROLLER
E & F
J & I
G & H
E, F, & G
J
G
I
F
E
C
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19989
Software Design
TRANSFORMFUNCTION
A
TRANSFORMFUNCTION
B
INPUTFUNCTION
A
INPUTFUNCTION
D
INPUTFUNCTION
B
OUTPUTFUNCTION
A
INPUTFUNCTION
C
OUTPUTFUNCTION
C
BOSS
CENTRALTRANSFORMCONTROLLER
OUTPUTFUNCTION
B
E & F
J & I
J
G & H
E, F, & GI
J
G
I
F
K
E
C
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199810
Software Design
P
READ
PRODUCT
CONTAINED
ON ORDER
P
READ
MEMBER
P
CALCULATE
ORDER
VOLUMES
P
WRITE
REPORT
ACTIVITY
DETAILS
P
READ
MEMBER
ORDER
P
GET
ORDER
DETAILS
P
FORMAT
MEMBER
ACTIVITY
DETAILS
D PRODUCT ON AN
ORDER
D ACTIVITY REPORT FILE
D MEMBER
D MEMBER ORDER
MEMBER
ORDER
ACTIVITY
FORMATED
ACTIVITY
DETAILS
UNFORMATTED
ACTIVITY
DETAILS
MEMBER
ORDER
DETAILS
CUSTOMER
AND ORDER
DETAILS
PRODUCT
ON AN
ORDER
DETAILS
MEMBER DETAILS
PRODUCT
ON AN ORDER
DETAILS
MEMBER
DETAILS
MEMBER
ORDER
DETAILS
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199811
Software DesignMAINTAIN MEMBER
GET ORDER DETAILS
CALCULATE ORDER
VOLUMES
FORMAT MEMBER ACTIVITYDETAILS
WRITE REPORT ACTIVITYDETAILS
READ MEMBER
READ MEMBER ORDER
READ PRODUCT
CONTAINED ON ORDER
CUSTOMER
AND ORDER
DETAILS
CUSTOMER
AND ORDER
DETAILS
UNFORMATED
ACTIVITY
DETAILS
UNFORMATED
ACTIVITY
DETAILS
FORMATED
ACTIVITY
DETAILS
FORMATED
ACTIVITY
DETAILS
MEMBER
DETAILS
MEMBER
NUMBER
PRODUCT
ON AN
ORDER
DETAILSORDER
NUMBER
MEMBER
ORDER
DETAILS
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199812
Software Design
P
INPUTFUNCTION
A
P
PROCESSTRANSACTION
TYPE B
P
TRANSACTIONCENTER
A
P
PROCESSTRANSACTION
TYPE A
BOUNDARYA
P
PROCESSTRANSACTION
TYPE C
P
DISPLAYRESULT
BOUNDARYB
RESULT
TRANSACTION
VALIDTRANSACTION
TYPE CRESULT
TYPE BRESULT
TYPE ARESULT
TRANSACTIONTYPE C
TRANSACTIONTYPE B
TRANSACTIONTYPE A
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199813
Software Design
TRANSACTIONCENTER
PROCESSTRANSACTION
TYPE C
PROCESSTRANSACTION
TYPE B
PROCESSTRANSACTION
TYPE A
DISPLAYRESULT
INPUTFUNCTION
A
BOSS
VALIDTRANSACTION
TRANSACTION
TYPE A, B, ORC RESULT
TYPE ARESULT
TRANSACTIONTYPE A
TYPE BRESULT
TYPE A, B, ORC RESULT
TRANSACTIONTYPE C
TYPE CRESULT
TRANSACTIONTYPE B
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 199814
Software DesignINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
(facilitation)
SYSTEM
BUILDERS
(com ponents)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requirem ents)
SYSTEM
OW NERS
(scope)
Database Scehma
Chapter 12
FOCUS ON
SYSTEM
DATA
Application Schema
Chapters 11, 16
FOCUS ON
SYSTEM
PROCESSES
Interface Schema
Chapters 11, 13, 14, 15
FOCUS ON
SYSTEM
INTERFACES
Network Schema
Chapter 11
FOCUS ON
SYSTEM
GEOGRAPHY
Order Form
Help +
Customer
Form
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
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
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
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
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Object-Oriented Design
Generate OrderError Report
Send OrderRejection Notice
Calculate Subtotal& Sales Tax
Submit PropostionOrder
Generate WarehousePicking Ticket
uses uses
extends extends
Extension Use Cases
Abstract Use Cases
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Object-Oriented Design
INTERFACE OBJECTS CONTROLLER OBJECTS ENTITY OBJECTS
Member Services Main Window Order Processor MEMBER
Order Processing Window Ticket Generator PRODUCT
Picking Ticket Printer MEMBER ORDER
MEMBER ORDERED PRODUCT
1 2 3
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19983
Object-Oriented Design
MEMBER
Member NumberMember NameMember StatusMember Street AddressMember P.O. Box NumberMember CityMember StateMember Zip CpdeMember Daytime Phone NumberDate Of Last OrderMember Balance DueMember Bonus Balance
persistent
MEMBER ORDERED PRODUCT
Quantity OrderedQuantity ShippedQuantity BackorderedPurchased Unit PriceExtended CostCredits EarnedOrdered Product Status
persistent
MEMBER ORDER
Order NumberOrder Creation DateOrder Automatic Fill DateOrder Sub-total CostOrder Sales TaxOrder Status
persistent
PRODUCT
Product NumberQuantity AvailableProduct NameSuggested Unit Price
persistent
1+
sells
sold as
placed
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19984
Object-Oriented Design
PROMOTIONORDER
SPECIALIST
WAREHOUSE
CLUB MEMBER
Picking Ticket Printer
Order ProcessingWindow
PRODUCT ONORDER
MEMBER ORDER
Main Window
Ticket Generator
MEMBER
PRODUCT
Order Processor
1 2
3
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19985
Object-Oriented Design
System
Border
Customer selects “process promotion
order” option
Do until no more member orders
Customer enters member number
If member number valid
Get current promtion order header
Do until no more ordered products
Get ordered product information
Get product information
Display order
Else
Display error message
Clear Message
Endif
Main
Window
Order
Processer
Order
Processing
Window
StartStart order
process
Request member number
isMember
Member Member
Order
reportOrder
Member
Ordered
Product
Product
Validate member
number
Display order
Display error message
reportProduct
reportOrderedProduct
Clear
New member number
-
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19986
Object-Oriented Design
MEMBER
Member NumberMember NameMember StatusMember Street AddressMember P.O. Box NumberMember CityMember StateMember Zip CpdeMember Daytime Phone NumberDate Of Last OrderMember Balance DueMember Bonus Balance
isMemberreportMemberreportStatus
persistent
MEMBER ORDERED PRODUCT
Quantity OrderedQuantity ShippedQuantity BackorderedPurchased Unit PriceExtended CostCredits EarnedOrdered Product Status
setStatuscalculateQuantityBackorderedcalculateExtendedCostreportOrderedProduct
persistent
MEMBER ORDER
Order NumberOrder Creation DateOrder Automatic Fill DateOrder Sub-total CostOrder Sales TaxOrder Status
reportOrdersetStatusCalculateSalesTaxcalculateSubtotal
persistent
PRODUCT
Product NumberQuantity AvailableProduct NameSuggested Unit Price
reportProductcalculateQuantityAvailable
persistent
1+
sells
sold as
placed
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19981
Systems Implementation
Delivery
Phase
Construction
Phase
Repository
Documentation
Documentation
Operational System
System
Owners/Users
Production
Information
System
Approval to Continue Project
Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 19982
Systems ImplementationINFORMATION SYSTEMS FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
SYSTEM
BUILDERS
(components)
SYSTEM
DESIGNERS
(specification)
SYSTEM
USERS
(requiremen