![]() |
subject > process > requirements gathering > Joint Application Development |
![]() ![]() | ||||
Joint Application Development (JAD) | ||||
subject | fact |
Joint Application Development | has definition An approach to defining requirements, in which all the stakeholders meet intensively for several days in a secluded location | ![]() |
has benefit the energy generated by intense JAD sessions can often shorten the period required to work out the requirements from several months to several days | ![]() | |
has result a written requirements document | ![]() | |
involves developers meeting with customers and users in a secluded location for a period of three to five days to define the requirements | ![]() | |
is a subtopic of 4.6 - Some Techniques for Gathering and Analyzing Requirements | ![]() | |
is abbreviated as JAD | ![]() | |
is related to brainstorming | ![]() | |
is a kind of requirements gathering | ![]() | |
may include regular brainstorming, and negotiation of specific wording | ![]() | |
takes place away from the offices of any of the participants so that nobody is interrupted by any other activity | ![]() | |
requirements gathering | is part of requirements and specification | ![]() |
process | see also process^2 | ![]() |