Rapid Development
Femme Sabaru - 1501170135 | Aditya Gisheila 1501152025 | Aninda Harapan - 1501152744 |
Harry - 1501145272 | Andrew Khosugih 1501156143
06PLM – GROUP 9
ABSTRACT
Rapid development to some people is consists of the application of a single pet tool or
method. For some manager, whatever practice was highlighted in the most recent
issue of Business Week. Rapid development is merely a descriptive phrase that
contrasts with "slow and typical development". Rapid development is a generic term
that means the same thing as "speedy development" or "shorter schedules". It means
developing software faster than you do now. Rapid-development project, then, is any
project that needs to emphasize development speed. If you work in a typical
organization and follow the practices of rapid development, you'll be able to cut your
development time significantly, perhaps by as much as half, and boost your
productivity significantly too. You'll be able to do that without harming quality, cost,
performance, or maintainability. Rapid product development is not a quick fix for
getting one product -which is probably already late- to market faster. Instead, it is a
strategic capability that must be built from the ground up --Preston G. Smith and
Donald G. Reinertsen, Developing Products in Half the Time.
Keywords: Developments, Speed development, Fast Development, Efficient
Development, Short Schedule, Method, Strategic, Effective practices, Scheduleoriented practices, Speed-oriented
Table of Contents
ABSTRACT .................................................................................................................. 2
CHAPTER 1 INTRODUCTION ................................................................................ 5
BACKGROUND ................................................................................................................. 5
SCOPE ................................................................................................................................. 6
OBJECTIVE AND BENEFITS ......................................................................................... 6
METHODOLOGY.............................................................................................................. 6
CHAPTER 2 LITERATURE REVIEW .................................................................... 7
Definition of System ............................................................................................................ 7
Definition of Development .................................................................................................. 7
Definition of Life Cycle ....................................................................................................... 7
Definition of Rapid Application Development ................................................................. 7
Definition of Prototyping .................................................................................................... 8
Definition of Joint Application Development ................................................................... 8
Definition of Prototype ....................................................................................................... 8
CHAPTER 3 DISCUSSION........................................................................................ 9
WHAT IS RAPID DEVELOPMENT ............................................................................... 9
ADVANTAGES OF RAPID DEVELOPMENT ............................................................ 11
DISADVANTAGES OF RAPID DEVELOPMENT ...................................................... 11
STEPS IN RAPID DEVELOPMENT ............................................................................. 12
AGILE DEVELOPMENT VS RAPID DEVELOPMENT............................................ 14
CHAPTER 4 CONCLUSION ................................................................................... 15
CONCLUSION.................................................................................................................. 15
SUGGESTION .................................................................................................................. 15
References ................................................................................................................... 17
BIOGRAPHY ............................................................................................................. 18
CHAPTER 1
INTRODUCTION
BACKGROUND
A structured approach to systems development has been around since the
1960s and 1970s when large mainframe applications were developed. These
applications were built when (1) systems were relatively simple and independent from
each other, (2) computer hardware was relatively more expensive than the labor, and
(3) development and programming tools were primitive compared to today (Satzinger,
Jason, Burd, 2002)
On the other hand, one can take a less-structured approach to developing
systems. Today, taking less time to conceive, develop, and implement an information
system can provide the organization with a competitive advantage. In addition, as
evidenced by the CHAOS study, larger projects that take longer to develop are riskier
than smaller and shorter projects. Satzinger, Jackson, and Burd (Object - Oriented
Development And The Unified Process, 2002) define RAD as "a collection of
development approaches, techniques, tools, and technologies, each of which has been
proven to shorten development schedules under some conditions." This means that
different development approaches, tools, techniques, and so forth can be mixed and
matched depending on the project.
So, we provide solution by providing this writing, which can help people in
developing their system processes. Also we provide information about the benefit and
drawbacks in using the RAD process also comparison with other SDLC methodology.
So, in the end people will get the best method in developing their system life cycle
with the most effective and efficient method.
SCOPE
Our boundaries that we make so we don’t off track in our research are we
definite what RAD (Rapid Application Development) is, the advantages if we use
RAD in our SDLC, we also provide information about the drawbacks of RAD, and
compare with the other SDLC development methodology which is the Agile
Development method.
OBJECTIVE AND BENEFITS
Our Objectives are to create a writing that can help people in understanding
RAD method easier. Because some statement in this writing based on trusted
reference. So, it’ll increase people’s efficiency in finding sources when understanding
the RAD method. And the other method is to fulfill the requirement to pass TeoriTeori Lanjutan subject.
The advantages that come from this writing that provide:

