Joint Application Development (JAD) Methodology

The Joint Application Development (JAD) methodology aims to involve the client in the design and development of an application. This is accomplished through a series of collaborative workshops called JAD sessions. In contrast to the Waterfall approach, JAD is thought to lead to shorter development times and greater client satisfaction, both of which stem from the constant involvement of the client throughout the development process. On the other hand, with 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. Rapid application development (RAD), a variation on JAD, attempts to create an application more quickly through strategies that include fewer formal methodologies and reusing software components.

Rapid Application Development (RAD) Methodology:
RAD (rapid application development) proposes that products can be developed faster and of higher quality by: y y y y y Using workshops or focus groups to gather requirements. Prototyping and user testing of designs. Re-using software components. Following a schedule that defers design improvements to the next product version. Keeping review meetings and other team communication informal.

Rapid application development (RAD): This system employs tools, techniques, and methodologies designed to speed application development. Rapid application development makes extensive use of joint application development (JAD) for data collection and requirements analysis. JAD involves group meetings in which users, and IS professionals work together to analyze existing systems, propose possible solutions, and define the requirements of a new or modified system. JAD often uses Group support systems (GSS) software to foster positive group interactions, while suppressing negative group behavior.

Sign up to vote on this title
UsefulNot useful