0% found this document useful (0 votes)
48 views2 pages

Benefits of JAD

JAD (Joint Application Design) is a methodology developed in the late 1970s that involves clients in collaborative workshops called JAD sessions to design and develop applications. It was created by Chuck Morris and Tony Crawford of IBM. JAD is thought to lead to faster development times and greater client satisfaction than traditional development approaches because the client is involved throughout the process. A variation of JAD is rapid application development (RAD) which creates applications more quickly by using fewer formal methodologies and reusing software components. When implemented correctly, JAD saves time and money on projects.

Uploaded by

Siobhan Roche
Copyright
© Attribution Non-Commercial (BY-NC)
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
0% found this document useful (0 votes)
48 views2 pages

Benefits of JAD

JAD (Joint Application Design) is a methodology developed in the late 1970s that involves clients in collaborative workshops called JAD sessions to design and develop applications. It was created by Chuck Morris and Tony Crawford of IBM. JAD is thought to lead to faster development times and greater client satisfaction than traditional development approaches because the client is involved throughout the process. A variation of JAD is rapid application development (RAD) which creates applications more quickly by using fewer formal methodologies and reusing software components. When implemented correctly, JAD saves time and money on projects.

Uploaded by

Siobhan Roche
Copyright
© Attribution Non-Commercial (BY-NC)
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
You are on page 1/ 2

JAD (Joint Application Design) is a methodology that involves the client or end user in the design and development

of an application, through a succession of collaborative workshops called JAD sessions. Chuck Morris and Tony Crawford, both of IBM, developed JAD in the late 1970s and began teaching the approach through workshops in 1980. The JAD approach, in comparison with the more traditional practice, is thought to lead to faster development times and greater client satisfaction, because the client is involved throughout the development process. In comparison, in the traditional approach to systems development, the developer investigates the system requirements and develops an application, with client input consisting of a series of interviews. A variation on JAD, rapid application development (RAD) creates an application more quickly through such strategies as using fewer formal methodologies and reusing software components. When done properly JAD saves time and money.

JAD can be successfully applied to a wide range of projects, including the following: New systems Enhancements to existing systems System conversions Purchase of a system Project Characteristics

Not all projects, however, are good candidates for JAD. An appropriate project exhibits at least some of the following characteristics: Involves many groups of users whose responsibilities cross traditional department or division boundaries Is considered critical to the future success of the organization Involves willing users Is a first-time project for the organization Has a troubled project history or relationship between the systems and user organizations

Benefits of JAD

The JAD approach provides the following benefits: Accelerates design Enhances quality Promotes teamwork with the customer Creates a design from the customer's perspective Lowers development and maintenance costs

JAD achieves these benefits because of the following factors: 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.

Ref: <http://www.umsl.edu/~sauterv/analysis/488_f01_papers/rottman.htm>

You might also like