We can fulfill one requirement to pass the Teori-Teori Lanjutan subject.

We can help people more understand the RAD method.

We learn how to write a proper paper
METHODOLOGY
Method that will be used in this writing:

Literature Study: We research from any source, especially on books and
journals, which has relationship with this research
CHAPTER 2
LITERATURE REVIEW
Definition of System
System is a collection of interrelated components that function together to
achieve some outcome. (Satzinger, Jackson, & Burd, 2004)
Definition of Development
1. The act or process of growing or causing something to grow or become larger
or more advanced
2. The act or process of creating something over a period of time
3. The state of being created or made more advanced
(Merriam Webster, 2014)
Definition of Life Cycle
Life Cycle is a series of stages through which something (as an individual,
culture, or manufactured product) passes during its lifetime. (Merriam Webster,
2014).
Definition of Rapid Application Development
Rapid Application Development is the merger of various structure and
techniques (especially the Data- Driven information engineering) with prototyping
techniques and joint application development techniques to accelerate systems
development. (Whitten, Bentley, & Dittman, System Analysis and Design Methods,
2000)
Rapid Application Development (RAD): Systems development methodology
created to radically decrease the time needed to design and implement information
systems. It relies on heavy user involvement, Joint Application Development sessions,
prototyping, integrated CASE tools and code generator. (Hoffer, George, & Valacich,
1996)
Definition of Prototyping
Prototyping is a technique for quickly building a functioning, but incomplete
model of information system using rapid application development tools. (Hoffer,
George, & Valacich, 1996)
Definition of Joint Application Development
Joint Application Development (JAD) is a process that accelerates the design
of information technology solutions. JAD uses customer involvement and group
dynamics to accurately depict the user's view of the business need and to jointly
develop a solution (UMSL, 2014)
Definition of Prototype
Prototype is a smaller scale, representative or working model of the users
requirements or a proposed design for an information system. (Whitten, Bentley, &
Dittman, Systems Analysis and Design Methods, 2001)
CHAPTER 3
DISCUSSION
WHAT IS RAPID DEVELOPMENT
Rapid Development, also known as Rapid Application Development, is a collection of
methodologies that emerged in response to the weaknesses of waterfall development
and its variations (Roth, Dennis, & Wixom, 2013). Rapid Application Development is
also a system development strategy that focuses on the speed of development through
the extensive involvement of users during construction of a system prototype that
later will be a final system (or a certain version).
There are several ways in conducting the Rapid Application Development:

Iterative Development: This certain way of the Rapid Application
Development is by breaking the overall project into a series of versions
that are developed sequentially (Roth, Dennis, & Wixom, 2013).

Iterative Development (Slepi)
System Prototyping: The way of performing the analysis, design and
implementation phases concurrently in order to quickly develop a
simplified version of the proposed system and five it to the users for
evaluation and feedback (Roth, Dennis, & Wixom, 2013).
System Prototyping (Slepi)

Throwaway Prototyping: Development of prototypes, but uses the
prototypes primarily to explore design alternatives rather than as the actual
new system (as in system prototyping) (Roth, Dennis, & Wixom, 2013).
Throwaway Prototyping (Slepi)
ADVANTAGES OF RAPID DEVELOPMENT
The Rapid Application Development approach has several advantages
(Whitten, Bentley, & Dittman, System Analysis and Design Methods, 2000):

Useful to projects where the user requirements’ are uncertain and unclear

It pushes the users to be active and management participation to encourage
end user enthusiasm in of the project

Projects have visibility and more support due to the extensive involvement
of users during the process

Users and management can see the solutions that are software-based and
work faster than model-driven development

Error and bugs are detected earlier in the prototype than in system
modeling

Testing and training are additional aspects of the basic prototyping
approach

Iterative approach is a process that is more “natural” because change is the
factor that is expected during development
DISADVANTAGES OF RAPID DEVELOPMENT
The Rapid Application Development approach has several disadvantages too
(Whitten, Bentley, & Dittman, System Analysis and Design Methods, 2000):

Some people thinks that the Rapid Application Development pushes the idea
of “coding, implementing, and fixing” that increases the lifetime cost that is
needed to operate, support and maintain the system

