Wednesday, July 3, 2013

JAD and RAD



JAD Advantage and Disadvantage

4 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.

4 Many companies find, however, that JAD allows key users to participate effectively in the requirements modeling process. When users participate in the system development process, they are more likely to feel a sense of ownership in the results, and support for the new system.

4 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.




Rapid Application Development


      Rapid application development (RAD) is 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 requirement model, the end product of RAD is the new information system.

     RAD is complete methodology, with a four-phase life cycle that parallels the traditional SDLC phases. Companies use RAD to reduce cost and development time, and increase the probability of success.



RAD Phases and Activities

The RAD model consists of four phases: requirements planning, user design, construction, and cutover).  There is continuous interaction between the user design and construction phases.



1.  Requirement PlanningThe requirements planning phase combines elements of the systems planning and systems analysis phase of the SDLC.

Ø Users, managers, and IT staff members discuss and agree on business needs, project scope, constraints, and system requirements. The requirements planning phase ends when the team agrees on the key issues and obtains management authorization to continue.

2.  User Design. During the user design phase, users interact with systems analysts and develop models and prototype that represent all system processes, outputs, and inputs.

Ø The RAD group, or sub groups typically use a combination of JAD techniques and CASE tools to translate user needs into working models. User design is a continuous, interactive process that allows users to understand, modify, and eventually approve working model of the system that meets their needs.

3.  Construction. The construction phase focuses on program and application development tasks similar to the SDLC.

Ø In RAD, however, users continue to participate and still can suggest changes or improvements as actual screens or reports are developed.

4.  Cutover. The cutover phase resembles the final tasks in the SDLC implementations phase, including data conversion, testing, and changes over to the new system, and user training.

Ø Compared with traditional methods, the entire process is compressed. As a result, the new system is built, delivered, and placed in operation much sooner.



RAD Objectives

Ø 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.





RAD Advantages and Disadvantages

4 The primary advantage is that system can be developed more quickly with significant cost savings.

4 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, but the corporate and long-term objective for the system might not be met.

4 Another potential disadvantage is that the accelerated time cycle might allow less time to develop quality, consistency, and design standards.

4 RAD can be an attractive alternative, however, if an organization understands the possible risks.

2 comments: