100% found this document useful (1 vote)
375 views13 pages

Joint Application Development JAD

Uploaded by

dancostache
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
375 views13 pages

Joint Application Development JAD

Uploaded by

dancostache
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
  • Introduction to Joint Application Development (JAD): Introduces Joint Application Development (JAD) process, highlighting its purpose, history, and effectiveness.
  • Generic JAD Life Cycle: Outlines the stages of the JAD life cycle: Planning, Preparation, Design Sessions, and Finalization, detailing tasks within each.
  • JAD Participants and Roles: Describes various roles within a JAD session, including project leader, top management, and systems analysts.
  • JAD Pros: Lists advantages of JAD, such as effective communication and quick valuable information production.
  • Making JAD Successful - Participation Rules: Specifies general rules for JAD participant operations to ensure success.
  • JAD Cons: Outlines the challenges and disadvantages associated with implementing JAD, such as time and resource intensity.

Joint Application Development (JAD)

• 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.
• Before the initiation of JAD, requirements were identified by interviewing stakeholders
individually.
• The ineffectiveness of this interviewing technique, which focused on individual input rather
than group consensus, led to the development of the JAD approach.

SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE


Joint Application Development (JAD)
• JAD offers a team oriented approach to the development of information management
solutions that emphasize a consensus based problem-solving model.
• By incorporating facilitated workshops and emphasizing a spirit of partnership, JAD enables
system requirements to be documented more quickly and accurately than if a traditional
approach were used.
• JAD combines technology and business needs in a process that is consistent, repeatable, and
effective

SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE


Generic JAD Life Cycle
• Planning/Definition
• Preparation
• Design Sessions
• Finalization

SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE


Planning/Definition
To complete the Planning stage, perform the following tasks:
• Designate the executive sponsor.
• Establish the need for the system.
• Select team members for the definition component.
• Define the scope of the session.

SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE


Preparation
To complete the Preparation stage, you must perform the following tasks:

• Schedule design sessions.


• Conduct orientation and training for design session participants.
• Prepare the materials, room, and software aids.
• Customize the design session agenda.
• Conduct the kickoff meeting.

SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE


Design Sessions

To complete the Design Session component of JAD, you must perform the following
tasks:
• Review the project scope, objectives, and definition document.
• Identify data, process, and system requirements.
• Identify system interfaces.
• Develop a prototype.
• Document decisions, issues, assumptions, and definitions of terms.
• Assign someone to resolve all issues.

SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE


Finalization
To complete the Finalization component, you must perform the following tasks:
• Complete the design documents.
• Sign off on the design documents.
• Make a presentation to the executive sponsor.
• Demonstrate the prototype.
• Obtain the executive sponsor's approval to proceed.
• Evaluate the JAD process.

SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE


JAD participants and roles
• Project leader
• Top management
• Managers
• Users
• Systems analysts and other IT staff members
• recorder

SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE


JAD participants and roles
Project leader
• Project leader develop an agenda, acts as facilitators, and leads the JAD
session

Top management
• Provide enterprise level authorization and support for the project

Managers
• Provide department level support for the project and understanding of
how the project must support business functions and requirements
SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE
JAD participants and roles
Users
• Provide operational level input on current operations, desired changes, input and output
requirements, user interface issues, and how the project will support day-to-day tasks

Systems analysts and other IT staff members


• Provide technical assistance and resources for JAD team members on issues such as
security, backup, hardware, software, and network capability

Recorder
• Documents results of JAD sessions and work with system analysts to build system models
and develop CASE tool documentation

SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE


JAD PROS
• Allows for simultaneous congregation and alliance of excessive information.
• Produces huge amount of valuable information in short period
• Immediate resolving of differences with suitable assistance
• Provides forum to explore multiple points
• The decision makers are all present.
• The facilitator keeps the group focused on the goals.
• Differing views are handled immediately.
• Most errors are caught in the Analysis and Design stages.
• The system design reflects the user's desires.
• Issues are resolved quickly.
• Assumptions are documented and understood.
• The process tends to gain momentum, not lose it.
SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE
Making JAD Successful Participation Rules

The following are general rules under which JAD participants should operate:
·Gain agreement.
·Agree on a time limit rule for disagreements.
·Establish the executive sponsor as the decider.
·Require mandatory attendance.
·Stress that all participants are equal regardless of job code.
·Require open participation.
·Allow only one conversation to occur at a time.
·Respond to ideas, not to people.

SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE


JAD CONS
• Takes excessive amount of time for planning and scheduling

• Requires significant investment of time and effort

• Calls for highly trained experts, which is tough to find

SCHOOL OF COMPUTING - SAD - ANURADHA JAYASINGHE

You might also like