Rapid Application Development Prototypes can easily solve wrong problems
because of the shortened or neglected problem analysis

RAD-based prototype may make the analysts feel small in considering other
valuable technical alternatives

Sometimes it is better to throw away prototypes, but stakeholders are often
reluctant to go so because they think that it is a loss of time and effort of the
product

Accentuation on speed can have negative impact on quality that is caused by
shortcuts badly advised through the methodology
STEPS IN RAPID DEVELOPMENT
Basically the Rapid Development has four fundamental phases:

Planning: The fundamental process of understanding why information should
be built and determining how the project team will go about building it (Roth,
Dennis, & Wixom, 2013). Consisting two steps:
o During project initiation: Identification of system’s business value to
the organization
o During project management: Describing how the project team will go
about developing the system

Analysis: Answering the questions of who will use the system, what the
system will do, and where and when it will be used. Consisting of three steps:
o Analysis strategy: Developed to guide the project the project team’s
efforts
o Requirement Gathering: Development of a concept for a new system
o System Proposal: Combination of analyses, system concepts, and
models

Design: Deciding on how the system will operate in terms of the hardware,
software, and network infrastructure that will be in place; the user interface,
forms, and reports that will be used; and the specific programs, databases, and
files that will be needed. Consisting of four steps:
o Design Strategy: Clarification of whether the system will be developed
by the company’s own programmers, whether its development will be
outsourced to another firm or whether the company will buy an
existing software package
o Architecture Design: Describing the hardware, software, and network
infrastructure that will be used; Interface Design: Specifying how the
users will move through the system and the forms and reports that the
system will use
o Database and file specification: Defining exactly what data will be
stored and they will be stored
o Program Design: Defining the programs that need to be written and
exactly what each program will do

Implementation: Phase where the system is actually built (or purchased, in the
case of a packaged software design, and installed). Consisting of three steps:
o System construction: Building and testing system to ensure that it
performs as designed.
o Installation: The process by which the old system is turned off and the
one is turned on; Training Plan: Teaching users how to use the new
system and help manage the changes caused by the new system
o Support Plan: Formal or informal post-implementation review, as well
as a systematic way for identifying major and minor changes needed
for the system
AGILE DEVELOPMENT VS RAPID DEVELOPMENT
Usefulness in
Developing
Systems
Rapid Application Development
Agile
Development
Iterative
System
Prototyping
Throwaway
Prototyping
With unclear
user
requirements
Good
Excellent
Excellent
Excellent
With
unfamiliar
technology
Good
Poor
Excellent
Poor
That are
complex
Good
Poor
Excellent
Poor
That are
reliable
Good
Poor
Excellent
Good
With short
time schedule
Excellent
Excellent
Good
Excellent
With schedule
visibility
Excellent
Excellent
Good
Good
Criteria for Selecting a Methodology (Roth, Dennis, & Wixom, 2013)
CHAPTER 4
CONCLUSION
CONCLUSION
Based on the analysis and information system design, we conclude that:
There are several ways in conducting the Rapid Application Development:

Iterative Development

System Prototyping

Throwaway Prototyping
Basically the Rapid Development consist four important phases:

Planning

Analysis

Design

Implementation
The best methodology that can be adapted is using Rapid Application Development in
Throwaway Prototyping method. It provides the most excellent result in prototype
implementation.
The RAD (Rapid Application Development) process only requires a small amount of
highly skilled and trained peoples to work together in perform prototyping and
construction of the software product, especially in dealing new technologies and
techniques are crucial.
SUGGESTION
Because of the limitation of time, we are suggesting some necessary parts that
need to be developed:

RAD (Rapid Application Development) should be implemented in creating a
system module in order to reduce maximum cost for organizational effective
and efficient budget for short period of time.

Highly risk operational method in implementing RAD that the systems are
related one to another which can effect to the other system if one of them is
error. It needs well-done preparation and good backup plan.

