System Life Cycle

System Life Cycle

Main Menu 1 of 38
System Life Cycle

Objective

To understand various activities involved

in system life cycle and different life
cycle models

Main Menu 2 of 38
System Life Cycle

Scope
 Activities involved in life cycle model
 Different life cycle models
• Waterfall Model
• Prototyping
• Object Oriented
• Dynamic System Development Model
 Comparing different models

Main Menu 3 of 38
System Life Cycle

Activities in System Life Cycle

Start

Preliminary
If new additions are to be Investigation
introduced in the system

Analysis
Stop Implementation
and maintenance

Design
Testing

Development/
coding

Main Menu 4 of 38
System Life Cycle

Activities in System Life Cycle

 Preliminary Investigation
• Identification of problem
• Listing down of possible solutions
• Feasibility Study
• Recommendations
 Analysis
• It is the detailed study of various operations
performed by the system

Main Menu 5 of 38
System Life Cycle

Activities in System Life Cycle

 Design
• Structure or design for the proposed system is
finalized.These includes files, databases, inputs,
outputs, and screens.
 Development
• System is built using design specification
 Testing
• System is tested for its accuracy

Main Menu 6 of 38
System Life Cycle

Activities in System Life Cycle

 Implementation and Maintenance
• Implementation is putting the system on users’
site for operation
• Possible changes leading to changes during the
implementation are:
• change in the policies of organization or
• change in user’s requirements,
• For this maintenance is required.

Main Menu 7 of 38
System Life Cycle

Life Cycle Models

 Waterfall Model
 Prototyping
 Object oriented
 Dynamic System Development Method
(DSDM)

Main Menu 8 of 38
System Life Cycle

Waterfall Model
System Engg.

Analysis

Design

Coding

Testing

Maintenance

Main Menu 9 of 38
System Life Cycle

Prototyping
 Steps:
• Identify the user’s information and operating
requirements.
• Based upon these, build a working prototype of
the proposed system.
• Let the customer evaluate the prototype. If there
are changes suggested, incorporate them in the
prototype.
• Repeat the process unless the system meets full
user requirements

Main Menu 10 of 38
System Life Cycle

Prototyping
Start
Requirement Quick Design Building
gathering Prototype

Stop
Engineer Product Refining Customer
Prototype evaluation

Prototype Model

Main Menu 11 of 38
System Life Cycle

Object Oriented Model

 This model uses object oriented techniques
during different system development phases
(e.g. analysis, design, implementation)
 Everything is viewed as Objects.
 Objects can be any distinguishable thing.
 It can be person, place, thing, or some
concept.

Main Menu 12 of 38
System Life Cycle

Object Oriented Process

 The system to be developed is observed and
analyzed and the requirements are defined as
in any other method of system development.
 Then the objects in the required system are
identified.
 Relationships between objects are identified

Main Menu 13 of 38
System Life Cycle

Object Oriented Process

 The basic steps of system designing using
Object Modeling
• System Analysis
• System Design
• Object Design
• Implementation

Main Menu 14 of 38
System Life Cycle

O O Modeling - System Analysis

 Developer interacts with the user of the
system to find their requirements
 Study of the system is also done to understand
the functioning
 Analyst prepares a model of the desired
system showing its possible objects
 This model shows the functionality of the
system. It doesn’t show implementation
details.
Main Menu 15 of 38
System Life Cycle

O O Modeling - System Design

 Architecture of the desired system is decided
 The system is organized as a set of
subsystems interacting with each other
 The stress lies on the objects comprising the
system

Main Menu 16 of 38
System Life Cycle

O O Modeling - Object Design

 The details of the system analysis and system
design are implemented.
 The objects identified in the system design
phase are designed.

Main Menu 17 of 38
System Life Cycle

O O Modeling - Implementation
 The class objects and the interrelationships of
these classes are coded using programming
language decided upon.
 The databases are made and the complete
system is given a functional shape.

Main Menu 18 of 38
System Life Cycle

Basic Object Models

 models used by analyst to analyze and depict
objects in a system:
• Object Model
• Dynamic Model
• Functional Model

Main Menu 19 of 38
System Life Cycle

Basic Object Models

 Object Model
• describes the objects in a system and their
interrelationships
• Observes all the objects as static
• Does not pay any attention to their dynamic
nature.

Main Menu 20 of 38
System Life Cycle

Basic Object Models

 Dynamic Model
• depicts the dynamic aspects of the system
• Portrays the changes occurring in the states of various
objects with the events that might occur in the system.
 Functional Model
• basically describes the data transformations of the
system
• Describes the flow of data and the changes that occur
to the data throughout the system

Main Menu 21 of 38
System Life Cycle

