Professional Documents
Culture Documents
Objectives
2
Application Programming II
Rapid Application Development and
Prototyping
What is RAD?
3
RAD Approaches
4
2/29/2016
What is RAD?
5
What is RAD?
6
With
the
previous
methodologies,
large
applications took so long to build that requirements
would change before the system was complete,
resulting in unusable systems.
Rapid Application Development and Prototyping
2/29/2016
1.
2.
3.
4.
5.
6.
11
2/29/2016
RAD Rationale
15
14
RAD Rationale
16
1.
2.
3.
2/29/2016
17
18
A.
1.
a.
b.
c.
1.
Sensible RAD: tilts away from economy and quality toward fastest schedule
2.
a.
b.
c.
2.
All-out RAD: "code like hell (fast, loose, all-as-you-go coding i.e. Code-&-Fix)
3.
a.
b.
c.
19
1.
2.
3.
prototyping,
iterative development,
small teams,
E.g. to develop models (using eg UML diagrams) and directly generate code
based on those models instead of hard coding.
Rapid Application Development and Prototyping
2/29/2016
21
RAD Phases
22
Defines the business functions and data subject areas that the system will
support and determines the systems scope.
uses workshops to
model the systems data and processes and to
build a working prototype of critical system components.
Construction Stage
Implementation Stage
includes final user testing and training, data conversion, and the
implementation of the application system.
Characteristics of RAD
23
Characteristics of RAD
24
1.
1.
both
developers and
users of the system plus
anyone else who has a stake in the requirements.
fulltime
2/29/2016
25
Characteristics of RAD
1. RAD uses hybrid teams (cont)
Characteristics of RAD
26
User Review Board: A team of users who review the system after
construction and decide whether modifications are necessary before
cutover.
2.
Visual development.
Creation of fake prototypes (pure simulations)
Creation of working prototypes.
Multiple languages.
Team scheduling.
Teamwork and collaboration.
Use of reusable components
Use of standard APIs
Version control
Characteristics of RAD
27
Characteristics of RAD
28
2.
3.
i.
JAD (Joint Application Development) meeting: Highlevel end-users and designers meet in a brainstorming
session to generate a rough list of initial requirements.
Developers
Customers
ii.
2/29/2016
Characteristics of RAD
29
Constraints of RAD
31
Constraints of RAD
32
2/29/2016
Constraints of RAD
33
Constraints of RAD
34
Makes sense if you can only trust one person with this power.
Does NOT make sense if you have a team of good people as it becomes
inefficient and inhibits working at full potential.
The team must include all the necessary team members to make
decisions, and make them in a timely manner.
Any interference with the project team is disruptive and reduces their
motivation to deliver.
2/29/2016
An Evaluation of RAD
38
defeats parallelism
Rapid Application Development and Prototyping
RAD Strengths
39
RAD Strengths
40
Early visibility
Greater flexibility
because of prototyping
Rapid Application Development and Prototyping
Rapid Application Development and Prototyping
10
2/29/2016
RAD Strengths
41
RAD Disadvantages
42
Less efficient
because
because
RAD Disadvantages
43
RAD Disadvantages
44
because
because
11
2/29/2016
Summary
45
Change is
development.
often
the
reason
for
delays
in
application
RAD combats scope and requirements creep by limiting the project's exposure to
change - shortening the development cycle and limiting the cost of change by
incorporating it up-front before large investments are made in
development and testing..
Rapid Application Development and Prototyping
12