35 of 365: Development Cycle design principle


35 of 365 - Development Cycle design principle by John LeMasney via lemasney.com
35 of 365 – Development Cycle design principle by John LeMasney via lemasney.com

The Development Cycle is a studied and recognized series of actions in a design process that tend to lead to more successful production outcomes.

The Requirements part of the process is a discovery process, where stakeholders are given a formal way of reporting their needs through codified inquiry. Simply asking what someone “likes” or “needs” may result in a less effective response than a form that asks qualifiable, reliable questions about the product in question.

The Design part of the process is where the requirements are turned into actions in the design. Stakeholder requirements drive the answers to the key questions of the design.

Development is where the real product is produced, incorporating all the requirements and design.

Testing is where the product is used, reviewed, and benchmarked. If needs arise at any stage in the development cycle, they are reincorporated at the next cycle. After a few cycles, a product may stabilize.

 

This content is published under the Attribution 3.0 Unported license.


About lemsy

John LeMasney is an artist, graphic designer, and technology creative. He is located in beautiful, mountainous Charlottesville, VA, but works remotely with ease. Contact him at: lemasney@gmail.com to discuss your next creative project.

Leave a Reply