The Fun Filled World of

Methodologies

By Eric DeLisle & Sasan Rastegarlari

Presentation Overview
 What is a Methodology?
 Who uses Methodologies?
 What are Methodologies used for?
 Several types of Methodologies
 Waterfall
 SDLC
 RAD
 Agile
 Object-Oriented
What is a Methodology?
 Multi-step approach to systems
development
 Influences the quality of the Final
product
 Comprehensive
 Consistent method with the
Organizations management style.
Who Uses Methodologies?
 Most Organizations and Firms Today
 IBM, Microsoft, Monsanto, NASA, AT&T,
Drury Hotels, Edward Jones, A.B.
 Majority of Organizations and Firms
use a specific type of methodology
that is tailored to their needs.
What Are Methodologies Used For?
 Systems Development
 Guidelines or References
 Step by Step process
 Leads to final product
 Analysis
 Information
 Gathered and Used to help the
development process
History of Methodologies
 Present
Computer-based Info Systems began
day Info Systems

in Internet, Intranet, and Extranets.
the 1950’s.
 1980’s introduced microcomputers
 CASE tools development
 System developers went from builders to
integrators.
 1990’s brought systems integration.
 Visual programming environments.
Popular Methodologies
 The Waterfall Methodology
 The SDLC Methodology
 The RAD Methodology
 Agile Methodologies
 eXtreme Programming (XP)
 Object-Oriented Methodologies
 Rational Unified Process (RUP)
Waterfall Methodology
Waterfall Methodology
 Overview
 Introduced by W.W. Royce in 1970
 It was later redesigned using a more
iterative process, unfortunately this way
was ignored resulting in the current
Waterfall methodology
 Most System Analysts do not like the
Waterfall Method
 Each phase must be completed perfectly
 There is no overlap or moving backward
in phases
Waterfall Methodology
 Phases
 Testing:
 Requirements: The requirements
After integration the systemof is
the system
tested are collected
and bugs and set in
are removed.
stone.
 Installation & Maintenance: The final
 installation
Design: A of blueprint is made
the system for the
is done at this
programmers
phase. using
Users are the previously
trained and the system
collected
is requirements.
maintained by the system designers.
 Implementation: System components
are designed by coders and integrated
together.
Waterfall Methodology
 Cons
Pros

 Impossible
Time spenttoearly
knowin exactly what is
production can
needed in each phase
save a company of the software
hundreds of
process
thousandsbefore some time is spent in the
of dollars.
 phase following it.
More emphasis is placed on
 Requirments are locked in too early
documentation than any other
leaving no room for user feedback and
methods.
modification.
 Too much emphasis on deadlines rather
than user requirments.
Systems Development Life Cycle (SDLC)

Planning
Maintenance First phase
Fifth phase

Analysis
Second
phase
Implementation
Fourth phase

Design
Third phase
Systems Development Life Cycle (SDLC)
 Overview
 Traditional Methodology
 Used to develop, maintain, and replace info
systems
 Common method for systems development
 Contains several phases
 Planning, Analysis, Design, Implementation,
Maintenance.
Systems Development Life Cycle (SDLC)
 Phases

 Implementation
Planning
 System
 Identification phase specs turned over to
and Written
 programmers
Needs are examined as a whole
 
Analysis
Implementation process
 Studies current
Coding, procedures
testing, installationand Info Systems
 Sub phase - Requirement determination
 Maintenance
 Design
 Systems are in operation
 Convert alternative solutions
 Specific problems or changes are made
 Inputs and Outputs
 Reports, databases, computer processes
Rapid Application Development (RAD)

Requirements
Requirements Planning
Planning

User
User Design
Design

Construction
Construction

Cutover
Cutover
Rapid Application Development (RAD)
 Overview
 Methodology used to decrease time in
development process.
 Efficient and Cheaper
 Allows systems developers and end
users work together from the beginning.
 Becoming a more legitimate way of
developing Web Based systems.
 E-business applications
 VisualAge Generator, Java, WebSphere Stuido
etc.
Rapid Application Development (RAD)
 Phases
 RAD phases are similar to SDLC
 Shortened and Combined – simplifies the
development process.
 Systems are analyzed in isolation to other systems.
 Eliminates time consuming activities.
 Coordinating with existing standards and
systems during the Design and Development
phases
 RAD focuses on Prototyping similar to JAD
 Prototyping becomes the basis for the new system