Special trained developers and designer are required.
References
Satzinger, J., Jackson, R., & Burd, S. (2010). Systems Analysis and Design in a
Changing World (5th Edition ed.). Boston: Course Technology.
Roth, R. M., Dennis, A., & Wixom, B. H. (2013). Systems Analysis and Design.
Singapore: John Wiley & Sons.
Slepi. (n.d.). Retrieved February 2014, from Slepi: http://www.slepi.net/slepi/wpcontent/uploads/sdlc_prototype.gif
Satzinger, Jackson, & Burd. (2004). Object Oriented Analysis and Design with
Unified Process. In Satzinger, Jackson, & Burd, Object Oriented Analysis and Design
with Unified Process (p. 6).
Merriam Webster. (2014). From Merriam Webster: http://www.merriamwebster.com/dictionary/development
Whitten, J. L., Bentley, L. D., & Dittman, K. C. (2000). System Analysis and Design
Hoffer, J. A., George, J. F., & Valacich, J. S. (1996). Modern System Analysis and
Design. In J. A. Hoffer, J. F. George, & J. S. Valacich, Modern System Analysis and
Design (p. 827). USA: The Benjamin/Cummings Publishing Company, Inc.
UMSL. (2014). UMSL. From UMSL:
http://www.umsl.edu/~sauterv/analysis/488_f01_papers/rottman.htm
Whitten, J. L., Bentley, L. D., & Dittman, K. C. (2001). Systems Analysis and Design
Methods. In J. L. Whitten, L. D. Bentley, & K. C. Dittman, Systems Analysis and
Design Methods (p. 98). West Lafayette: McGraw Hill Companies.
Roger S. Pressman, P. (2010). Software Engineering: A Practitioner's Approach. In P.
Roger S. Pressman, Software Engineering: A Practitioner's Approach (p. 4). New
york: The McGraw Hill Companies.
BIOGRAPHY
A. Biography
1
Full Name (with title)
Femme Lienda Hiwusala Sabaru
2
Gender
Female
3
Major
Information System
4
NIM
1501170135
5
D.O.B.
February 22nd 1993
6
E-mail
femme.sabaru@gmail.com
7
Tel. Number / HP
081999100630
B. Education History
SD
SMP
SMA
Institution
Sekolah
Dyatmika, Bali
Sekolah
Dyatmika, Bali
SMA Taman
Rama, Jimbaran
Year
1999-2005
2005-2008
2008-2011
C. Rewards & Appreciations
No
Reward Type
Institution
Year
A. Biography
1
Full Name (with title)
Aditya Gisheila Nastiti Prameswara
2
Gender
Female
3
Major
Information System
4
NIM
1501152025
5
D.O.B.
19th October 1993
6
E-mail
adityagh19@gmail.com
7
Tel. Number / HP
0811 877 3538
B. Education History
SD
SMP
SMA
Institution
SDS Angkasa 1,
Jakarta
SMP N 103,
Jakarta
SMAT Krida
Nusantara,
Bandung
Year
1999 – 2005
2005 – 2008
2008-2011
C. Rewards & Appreciations
No
Reward Type
Institution
Year
A. Biography
1
Full Name (with title)
Aninda Harapan
2
Gender
Female
3
Major
Information System
4
NIM
1501152744
5
D.O.B.
April 22nd 1994
6
E-mail
nindaaninda94@gmail.com
7
Tel. Number / HP
087883496826
B. Education History
SD
SMP
SMA
Institution
Baptis Elim
Kristen
Ketapang 1
Kristen Ketapang
1
Year
1999-2005
2005-2008
2008-2011
C. Rewards & Appreciations
No
Reward Type
Institution
Year
A. Biography
1
Full Name (with title)
Andrew Khosugih
2
Gender
Male
3
Major
Information Systen
4
NIM
1501156143
5
D.O.B.
1st February 1993
6
E-mail
Andrew_khosugih@yahoo.co.id
7
Tel. Number / HP
08988081295
B. Education History
SD
SMP
SMA
Institution
Chandra Kusuma
Chandra Kusuma
Ricci 1
Year
1999-2005
2005-2008
2008-2011
C. Rewards & Appreciations
No
Reward Type
Institution
Year
A. Biography
1
Full Name (with title)
Harry
2
Gender
Male
3
Major
Information System
4
NIM
1501145272
5
D.O.B.
April 5th 1993
6
E-mail
harrybinusorg@gmail.com
7
Tel. Number / HP
087869551230
B. Education History
SD
SMP
SMA
Institution
SD Methodist 3,
Medan
SMP Methodist
3, Medan
SMA Methodist
2, Medan
Year
1999-2005
2005-2008
2008-2011
C. Rewards & Appreciations
No
Reward Type
Institution
Year