乔伊·F·乔治-现代系统分析与设计（第6版）hoffer_msad6e_ch06.pptVIP

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Copyright ? 2011 Pearson Education, Inc. Publishing as Prentice Hall * Chapter 6 JAD (Cont.) JAD Participants: Session Leader: facilitates group process Users: active, speaking participants Managers: active, speaking participants Sponsor: high-level champion, limited participation Systems Analysts: should mostly listen Scribe: record session activities IS Staff: should mostly listen Copyright ? 2011 Pearson Education, Inc. Publishing as Prentice Hall * Chapter 6 JAD (Cont.) End Result Documentation detailing existing system Features of proposed system Copyright ? 2011 Pearson Education, Inc. Publishing as Prentice Hall * Chapter 6 CASE Tools During JAD Upper CASE tools are used Enables analysts to enter system models directly into CASE during the JAD session Screen designs and prototyping can be done during JAD and shown to users Copyright ? 2011 Pearson Education, Inc. Publishing as Prentice Hall * Chapter 6 Using Prototyping During Requirements Determination Quickly converts requirements to working version of system Once the user sees requirements converted to system, will ask for modifications or will generate additional requests Copyright ? 2011 Pearson Education, Inc. Publishing as Prentice Hall * Chapter 6 Using Prototyping During Requirements Determination (Cont.) Most useful when: User requests are not clear. Few users are involved in the system. Designs are complex and require concrete form. There is a history of communication problems between analysts and users. Tools are readily available to build prototype. Copyright ? 2011 Pearson Education, Inc. Publishing as Prentice Hall * Chapter 6 Using Prototyping During Requirements Determination (Cont.) Drawbacks Tendency to avoid formal documentation Difficult to adapt to more general user audience Sharing data with other systems is often not considered Systems Development Life Cycle (SDLC) checks are often bypassed Copyright ? 2011