‭Rapid Application Development:‬ ‭ DM is an example of a method that focuses on process control step-by-step‬ S ‭elaboration of the total functionality of an information system (the 'waterfall' model).‬ ‭ owever, the commonly used waterfall method is becoming increasingly popular due to the‬ H ‭use of modern tools increasingly replaced by a strategy called 'incremental development'. This‬ ‭strategy does not attempt to realize the entire desired functionality of an information system in‬ ‭one go, but does this in steps („increments‟) that are first embedded in the organization before‬ ‭development is continued. The end goal therefore does not have to be known in detail initially.‬ ‭W e often work with a prototype that is continuously refined.‬ I‭n the first steps, the most important functionalities are developed in such a way that‬ ‭they are already usable for the organization. In each subsequent step, the number of‬ ‭functionalities is expanded and/or refined. The information system therefore gradually‬ ‭grows in both breadth and depth of functionality. An example of such an approach is‬ ‭the Rapid Application Development (RAD) method. While SDM is based on a strict‬ ‭phasing and activity-oriented approach, a more prototyping-like approach such as‬ ‭RAD is also possible.‬ ‭RAD is also applied in phases:‬ ‭1.‬‭Preparation phase (planning and analysis):‬ ‭Objectives, scope of work, responsibilities and authorities are defined in close‬ ‭c ollaboration between the RAD team and management. A global overview of the‬ ‭steps (increments) to be taken in further elaboration is also provided‬ ‭2.‬‭Design and realization of the increments (design‬‭and build):‬ ‭The next phases consist of realizing the globally defined increments. The‬ ‭functionality of the increment is designed and built in close collaboration‬ ‭between the users and the developers. Determination of the information needs‬ ‭and design and construction of the software are a repetitive process within this‬ ‭phase. The RAD approach is based on modern development techniques and‬ ‭tools with which applications can be realized in a short period of time. The‬ ‭activities that are carried out within SDM to realize the software are of course‬ ‭also carried out at RAD, but not in such a step-by-step structured manner, but,‬ ‭as already noted, in a more iterative manner.‬ ‭2.‬‭Controlling a RAD project:‬ ‭RAD teams are small and the total project generally has little formal structuring in‬ ‭the form of phases, etc. The lack of a formal structure is compensated for by‬ ‭deploying well- qualified users (full-time, sufficient subject matter knowledge,‬ ‭etc.) and developers (generalists). inICT area with specific skills) with its own‬ ‭mandate.‬ ‭ rototyping (RAD: Rapid application development):‬ P ‭Quickly build and implement until the 'perfect' prototype is created.‬ ‭Time boxing‬ ‭ he time-box technique is often used in combination with RAD. A time-box is a fixed‬ T ‭period of time after which the project team must deliver a working system. If necessary,‬ ‭the project team must limit time or limit the number of functions to be performed by the‬ ‭system to be completed on time. This is to avoid the common mistake of wanting to‬ ‭specify too much in a prototype.‬ ‭Proponents‬‭of‬‭this‬‭method‬‭argue‬‭that‬‭it‬‭is‬‭better‬‭to‬‭have‬‭a‬‭working‬‭system‬‭quickly‬‭and‬ ‭improve‬‭it‬‭gradually‬‭than‬‭to‬‭try‬‭to‬‭think‬‭of‬‭everything‬‭at‬‭once.‬‭Teams‬‭in‬‭a‬‭RAD‬‭project‬ ‭work in a time-box for an average of 2 to 4 months.‬