Sei sulla pagina 1di 32

Systems Development

14-1

Concept of
Systems Development Life Cycle
(SDLC)
Definition of SDLC
Stages of SDLC
Traditional versus modern SDLCs

14-2

Systems Development Life Cycle


(SDLC)
An SDLC represents a set of general
categories that show the major steps, over
time, of an information systems
development project.

14-3

An Eight-Stage SDLC

Project initiation
Feasibility study
Logical analysis and design
Acquisition and development
Implementation
Operation
Post-audit evaluation
Maintenance
14-4

SDLC

14-5

Project Initiation
Functional Manager
Formal planning process
IS organization

14-6

Feasibility Studies

Technology
Economics
Organizational factors
Legal, ethical, and other constraints

14-7

Logical Analysis and Design

Determine the systems functions


How will it accomplish those functions
Logical design
Physical design / technical design

14-8

Logical Design
Generic IS functions: input, output, and
storage
Modeling tools: DFDs, ERDs
User involvement

14-9

Implementation

Parallel conversion
Direct cutover
Pilot conversion
Phased

14-10

Traditional versus Modern SDLC

Minimal overhead
Flexibility and responsiveness
Concurrent tasks
Focused analysis

14-11

Methods for Complex or Quickly


Needed Systems

Prototyping
Rapid Application Development (RAD)
Object-Oriented Development (OOD)
End-User Development (EUD)

14-12

Prototyping
The prototyping approach to systems
development is, in many ways, the very
opposite of an old-style SDLC. The focus
of prototyping is to develop something
quickly from the users initial set of
requirements. Then refine and extend it
based on the users requirements, which are
identified by using the prototype.
14-13

Rapid Application Development


Rapid Application Development (RAD)
methodologies and tools have capabilities to
meet the demands of the new environment.

14-14

Components and Capabilities of


RAD

GUI development environment


Reusable components
Code generator
Programming language

14-15

Object-Oriented Development
Benefits
Reduces complexity of systems
development
Systems are quicker and easier to build and
maintain
Improves productivity
Objects may be reused

14-16

Object-Oriented Development
Benefits
Systems are more flexible
Allows analysis to think in real world terms
Ideal for Web development

14-17

End-User Development
Trends

Increasingly powerful desktop hardware


Declining hardware costs
Increasingly diverse software capabilities
Increasingly computer-literate population
Backlog of IS projects

14-18

End-User Development
Trends

Development speed
Business orientation
Small applications
Control
Apparent cost savings

14-19

14-20

EUD Problems
Additional spending

Hardware
Software
Training
Support

Neglecting other duties

14-21

EUD Problems
Limited managerial technical skills
Documentation
Security

14-22

EUD Solutions
Auditing EUD programs
Dividing computing responsibilities

14-23

Third Party Software


Application software packages
Outsourcing
Enterprise software

14-24

Acquiring New Systems


Desirable outcomes and implementation
issues
Managerial considerations

14-25

Desirable Outcomes and


Implementation Issues

On-time
On-budget
Full functionality
User acceptance
Favorable costs-to-benefits ratio

14-26

Desirable Outcomes and


Implementation Issues

Low maintenance
Scalability
Integration with other systems
Minimal negative cross impacts
Reusability

14-27

Management Considerations

Traditional SDLC methodology


Prototyping
Rapid Application Development (RAD)
Object-Oriented Development (OOD)
End-User Development (EUD)
Purchasing or outsourcing
14-28

System Development Issues

Internet and intranet applications


JAVA
CASE tools
IS-9000
Project planning

14-29

Managerial Issues
Importance
Building interorganizational and
international information systems
Ethical and legal issues
User involvement
Traditional approaches vs. prototyping
14-30

Managerial Issues

Tool use by developers


Quality assurance vs. schedules
Behavior problems
Perpetual development

14-31

Copyright 1999 John Wiley & Sons, Incorporated. All rights


reserved. Reproduction or translation of this work beyond that
permitted in Section 117 of the 1976 United States Copyright Act
without the express written permission of the copyright owner in
unlawful. Request for further information should be addressed to
the Permissions Department, John Wiley & Son, Inc. Adopters of
the textbook are granted permission to make back-up copies for
his/her own use only, to make copies for distribution to student of
the course the textbook is used in, and to modify this material to
best suit their instructional needs. Under no circumstances can
copies be made for resale. The publisher assumes no
responsibility for errors, omissions, or damages, caused by the use
of these programs or from the use of the information contained
herein.
14-32

Potrebbero piacerti anche