optional · CSS study notes
Joint Application Development (JAD) (2017)
CSS CS Optional — Paper-I, Section-B, Topic V.
🔑 Definition
- Structured requirements-gathering technique — facilitated workshops ("JAD sessions") with business + technical staff together, in real time.
📌 Roles in a JAD Session
- Facilitator/session leader — runs workshop, stays neutral
- Scribe — records decisions/open issues
- Business/end users — represent requirements
- IT/technical staff — assess feasibility live
- Executive sponsor — resolves disputes, confirms decisions
📌 Why It's Used
- Shortens requirements timeline vs. individual interviews
- Resolves conflicting requirements immediately, in the room
- Increases stakeholder buy-in
📌 Relation to RAD
- JAD = requirements-gathering front-end that feeds RAD's rapid build.
- Commonly paired in exam questions: "how does JAD support RAD?"
⚠️ MCQ Trap
- JAD = requirements-elicitation technique, NOT a full SDLC model like RAD.
📜 Past-Paper Questions & MCQs (CSS 2016–2026)
2017 · Paper-I · Q4(a) · part of 8 marks
JAD characteristics: structured workshops where users, managers, analysts and developers define requirements and design together, guided by a neutral facilitator and a scribe. It gives fast agreement, fewer misunderstandings and early user buy-in. Full answer on Evolutionary Model (2017).