Joint Application Design (JAD), Essay Example

Introduction

Joint Application Design is a process of management which permits Information System to function more efficiently with users in not a longer time frame. The Joint Application Design has confirmed to be an efficient system for building the user obligation to the accomplishment of the systems regarding the application via their energetic contribution in the requirements analysis and the system design specification (Corbin, 1991). The power of Joint Application Design is in the incorporation of group and behavioral dynamics system within the arrangement of a thoroughly methodology that is engineered. On the other side, workshops are effectual at all stages including business area, application, and enterprise and implementation project management. Nowadays workshops are used for strategic Information System plans, re-engineering, detailed system design, and strategic business planning and project management.

Joint Application Design and the Traditional Method of Fact-Finding

The Joint Application Design is considered to have lead to quick periods of development and superior client satisfaction, in contrast with the more traditional practice, since the customer is engaged throughout the process of development (Dennis, Hayes, Daniel, 1999). In contrast, in the traditional loom to the systems improvement, the developer, goes through the system obligations and develops an application, with customer contribution including of a sequence of interviews.

Potential Advantages of Joint Application Design

• Joint Application Design reduces time and costs related with necessities elicitation development.
• Joint Application Design helps convey experts together offering them a place to share their thoughts, and understand other people’s views and enlarge the sense of ownership project.
• The methods of Joint Application Design completion are well known as it is, and it can be with no trouble applied by any group.

Potential Disadvantages of Joint Application Design

• The chosen team to take part in Joint Application Design workshop must comprise of the employees proficient to offer input on most, if not all, essential parts of the dilemma.
• Facilitator as a leveling and inspirational strength has to ensure that all those who have participated have a chance to offer their ideas, opinions and thoughts.

References

Christel, M., Kang, K. (1987). “Issues in Requirements Elicitation”. Carnegie Mellon Software Engineering Institute.

Corbin, D. (1991).”Team Requirements Definition: Looking For a Mouse and Finding an Elephant”. Journal of Systems Management, May 1991, Volume 42, Issue 5, Page 28.

Dennis, A., Hayes, G., Daniel Jr., R. (1999). “Business Process Modeling With Group Support Systems”. Journal of Management Information Systems, Spring, Pages 115-142.