Chapter 7.

Systems Development and

Implementation
Key Topics

SDLC
The Waterfall Method
Prototyping
Rapid Applications Development
Joint Applications Development
Agile Software Development
Object-Oriented Analysis and Design
RUP
SCRUM

Chapter 7. Systems Development and

Implementation
Why do we need to know this process?

Chapter 7. Systems Development and

Implementation
Why do we need to know this process?

Chapter 7. Systems Development and

Implementation
Why do we need to know this process?

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation Waterfall method

Chapter 7. Systems Development and

Implementation Waterfall method

http://en.wikipedia.org/wiki/Waterfall_model

Chapter 7. Systems Development and

Implementation Waterfall method

DOJ= Dept of Justice

Advantages and Disadvantages of SDLC

Advantages and Disadvantages of SDLC

When to use SDLC

When to use SDLC

Prototyping

Prototyping

When to use Prototyping

Rapid Application Development (RAD)

Rapid Application Development (RAD)

When to use RAD:

Prototyping

Agile Software Development

Agile Software Development

Agile Software Development is a group of software development

methodologies based on iterative and incremental development, where
requirements and solutions evolve through collaboration between selforganizing, cross-functional teams.

Agile Software Development

http://en.wikipedia.org/wiki/Agile_software_development

Agile Software Development

Goals of Agile Software Development:

Customer satisfaction by rapid delivery of useful software

Welcome changing requirements, even late in development
Working software is delivered frequently (weeks rather than months)
Working software is the principal measure of progress
Sustainable development, able to maintain a constant pace
Close, daily co-operation between business people and developers
Face-to-face conversation is the best form of communication (co-location)
Projects are built around motivated individuals, who should be trusted
Continuous attention to technical excellence and good design
Simplicity
Self-organizing teams
Regular adaptation to changing circumstances
http://en.wikipedia.org/wiki/Agile_software_development

When to use Agile Software Development

Joint Application Development (JAD)

Joint Application Development (JAD)

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

When to use JAD

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Chapter 7. Systems Development and

Implementation

Rational Unified Process (RUP)

The Rational Unified Process (RUP) is originally developed by Rational

Software, which was acquired by IBM in February 2003.
The RUP has four phases:
Inception Phase
Stakeholder concurrence on scope definition and cost/schedule estimates.
Requirements understanding as evidenced by the fidelity of the primary use
cases.
Credibility of the cost/schedule estimates, priorities, risks, and development
process.
Establishing a baseline by which to compare actual expenditures versus
planned expenditures.
http://en.wikipedia.org/wiki/IBM_Rational_Unified_Process

Rational Unified Process (RUP)

Elaboration Phase
A use-case model in which the use-cases and the actors have been identified
An executable architecture that realizes architecturally significant use cases.
Business case and risk list which are revised.
A development plan for the overall project.
Prototypes that demonstrably mitigate each identified technical risk.
Construction Phase
The primary objective is to build the software system. In this phase, the main
focus is on the development of components and other features of the system.
This is the phase when the bulk of the coding takes place.
Transition Phase
The primary objective is to 'transit' the system from development into
production, making it available to and understood by the end user.
http://en.wikipedia.org/wiki/IBM_Rational_Unified_Process

Rational Unified Process (RUP)

http://en.wikipedia.org/wiki/IBM_Rational_Unified_Process

SCRUM
Scrum is an iterative, incremental framework for project management often
seen in agile software development
Scrum contains predefined roles. The main roles in Scrum are:
the ScrumMaster, who maintains the processes (typically in lieu of a
project manager)
the Product Owner, who represents the stakeholders and the business
the Team, a cross-functional group who do the actual analysis,
design, implementation, testing, etc.
During each sprint, typically a two to four week period (with the length
being decided by the team), the team creates a potentially shippable
product increment (for example, working and tested software).

SCRUM

Summary

Summary