AGILE MODELING AND

PROTOTYPING

Major Topics

Prototyping
RAD(Rapid Application Development)
Extreme Programming(XP)

SDLC

Software is created on a well

planned pattern.
Efficient as planned.
Everything will be as written.
Focuses on developers, not users.
Harder to ALTER.

SDLC
PLANNING

LAUNCHING

CONSULTATION

DOCUMENTATION

CREATION

TESTING

Prototyping

Not based on planning.

One after another until the perfect one is
formed.
User can test and improve!

Prototyping

Prototyping is an information-gathering
technique.
In manyprogramming languages,
afunction prototypeis thedeclarationof
afunction.
Prototypes are useful in seeking user
reactions, suggestions, innovation, and
revision plans.
Prototyping may be used as an alternative
to the systems development life cycle.

Four Kinds of Prototypes

The four conceptions of prototypes are :

Patched-up prototype.
Nonoperational scale model.
First-of-a-series.
Selected Features Prototype

Patched-up Prototype

Encourages cooperation of different

developers.
Everyone plays his part.
A fast development model.
no need to overlap in a specific
function of work.
needs a strong project manager.
Manager controls the work flow.

Non-Operational Prototype

Used when only a certain part of the program

should be updated.
Specific part will work and could be tested.
Main prototype is not effected by the
dummy.
Implemented when certain problems in a
specific part of the program arises.
Alteration and maintenance is important.
smart way of creating software.

First of a Series Prototype

Known as a beta version.

Efficient if launched properly.
Public gets a chance to test.
Aim is to receive feedbacks.
Best to test firewall and security.
It could be hacked, backfire and
destroyed.

Selected Features
Prototype

Full version software but LIMITED.

Is applied to a bigger suite of programs.
Independent of suite.
To test independent features.

Types of Prototyping

Prototype Model Disadvantages

Models presented in the early stage are

not complete.
Usually they lack flaws.
Documentation is a nightmare.

Prototype Model
Advantages

More effort is placed in creating the

actual software.
Reducing man hours in creating a
software.
Software is created using lots of user
feedbacks.
Over Design could also be avoided.
Has great advantage over other SDLC
models.

Rapid Application
Development (RAD)

Rapid Application
Development(RAD)

Software is not a physical tool that can be lost

once it gets developed.
Little changes are made in the interface to
meet the requirement of the client.
Tools as code generators are in the market.
RAD an object-oriented approach to systems
development.
Focuses more on the visual instead of the
coding.

How RAD is different from other

SDLC systems?

RAD Phases

The three broad phases to RAD are :

Requirements planning.
RAD design workshop.
Implementation.

Requirements Planning
Phase

Users and analysts meet to identify

objectives of the application or system
Oriented toward solving business
problems

RAD Design Workshop

Design and refine phase.
Programmers and analysts can build and show
visual representations of the designs and
workflow to users.
Analysts refine designed modules based on
user responses.

Implementation Phase

As the systems are built and refined, the

new systems or partial systems are
tested and introduced to the
organization.
When creating new systems, there is no
need to run old systems in parallel.

RAD Phases

RAD and the SDLC

RAD tools are used to generate screens

and exhibit the overall flow of the
application.
Users approve the design and sign off on
the visual model.
Implementation is less stressful because
users help to design the business aspects
of the system.

When to Use RAD

RAD is used when:
The team includes programmers and analysts
who are experienced with it.
There are hard pressing reasons for speeding
up application development.
The project involves a Novel ecommerce
application and needs quick results.
Users are sophisticated and highly engaged
with the goals of the company.

Disadvantages of RAD

This requires highly skilled developers.

Requires longer percentage of time of
stakeholders and users than other
approaches.

Extreme Programming (XP)

Extreme Programming (XP)

Extreme programming (XP) takes

good systems development
practices to the extreme.
It is denoted by XP.

Four Values of Extreme

Programming

Communication.
Simplicity.
Feedback.
Courage.

Kendall & Kendall

2005 Pearson Prentice Hall

6-28

Five XP Principles

Providing rapid feedback.

Assuming simplicity.
Changing incrementally.
Embracing change.
Encouraging quality work.

Kendall & Kendall

2005 Pearson Prentice Hall

6-29

Five XP Principles

Kendall & Kendall

2005 Pearson Prentice Hall

6-30

Four Basic Activities of XP

Coding.
Testing.
Listening, to the programming partner
and customer.
Designing.

Kendall & Kendall

2005 Pearson Prentice Hall

6-31

Four XP Resource Control

Variables

Time.
Cost.
Scope.
Quality.

Kendall & Kendall

2005 Pearson Prentice Hall

6-32

Four XP Core Practices

The four XP core practices are:
Short releases, work with the most important
features first.
Having a 40-hour work week.
Having an onsite customer.
Pair programming with another programmer.

Kendall & Kendall

2005 Pearson Prentice Hall

6-33

XP Relationships

Kendall & Kendall

2005 Pearson Prentice Hall

6-34

XP Development Process
The phases of the XP development process
are:
Exploration.
Planning.
Iterations to the first release.
Productionizing.
Maintenance.

Kendall & Kendall

2005 Pearson Prentice Hall

6-35

XP Stories

XP stories are a spoken interaction

between developers and users.
It is not written communication.
The goal is prevention of
misunderstanding or misinterpretations
of user requirements.

Kendall & Kendall

2005 Pearson Prentice Hall

6-36

XP Lessons
The six lessons that can be drawn from
the XP development approach are:
Short releases allow the system to evolve.
Pair programming enhances overall quality.
Onsite customers are mutually beneficial to
the business and the XP team.

Kendall & Kendall

2005 Pearson Prentice Hall

6-37

XP Lessons

The six lessons that can be drawn from

the XP development approach
(continued)
The 40-hour work week improves worker
effectiveness.
Balanced resources and activities support
project goals.
XP values are crucial to success.

Kendall & Kendall

2005 Pearson Prentice Hall

6-38

XP Lessons

Kendall & Kendall

2005 Pearson Prentice Hall

6-39

Agile Modeling

Agile modeling is similar to XP.

In addition to the values of
communication, simplicity, feedback and
courage, it has a fifth value of humility.

Kendall & Kendall

2005 Pearson Prentice Hall

6-40

Agile Modeling (Continued)

Agile modeling process is:

Listen to user stories.
Draw a logical workflow model.
Create new user stories based on the
workflow.
Develop some prototypes.
Use feedback from the prototypes and logical
workflow to create physical model.

Kendall & Kendall

2005 Pearson Prentice Hall

6-41

Scrum

Scrum is an Agile approach that has an

emphasis on teamwork.
Team success is of primary importance.
Individual success is secondary.
The team works within a strict time
frame.
The project leader has some but not
much influence on detail.

Kendall & Kendall

2005 Pearson Prentice Hall

6-42