Information System Analysis

and Design
Lec 4
 Joint Application Design(JAD)
• In the late 1970s, systems development personnel at IBM developed a new
process for collecting information system requirements and reviewing
system designs. The idea behind JAD is to structure the requirements
determination phase of analysis and the reviews that occur as part of the
design. Users, managers, and systems developers are brought together for a
series of intensive structured meetings run by a JAD session leader.
list of typical JAD participants

1- JAD session leader

2- Users

3-Sponsor

4-Systems analysts

5-Scribe

6- IS staff
JAD sessions are usually held in special-purpose rooms where participants sit around
horseshoe-shaped tables These rooms are typically equipped with whiteboards (possibly
electronic, with a printer to make copies of what is written on the board). Other audiovisual
tools may be used, such as magnetic symbols that can be easily rearranged on a whiteboard,
flip charts, and computer-generated displays. Flip-chart paper is typically used for keeping
track of issues that cannot be resolved during the JAD, or for those issues requiring additional
information that can be gathered during breaks in the proceedings.
When the JAD is over, the session leader and her assistants must prepare a report that
documents the findings in the JAD and then circulate it among users and analysts.
 JAD Advantages and Disadvantages

• Compared with traditional methods, JAD is more expensive and can be

cumbersome if the group is too large relative to the size of the project. Many
companies find, however, that JAD allows key users to participate effectively in
the requirements modeling process. When users participate in the systems
development process, they are more likely to feel a sense of ownership in the
results, and support for the new system. 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
Computer-Aided Software Engineering (CASE)
Tools
1- Diagramming tools that enable system process, data, and control
structures to be represented graphically.
2- Computer display and report generators that help prototype how systems
“look and feel” to users.
3- Analysis tools that automatically check for incomplete, inconsistent, or
incorrect specifications in diagrams, forms, and reports.
4- A central repository that enables the integrated storage of specifications,
diagrams, reports, and project management information.
5-Documentation generators that help produce both technical and user
documentation in standard formats.
6- Code generators that enable the automatic generation of program and
database definition code directly from the design documents, diagrams,
forms, and reports.
 Rapid Application Development(RAD)

• Prototyping, CASE, and JAD are key tools that support rapid application
development (RAD).
• Is a team-based technique that speeds up information systems
development and produces a functioning information system
• Like JAD, RAD uses a group approach, but goes much further. While the end
product of JAD is a requirements model, the end product of RAD is the new
information system.
• RAD relies heavily on prototyping and user involvement. The RAD process
allows users to exaV mine a working model as early as possible, determine if
it meets their needs, and suggest necessary changes.
 RAD Objectives
RAD Advantages and Disadvantages
• The main objective of all RAD approaches is to cut development time and
expense by involving users in every phase of systems development. Because
it is a continuous process, RAD allows the development team to make
necessary modifications quickly,
• as the design evolves, in times of tight corporate budgets.
• A disadvantage is that RAD stresses the mechanics of the system itself and
does not emphasize the company’s strategic business needs. The risk is that
a system might work well in the short term.
 Agile Methodologies

A family of development methodologies characterized by short iterative cycles and

extensive testing; active involvement of users for
establishing, prioritizing, and verifying requirements; and a focus on small teams of
talented, experienced programmers.
share three key principles:
(1) a focus on adaptive rather than
predictive methodologies.
(2) a focus on people rather than
roles.
(3) a self-adaptive process.
 Agile Method Advantages and Disadvantages
• Agile, or adaptive, methods are very flexible and efficient in dealing with
change. They are popular because they stress team interaction and reflect a
set of community-based values. Also, frequent deliverables constantly
validate the project and reduce risk.

• However, some potential problems exist. For example, team members need
a high level of technical and interpersonal skills. Also, a lack of structure and
documentation can introduce risk factors. Finally, the overall project may be
subject to significant change in scope as user requirements continue to
evolve during the project