SOFTWARE

DEVELOPMENT
METHODOLOGIES
Reported by :
ENGR. JANE J. PANGANIBAN
Items to be reported :
Prototype Methodology

Rapid Applications Development

Joint Application Development Methodology

a. Definition

b. Pros

c. Cons
PROTOTYPE METHODOLOGY
It is a specialized software development
procedure that initiates developers towards
making only the sample of the resolution to
validate its functional essence to the
customers, and make essential changes
before creating the authentic final solution.

In fact, the best part of this methodology is that

it tends to resolve a set of diversifying issues
occurring with the waterfall method
PROTOTYPE METHODOLOGY

MAINTAIN
PROTOTYPE METHODOLOGY
PROS :
1. Gives clear idea about the functional
process of the software
2. Reduces the risk of failure in a software
functionality
3. Assists well in requirement gathering and
the overall analysis
PROTOTYPE METHODOLOGY
CONS :
1. Chances of extension in management cost
2. Excessive involvement of client can affect
processing
3. Too many changes affect the workflow of the
software
RAPID APPLICATIONS
DEVELOPMENT
Aimed at providing quick results, rapid
application development is meant to give
excellent development processes with the
assistance of other development approaches.
It is created to take the maximum advantage
from the development software.
Undoubtedly, it is designed to augment the
workability of the whole software development
procedure for highlighting the participation of
an active user.
RAPID APPLICATIONS
DEVELOPMENT
RAPID APPLICATIONS
DEVELOPMENT
PROS :
1. Makes the entire development process
effortless
2. Assists client in taking quick reviews
3. Encourages feedback from customers for
improvement
RAPID APPLICATIONS
DEVELOPMENT
CONS :
1. Dependant on the team for performance
2. Works on modularized system confined on
this methodology
3. Requires extremely skilled personnel to
handle complexities
4. Not applicable for the small budgeted
projects
JOINT APPLICATIONS
DEVELOPMENT
Two employees of IBM, Chuck Morris and
Tony Crawford, developed the JAD
methodology in the late 1970s and began
teaching the approach in to the 1980s.
It tends to lay emphasis on the business
difficulty rather than methodical details.
JOINT APPLICATIONS
DEVELOPMENT
This is a requirements-classification and user-
interface expansion approach that necessitates for
the end-users, clients and developers attend a
powerful off-site conference to accentuate and
confirm software system.
This methodology serves towards including the
client in the design and expansion of an
application.
This is effortlessly proficient through a sequence
of concerted workshops known as JAD sessions.
JOINT APPLICATIONS
DEVELOPMENT
PROS :
1. Allows for simultaneous congregation and
alliance of excessive information.
2. Produces huge amount of valuable
information in short period
3. Immediate resolving of differences with
suitable assistance
4. Provides forum to explore multiple points
JOINT APPLICATIONS
DEVELOPMENT
CONS :
1. Takes excessive amount of time for planning
and scheduling
2. Requires significant investment of time and
effort
3. Calls for highly trained experts, which is
tough to find
REFERENCES :
www.itinfo.am/eng/software-development-methodologies/
en.wikipedia.org/wiki/Software_development_process
acodez.in/12-best-software-development-methodologies-pros-cons/
en.wikibooks.org/wiki/Introduction_to_Software_Engineering/Proces
s/Methodology#Prototyping
THANK YOU!