Rapid application development as one alternative software development method

The main purpose of all system development methods is to provide a system that can meet the expectations of the users, but often in the development of a system does not involve the users of the system directly, so this causes the information system made far from the expectations of users who can result in such a system though acceptable but users are refuse to use it.

---

Contributor:
Husna Mustika Sari

---

Definition RAD

Rapid Application Development (RAD) is one method of developing an information system with a relatively short time. For the development of a normal information system takes at least 180 days, but by using RAD method a system can be completed only within 30-90 days.

When RAD is implemented, users can become part of the overall system development process by acting as decision makers at every stage of development. RAD can generate a system quickly because the system developed can meet the desires of the users so as to reduce the time for re-development after the implementation phase.

Weakness of conventional methods

The weaknesses found in conventional methods are as follows:

1. There is a long time limit from the beginning of the system creation until the consumer can use the system.
2. If the process of developing a system takes a long time then the needs of consumers on the system will experience changes in line with changes in business processes undertaken by consumers.
3. The developed system will have no benefit if it has not been completely resolved.

The reason why to choose RAD methods

In choosing the RAD method should consider the following reasons:

Poor reasons

1. When using RAD just to save on development costs system. Requires a team that understands well about cost management. If not, then the cost will be larger.
2. When using RAD just to save some development time system. Requires a team that understands timely management. If not, then the time required will be longer.

Good reasons

1. To obtain an acceptable design by consumers and can be developed easily.
2. To provide restrictions on a system so as not to change.
3. To save time, and if possible save cost and produce a quality product.

 

Schedule vs economics vs. quality products

There are several things that need to be considered in developing a system using RAD method based on schedule, economy and product quality such as development model, negotiation, and objectives.

Development Model

At the time of developing a system must be faced with 3 choices of models that is:

Efficient Development (development model that prioritizes the schedule, economy and product quality in a balanced manner).

1. Schedule: faster than average
2. Economy: the cost is cheaper than the average
3. Product: better than average quality

Sensible RAD (development model that prioritizes the schedule compared to economy and product quality).

1. Schedule is faster than average
2. Economy is the cost slightly cheaper than average
3. The product is slightly better than average quality

All-out RAD (development model that prioritizes the schedule at the expense of economy and product quality).

1. Schedule is fastest
2. Economy cost is more expensive than average
3. The product quality is more lowest than average

 

Negotiation

1. To produce a system that suits the needs and wants of the user it is necessary to conduct a negotiation and not just prioritize the schedule.
2. RAD can be done quite successfully if the consumer is able to negotiate to determine the economy or quality of a system.
3. RAD can achieve better success if consumers are able to negotiate to determine the economy and quality of a system.
4. However, the thing to note is that the definition of quality negotiations does not mean that consumers can accept more of more mistakes, but what is meant by negotiations is that the products received have a disadvantage either on the use, completeness of facilities or less efficient.
5. but what is meant by negotiations is that receive the disadvantages of products either on the use, completeness of facilities or efficient

Purpose

By using RAD then there is one or more of the following objectives that can not be achieved simultaneously:

1. Possibility of a small error, because the developer has no right to change the components used in developing a system.
2. The highest level of customer satisfaction, because the secondary needs of consumers must be sacrificed so that a system can be completed on schedule.
3. Development costs are the cheapest, because by using existing components can cause a greater cost when compared to developing its own components.

Phases on RAD

The RAD method has 3 main stages as shown in Figure 1.

Requirement Planning

At this stage, users and analysts do some sort of meeting to do identify the purpose of the application or system and identify the information needs to achieve the objectives. At this stage the most important thing is the involvement of both parties, not just the approval of the proposals that have been made. The rest, user involvement is not just from one level in an organization, but some level of organization so that the information needed for each user can be met well. In addition, it can also coordinate with the Chief Information Office (CIO) or part of strategic planners primarily to develop a Web-based E-commerce application to get more detailed information about the goals of an organization. This kind of meeting is often called Joint Aplication Development.

Design Workshop

At this stage, the design user and analyst to do the design process and make improvements if there is still a mismatch between them. For this stage the activation of the user involved is crucial to achieve the goal, because the user can directly comment if there is a mismatch on the design. Usually, users and analysts come together and sit on a circular table where each person can see each other without a hitch.

Whenever possible, each user is assigned one computer connected to each other, so that each can see the design created and comment directly. This is often called Group Decision Support System (GDSS). In some cases, this GDSS is an ideal step, because users and analysts can approve the design that is made to be followed by the programmer in making the prototype of the app in question by instantly displaying to the user the results quickly.

