Joint Application Development：联合应用开发.ppt

Joint Application Development Katie Abbott Ryan Abbott Agenda: Joint Application Development Introduction Systems Development Lifecycle Origin Evolution Other Names Basic Components of a JAD Session Guidelines for a Successful JAD Automated JAD Examples Summary Introduction What is Joint Application Development? Joint Application Development, or JAD, is a process originally developed for designing a computer-based system. It brings together business area people (end users) and IT (Information Technology) professionals in a highly focused workshop. The advantages of JAD include a dramatic shortening of the time it takes to complete a project. It also improves the quality of the final product by focusing on the up-front portion of the development lifecycle, thus reducing the likelihood of errors that are expensive to correct later on. Introduction (Cont.) JAD centers around a structured workshop session. Participants get together in a room to discuss the problem/project. Everyone hears what the rest of the group has to say. JAD can eliminate many of the problems with traditional meetings. Meetings are not well regarded as a productive forum. JAD turns meetings into workshops. They are less frequent More structured, and productive An agenda provides the structure The facilitator directs the process Visual aids clarify concepts being discussed and the group dynamics, with constant feedback, stimulates creativity Introduction (Cont.) JAD Purpose: to define the project, design a solution, and monitor the project until it reaches completion. JAD Philosophy: The JAD process is based on four simple ideas: People who actually do a job have the best understanding of that job. People who are trained in information technology have the best understanding of the possibilities of that technology. Information systems and business processes rarely exist in isolation -- they transcend the confines of any single system or office and effect work in related departments. Peo