One of the fastest, easiest, and most effective ways to define Level of Quality (LOQ) for a repetitive drawing task is to develop a prototype; a full working solution. Prototypes make sense in any project because they ultimately save time.

Prototyping and iterative design have a reputation for being difficult to manage. The keys to managing a prototyping effort are becoming clear, however; they include knowing what you want to learn from the prototype, access to rapid prototyping techniques, and end-user involvement in development of the prototype. This article provides a framework for prototyping within the development process.

This report presents an overview of technology and literature relating to the creation and use of software system prototypes. In addition to an annotated bibliography of recent prototyping literature, a technology framework, taxonomy, and series of classifications are provided. The intent of this report is to provide a basic roadmap through the available literature and technology

In this article, we first look at some important characteristics of prototypes. Then we discuss the general problems of software development (a big part of prototyping) and the reason for the emergence of "agile" methods for software development. We next consider the use of agile methods for developing complex software products and identify some shortcomings. Finally, we observe that some of the shortcomings for product development are not relevant to prototype development and reach a conclusion on agile methods and prototyping.

Ruby on Rails has raised the bar in terms of rapid development of data-driven Web sites. The JRuby project is making Ruby faster and more scalable than ever. One of the great advantages to running Rails on the Java Virtual Machine is that you can leverage other Java libraries, like the Apache Derby embedded database. The combination of Derby, JRuby, and Rails allows for rapid prototyping of dynamic Web applications. Learn how to use these technologies together to help you prototype your next great idea.

Usability testing based on paper prototypes and early versions of the software were added to the agile development process for the second application release resulting in a significant reduction of usability related rework. The paper prototype became a tangible representation of the project vision that was used in many ways that contributed to the resounding success of the project.

Software provided as an online service, rather than a desktop-based application, continues to grow in popularity at a exponential rate. I've been involved with a number of businesses centered around SaaS. And during that time, I've assembled 10 key elements specific to software development that can determine whether an SaaS application becomes successful and — in many cases — whether it makes it to release. These tips are intended to provide an enlightening perspective on SaaS-based development.