It this stage of the design takes a few days, but it can take longer, depending on the size of the system created. At that time interval, the user can give response to the system that has been developed for further improvement. Thus the process of developing a system takes a fast time.

Implementation

After the design of the system to be made has been approved by both the user and analyst, then at this stage the programmer develops the design into a program. After the program is completed either partly or as a whole, then do the process of testing the program whether there is an error or not before applied to an organization. At this time the user can respond to the system that has been made and approval of the system.

The most important thing is that the involvement of the user is needed so that the system developed can give satisfaction to the user, and in addition, the old system does not need to run in parallel with the new system.

Overall stages

Based on the stages mentioned above, the main process of developing a system using RAD method is as follows:

1. Developers create prototypes based on predefined needs
2. Designers make an assessment of the prototype
3. Users tested the prototype and provided input on the underlying needs.
4. Users and developers conduct meetings to provide assessment of the products together, adjust the needs and provide comments if necessary changes.
5. All the needs of the system and the changes that occur are "timeboxed" with two possibilities: The first is changes that can not be accommodated as planned should be eliminated. And the second, if necessary, secondary needs are eliminated.

Condition affecting RAD

At the time of using RAD methods need to consider the conditions that can support and inhibit the success of a system.

Supporting Conditions

Some conditions that can support the success of RAD are as the following:

1. System running alone (standalone).
2. Performance of the system is not the most important factor.
3. Distribution of narrow products.
4. Limited scope.
5. Reliability of the system is not the most important factor.
6. Requires technology that is not too new (more than 1 year).
7. System can be broken down into smaller parts.

Inhibiting Conditions

Some conditions that may hinder the success of RAD are as follows:

1. The system must be able to run simultaneously with the old system.
2. Supporting components are very rare to obtain.
3. Optimal performance is the most important factor.
4. Distribution of products that are wide.
5. Wide scope.
6. When used to create the Operating System, which requires a reliable system.
7. The system can not be broken down into smaller parts.

ADVANTAGES AND DISADVANTAGES OF RAD

In using RAD there are some things to note especially related to the advantages and disadvantages.

Advantages of RAD

1. Some of the advantages of using the RAD method are as follows:
2. Buying a new system make it possible to save more money instead of developing it yourself.
3. The delivery process becomes easier, this is because the process of making more use of script deductions.
4. Easy to observe, because it uses a prototype model, so users better understand the system developed.
5. More flexible, because the developer can do the redesign process at the same time.
6. Can reduce the writing of complex code because it uses wizard.
7. Increased user engagement as it is part of the team as a whole.
8. Able to minimize errors using the help tools (CASE tools).
9. Accelerate overall system development time as it tends to ignore quality.
10. Display more standard and comfortable with the help of supporting software.

Disadvantages of RAD

Some of the disadvantages of using the RAD method are as follows:

1. By making a purchase may not be able to save costs compared with developing their own.
2. Requires a separate cost to buy supporting equipment such as software and hardware.
3. Difficulty in making measurements of process progress.
4. Less efficient because when doing the coding by hand can be more efficient.
5. The accuracy becomes reduced because it does not use a formal method of coding.
6. More errors occur when only prioritizing speed compared to cost and quality.
7. Many facilities are reduced due to the limited time available.
8. The system is difficult to apply elsewhere.
9. Unnecessary facilities sometimes need to be included, as they use ready-made components, so this makes costs increasing as the price of the more complete components becomes more expensive.

Conclusion

Based on the above discussion, then in using the RAD method can be summed up as follows:

1. The use of RAD should be used appropriately, because otherwise it will cause losses such as increasingly bloated costs and longer time.
2. The use of RAD methods should be used with regard to time and cost aspects in a balanced way, not to be prioritized one by one.
3. As an alternative to the SDLC RAD can be used as a reference to develop an information system that is superior in terms of speed, accuracy and lower costs.
4. By using RAD, the user's involvement becomes increasingly which can ultimately increase user satisfaction with the developed system.

Reference

Kendal & Kendal. Systems Analysis and Design Fifth Edition. Prentice-Hall International, Inc. 2002.
Jeffrey A. Hoffer, Joey F. George, Joseph S. Valacich. Modern Systems Analysis and Design Second Edition. Addison-Wesley. 1997.
Jeffrey L. Whitten, Lonnie D. Bentley, Kevin C. Dittman. Systems Analysis and Design Methods. McGraw-Hill. 2001.
Ramez El Masri, Shamkant B. Navache. Fundamental of Database Systems. The Benjamin/Cummings Publishing Company,Inc. 1994.
Raymond McLeod, George Schell. Management Information Systems 8/e. Prentice-Hall, Inc. 2001.