Object Modeling User Interface Design (Addison-wesley Object Technology Series) (英語) ペーパーバック – 2001/4/1
Kindle 端末は必要ありません。無料 Kindle アプリのいずれかをダウンロードすると、スマートフォン、タブレットPCで Kindle 本をお読みいただけます。
Object modeling with UML gives developers powerful tools for building software that meets the requirements of its users. Now, in this book, the field's leading experts extend UML to user interface design -- a breakthrough that will enable the creation of far more usable, productive software systems. This book introduces techniques for integrating today's best methods and modeling approaches from both the object technology and the user interface development communities -- ensuring a stronger focus on the user than ever before. The book's coverage encompasses four richly interconnected sources of user, domain, and system modeling information: participative design, task analysis, scenario-based design, and use case analysis. It also demonstrates exactly how UML object models can be used to record user interface design information -- giving developers practical information for designing and constructing software that responds more fully to user requirements and expectations. With contributions from Larry Constantine and other leading software design experts, this book combines theory, practice, and real world "advice from the trenches."
Mark van Harmelen is an independent consultant who has been involved with object-oriented technology and human-computer interaction since 1985. Mark is also an Honorary Research Fellow in the Department of Computer Science at the University of Manchester, U.K. Previously Mark has been a Senior Researcher at Matsushita's (Panasonic's) Tokyo Research Laboratory, a tenured member of the academic staff at Manchester University, and has held various positions in industry. He has degrees in Computer Science and Psychology, including a Ph.D. in Computer Science. He started working on the integration of object modeling and user interface design in 1991, and initiated worldwide cooperation in the field in 1997. He continues to foster this cooperation. 0201657899AB04062001
All the authors are trying to solve constraints or deficiencies in existing methods. Since these are all new or experimental techniques, each author explains exactly what problem s/he is trying to solve, where the new method might be best used, and how it worked in practice. Most of the sections work through a couple of cases, so you can see how the method works.
A couple of the writers have pointed out how difficult current heavy-weight methodologies are to use. The models generated, unless the modeler is extremely experienced, are usually not correct. What's more, as the first chapter notes, the modelers don't realize that their models are bad. A couple of writers have tried to deal with the problem that business customers can't understand UML-style notation, and don't mentally describe their jobs in terms of classes or windows. That cuts customers out of the system design process at exactly the point where they should be most engaged.
The editor repeats what is generally recognized: that very few people use a methodology as such. Most of us use a grab bag of techniques from a mix of methods, heavily customized to our own needs. Mark van Harmelen's book may be best addressed to those who use mixed methods, because it helps us to see how experienced architects decide which techniques to use in different circumstances and how we can determine whether we were successful.