70 likes | 108 Views
Learn about Joint Application Development (JAD) and Rapid Application Development (RAD) techniques, with insights on Agile development & Extreme Programming (XP) for efficient systems analysis and design. Discover the benefits, drawbacks, and conditions that support the use of JAD in organizational settings.
E N D
Week 15: Wrap-up and OtherAdvanced Design Methods IFS 410: Advanced Analysis and Design
Strategies for Systems Analysis and Design • Structured Analysis and Design • Object-Oriented Analysis (OOA) and Design (OOD)
JAD & RAD • Joint Application Development (JAD) is a technique that complements other systems analysis and design techniques by emphasizing participative development among system owners, users, designers, and builders. • Rapid Application Development (RAD) is the merger of various techniques (especially the data-driven information engineering) with prototyping techniques and joint application development techniques to accelerate systems development.
Joint Application Development • Sometimes Joint Application Design • JAD participants typically include: • Facilitator – facilitates discussions, enforces rules • End users – 3 to 5, attend all sessions • Developers – 2 or 3, question for clarity • Tie Breaker – Senior manager. Breaks end user ties, usually doesn’t attend • Observers – 2 or 3, do not speak • Subject Matter Experts – limited number for understanding business & technology
Conditions that support the use of JAD • User groups are restless and want something new; not a standard solution • The organizational culture supports joint problem-solving behaviors among multiple levels of employees • Analysts forecast that the number of ideas generated via one-to-one interviews will not be plentiful • Organizational workflow permits the absence of key personnel during a two-to-four-day block of time
Pro’s and Con’s of JAD • Pro’s • Time savings in interview • Rapid development • Improved sense of ownership • Creative development • Con’s • Time commitment from all participants • Inadequate preparations and follow-ups will result in less than satisfactory design • Organizational culture may hinder effort required to be productive
Agile development & XP • Agile software development: • calls for keeping code simple, testing often, and delivering small, functional bits of the application as soon as they're ready. The focus is to build a succession of parts, rather than delivering one large application at the end of the project. • eXtreme programming (XP): • Extreme Programming (XP) is a pragmatic approach to program development that emphasizes business results first and takes an incremental, get-something-started approach to building the product, using continual testing and revision.