However, I think Korman misses Raskin's point about the value of an engineering approach. Due to popular demand from several groups including the OMG's eCommerce Domain Task Force, some recent work by uidesign.net editor David Anderson in the field of OO Modeling is being made available through uidesign.net. I'm also worried it would make UI design retired. As a result, you must adopt a process which expects the unexpected and is flexible to change. Waterfall methodology is definitely out.
Iterative methods are essential.
IBM have continued to develop OVID as a potential addition to UML and to integrate it with an XML DTD and generator for auto-generation of UI code from a navigation model, created in Rational Rose. This represents a significant step forward in UI Design technology. The OVID notation is not yet complete and it does not meet all the criteria presented in the laundry list of necessary attribiutes for a navigation modeling language, by David Anderson, here at uidesign.net. I will be presenting proposals for two distinct levels of abstraction in the development of a user interface design. For the higher level, the Interaction Design, I will seek to layout a laundry list of attributes that would be required by a good modeling language for Interaction Design.