Sanjoy Barman Ray

Understand the proposed project Ensure that the project will support business requirements Build a solid foundation for system development

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

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

JAD is a team-oriented technique for factfinding and requirements modeling In other words, JAD is a popular fact-finding technique that brings users into the development process as active participants

A JAD team may include users, managers, IT professionals who works together to identify and document requirements for a new system The objective is to analyze the existing system, work on potential solutions, and agree on requirements for the new system.

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 user requirements for the new system

JAD Advantages and Disadvantages

Advantages
Allows key users to participate effectively When properly used, JAD can result in a more accurate statement of system requirements, a better understanding of common goals, and a stronger commitment to the success of the new system More expensive and can be cumbersome if the group is too large relative to the size of the project

Disadvantages

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

1. 2. 3. 4. 5.

Systems development methodology created to radically decrease the time needed to design and implement information systems radically. Five key factors
Extensive user involvement Joint Application Design sessions Prototyping Integrated CASE tools Code generators

19.1 0

RAD is a general strategy rather than a single methodology Goals

Traditional SDLC steps are followed, but phases are combined Iteration is limited to design and development phases

To analyze a business process rapidly To design a viable system solution through intense cooperation between users and developers To get the finished application into the hands of the users quickly

19.1 2

User involvement is key to success Prototyping is conducted in sessions similar to Joint Application Design (JAD) Prototyping screens become screens within the production system CASE tools are used to design the prototypes

19.1 3

Martins pillars of RAD

Four pillars
Tools People Methodology Management

Conversion to RAD within organization should be done with a small group of well-trained and dedicated professionals, called a RAD cell Over time, cell can grow until RAD is the predominant approach of the information systems unit

19.1 4

McConnells pillars of RAD (continued)

Development mistakes
Weak personnel
Employees that are not as well trained in skills necessary for success of the project Occurs when developers believe that a new and untried technology is all that is needed to cure the ills of any development project More and more features are added to a system over course of development Project may have more requirements than needed

Silver-bullet syndrome

Feature creep

Requirements gold-plating

19.1 5

Software tools
Case tools can be used for
Prototyping Code generation Example: COOL:Gen

Visual Development Environments

Visual Basic Delphi

19.1 6

Martins RAD Life Cycle

Systems requirement determination is done in context of a discussion of business problems and business areas User Design
End users and IS professionals participate in JAD workshops CASE tools are used to support prototyping

Construction

Cutover

Designer creates code using code generator End user validates screens and other aspects of design New system is delivered to end users

19.17

Inprise/Borlands Delphi
Requirements

U.S. Navy Fleet Modernization

Move from three character-based systems to a unified, GUI-based system based on a single database Support for rapid prototyping Promise of re-use of components System developed in 6 months Estimated development savings of 50 percent New system resulted in immediate 20 percent savings due to reduced maintenance costs

Reasons for choosing Delphi Outcome

19.18

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 data on-line

19.19

VisualAge for Java

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

Programming modules that expand the functions of the Web server Embedded code run from client browser Three months of research Three months of coding Three months of testing

Nine months to completion

19.20

The three broad phases to RAD are :

Requirements planning. RAD design workshop. Implementation.

2005 Pearson Prentice Hall

Kendall & Kendall

621

Users and analysts meet to identify objectives of the application or system Oriented toward solving business problems

2005 Pearson Prentice Hall

Kendall & Kendall

622

 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 and workflow to users. Users respond to actual working prototypes. Analysts refine designed modules based on user responses.

2005 Pearson Prentice Hall

Kendall & Kendall

623

As the systems are built and refined, the new systems or partial systems are tested and introduced to the organization. When creating new systems, there is no need to run old systems in parallel.

2005 Pearson Prentice Hall

Kendall & Kendall

624

RAD is a team-based technique that speeds up information systems developments. Like JAD, RAD uses a group approach, but goes much further. RAD resembles a condensed version of the entire SDLC, with users involved every step of the way.

Requirement planning
User Design

Users, managers, and IT staffs agree upon business needs, project scope and system requirements Interact with users, build models and prototypes, and conduct intensive JAD-type sessions Program and application development, coding, integration and system testing Data conversion, full scale testing, system changeover, user training

Construction

Cutover

RAD Phases and Activities

RAD tools are used to generate screens and exhibit the overall flow of the application. Users approve the design and sign off on the visual model. Implementation is less stressful because users helped to design the business aspects of the system.

2005 Pearson Prentice Hall

Kendall & Kendall

628

 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.

RAD is used when:

2005 Pearson Prentice Hall

Kendall & Kendall

629

Extreme programming (XP) takes good systems development practices to the extreme.

2005 Pearson Prentice Hall

Kendall & Kendall

630

The four values of extreme programming are:

Communication. Simplicity. Feedback. Courage.

2005 Pearson Prentice Hall

Kendall & Kendall

631

The five XP principles are:

Providing rapid feedback. Assuming simplicity. Changing incrementally. Embracing change. Encouraging quality work.

2005 Pearson Prentice Hall

Kendall & Kendall

632

 2005 Pearson Prentice Hall

Kendall & Kendall

633

The four basic activities of XP are:

Coding. Testing. Listening, to the programming partner and customer. Designing.

2005 Pearson Prentice Hall

Kendall & Kendall

634

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

A system requirement is a characteristic or feature that must be included in an information system to satisfy business requirements and be acceptable to users.
Outputs Inputs Processes Performance Controls

The inventory must produce a daily report The purchasing system must provide supplier with up-to-date specifications The Web site must report online volume statistics

Each input form must include date, time, product code, customer number, and quantity Manufacturing employees must swipe their ID cards

The students records system must allow record access by either students name or number The video rental system must not execute new rental transaction for customers who have overdue tapes

The system must support 25 users online simultaneously Response must not exceed four seconds The system must be operational seven days a week, 365 days a years

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

A systems ability to handle increased business volume and transactions in the future.

Answer Who, What, When, How and Why?

Interviews Document Review Observation Questionnaires and Surveys Research

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

Scrum is an Agile approach that has an emphasis 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.

2005 Pearson Prentice Hall

Kendall & Kendall

646