Hi Andrei, What you expressed is very important(to me), that is what's the deliverable for, but peter seems already expresses similiar thinking in his article " Of course, compiling a list is only the first step. For each project, we must strive for the optimal mix. Since our deliverables resist a taxonomy, asking questions may help derive their folksonomy.
. Audience. Who must you reach? . Content. What is the message? . Context. Where is the conversation? . Process. When is the message? . Problem. Why are you communicating? " If peter arrange according to above guidelines( i guess some stuffs here will be changed), it'll answer your essential request nicely; like what you said blueprint(maybe wrong) could be similiar with concept design + prototypes, which both serve as communicating tools between design side and engineering side. What's the important is the meaning instead of the name. Regards, Jarod >> >> It's not a big stretch. It's apples and oranges. Concept design and >> pixel-perfect screen mockups simply cannot be clumped together. > > Add to the end: ...cannot be clumped together to be used for the exact same > purposes. While a variety of deliverable types -- paintings, illustrations, > ink renderings, pencil sketches, pixel-perfect mockups -- can be used for > concept design, only pixel-perfect mockups can be used for specification (or > blueprints). > > The larger point remains for me. I felt Peter's article was lacking the most > important deliverable: the blueprint. -- http://designforuse.blogspot.com/ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... disc...@ixda.org Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