eXtreme Programming (XP)
eXtreme Programming (XP)
 Overview
 An Agile Methodology invented about 8
years ago by Kent Beck
 Successful because it stresses customer
satisfaction and software creation on
demand
 Responsive to changing customer
requirements even late in the life cycle
 Improves software projects in four essential
ways; communication, simplicity, feedback,
and courage.
eXtreme Programming (XP)
 Phases

 Coding:
Planning: Very iterative
User stories process usually
are collected
done withcustomer.
from the teams of 2 programmers
Feedback at a
is given to
time. Customer
the customer to feedback
help betteris understand
constantly
used during the coding process.
the requirements.

 Testing:
Designing: Consistently
Primary focusdoneisafter each
on keeping
portion of code
the design is created.
simple. ConstantIf bugs are
found the code is
communication reworked
with and retested.
the customer is
 Releases:
used to design andare
These redesign
usuallyover
doneandin
over again
small until Final
portions. they product
have reached
is thenan
acceptable tested
thoroughly solution.upon release.
eXtreme Programming (XP)
 Cons
 Pros
 Really
 Code will be developed,
there tested,
are no cons to and
XP besides
implemented
the fact thatinto the system
it may not bewithin a few hours
applicable to
after it has been written.
every project.
 XP is governed by very simple rules and
practices.
 Pair programming used in XP produces more and
better communication among developers, higher
levels of productivity, higher quality code, and
reinforcement of the other practices in XP, such
as the code-and-test discipline.
Rational Unified Process (RUP)

Simple Diagram
Rational Unified Process (RUP)
Detailed Diagram
Rational Unified Process (RUP)
 Overview

 An
The Object-Oriented
RUP uses six key iterative software
principles in its
developmentprocess
development process.created by the
Rational
4.
1. Adapt Software
6. Demonstrate
the process:
Focus continuously Corporation
value iteratively:
Decide (a right
on the
on quality: division
Projects
Encouragesare
size
delivered
of IBM since
project
quality andin2003)
checks an through
incremental
budget around
for the andnot
1998. iterative
organization.
testing only at
2. fashion.
 RUP the end
Balance Thisduring
but encourages
stakeholder the feedback
creation
priorities:
is like an online mentor that of from
the
Determines
stakeholders
projects.
business goalsand
andallows projectsneeds.
stakeholder to adjust
provides guidelines,
to changing templates, and
requirements.
3. Collaborate
examples for across
all teams:
aspects With
and a broad
stages of
5. Elevate the level
variety development. of abstraction: Motivates
of stakeholders, all voices need to
program
the reuse of software or Framework already
be heard. Everyone within the project
created.
shares information, opinions, and ideas.
Rational Unified Process (RUP)
 Phases

 Construction:
Inception: AnalystsThe software
define the is actually
scope,
coded,
determinetested,
the and documented.
feasibility At the
of the project,
end of this phase
understand a beta versionand
user requirements, of the
project
prepareisareleased
softwarethat should have
development plan.
 operational
Elaboration: capabilities.
Analysts detail user
 Transition:
requirementsThe andsystem
develop a baseline
is deployed,
architecture.
problems are In this phase
corrected, and anthe
executable
users
demonstration
are trained andof the critical
supported. pieces will
Once
be developed.
acceptable criteria are met the product
can then be scheduled for final release.
Rational Unified Process (RUP)

 Cons
Pros
 Establishes a better understanding and
 If the users ofchannel
communication RUP dobetween
not understand
business
engineering
that RUP isand softwareframework,
a process engineering. they
 Provides pre-configured process templates for
may perceive it as a weighty and
small, medium and large projects, which can be
expensive process.
used for easier adoption.
 Allows for constant feedback from the business
 Requires RUP process expert.
an stakeholders.
as well as the
 Encourages the use of reusable assets such as
 May not be applicable to all situations.
software pattern, 4GL or Framework which in
turn prevents software engineers from having to
custom make software.
Conclusion
 Who uses Methodologies?
 What are Methodologies used for?
 A brief history of Methodologies?
 Popular methodologies in the Systems
Design Process.
 Waterfall
 Systems Development Life Cycle (SDLC)
 Rapid Application Development (RAD)
 eXtreme Programming (XP)
 Rational Unifide Process (RUP)
Thank You
You May Now
Applause!