New Analysis and Design Techniques

Introduction:-

 In 1977 Chuck Morris of IBM conceived JAD as a method for gathering the requirements for geographically distributed systems.(4)

 In 1980, IBM Canada adopted and refined the approach.(4)

 In 1984, IBM formalized JAD by publishing the JAD Overview pamphlet.(4)

 By the late 1980s until now, many companies were implementing facilitated JAD workshops for analysis and design.(4)


Definition

 JAD is a short for Joint Application Development which is a process that accelerates the design of a computer-based system.

 Brings together business area people (users) and IT professionals in a highly focused workshop. (4)

 JAD Is a technique for rabid requirements gathering by merging the system users, owners and analysts in one room to discuss the system for about 4 – 8 hours sessions per day for one day to couple of weeks. (2)


Planning JAD:-

 The success of any JAD session is dependent upon proper planning and effectively carrying out that plan.

 Selecting a Location for JAD Sessions:
 JAD sessions should be conducted at a location that is away from company workplace. And its must be a conference room.

 Selecting JAD Participants:
 Developers, Analysts, observer and others.

 Preparing a JAD Session Agenda:
 The agenda indicates issues to be discussed during the session and amount of time allocated to each item.


Participants:

 JAD sessions must contain:

– Facilitator: facilitates discussions, enforces rules
– End users: 3 to 5, attend all sessions
– Developers: 2 or 3, question for clarity
– Scribe: to record every thing in the discussions
– Observers: 2 or 3, do not speak
– Subject Matter Experts: limited number for understanding business & technology.

JAD Benefits:-

 The JAD approach provides the following benefits:
– Accelerates design.
– Enhances quality.
– Promotes teamwork with the customer.
– Creates a design from the customer's perspective.
– Lowers development and maintenance costs.


 JAD achieves these benefits because of the following factors:
– The decision makers are all present.
– Differing views are handled immediately.
– Most errors are caught in the Analysis and Design stages.
– The system design reflects the user's desires.
– Assumptions are documented and understood.


Disadvantages:-

 Systems analysts always have to keep in mind that none of techniques they use are a full-proof way to acquire the information, neither is JAD.

 Many systems analysts feel that JAD can be ineffective if not used correctly.

 The Main Disadvantages for JAD are
- Wrong problem can be addressed; wrong people can be invited to participate in the sessions.
- Not all participants can explain there opinions either they did not get the chance to or the lake of understanding what they said from others. And this problem may lay on the facilitator of the session who must give all participants a chance to discuss any point in the agenda.



Conclusion:-

 JAD is used as a technique for gathering business system requirements and is typically used in the early stages of a systems development project.

 The purpose of JAD is to bring together ISM and end users in a structured workshop setting; to extract consensus requirements based on the system nature.

 This is accomplished by using a trained JAD facilitators and customized, planned agendas to assist the participant in arriving at complete, high quality requirements.

 Experience has shown that the JAD process substantially reduces development time, costs and errors.

My Opinion:-

 First of all the strength and efficiency in functionality for any system depends on the will development and design that also depends on the complete and efficient system requirements gathering and analysis.

 And I see that the amount and completeness of the requirements that yields from JAD technique makes it easy and simple to build a full functional system based on those requirements.

 So for me JAD is the best methodology where system analysis and development should be applicable in a flexible way.


References:-

1. Hoffer, George and Valacich. Modern Systems Analysis and Design. Prentice Hall 2002

2. Marchand, Davenport and Dickson. Mastering Information Management. Prentice Hall 2000.

3. PCS Networks. Joint Applications Development

4. Joint Application Development (JAD) for Requirements Collection and Management White Paper by Alan Cline / Carolla Development (www.carolla.com)