Collaboration and then building software is the key power which drives technology and its innovation. JAD is a model for software development that augments the stakeholders' association in cycles of software development. Its life cycle has been adopted for areas of the dynamic software development method. It collects business and system requirements while building a new information system for any organization or enterprise. In this chapter, you will learn about the JAD model in detail.
The Joint Application Development (JAD) Approach
JAD (Joint Application Development) is a software development approach that engages the client and/or the end-users to design and develop the system. This model was designed and put forward by Dr. Chuck Morris and Dr. Tony Crawford of IBM, who propose this model in the late 1970s. As compared to other primitive SDLC models, the Joint Application Development model leads to faster progression of the system development, which has better client approval.
This model, furthermore, is vast when it comes to agile delivery wherein the software products need to be developed as well as shipped in short iterations depending on agreements among the industrial as well as industry stakeholders, which are termed as Minimum Viable Product (MVP).
Phases of JAD Model
Since you have become familiar with the JAD concept, it is time to know about its phases and how the model's design and development approach works:
- Define Specific Objectives: The facilitator, in partnership with stakeholders, sets all the objectives and a list of items, which is then distributed to other developers and participants to understand and review. This objective contains elements like the scope of this projected system, its potential outcome, technical specifications required, etc.
- Session Preparation: The facilitator is solely responsible for this preparation, where all relevant data is collected and sent to other members before time. For better insight, research is carried out to know the system requirement better and gather all the necessary information for development.
- Session Conduct: Here, the facilitator is accountable for identifying those issues that have to be working out to make the system error-free. Here the facilitator will serve as a participant but will not have a say regarding any information.
- Documentation: After the product is developed, the records and published documents are put forward into the meeting so that the stakeholders and consumers can approve it through the meeting.
Benefits of Using JAD Model
- Improved Delivery Time: The time required to develop a product using the JAD model is lesser and more efficient than that of other traditional models.
- Cost Reduction: Efficiently analyzing the requirements and facts with business executives and stakeholders will make less effort to develop the system. Hence, less cost will be required for the entire development process.
- Better Understanding: Since the entire requirement is analyzed by business executives, followed by a cautious choice of developers and team members who can professionally interact with each other better usually helps understand product development better.
- Improved Quality: Since all the key decision-makers and stakeholders of the project are involved in the development of the project, so there is the least chance of error, and hence the product quality becomes better and more accurate.