Hi everyone. Angel said: " # 3: Be concise! Nobody wants to read a 500 page spec no matter how pretty it is. ;-) "
Now I have to reply to this. To "be as specific as possible" means to give as much detail as one would need to perfectly and thouroughly understand the problem at hand. Isn't this rule in contradiction with your #3? :-P I feel devs need to be explained. Assuming that the login system shouldn't be explained, because it's ...well.. too common, is a bad step, imo. Designers and developers often have different backgrounds, coming from different cultures, things that influence their take on certain aspects of the web. Therefore, "more is more", I think, when it comes to documents: taking out all the assumptions and just documenting the project all the way might save valuable time. That being said, a picture not only tells more (#2), but it occupies less space. So, the answer is probably in the middle somewhere. ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
