JAD-RAD

  • Upload
    sbr11

  • View
    213

  • Download
    0

Embed Size (px)

Citation preview

  • 7/29/2019 JAD-RAD

    1/46

    Sanjoy Barman Ray

  • 7/29/2019 JAD-RAD

    2/46

    Understand the proposed project Ensure that the project will support business

    requirements

    Build a solid foundation for systemdevelopment

  • 7/29/2019 JAD-RAD

    3/46

    Analytical skills Identify problem, evaluate the key elements, and

    develop a useful solution

    Interpersonal skills Work with, balance conflicting needs of users, and

    communicate effectively

  • 7/29/2019 JAD-RAD

    4/46

    Joint Application Development (JAD) Rapid Application Development (RAD)

  • 7/29/2019 JAD-RAD

    5/46

    JAD is a team-oriented technique for fact-finding and requirements modeling

    In other words, JAD is a popular fact-findingtechnique that brings users into thedevelopment process as active participants

  • 7/29/2019 JAD-RAD

    6/46

    A JAD team may include users, managers, ITprofessionals who works together to identifyand document requirements for a new system

    The objective is to analyze the existingsystem, work on potential solutions, andagree on requirements for the new system.

  • 7/29/2019 JAD-RAD

    7/46

    JAD Participants and Roles JAD participants should be insulated from the

    distraction of day-to-day operations

    Objective is to analyze the existing system, obtain

    user input and expectations, and document userrequirements for the new system

  • 7/29/2019 JAD-RAD

    8/46

    JAD Advantages and Disadvantages Advantages

    Allows key users to participate effectively

    When properly used, JAD can result in a moreaccurate statement of system requirements, abetter understanding of common goals, and astronger commitment to the success of the newsystem

    Disadvantages More expensive and can be cumbersome if the

    group is too large relative to the size of theproject

  • 7/29/2019 JAD-RAD

    9/46

    Advantages More accurate statement of system requirements

    Better understanding of common goals

    Stronger commitment to the success of the new

    system

    Disadvantages More expensive

    Can be cumbersome if the group is too large

  • 7/29/2019 JAD-RAD

    10/46

    Systems development methodologycreated to radically decrease the timeneeded to design and implementinformation systems radically.

    Five key factors1. Extensive user involvement2. Joint Application Design sessions3. Prototyping

    4. Integrated CASE tools5. Code generators

    19.10

  • 7/29/2019 JAD-RAD

    11/46

  • 7/29/2019 JAD-RAD

    12/46

    RAD is a general strategy rather than asingle methodology

    Goals To analyze a business process rapidly To design a viable system solution through

    intense cooperation between users anddevelopers To get the finished application into the

    hands of the users quickly Traditional SDLC steps are followed, but

    phases are combined Iteration is limited to design anddevelopment phases

    19.12

  • 7/29/2019 JAD-RAD

    13/46

    User involvement is key to success

    Prototyping is conducted in sessionssimilar to Joint Application Design (JAD)

    Prototyping screens become screenswithin the production system

    CASE tools are used to design theprototypes

    19.1

    3

  • 7/29/2019 JAD-RAD

    14/46

    Martins pillars of RAD Four pillars

    Tools People Methodology Management

    Conversion to RAD within organization shouldbe done with a small group of well-trainedand dedicated professionals, called a RAD cell

    Over time, cell can grow until RAD is the

    predominant approach of the informationsystems unit

    19.1

    4

  • 7/29/2019 JAD-RAD

    15/46

    McConnells pillars of RAD (continued) Development mistakes

    Weak personnel Employees that are not as well trained in skills necessary for

    success of the project

    Silver-bullet syndrome Occurs when developers believe that a new and untried

    technology is all that is needed to cure the ills of anydevelopment project

    Feature creep

    More and more features are added to a system over course ofdevelopment

    Requirements gold-plating Project may have more requirements than needed

    19.1

    5

  • 7/29/2019 JAD-RAD

    16/46

    Software tools Case tools can be used for

    Prototyping

    Code generation

    Example: COOL:Gen Visual Development Environments

    Visual Basic

    Delphi

    19.1

    6

  • 7/29/2019 JAD-RAD

    17/46

    Martins RAD Life Cycle Systems requirement determination is done in

    context of a discussion of business problems andbusiness areas

    User Design End users and IS professionals participate in JAD

    workshops CASE tools are used to support prototyping

    Construction Designer creates code using code generator End user validates screens and other aspects of design

    Cutover New system is delivered to end users

    19.17

  • 7/29/2019 JAD-RAD

    18/46

    Inprise/Borlands Delphi U.S. Navy Fleet Modernization

    Requirements Move from three character-based systems to a unified,

    GUI-based system based on a single database Reasons for choosing Delphi

    Support for rapid prototyping

    Promise of re-use of components

    Outcome System developed in 6 months

    Estimated development savings of 50 percent

    New system resulted in immediate 20 percent savingsdue to reduced maintenance costs

    19.18

  • 7/29/2019 JAD-RAD

    19/46

    Inprise/Borlands Delphi (continued) First National Bank of Chicago

    Electronic Federal Tax Payment System

    Delphi enabled rapid prototyping and development

    10 months of development time

    125 programmers

    250 million rows of data and 55 gigabytes of dataon-line

    19.19

  • 7/29/2019 JAD-RAD

    20/46

    VisualAge for Java Comdata

    Modular Over the Road System (MOTRS) IBM Global Services chosen as vendor Servlets

    Programming modules that expand the functions of theWeb server

    Applets Embedded code run from client browser

    Nine months to completion Three months of research Three months of coding Three months of testing

    19.20

  • 7/29/2019 JAD-RAD

    21/46

    Kendall & Kendall 2005 Pearson Prentice Hall

    6-

    21

    The three broad phases to RAD are : Requirements planning.

    RAD design workshop.

    Implementation.

  • 7/29/2019 JAD-RAD

    22/46

    Kendall & Kendall 2005 Pearson Prentice Hall

    6-

    22

    Users and analysts meet to identify objectivesof the application or system

    Oriented toward solving business problems

  • 7/29/2019 JAD-RAD

    23/46

    Kendall & Kendall 2005 Pearson Prentice Hall

    6-

    23

    Design and refine phase. Use group decision support systems to help users

    agree on designs.

    Programmers and analysts can build and show

    visual representations of the designs andworkflow to users.

    Users respond to actual working prototypes.

    Analysts refine designed modules based on user

    responses.

  • 7/29/2019 JAD-RAD

    24/46

    Kendall & Kendall 2005 Pearson Prentice Hall

    6-

    24

    As the systems are built and refined, the newsystems or partial systems are tested andintroduced to the organization.

    When creating new systems, there is no needto run old systems in parallel.

  • 7/29/2019 JAD-RAD

    25/46

    RAD is a team-based technique that speedsup information systems developments.

    Like JAD, RAD uses a group approach, butgoes much further.

    RAD resembles a condensed version of theentire SDLC, with users involved every step ofthe way.

  • 7/29/2019 JAD-RAD

    26/46

    Requirement planning Users, managers, and IT staffs agree upon business needs,

    project scope and system requirements

    User Design Interact with users, build models and prototypes, and

    conduct intensive JAD-type sessions Construction

    Program and application development, coding, integrationand system testing

    Cutover Data conversion, full scale testing, system changeover, user

    training

  • 7/29/2019 JAD-RAD

    27/46

    RAD Phases and Activities

  • 7/29/2019 JAD-RAD

    28/46

    Kendall & Kendall 2005 Pearson Prentice Hall6-28

    RAD tools are used to generate screens andexhibit the overall flow of the application.

    Users approve the design and sign off on thevisual model.

    Implementation is less stressful becauseusers helped to design the business aspectsof the system.

  • 7/29/2019 JAD-RAD

    29/46

    Kendall & Kendall 2005 Pearson Prentice Hall6-29

    RAD is used when: The team includes programmers and analysts who

    are experienced with it. There are pressing reasons for speeding up

    application development. The project involves a novel ecommerce application

    and needs quick results. Users are sophisticated and highly engaged with

    the goals of the company.

  • 7/29/2019 JAD-RAD

    30/46

    Kendall & Kendall 2005 Pearson Prentice Hall6-30

    Extreme programming (XP) takes goodsystems development practices to theextreme.

  • 7/29/2019 JAD-RAD

    31/46

    Kendall & Kendall 2005 Pearson Prentice Hall6-31

    The four values of extreme programming are: Communication.

    Simplicity.

    Feedback.

    Courage.

  • 7/29/2019 JAD-RAD

    32/46

    Kendall & Kendall 2005 Pearson Prentice Hall6-32

    The five XP principles are: Providing rapid feedback.

    Assuming simplicity.

    Changing incrementally.

    Embracing change. Encouraging quality work.

  • 7/29/2019 JAD-RAD

    33/46

    Kendall & Kendall 2005 Pearson Prentice Hall6-33

  • 7/29/2019 JAD-RAD

    34/46

    Kendall & Kendall 2005 Pearson Prentice Hall6-34

    The four basic activities of XP are: Coding.

    Testing.

    Listening, to the programming partner and

    customer. Designing.

  • 7/29/2019 JAD-RAD

    35/46

    Advantages The system can be developed more quickly with

    significant cost savings

    Disadvantages RAD does not emphasize the companys strategic

    business needs

    Risks in term of long-term objective, quality,consistency, and efficiency

  • 7/29/2019 JAD-RAD

    36/46

    A system requirement is a characteristic orfeature that must be included in aninformation system to satisfy businessrequirements and be acceptable to users. Outputs

    Inputs

    Processes

    Performance

    Controls

  • 7/29/2019 JAD-RAD

    37/46

    The inventory must produce a daily report The purchasing system must provide supplier

    with up-to-date specifications

    The Web site must report online volumestatistics

  • 7/29/2019 JAD-RAD

    38/46

    Each input form must include date, time,product code, customer number, and quantity

    Manufacturing employees must swipe their IDcards

  • 7/29/2019 JAD-RAD

    39/46

    The students records system must allowrecord access by either students name ornumber

    The video rental system must not execute

    new rental transaction for customers whohave overdue tapes

  • 7/29/2019 JAD-RAD

    40/46

    The system must support 25 users onlinesimultaneously

    Response must not exceed four seconds

    The system must be operational seven days aweek, 365 days a years

  • 7/29/2019 JAD-RAD

    41/46

    The system must provide log-on security An employee record must be updated by a

    member of human resource department The system must maintain separate levels of

    security for users and administrators

  • 7/29/2019 JAD-RAD

    42/46

    A systems ability to handle increasedbusiness volume and transactions in thefuture.

  • 7/29/2019 JAD-RAD

    43/46

    Answer Who, What, When, How and Why? Interviews

    Document Review

    Observation

    Questionnaires and Surveys Research

  • 7/29/2019 JAD-RAD

    44/46

    Record information as soon as you obtain it Use the simplest record method possible Record your findings in such a way that they

    can be understood by someone else

    Organize your documentation

  • 7/29/2019 JAD-RAD

    45/46

  • 7/29/2019 JAD-RAD

    46/46

    Scrum is an Agile approach that has anemphasis on teamwork.

    Team success is of primary importance. Individual success is secondary.

    The team works within a strict time frame. The project leader has some but not much

    influence on detail.