Glossary


Joint Application Development (JAD)

A-B-C- D-E-F- G-H-I- J-K-L- M-N-O- P-Q-R- S-T-U- V-W-X- Y-Z

Identification

Joint Application Development (JAD)

Definitions/Uses

2001
Reference /Scacchi, 2001/ Process Models in Software Engineering

Definition/
Use Joint Application Development (JAD)
is a technique for engaging a group or team of software developers, testers, customers, and prospective end-users in a collaborative requirements elicitation and prototyping effort /Wood, 1995/. JAD is quintessentially a technique for facilitating group interaction and collaboration. Consultants often employ JAD or external software system vendors who have been engaged to build a custom software system for use in a particular organizational setting. The JAD process is based on four ideas:

People who actually work at a job have the best understanding of that job

People who are trained in software development have the best understanding of the possibilities of that technology

Software-based information systems and business process rarely exist in isolation - they transcend the confines of any single system or office and effect work in related departments. People working in these related areas have valuable insight on the role of a system within a larger community

The best information systems are designed when all of these groups work together on a project as equal partners

Following these ideas, it should be possible for JAD to cover the complete development life cycle of a system. The JAD is usually a 3 to 6 month well-defined project, when systems can be constructed from commercially available software products that do not require extensive coding or complex systems integration. For large-scale projects, it is recommended that the project be organized as an incremental development effort, and that separate JAD's be used for each increment /Wood, 1995/. Given this formulation, it is possible to view open source software development projects that rely on group email discussions among globally distributed users and developers, together with internet-based synchronized version updates / Fogel, 1999/, as an informal variant of JAD.

Rationales The author classifies JAD as one of the Software Product Development Model

2001
Reference	/Scacchi, 2001/ Process Models in Software Engineering
Definition/ Use	Joint Application Development (JAD) is a technique for engaging a group or team of software developers, testers, customers, and prospective end-users in a collaborative requirements elicitation and prototyping effort /Wood, 1995/. JAD is quintessentially a technique for facilitating group interaction and collaboration. Consultants often employ JAD or external software system vendors who have been engaged to build a custom software system for use in a particular organizational setting. The JAD process is based on four ideas: People who actually work at a job have the best understanding of that job People who are trained in software development have the best understanding of the possibilities of that technology Software-based information systems and business process rarely exist in isolation - they transcend the confines of any single system or office and effect work in related departments. People working in these related areas have valuable insight on the role of a system within a larger community The best information systems are designed when all of these groups work together on a project as equal partners Following these ideas, it should be possible for JAD to cover the complete development life cycle of a system. The JAD is usually a 3 to 6 month well-defined project, when systems can be constructed from commercially available software products that do not require extensive coding or complex systems integration. For large-scale projects, it is recommended that the project be organized as an incremental development effort, and that separate JAD's be used for each increment /Wood, 1995/. Given this formulation, it is possible to view open source software development projects that rely on group email discussions among globally distributed users and developers, together with internet-based synchronized version updates / Fogel, 1999/, as an informal variant of JAD.
Rationales	The author classifies JAD as one of the Software Product Development Model

Identification

Definitions/Uses

See also