The Joint Application Development (JAD) process is a technique for developing business requirements for software projects. The purpose of JAD is to bring together the technology team and the business stakeholders in a structured workshop setting to define consensus based business requirements. This is accomplished by using a trained workshop facilitator and customized, planned agendas to assist the participants in decision making and creating high quality requirements. Experience has shown that the JAD process substantially reduces time, cost and errors.
Project Scope Definition
- Use Case Diagram/Mgt. Perspective
- Charter Document
Business Requirements Definition
- Process Flows, HL Use Cases, & Glossary
- CRCs Role Playing or
- Object Models & Interaction Diagrams
- Detailed Use Cases & Mock-ups
- Static Object Models
- Functional Specification and Data Dictionary
- Release Plan
- JAD – Final Prototype Review & Release
- Project Plan
Design the system and database
- Server Object Model, Sequence Diagram
- Design Document
Why use JAD?
JAD is a proven method that offers time and cost savings:
- 25% – 50% of time saved for requirements gathering
- 25% – 33% time saved over the entire project or 3-4 months out of a yearlong project
Not just time and cost savings using JAD:
- JAD and prototyping used together give 95% of the user-required functionality
- Getting it right the first time
- No redesign
- Consensus based requirements
- Key measure is customer satisfaction
- Provides a tool for communication between developer and customer
Industry studies have shown that 56% of the problems with software are due to poor requirements gathering while only 7% are due to poor coding. 82% of a company’s maintenance effort is due to poor requirements definition while only 1% of its maintenance effort is for fixing code problems
Why do facilitated sessions work?
They create a forum for conflict resolution, creative solutions, consensus and commitment. JAD provides a tool for clear communication and requirements definition. Documentors are available in the workshop to capture the group’s information creating a requirements document that can be distributed. Prototypes are reviewed and discussed.
What is RAD?
Rapid Application Development (RAD) is a process that speeds the delivery of functionality to end-users by segmenting software into pieces for delivery rather than delivering all of the software functionality in one large implementation. It is an iterative process utilizing a spiral methodology and is also customer driven following an evolutionary process using continuous application engineering in a time-boxed fashion with a dedicated professional team. The goal of the iterative approach is to reduce the time between requests and delivery of Business Application Software. Some of the primary characteristics of RAD projects are:
- There is a strict deadline for basic functionality
- Projects can be released in increments
- Techniques such as time-boxing, dedicated teams and focus sessions are used
- Business users are involved throughout the project and JAD is used
- Total project time is usually 3 – 6 months
What is UML?
An object-oriented graphical modeling language for specifying and communicating the structure and dynamics of software systems. Pierson uses the Unified Modeling Language (UML) and the Unified Process standards. It is used to create business models for requirements analysis, analysis models and design models.