JAD & RAD Process
JAD & RAD Process
JAD & RAD Process
(RAD)
Here's an example of how Joint Application Development (JAD) can be used in a software
development project:
Let's say a company wants to develop a new customer relationship management (CRM) system to
improve their sales processes. They decide to adopt JAD to involve all relevant stakeholders in the
development process and ensure that the system meets their needs effectively.
1. Planning: The project team, including business analysts, developers, and end-users, collaboratively
plan the JAD session. They define the objectives, select participants, and schedule the session.
2. JAD Session: The JAD session takes place in a workshop setting. It involves representatives from
different departments, such as sales, marketing, and customer support, who will use the CRM
system. The session is facilitated by a JAD facilitator who guides the discussions.
3. Requirements Gathering: During the JAD session, participants engage in brainstorming, group
discussions, and interactive exercises to identify and prioritize the functional and non-functional
requirements of the CRM system. The facilitator encourages open communication, captures ideas,
and ensures all perspectives are considered.
4. Analysis and Design: Based on the requirements identified in the JAD session, the development
team analyzes the gathered information and designs the architecture, data model, and user interface
of the CRM system. The design decisions are made in collaboration with the JAD participants, who
provide feedback and validation.
5. Prototyping: Using the information gathered in the JAD session, the development team creates a
prototype of the CRM system. The prototype is presented to the JAD participants for their feedback
and suggestions. The iterative process continues until a satisfactory prototype is achieved.
6. Development and Testing: Once the prototype is approved, the development team proceeds with
coding and building the CRM system. The development is conducted in iterative cycles, with each
cycle focusing on a specific set of features. Regular JAD meetings are held to review progress, provide
feedback, and address any emerging issues. Testing is performed at each iteration to ensure the
system meets the specified requirements.
7. Deployment: After the development and testing phases are completed, the CRM system is
deployed to the production environment. The JAD participants are involved in the user acceptance
testing (UAT) phase, where they validate the system's functionality and provide final approval for its
release.
By involving stakeholders through the JAD process, this example demonstrates how collaboration and
iterative feedback can help ensure that the CRM system meets the needs and expectations of the
end-users effectively.
Here's an example of how Rapid Application Development (RAD) can be used in a software
development project:
Let's consider a scenario where a company wants to develop a mobile application for tracking fitness
activities. They decide to adopt the RAD methodology to quickly deliver a functional application
while incorporating user feedback throughout the development process.
1. Requirements Gathering: The development team conducts initial discussions with key
stakeholders, including fitness enthusiasts, trainers, and potential users of the application. They
gather high-level requirements such as tracking different types of exercises, setting goals, and
providing performance analytics.
2. Prototyping: Based on the initial requirements, the development team creates a basic prototype of
the mobile application that includes core functionalities such as user registration, exercise tracking,
and basic analytics. The prototype is presented to a select group of users for early feedback.
3. User Feedback and Iterative Development: The prototype is shared with the target users who try
out the application and provide feedback on its usability, features, and overall experience. The
development team collects this feedback and iteratively improves the application based on the users'
suggestions.
4. Rapid Development Cycles: The RAD methodology emphasizes short development cycles. The
development team breaks down the application into smaller modules or features and works on them
in parallel. Each module is developed, tested, and integrated into the application during rapid
development cycles, typically lasting a few weeks or even days.
5. Continuous Integration and Testing: As each module is developed, it is integrated into the evolving
application, and integration tests are performed to ensure proper functionality and compatibility.
Automated testing techniques and tools are used to expedite the testing process and identify any
defects or issues.
6. Incremental Deployment: Once a sufficient number of features and improvements have been
implemented and tested, the development team deploys the application incrementally, making it
available to a larger user base. This allows for real-world usage and further user feedback for ongoing
enhancements.
7. Continuous Improvement: Throughout the RAD process, the development team actively
incorporates user feedback, addresses reported issues, and introduces new features based on
evolving requirements. This iterative and incremental approach ensures that the application is
continuously improved and aligned with the users' needs.
By utilizing the RAD methodology in this example, the development team can deliver a fitness
tracking application quickly while actively involving users in the development process. The iterative
nature of RAD allows for rapid feedback and enhancement cycles, resulting in a more user-centric
and feature-rich application.