Transcript No Slide Title

S
Y
S
T
E
M
S
D
E
S
I
G
N
A
N
A
L
Y
S
I
S
Chapter 1
Introduction
Jerry Post
Copyright © 1997
1
S
Purpose of This Class
Y
S  Systems development and programming is hard.
T  Many failures in the past and recently.
E
 Over budget.
M
 Over schedule.
S
 Total failure/not completed.
D
E
S
I
G
N
 Teamwork
 Large projects require teams of MIS workers.
 Need to split project into pieces, coordinate workers.
 Need to share and communicate.
 Need to control and evaluate progress.
 Design characteristics, tips, and tricks.
 Planning and scheduling.
 Tools.
2
S
Y
S
T
E
M
S
D
E
S
I
G
N
Runaway Projects

Technical measures




2 - 5 times over budget
2 - 5 times behind
schedule
Missing technical
objectives
Design problems



Duplication of efforts
Incompatibilities
User/designer conflicts
$
1994
1996
1998
3
S
Project Success and Failure
Y
 Reasons for Success
S  Reasons for Failure
 Lack of user input
 User Involvement
T
 Incomplete requirements
 Executive management
E
support
 Changing requirements and
M
specifications
 Clear requirements
S
 Lack of executive support
 Proper planning
 Lack of technical skills
 Realistic expectations
D
E
S
I
G
N
4
S
Development Trends
Y
 New tools
S  Development problems.
 Don’t meet deadlines.
 Project management
T
 Go over budget.
 Groupware for sharing
E
 Can’t control large projects.
 CASE: Computer-aided
M
software engineering
 Programmers are
S
expensive.
 Database management
D
E
S
I
G
N
 You can buy really good
software today.
 Transaction processing.
 Common applications.
 How long does software
last?
 Outdated? Functions and
needs change.
 Depends on hardware.
systems
 Powerful languages (Visual
Basic)
 The Internet!
 User Interface!
 A new way of looking at
development: object-oriented
design
5
S
Business Decisions
Y
S  Information is a valuable resource.
T  Information systems are used to
make business decisions.
E
 Operations
M
 Tactics
S
Strategic
 Strategy
D
E
S
I
G
N
 Information Systems





Transaction Processing
Process Control
Decision Support Systems
Expert Systems
Enterprise Information Systems
Mgt.
Tactical
Management
Business Operations
 Sharing information
 Group Decision Support
 Groupware tools
6
S
The Role of the Analyst
Y
S  Analyze and Design Systems
 Identify problems, opportunities,
T
objectives.
E
 Analyze information flows.
M
 Design computerized systems to
S
solve problems.
D
E
S
I
G
N




Problem solving.
Communication.
Change agent.
Control, planning, and structure.
7
S
Y
S
T
E
M
S
D
E
S
I
G
N
Systems Development Life Cycle
Feasibility &
Planning
Goals & plans
Systems
Analysis
Proposal
Problems &
Improvements
Business requirements
Systems
Design
Technical Design
Systems
Implementation
New System
Existing System
problems
revisions problems
revisions
Systems Maintenance: Incremental changes
8
S
Design Stages
Y
 Physical Design
S  Initiation
 Scope
 Table definitions
T
 Feasibility
 Application development
E
 Cost & Time estimates
 Data storage
M
 Security
S  Requirements Analysis
 User Views & Needs
D
E
S
I
G
N
 Forms
 Reports
 Processes & Events
 Objects & Attributes
 Conceptual Design
 Models
 Data flow diagram
 Entity Relationships
 Objects
 Procedures
 Implementation




Training
Purchases
Data conversion
Installation
 Evaluation & Review
 User feedback
9
S
SDLC Strengths and Weaknesses
Y
 Disadvantages
S  Advantages
 Control & targets
 Increased costs
T
 Formality
 Increased time
E
 Financial controls
 Hard for DSS
M
 User input
 Requires definitions up front
S
D
E
S
I
G
N
 Documentation
 Testing
 Ease of maintenance
 Rigid
10
S
Computer Assisted Software Engineering
Y
 CASE tool possibilities
 Case complications
S
 Personal productivity
 Expensive
T
 Diagrams
 No standards
E
 Store & Search
 Complex software, learning
 Team productivity
M
 Team must follow methodology.
 Sharing up-to-date changes
S
 CASE Levels
D
E
S
I
G
N
 One shared source of data
 Communication
 Development
 Reverse engineering
 Automated programming
 Maintenance
 Complete records for future
 Diagrams and context
 Reverse engineering
 Upper: front-end
 Lower: back-end
 CASE tool examples
 IEF
 Oracle
 Designer 2000
 Developer 2000
 Rational Rose
11