2. MODEL SDLC (BAG.

2)
CAPAIAN PEMBELAJARAN

2. 3.
1. Deskripsi Penerapan
Mampu
menjelaskan: Jenis-Jenis dan model SDLC
model SDLC Karakteristik pada proyek
model SDLC PL

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 2

AGENDA PEMBAHASAN
1. Dynamic Systems Development Method
(DSDM)
2. Extreme Programming (XP)
3. Scrum
4. Agile Unified Process (AUP)
5. Rational Unified Process (RUP)

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 3

DYNAMIC SYSTEMS DEVELOPMENT METHOD
(DSDM)
DSDM Process: Project Variables Comparison

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 4

DYNAMIC SYSTEMS DEVELOPMENT METHOD
(DSDM)
Deskripsi dan karakteristik:
• Introduced by DSDM Consortium
(1994), universally available in 2007
• DSDM Consortium became Agile
Business Consortium (2016) 🡪 url:
https://www.agilebusiness.org/
• Improvement to RAD (lack of rigour 🡪
reduced quality)
• Implements Agile approach (Agile
Manifesto)

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 5

DYNAMIC SYSTEMS DEVELOPMENT METHOD
(DSDM)
KELEBIHAN KEKURANGAN

• Early implementation to business problems • Costly to implement

• Reducing risk of building the wrong solution
• Incorporate stakeholders into the
development process
• Incremental delivery
• Users will be better trained
• Deployment is more likely to go smoothly
• IT professionals and end users must be
trained accordingly
• Requires full commitment to DSDM process
• Involves progressive development of
requirements

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 6

MENERAPKAN MODEL DSDM BILA:

• Systems that are time constrained

• Systems where requirements can be prioritized
• Interactive systems, where functionality is clearly demonstrable at the user
interface
• Inappropriate for critical-mission projects

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 7

EXTREME PROGRAMMING (XP)
Deskripsi dan karakteristik:
• Developed by Kent Beck (1996)
• Recognizes 5 values:
communication, simplicity,
feedback, courage, respect
• Implements Agile approach (Agile
Manifesto)
• Relies on constant code
improvement, pairwise
programming
• 5 basic principles: small releases,
40-hour work week, on-site
customer, collective ownership,
coding standards

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 8

EXTREME PROGRAMMING (XP)
KELEBIHAN
• Eliminate defects early, reducing cost
• User involvement in the development
team
• Increased user satisfaction
• Cohesive developer environment
• High productivity and quality code
KEKURANGAN
• Lack of specification and design documents
• Requirements are expressed informally
• Requirements conflicts due to multiple
stakeholders
• Potentially scope creep
• Neglected planning
• Requires experienced developers
RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 9
MENERAPKAN XP BILA:

• Requirements are vague and rapidly changing

• For small-to-medium size projects
• Not recommended for a team with more than ten members

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 10

SCRUM
Deskripsi dan karakteristik:
• Conceived by Jeff Sutherland
(early 1990s) and developed
further by Schwaber and Beedle
(2002)
• Consistent with the agile
manifesto
• Framework activities include:
requirements, analysis, design,
evolution, and delivery
• Scrum emphasizes the use of a
set of software process patterns:
backlog, sprints, scrum meetings
(led by scrum master), and
demos

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 11

SCRUM
KELEBIHAN
• Assumes up-front the existence of chaos
• Uncover potential problems as early as possible
• Promote a self-organizing team structure through
daily meetings
• Help teams complete project deliverables quickly and
efficiently
• Large projects are divided into easily manageable
sprints
• Adopts feedback from customers and stakeholders
• The individual effort of each team member is visible
during daily scrum meetings
KEKURANGAN
• Often leads to scope creep, due to the lack of a definite end-
date
• The chances of project failure are high if individuals aren't
very committed or cooperative
• Adopting the Scrum framework in large teams is challenging
• The framework can be successful only with experienced
team members
• Daily meetings sometimes frustrate team members
• If any team member leaves in the middle of a project, it can
have a huge negative impact on the project
• Quality is hard to implement until the team goes through an
aggressive testing process
RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 12
MENERAPKAN MODEL SCRUM BILA:

• Where the elimination of uncertainty is impossible

• Fast-moving development projects
• Relatively small team
• Experienced team members

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 13

AGILE UNIFIED PROCESS (AUP)
Deskripsi dan karakteristik:
• Adopts a “serial in the large” and
“iterative in the small” philosophy
• Serial overlay of classic UP phased
activities: inception, elaboration,
construction, and transition but iterative
within each of the activities to achieve
agility and to deliver meaningful
software increments to end users as
rapidly as possible.
• Activities within each iteration:
modeling, implementation, testing,
deployment, configuration and project
management, environment
management.

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 14

AGILE UNIFIED PROCESS (AUP)
KELEBIHAN
• Rapid generation of operational software
• Fast delivery and acquisition of feedback
from end users
• Adopting the classic UP phased activities
• UML representations of the business and
problem domains
KEKURANGAN
• “Just barely good enough” models (to
stay agile)
• Management seems to love but
developers seems leery of due to the
large number of artifacts
• Extreme Programmers will likely find the
AUP fairly heavy, and "traditional RUP"
users may find that it's too streamlined
RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 15
MENERAPKAN MODEL AUP BILA:

• If you want something in between XP and traditional RUP (a process that is agile
yet explicitly includes activities and artifacts which you're accustomed to)
• Your staff knows what they're doing

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 16

RATIONAL UNIFIED PROCESS (RUP)
Deskripsi dan karakteristik:
• Mid. 1990s – 2008 🡪 discontinued by IBM
• Iterative development process, geared
towards the development of object-
oriented systems, complements UML.
• Intermediate between document-driven
and agile methods.
• Reasonably extensive upfront
requirements engineering activities, yet
emphasizes stakeholder involvement
through its use-case driven nature.
• 2 dimensional process structures: Phases &
Workflows

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 17

RATIONAL UNIFIED PROCESS (RUP)
KELEBIHAN
• Popular language (UML) and process
model (good tool support)
• Architecture-centric / Component-based
• Core workflow definitions and
incorporation of Business Processes
• Allows for the adaptive capability to deal
with changing requirements throughout
the development life cycle
KEKURANGAN
• Tries to be “all things to all people”
• Often misappropriately instantiated as a waterfall
(with Inception as a big requirements up front
(BRUF) phase, Elaboration as a detailed
architecture phase, and Transition as a testing
phase.
• Often misappropriately instantiated in a heavy
and onerous manner.
• Heavily relies on proficient and expert team
members
• Implementation is challenging, particularly for
smaller businesses, teams or projects.
RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 18
MENERAPKAN MODEL RUP BILA:

• Suggested for medium to large scale projects

• Team consist of proficient and expert members
• Need for accurate documentation

RPL - CIF61019 - Model SDLC (Bag. 2) / Tim Pengelola MK RPL 19