DSDM- Dynamic System Development Model

 Dynamic approach towards system
development
 It is a Rapid Application Development
method
 Uses incremental prototyping.
 Is independent of tools
• As it can be used with both structured analysis
and design approach or object-oriented approach.

Main Menu 22 of 38
System Life Cycle

DSDM
 Is particularly useful in situations where
• System is to be developed in short time span
• requirements cannot be frozen at the start of the
application building.

Main Menu 23 of 38
System Life Cycle

DSDM
 DSDM is five phase life cycle
• Feasibility
• Business Study
• Functional Model Iteration
• Design and Build Iteration
• Implementation

Main Menu 24 of 38
System Life Cycle

DSDM - Feasibility Study

 Problem is defined
 Technical feasibility of the desired
application is verified
 Application’s suitability for Rapid
Application Development (RAD) approach is
checked

Main Menu 25 of 38
System Life Cycle

DSDM - Business Study

 Overall business study of the desired system
is done
 The business requirements and information
requirements out of the system are identified
 The basic architectural framework of the
desired system is prepared

Main Menu 26 of 38
System Life Cycle

DSDM-Functional Model Iteration

 Prototype for the system is built iteratively
 Prototype is improved through
• demonstration to the user
• taking the feedback and
• incorporating the changes.
 Cycle is repeated generally twice or thrice
until a part of functional model is agreed upon

Main Menu 27 of 38
System Life Cycle

DSDM-Design and Build Iteration

 This phase stresses upon ensuring that the
prototypes are satisfactorily and properly
engineered to suit their operational
environment
 Software components designed during the
Functional modeling are further refined till
they achieve a satisfactory standard.
 The product of this phase is a tested system
ready for implementation.

Main Menu 28 of 38
System Life Cycle

DSDM - Implementation
 Users are trained
 The system is actually put into the operational
environment.

Main Menu 29 of 38
System Life Cycle

DSDM – System Life Cycle

Feasi bilit y

Busi ness
St udy

Agr ee pl an I mpl e ment

Cr eat e Revi e w
Func. Functi onal Identify Busi ness
Mo del func Tr ai n
Pr ot o. I mpl e ment ati on Us ers
It erati on Pr ot o
Revi e w Pr ot ot ype Us er appr oval & gui deli nes

Identify desi gn prot ot ype

Agr ee Revi se
Desi gn & desi gn
pl an
buil d iterati on
pr ot o
Cr eat e desi gn prot ot ype

Main Menu 30 of 38
System Life Cycle

Comparing different models

 Waterfall Model
 Limitations
• Real projects rarely follow sequential flow.
Iterations are always required.
• Requirements may not be clearly defined in the
beginning phase.
• Customer would have no idea of the working
program until the end.
• Product delivery takes much time.

Main Menu 31 of 38
System Life Cycle

Prototyping
 Limitations
• Because of quick design, there can be
compromise on quality.
 Advantages:
• Reduces risk of uncertainty
• Allows early stoppage of unsuccessful projects.
• User interaction and involvement is more.
• Less chances of error during system design.

Main Menu 32 of 38
System Life Cycle

DSDM Model
 Advantages:
• Quality of the product is improved due to
• Active user participation throughout the life of the
project
• Iterative nature of development
• DSDM ensures rapid deliveries
• Reduced project costs due to advantages
mentioned above

Main Menu 33 of 38
System Life Cycle

Object Oriented Method

 Advantages
• Easier to produce and understand designs – as it
closely represents the problem domain
• Allows changes more easily – as the objects in the
system are immune to requirement changes
• Encourages re-use - new applications can use the
existing modules
• Reduced development cost and cycle time.
• Is more natural
• provides nice structure for thinking and
abstracting and leads to modular design.
Main Menu 34 of 38
System Life Cycle

Summary
 The system’s development life cycle consists
of following 5 phases:
• Analysis
• Design
• Coding
• Testing
• Maintenance

Main Menu 35 of 38
System Life Cycle

Summary
 Various life cycles models are available in the
industry.
• Traditional(Waterfall)
• Prototype
• Object-Oriented
• Dynamic systems development method

Main Menu 36 of 38
System Life Cycle

Summary
 Waterfall Model is a sequential model where
each stage can only start after the previous
stage has finished.
 Prototype is an iterative model where
enhancements are made on the prototype of
the system.
 Object Oriented Model uses object oriented
techniques during different stages of
development
Main Menu 37 of 38
System Life Cycle

Summary
 DSDM combines RAD with incremental
model of system development.
 Each model has its own limitations and
advantages. These should be taken into
consideration while deciding for a
methodology.

Main Menu 38 of 38