Rapid Prototype Blog

Posts Tagged ‘software development methodology’

What is rapid application development (RAD) and how can it help user interface designers?

Rapid application development is a software development methodology that emphasizes minimal planning and rapid prototyping.  It is an act first, think later method. The planning takes place through the fast flow of creative ideas and problem solving that take place during the rapid prototyping process.  Thus, rapid application development is very flexible and leaves room for endless improvements and a quicker software writing process.  In this article I will take a look at the history of the method as well as the pros and cons of using the strategy in user interface design.

Rapid application development: history and implementation

Rapid application development was introduced as a software design method in 1991 by James Martin, an IT consultant and Pulitzer Prize nominated author.  Since its inception, rapid application development (RAD) has evolved from strictly iterative development and prototypes to a method that can be defined more broadly, encompassing the use of various software frameworks and web application frameworks.

Rapid application development is a method that is designed first and foremost to deliver systems fast.  Before venturing down this speedy path in a user interface design project, make sure that you are using it to develop an interface design that can be delivered quickly.  For example, it is probably not the best method for designing a complex air traffic control system, but would work well if you are revamping an extant e-Commerce site.  Here are a few criteria that can help you discern whether or not to implement the method for the design of your new user interface:

•    Project Scope: a project with a scope that is narrow and well-defined is suitable for rapid application development, but a project with a broad and obscure scope is not.

•    Project Data: Project data that already exists (and therefore does not need to be analyzed) is suitable for RAD, but project data that needs to be generated and analyzed is not.

•    Project Decisions: Project decisions that can be made quickly by a small group of people who are always on-call are suitable for RAD, project decisions that must be made by a wide-range of people who are not always available are not.

•    Project Team: A small project team (about six or less) is suitable for RAD, a large product team (more than six) is not.

The abovementioned criteria can serve as a guideline to help you discern whether or not rapid application development is the right user interface design method for you, but it is ultimately your choice. If you do decide that rapid application development is a good fit, a typical RAD process can be broken down into the following steps:

•    Select a team: you should choose a team of designers/collaborators who will be able to give timely, efficient input and feedback.

•    Analysis: Assess your project goals and understand what you need to do, why you need to do it, and how you need to do it to realize the goal of your project.

•    Design workshop: Create a design workshop during which you and your team can rapidly iterate, prototype and conduct usability tests on each updated version of your user interface design until it has reached a point of satisfaction that aligns itself with your goals. At this point you are ready for implementation. The process of RAD is relatively unstructured so as not to impede the creative flow, but make sure you can work many uninterrupted hours—RAD is not for the faint of heart.

Pros and Cons of rapid application development in user interface design projects

Rapid application development can be a very effective user interface design method if used for the right reasons and under the right circumstances.  RAD promotes a collaborative and creative environment in which all stakeholders can take part in a very detailed project.  RAD can give fast results and bring forth successful new ideas that might have seemed too risky to use in a more deliberate process. However, RAD also has its drawbacks.  Its use is contingence upon a strong, cohesive team that does not have time constraints.  Its quick nature can allow for many errors and does not promote organization or well-thought-out solutions.  However, experience shows that the consequences of RAD pitfalls can generally be avoided if you carefully assess whether or not it is an appropriate method for your project—careful assessment at the beginning can open the floodgates to rapid success.

Related User Interface Prototyping Articles

Once you are in the software development field, you will come across a variety of development methodologies followed while developing any software project. This methodology refers to processes used to plan the strategies for software development.

A software methodology used in one project may or may not be suited to another project. Each software methodology may have its own strengths and drawbacks. There are a variety of software approaches developed over time, which are well-matched to specific kind of projects. Read on to learn a few points on the various methodologies developed.

§         Waterfall Method: In waterfall method, which is the oldest software development methodology the software development stages are performed in a sequential manner to ensure the quality and reliability of the software. Even though this model provides complete documentation, over quality software and also the work is being done in stages, the waterfall methodology is cumbersome and slow in approach. The basic principles applied here is that the project is divided into different phases, which are sequential in nature. There is stress given on planning and implementation of the overall system and a firm control is maintained on the overall life of the project.

§         Prototyping Method: Software prototyping refers to creation of incomplete models of the software program during the software development process which may be different from the final product. Prototyping helps the software users to evaluate the software during the design stage before actually trying them out. In this model, the users are thoroughly involved in the software development process, which increases their acceptance of the final implementation. It also helps the users to understand the business problem, which is necessary to avoid solving the wrong problem.

Incremental Development Method: Incremental software development methodology involves breaking the project into small section, so as to make the change simplified during the development process.

§         Spiral Methodology: In this methodology various steps are staged for manifold deliveries. Spiral methodology works on the principle that the team is able to start small and help from the trial and error method.

§         Rapid application development: Rapid application development (RAD) refers to speedy development and delivery of best quality results at a relatively low investment cost.Rapid application development is asoftware development methodology that involves nominal planning, thus the software can be written in much shorter time. RAD takes benefit of preset tools and techniques to streamline the process of building information systems. Rapid Application Development has four important features:  methodology, people, management, and tools.Development would be slow, If any one of these ingredients is insufficient.

§         Extreme Programming: Extreme Programming is based on values of simplicity, admiration, communication, advice, and guts. In this changes are implemented as per the customer’s suggestion.

More Prototyping Based Methodology Articles