RAD
(Rapid Application Development) and JAD (Joint Application Design) Workshops
Primary Reference Sources -
Andrews, D.C. (1991) JAD: A crucial dimension for rapid applications
development’. Journal of systems management, March 23-31.
Summary Description
RAD:- Workshops are set up in which 8-20 individuals make decisions through
the consensus building leadership of a trained, unbiased facilitator who
is not a stakeholder in the future system. A number of different formats
for the method are offered. One variation produces formal outputs such
as entity-relationship models, which can be input directly into the system
specification.
JAD is a specific variation developed within IBM. Here users and information
systems professionals are drawn together to design a system jointly in
a facilitated group session. Six roles are defined including: session leader,
user representative, specialist, analyst, an information systems representative
and an executive sponsor. A 20% to 60% increase in productivity over traditional
design methods is claimed.
Benefits
-
Improves quality and speed of system specification and design.
-
Is integrated with current structured methods and CASE tools.
-
Promotes co-operation, understanding and teamwork among the various user
groups and information systems staff.
-
Can be used at various levels of detail, including: concept, requirements,
specification and design.
Limitations
-
Workshops tie up stakeholders often for several days at a time.
-
Appears to have only been used effectively for smaller systems.
-
Group sessions needs skilful running to ensure group they are productive
and reach a consensus.
Costs of Use
Workshops require up to 3 weeks of planning. Post workshop activities may
also be required.
Suitability for requirements engineering in Telematics
T
he essential structure of method may be appropriate to adopt within
projects where there is a need to integrate the interaction of various
groups or Centres who may be working to different goals.
How to get it
High level method documented in the literature. Specific details could
be obtained from author. Cost unknown.
Main stages of the method
-
JAD Planning session (1-5 days).This session includes: participation orientation,
definition, definition of high-level requirements, bounding system scope,
identify designs to be produced, identify participants, schedule design
sessions, deal with documentation issues.
-
JAD Design session (3-10 days). This session includes :participation orientation,
review and refine requirements and scope, develop workflow diagrams and
descriptions, identify system data groups and functions, specify processing
requirements, deal with documentation issues.
-
JAD teams are given guidance and proformas which can be used as a basis
for the agenda for group sessions. The proformas may be compiled into a
workbook, preferably customised to the problem situation, for the team
to complete either during session or as part of a follow-up. They may include
participant matrix forms, issues forms, estimating assumptions forms, screen
layout forms, report layout forms, interface description forms, and function
description forms.