Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Introduction
SYSTEMS DESIGN
Documentation
Configuration
Phase
Documentation
Technology
Repository
Requirements
Procurement
Phase
Documentation
Technology
Design Integration
Requirements Requirements
Design
&
Integration
Phase to the
construction
phase
Prototyping
JAD
RAD
Subscriber's Acceptance
name decision
Standing and Acceptance
time account decision
closed
Reviewed
Standing and application
1.2.1 time account 1.2.3
closed 1.2.2
Get past Record
Determine
member account reviewed
acceptance
standing application
1.2.3.1 1.2.3.2
Past Member Reject Accept
applicant applicant
Rejected New
application member
details
Rejected
Members
applications
Prototyping
A prototype, according to Webster's dictionary, is ``an original or
model on which something is patterned'' and/or ``a first full-scale
and usually functional form of a new type or design of a
construction (as an airplane).''
Engineers build prototypes of engines, machines, automobiles, and
the like, prior to building the actual products.
Prototyping allows engineers to isolate problems in both
requirements and designs.
The prototyping approach is an iterative process involving a close
working relationship between the designer and the users.
Prototyping
The prototyping approach has several advantages.
Prototyping encourages and requires active end-user
participation.
Iteration and change are a natural consequence of systems
development -- that is, end-users tend to change their minds.
It has often been said that end-users don't fully know their
requirements until they see them implemented.
Prototypes are an active, not passive, model that end-users can
see, touch, feel, and experience.
An approved prototype is a working equivalent to a paper
design specification, with one exception -- errors can be
detected much earlier.
Prepared by Kevin C. Dittman for
Systems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley Copyright Irwin/McGraw-Hill 1998
11
Systems Design and Construction
Strategies For System Design
Prototyping
The prototyping approach has several advantages. (continued)
Prototyping can increase creativity because it allows for
quicker user feedback which can lead to better solutions.
Prototyping accelerates several phases of the life cycle,
possibly bypassing the programmer.
Prototyping
The prototyping approach has several disadvantages.
Prototyping encourages a return to the ``code, implement, and
repair'' life cycle that used to dominate information systems.
Prototyping does not negate the need for the survey and study
phases.
You cannot completely substitute any prototype for a paper
specification.
There are numerous design issues not addressed by prototyping.
Prototyping
The prototyping approach has several disadvantages. (continued)
Prototyping can reduce creativity in designs.
Prototyping
Prototypes can be quickly developed using many of the 4GLs and
object-oriented programming languages available today.
Prototypes can be built for simple outputs, computer dialogues,
key functions, entire subsystems, or even the entire system.
Each prototype system is reviewed by end-users and
management, who make recommendations about requirements,
methods, and formats.
The prototype is then corrected, enhanced, or refined to reflect
the new requirements.
The revision and review process continues until the prototype is
accepted.
FAST
The FAST methodology does not impose a single design technique
on system developers.
FAST integrates all of the popular design strategies we’ve
discussed: structured design (via process modeling), information
engineering (via data modeling), prototyping (via rapid application
development), joint application development (for all methods), and
rapid application development.
Progressive FAST developers can use object-oriented design in
conjunction with object technology for prototyping to fully exploit
the object paradigm.
Configuration Phase
The purpose of the configuration phase is to identify candidate
solutions, analyze those candidate solutions, and recommend a
target system that will be designed and implemented.
The fundamental objectives of the configuration phase are:
To identify and research alternative manual and computer-
based solutions to support our target information system.
To evaluate the feasibility of alternative solutions and
recommend the best overall alternative solution.
The configuration phase marks the first point in the systems
development process that we have placed emphasis on how the
new system might operate.
FOCUS ON
SYSTEM
FOCUS ON
SYSTEM
FOCUS ON
SYSTEM
FOCUS ON
SYSTEM
REASON
DATA PROCESSES INTERFACES GEOGRAPHY Methodology
Survey Phase
R e c e iv a ble
D a t a ba s e
Marketing
Customers order zero,
C re dit
Study Phase
Data Requirements Business Processes Interface Requirements Communication Reqts.
rejected order
St.
PRODUCT EDI
order Louis
catalog Products
credit Cust changes Catalog
CUSTOMER product-no Customers
Check HQ
credit
customer-no product-name Fi recracker Sales
order-no valid
customer
T order-date picking
service
A
N Definition Phase
A
L
Y
S
T
SYSTEM
S
DESIGNERS
(specification)
SYSTEM
BUILDERS
(components)
Interface
Software Technology
Networking
(and Hardware)
Database Telchnology
Technology (and standards)
Technology
(and standards)
(and standards) Configuration
(and standards)
Phase
Approval
System to 1
Owners continue Define
project Various
Candidate H/W & S/W
Outside
Solutions Specifications
Sources
Technology
Requirements
Payback period (discounted): Approximately 4.5 years. Approximately 3.5 years. Approximately 3.3 years.
• project plan
• size estimates
• candidate solutions
• completed feasibility analysis
I. Introduction
A. Purpose of the report
B. Background of the project leading to this report
C. Scope of the project
D. Structure of the report
II. Tools and techniques used
A. Solution generated
B. Feasibility analysis (cost/benefit)
III. Information systems requirements
IV. Alternative solutions and feasibility analysis
V. Recommendations
VI. Appendices
FOCUS ON
SYSTEM
FOCUS ON
SYSTEM
FOCUS ON
SYSTEM
FOCUS ON
SYSTEM
REASON
DATA PROCESSES INTERFACES GEOGRAPHY Methodology
Survey Phase
R e c e iv a ble
D a t a ba s e
Marketing
Customers order zero,
C re dit
Study Phase
Data Requirements Business Processes Interface Requirements Communication Reqts.
rejected order
St.
PRODUCT EDI
order Louis
catalog Products
credit Cust changes Catalog
CUSTOMER product-no Customers
Check HQ
credit
customer-no product-name Fi recracker Sales
order-no valid
customer
T order-date picking
service
A
N Definition Phase
A
L
Database Schema Application Schema Interface Schema Network Schema
Y
S Or der
P r ocessing
P r ogr am
New Cust ome r
Cust omer
Form
PRODUCT
T CUSTOMER product_no [Alpha(10)] INDEX
Logon Order Accept ed
SYSTEM customer_no [Alpha (10)] INDEX product_name [Alpha(32)] Change Communicat ions St . Louis
S customer_name [Alpha(32)]
Initiation
Routine
P r ocess
an Order
S hutdown
Routine
of Cont roller Mainframe
DESIGNERS unit_of_measure [Alpha(2)]
customer_rating [Alpha(1)] INDEX
unit_price [Real(3,2)]
New Order Address
Get an V alidate File an Order Help Complet e Order Form First Order
Or der an Order Or der PBX NT Server N Y
(specification) Request
Et hernet LA N/NT
Request Orde r Help
Product Et hernet LA N/NT
Check Check Check Release
ORDER_PRODUCT Lookup
ORDER Custom er
Cr edit
P r oduct
Data
Cr edit
Data
an
Or der
order_no [Alpha(12)] INDEX ORDER.order_no Help +
Request Product Lookup Help
order_date [Date(mmddyyyy) PRODUCT.product_no Indy AIX Serve r Client PC Client PC
Procurement
Manager
Phase
SYSTEM
BUILDERS
(components)
Interface
Software Technology
Networking
(and Hardware)
Database Telchnology
Technology (and standards)
Technology
(and standards)
(and standards) Configuration
(and standards)
Phase
Research
Technical
System Design Criteria Solicit
Owners Approval & Proposals
RFP
Options (or quotes)
Potential or
Vendors, RFQ
Potential Options, &
Vendors, Tech. Criteria
H/W & S/W H/W & S/W Options &
Approval Recommendation Tech. Criteria
RFP or RFQ
H/W & S/W and Selection
Requirements Criteria Vendor
Integration Proposal
Establish Requirements Validate and/or
Integration Vendor Quotation
Requirements Repository Validation Claims
Criteria &
H/W & S/W Performance
Specs
• The request for quotations is used when you have already decided
on the specific product, but that product can be acquired from
several distributors.
– Its primary intent is to solicit specific configurations, prices,
maintenance agreements, conditions regarding changes made
by buyers, and servicing.
I. Introduction
A. Background
B. Brief summary of needs
C. Explanation of RFP document
D. Call for action on part of vendor
II. Standards and instructions
A. Schedule of events leading to contract
B. Ground rules that will govern selection decision
1. Who may talk with whom and when
2. Who pays for what
3. Required format for a proposal
4. Demonstration expectations
5. Contractual expectations
6. References expected
7. Documentation expectations
III. Requirements and features
A. Hardware
1. Mandatory requirements, features, and criteria
2. Essential requirements, features, and criteria
3. Desirable requirements, features, and criteria
B. Software
1. Mandatory requirements, features, and criteria
2. Essential requirements, features, and criteria
3. Desirable requirements, features, and criteria
C. Service
1. Mandatory requirements
2. Essential requirements
3. Desirable requirements
IV. Technical questionnaires
V. Conclusion
Report writing.
Developing questionnaires.
Verbal presentations.
FOCUS ON
SYSTEM
FOCUS ON
SYSTEM
FOCUS ON
SYSTEM
FOCUS ON
SYSTEM
REASON
DATA PROCESSES INTERFACES GEOGRAPHY Methodology
Survey Phase
R e c e iv a ble
D a t a ba s e
Marketing
Customers order zero,
C re dit
Study Phase
Data Requirements Business Processes Interface Requirements Communication Reqts.
rejected order
St.
PRODUCT EDI
order Louis
catalog Products
credit Cust changes Catalog
CUSTOMER product-no Customers
Check HQ
credit
customer-no product-name Fi recracker Sales
order-no valid
customer
T order-date picking
service
A
N Definition Phase
A
L
Database Schema Application Schema Interface Schema Network Schema
Y
S Or der
P r ocessing
P r ogr am
New Cust ome r
Cust omer
Form
PRODUCT
T CUSTOMER product_no [Alpha(10)] INDEX
Logon Order Accept ed
SYSTEM customer_no [Alpha (10)] INDEX product_name [Alpha(32)] Change Communicat ions St . Louis
S customer_name [Alpha(32)]
Initiation
Routine
P r ocess
an Order
S hutdown
Routine
of Cont roller Mainframe
DESIGNERS unit_of_measure [Alpha(2)]
customer_rating [Alpha(1)] INDEX
unit_price [Real(3,2)]
New Order Address
Get an V alidate File an Order Help Complet e Order Form First Order
Or der an Order Or der PBX NT Server N Y
(specification) Request
Et hernet LA N/NT
Request Orde r Help
Product Et hernet LA N/NT
Check Check Check Release
ORDER_PRODUCT Lookup
ORDER Custom er P r oduct Cr edit an
Procurement
Cr edit Data Data Or der
order_no [Alpha(12)] INDEX ORDER.order_no Help +
Request Product Lookup Help
order_date [Date(mmddyyyy) PRODUCT.product_no Indy AIX Serve r Client PC Client PC
Phase
Manager
and
Design &
Integration Phase
SYSTEM
BUILDERS
(components)
Interface
Software Technology
Networking
(and Hardware)
Database Telchnology
Technology (and standards)
Technology
(and standards)
(and standards) Configuration
(and standards)
Phase
Technical
Design Normalized
Statement Distributed
Data Data Models
Models and
Revised
Present
and Prodess Data Model, Analyze
Models Target Solution, and
Review
Design & Process Distribute
Finished Models Processes
Design
Units Distributed
Process
Repository Models
Interface
Design Specs
Database
Interface
Design Units
Design Design I/O I/O
On-line Reqmts. Design Design Database
User Specs Reqmts. Design Specs
Interfaces Design
Database(s)
Design
Computer
Outputs
and
Inputs
Process Modeling.
Event Analysis.
Process Modeling.
Event Analysis.
Deliverables (outputs)
The principle deliverable of this is the database design
specification(s).
Applicable Techniques
Database Design
Prerequisites (Inputs)
The key inputs to this activity are finished design units.
Deliverables (outputs)
The principle deliverable of this activity is the technical design
statement.
Report writing.
Verbal presentations.
Project Management.
Summary
Introduction
What is System Design?
Strategies For System Design
Fast System Analysis Methods
The Configuration Phase of Systems Design
The Procurement Phase of Systems Design
The Design and Integration Phase of Systems
Design