Best Documentation: Prototyping

Thursday, October 9, 2008 8:42
Posted in category Programming

After reading an article of Martin Fowler about “Software Architects”: Who Need Architects? , I came to this point:

MOST IMPORTANT product of a Software Architect (SA) is The Prototype Project.

When you think of  ‘what does SA do in real world?’. he deals with some essential concepts !!!  Yes exactly right! He does not build the skyscraper itself, but finishes it on the paper. He predicts and solves some design issues before it occurs (Integration,user experience,features,vs…).  Since these concepts are vital. As development team, we need a proof.

Proof of Concept: Prototype Project/Prototyping

Although it is not the final product, it will give more idea not only to developers but also to the customers.  And both parties will make more effective assumptions about the final product.

What you will get:

  • Early customer feedback.
  • More predictable product development (Monkey See, Monkey Does)
  • Evaluation of new technology: most important benefit of prototyping
  • Effective documentation: proof of concept
Share and Enjoy:
  • Digg
  • del.icio.us
  • Netvouz
  • DZone
  • Wists
  • Technorati
  • YahooMyWeb
  • Furl
  • Slashdot
  • Google Bookmarks
  • Reddit
  • TwitThis
  • StumbleUpon
  • email

No related posts.

You can leave a response, or trackback from your own site.
Tags:

No Responses to “Best Documentation: Prototyping”

  1. mcakkan (mcakkan) says:

    October 10th, 2008 at 8:42 am

    http://tinyurl.com/3nacj2
    Best Documentation: Prototyping

Leave a Reply