Beruflich Dokumente
Kultur Dokumente
2
System Development Life Cycle
(SDLC)
Problem Definition
Requirement
Maintenance Analysis
System
Development
3
System Feasibility Study
Analysis Requirement Analysis
Logical Design
System
Design Physical Design
Coding &Testing
System
Development Transition
4
Why we need a life cycle in systems
development?
5
Provides a more Guides the systems
Facilitate project efficient / effective
review development
system
6
Waterfall Cycle
Problem Definition
Requirement Analysis
System Design
Implementation
System Testing
Maintenance
7
Definition the Problem
Provides a broad statement of user
Project requirements in users terms, or what
goals the users expect the system to do
Producing a high-level
description of the system
9
System Design
• Produces a design
specification for the
new system
Analysts
Design
10
System Design
• Things to be done:
• Select equipment
• Specify new programs
or changes to existing
programs
• Specify new database
or changes to existing
database
• produce detailed
procedures
Design
11
System Development
Individual system components are built and
tested
Data and tools are used to build the system
User interfaces are developed and tried by
users
Database is initialized with data
Analysts System 12
System testing
¾ Test and evaluate results, and
¾ the system ready to be
delivered to the user/client.
13
Maintenance
¾ Eliminate errors in the system
during its working life.
¾ Fixing any bugs and problem found
by users
¾ Tune the system to any variations in
its working environment
14
Problems with waterfall cycle
9 It has rigid design and inflexible procedure
9 It is top-down procedure
9 One phase must be completed before the
next phase starts, and
9 No phase can be repeated.
15
Criticisms fall into the following
categories:
9Real projects rarely follow the sequential
flow that the model proposes.
9At the beginning of most projects there is
often a great deal of uncertainty about
requirements and goals, and it is therefore
difficult for customers to identify these
criteria on a detailed level. The model does
not accommodate this natural uncertainty
very well.
16
Criticisms fall into the following
categories: cont…
17
Modified waterfall model
Problem Definition
Requirement Analysis
System Design
Implementation
System Testing
Maintenance
18
Spiral Model
• Requirement analysis
• Design prototype
• Develop and integrate
• Acceptances and testing
20
Life Cycle vs Methodology
21
Life Cycle vs Methodology
22
Life Cycle vs Methodology
• A system development methodology is
a very formal and precise system
development process that defines
– a set of activities,
– methods,
– best practices,
– deliverables,
– and automated tools
23
A System Development methodology
(Process) has some general principles.
P1: Get the owner and User Involved
System
Involved Development
24
P2: Use a problem-solving approach.
# Study and understand the problem and its
context
# Preliminary investigation
# Problem analysis
# Requirement analysis
# Decision analysis
# Design
# Construction
# Implementation 26
P4: Establish standards.
# Documentation # Quality
27
P5:Justify systems as capital investments.
# Cost-effectiveness
IS
cost
# Risk management
28
P6:Don’t be afraid to cancel or revise
scope.
longer feasible
# If project scope is to be
increased, reevaluate and adjust
the cost and schedule
29
P7:Divide and conquer.
#We divide a system into
subsystem and components
30
P8: Design systems for growth and change.
# Correcting simple mistakes
31
Development Process
Major
• Methodology Components
• Modeling Methods or Techniques
• Tools
32
Methodology
• Provides the framework
• Has a predefined set of steps
• Ensures that systems are built in the most
effective way
33
Methodology
Tools
Most Effective
Way of
Building
Methods
34
Modeling Methods
A set of techniques used to implement a
Methodology
• Data Flow Diagrams
• Entity Relationship Diagrams
• Structure Charts etc.
Different Views
of the System
35
System Development Methodologies
Supported by Modeling Methods or
Techniques
• Techniques used to implement the Methodology.
• Provides the descriptions of the business system
requirements from various view points.
36
Tools
• Software systems
• Assists analysts and designer to build
information systems.
37
System Development Methodologies.
Supported by Tools.
They will not replace Systems Analysts.
38
Methodology
Eg .Rational Unified Process
us
es
es
us