"And every day we have to use our creativity, smarts and talent to design the best tools for people to use."
-> No, sorry. The design of the tool is not a software designer's cocnern. It seems there is some misconception about software design going on here. Software design isn't concerned with the interface, but code. You could define software design as "a planning phase allowing the creation of efficient and understandable code". It is the phase that comes after gathering the requirements, so you already know what the system should do, and before actual implementation; laying out a framework or plan after which the coding should be executed. It's really just about analysing planned functionality, creating modules, decomposing them into functions, deciding upon algorithms, etc; so that programmers have a shared model of the final code structure before starting implementation. ...or maybe it's just me who has a wrong idea of the term. But I'm quite sure I'm right. Please correct me if I'm wrong. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=43357 ________________________________________________________________ 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
