ABSTRACT
IBM coined the term joint application design (JAD) in 1970, but some experts prefer joint application development. The cost and time associated with data collection, analysis, and requirements definition can be significantly reduced by using the JAD technique. JAD is particularly suited to projects that face tight time and scheduling constraints and it is an excellent choice for developing a system from scratch. JAD is used to determine the system requirements during the problem definition phase of the system development life cycle. The members of a JAD team consist of end users from the relevant business functional areas, managers from those same functional areas, systems analysts or information consultants, and appropriate systems specialists. The JAD team is divided into several brainstorming sub-teams, and a friendly competition is launched to see which sub-team can list the most ideas. Following a brainstorming session, the JAD team divides into sub-groups to investigate the ideas on the various lists.
