Collaborative Design Through Joint Application Development

UPI Study › Courses › Software Engineering › Free lessons › Lesson 4.2 Free with a free account

Collaborative Design Through Joint Application Development

Software Engineering · Chapter 4: Rapid Development, Testing, and Software EvolutionSection 4.2 · lesson 25 of 1036 min · free with a free account

← Speed-Driven Development: The RAD ApproachNext lesson: Guiding Products Forward with the Stage-Gate Process →

Earn 3 college credits for Software EngineeringRecommended for credit by NCCRS · Computer Science 301 · self-paced · one payment, lifetime access
Enroll in Software Engineering · $250 →Download the syllabus (PDF)

In this lesson

Working out requirements together, in the same room.

  • Define JAD, and the problem it is designed to solve
  • Identify the roles in a JAD workshop, and what each contributes
  • Describe the stages a workshop moves through
  • Explain why working together settles decisions faster

Transcript

Everything said in the video, section by section (836 words). Read along, or search it.

Rapid Development, Testing, and Software Evolution

Collaborative Design Through Joint Application Development

What if the people who know what a system should do, and the people who will build it, worked out the requirements together? In the same room, instead of passing documents back and forth for weeks. That is the idea behind Joint Application Development. This section covers who takes part, how a session runs, and why it is faster.

The Ordinary Way

1 Stakeholder at a Time

Picture a team gathering requirements the ordinary way. They interview one stakeholder, and write up notes. Then they interview the next stakeholder, and write up more notes. Only afterward do they discover the problem. The second stakeholder wants something that quietly contradicts what the first one asked for. Untangling that conflict now takes another round of meetings. And the project has barely started.

Definition

Everyone Into 1 Room

Joint Application Development, or J A D, is a structured approach built to avoid exactly that problem. Rather than collecting input one stakeholder at a time, and reconciling it later, it brings everyone together. The stakeholders, the intended users, and the developers all join a single, facilitated workshop. There, requirements and design decisions are worked out together, in real time. And everyone who needs to weigh in is already in the room.

Table 1

Who's in the Room

A J A D workshop only works if the right mix of people is present, and each person's role is clear before it starts. The facilitator runs the session, keeps the discussion on track, and makes sure no single voice dominates. The scribe records decisions and open questions as they happen, so the facilitator's attention stays on the room. Stakeholders and business users explain what the system needs to accomplish, for the people who will rely on it. Developers and technical representatives explain what is feasible, and surface trade-offs while decisions are still being made. And the sponsor holds final authority to resolve a disagreement the group cannot settle on its own. The facilitator deserves special attention. They have no stake in the outcome, so they can focus entirely on keeping the discussion productive.

The 5 Stages

How a Workshop Runs

A J A D workshop is not an unstructured meeting. It follows a recognizable sequence, designed to reach decisions rather than simply discuss options. First, preparation. The facilitator defines the session's scope, and confirms the right people are invited. Second, the opening. The group agrees on ground rules, and confirms what the session is meant to accomplish. Third, the working sessions. Stakeholders, users, and developers work through the questions together, while the scribe captures decisions. Fourth, review and closure. The group reviews what was agreed, and confirms a shared understanding before the session ends. And fifth, the follow-up document. The scribe's record is published as the agreed account of the session's decisions.

Think About It

Why Not Just End the Meeting?

Here is a question to think about. Why include a review and closure stage at all? Why not just end when the discussion winds down? Without that step, people might leave the room having understood the same decision differently in their own heads. A dedicated review moment makes the group confirm, out loud, that everyone agreed on the same thing. Only then does it become the official record.

Figure 2

Serial Interviews vs. 1 Workshop

This figure compares the two ways of working. On the left, serial interviews. Each stakeholder is interviewed separately, one after another. The decisions are spread across many separate conversations, and a conflict only appears when someone compares the notes, often weeks later. On the right, a J A D workshop. The facilitator, the scribe, the stakeholders, the developers, and the sponsor all meet in one session. The same decisions get settled together, and a conflict is visible at once.

Why It's Faster

Conflicts Surface While They Can Be Solved

So the advantage is not simply that people talk together instead of separately. It is that conflicts and misunderstandings surface immediately, while everyone who can resolve them is still in the room. In the serial approach, a conflict between two stakeholders is invisible until someone compares their separate notes. Resolving it then means scheduling yet another round of conversation. In a workshop, the same conflict is visible the moment both stakeholders describe what they want, and the facilitator can work through it on the spot. That is why a well-run workshop can compress weeks of scattered meetings into one focused session, or a short series of them.

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. Joint Application Development brings stakeholders, users, and developers into a facilitated workshop, to define requirements and design together. The facilitator runs the workshop and keeps discussion on track, without taking a stake in the outcome. The scribe records the workshop's decisions and open questions as they occur. And the sponsor is the person with the authority to resolve a disagreement, when the group cannot settle it on its own.

Key Takeaways

What to Carry Forward

To pull this together. Joint Application Development gathers stakeholders, users, and developers into one structured, facilitated workshop. It depends on clear roles. A facilitator, a scribe, stakeholders and users, developers, and a sponsor. It moves through a defined sequence. Preparation, opening, working sessions, review and closure, and a follow-up document. And bringing everyone together surfaces conflicts immediately, where serial interviews hide them until the notes are compared.

About Software Engineering at UPI Study

Software Engineering (Computer Science 301) is a self-paced online course of 103 video lessons in 15 chapters, from process models and agile to requirements, design, user interfaces, reliability, security and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take Software Engineering with UPI Study

How professional software gets builtSoftware Engineering covers how teams turn requirements into working, maintainable software: process models, agile, requirements, design, testing, reliability and project management. It is a core course in computer science and software degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Software Engineering carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Collaborative Design Through Joint Application Development

What is Joint Application Development (JAD)?
Joint Application Development is a structured approach that brings stakeholders, intended users, and developers together in a single facilitated workshop to define requirements and design decisions in real time. Instead of collecting input one stakeholder at a time and reconciling it later, everyone who needs to weigh in is in the same room while decisions are made.
What are the roles in a JAD session?
A JAD workshop typically includes a facilitator, a scribe, stakeholders and business users, developers, and a sponsor. The facilitator runs the session neutrally and keeps it on track. The scribe records decisions and open questions. Users explain what the system must accomplish, developers explain what is feasible, and the sponsor resolves disagreements the group cannot settle.
What are the steps of a JAD workshop?
A JAD workshop usually moves through five stages: preparation, opening, working sessions, review and closure, and a follow-up document. The facilitator first sets scope and invites the right people. The group agrees on ground rules, works through the questions together, confirms a shared understanding of what was agreed, and then publishes the scribe's record as the official account.
Why is JAD faster than interviewing stakeholders one by one?
JAD is faster because conflicts surface immediately, while everyone who can resolve them is still in the room. With serial interviews, a contradiction between two stakeholders stays hidden until someone compares the notes, often weeks later, and fixing it takes another round of meetings. A well-run workshop can compress weeks of scattered meetings into one focused session.

About the Software Engineering course

How many college credits is Software Engineering?
Software Engineering (Computer Science 301) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Software Engineering cost and what is included?
$250, paid once, with lifetime access: all 103 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Software Engineering take?
It is self-paced with no deadlines. The 103 lessons total about 11 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Software Engineering.

103 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Software Engineering →Download the syllabusEvery course with PRO →
Software Engineering
3 credits · NCCRSEnroll →