Skip to main content
 
Tying a Sensible Knot: A Practical Guide to State-Local Information Systems



Chapter 3. Best Practices

Use prototypes to ensure understanding and agreement about design


Prototyping your system as you develop it offers an excellent way for the project team and customers to see the design-in-progress and help refine and improve the system as it evolves.

The development environment for state-local information system projects is typically complex, due to the large number of project stakeholders, the need to consider numerous system requirements of each, and the demand from all stakeholders for rapid development and deployment. Creating systems in this kind of environment demands a system development method (SDM) that lends itself to rapid design and development. Often, the SDM best suited to this environment is prototyping.

Prototyping differs from the classic system development methods in that it allows for the building of the system to begin much earlier in the development process, and allows customers to see and influence the system as it is being built. The philosophy behind prototyping is that system development is more effective when customers are partners in the design process. The prototype makes tangible all the ideas that both designers and customers usually try to communicate to one another in words. The prototype makes it possible for both to see and understand the needs, functionality, and limitations of the design and to alter it as needed. Most of the projects we reviewed used prototyping to develop their systems and reported satisfaction with the results.





"With prototyping, customers become partners in the design process."