Content deleted Content added
Line 29:
There is also an obvious synergy between the concept of an OOUI and the idea of constructing software from [[business object (computer science) | ___domain objects]]. However, it does not follow that the objects that a user sees and interacts with in an OOUI have to correspond to the [[business object (computer science) | ___domain objects]] on which the application is built.
The [[IBM Common User Access | CUA]] guidelines stated that 'In an object-oriented user interface, the objects that a user works with do not necessarily correspond to the objects, or modules of code, that a programmer used to create the product.'<ref name = "cua">IBM, Common User Access - Guide to User Interface Design. 1991, IBM: Cary, North Carolina.</ref> The basic design methods described in CUA were refined further into the OVID<ref name = "OVID">Dave Roberts, Dick Berry, Scott Isensee & John Mullaly, Designing for the User with OVID: Bridging User Interface Design and Software Engineering MacMillan, 1998</ref> method which used [[Unified Modeling Language | UML]] to model the interface.
Mark van Harmelen states that 'Object-oriented user interface design does not require designers to take an object-oriented view of the problem from the beginning of the project. . .Furthermore, even if designers take an object-oriented perspective throughout, they will benefit from focusing separately on the object model and the object-oriented user interface design.'<ref name="harmelen">van Harmelen, M., ed. Object Modelling and User Interface Design. 2001, Addison-Wesley: Reading, MA.</ref>
| |||