Contents:

Related Video Shorts (0)

A use case description is often a finer-grained list of steps performed by an actor while using the envisioned system. Later, in South Africa, Terry Dyssell, and Chris and Elana Verster helped by generously providing access to various facilities that I needed while I finalized and checked the contents of this volume. Scenario- and task-based design methods constitute the second thematic section. In this the author's intent is to avoid the creation of another method, and to avoid the inevitable overhead in learning to use a new method. Would you like to report poor quality or formatting in this book?

Frequently used components in user-centered design approaches include an early focus on, contact with, and involvement of users, including the early and continual testing of prototypes by users to ensure the quality of the developing design, an appropriate division of work between the users and the computer system, and a multidisciplinary and iterative-design process. Participatory design is a less frequently used component in the approach, but it is gaining in popularity. Accumulated experience in the HCI field is that all of the previous components5 are important in the development of usable systems.

Magnus Lif's User Interface Modeling UIM method, an adjunct to use case based practice, is presented as an example of a user-centered design method. Finally, the description of the adoption of a customized user-centered method at the Swedish National Tax Board presents the authors' experience with and observations about one organization's development of a user-centered approach in the light of the organization's software development culture and needs. William Hudson, a user interface design consultant, provides useful recommendations in adopting a user-centered approach to UML-based developments.

Observing an informal UML-based design practice that is broadly adopted in industry, Hudson makes suggestions as to how to add to that practice using usability design techniques. In this the author's intent is to avoid the creation of another method, and to avoid the inevitable overhead in learning to use a new method. As a result of an Internet-based survey of effective usability-related practice adopted by usability practitioners, Hudson provides a ranking of 23 different user-centered techniques and tools and six user-centered design methods.

Hudson then provides suggestions as to how the top ten most popular techniques may be integrated with the informal UML method, thereby creating a user-centered approach to interactive system design. The new approach is then compared to the usage-centered design and RUP approaches. While this is, in part, a vision of the developing field, it also provides a framework within which to view and relate the diversity of the individual contributions in this book. Topics only alluded to in this preface are expanded and related material is introduced.

The intervention of HCI design techniques in early analysis phases allows for the up-front use of user-derived design information at the point in the development life cycle where it has the best effect, that is, when the overall design of the system is being formed. Notably, these techniques may involve participatory design techniques.

A very strong emphasis on abstract model construction and a broad-ranging HCI perspective on interactive system design are the means to establish the scope, functionality, and concrete user interface for interactive systems.

The methods treat interactive system design as an up-front and formative determinant on the design of user work, and the design of interactive system contents, functionality, and concrete user interface. The concrete user interface design and interactivity of the system is also designed up front, typically in a model-based design approach in which the previously designed abstract models are used in the design of the user interface.

The actions of detailed concrete design can motivate changes in the abstract models. This is to be expected and welcomed as an early design activity because changes are introduced for reasons of usability before the models are reused for the remaining OOA and OOD activities.

Domain Modelling for Interactive Systems Design

The application of quality checks to the developing interactive system design by the involvement of users in the evaluation of a range of prototypes throughout the design process. The evaluation must be performed formatively, that is, so that it contributes to the further design of the system. The process starts with the evaluation of prototypes that test and help establish the abstract design of the interactive system, and, over time, moves to evaluations of prototypes that contribute to the quality of the detailed concrete user interface design.

Change as a result of formative evaluation is expected and welcomed. Iterative redesign based on formative evaluation to converge on viable and usable support of users in their task-based behavior, with an appropriate division of work and activities between users and the interactive system. There is an important and general point to be made here: It is possible to integrate user interface design and object-oriented software engineering practice at a deep methodological level.

The significance of this is of critical importance for software engineers; the integration brings the consideration of user concerns and system usability into the object modeling design and development cycle as an up-front and centrally important activity. Such consideration helps in more than just the formulation of a detailed concrete user interface; it also helps markedly in determining the scope, contents, and core functionality of the interactive system. Importantly, consideration of user concerns determines an appropriate division of work and activities between the users and the system, and determines the subsequent work and activities of both the users and those who come into contact with them.

The commonalities and linkage between object-oriented and HCI practice represents an opportunity for the software engineering community to integrate HCI design techniques with their own discipline of interactive system design. The evidence put forth in this book is that the adoption of an integrated approach leads to an overall increase in usability. Even the adoption of only some of the techniques advocated here, for example, simple and early prototype testing and evaluation, would lead to a reduction in usability flaws.

The Harlequin Tea Set: An Agatha Christie Short Story?
Development and Evaluation of Drugs from Laboratory through Licensure to Market.
Domain Modelling for Interactive Systems Design : Alistair Sutcliffe : ;
Post navigation!

The editorial motivation for this book was primarily to make the object and component community aware of the possibilities for the integration of object modeling with the design of interactive systems as practiced in the HCI world. To ignore the overall potentialities of an integrated approach that draws on HCI expertise in interactive system design would, I feel, be a grossly negligent act.

The consequences include continued exposure of software engineers to the real and considerable risk regarding lack of user acceptance. Worse still, neglect of the possibilities will certainly condemn our users to more decades of suboptimal and unusable systems. As software engineers and methodologists, the choice is ours to make. Any mistakes or errors remain my own responsibility. This work could not have been produced without the kind help and support of several individuals: Katsura Kawakami provided me with the freedom to consolidate my ideas about interactive system design in an object-oriented style at the beginning of the nineties.

Later, in South Africa, Terry Dyssell, and Chris and Elana Verster helped by generously providing access to various facilities that I needed while I finalized and checked the contents of this volume. Various friends and relatives have been amazingly tolerant of my editing work during the past two years; thankfully my relationships with these individuals remain largely unchanged.

Two institutions have given me support during the editing of this book. The Department of Computer Science at the University of Manchester supplied me with library and other facilities; it has been particularly rewarding to continue my long association with this distinguished university, home of the first stored program computer where, as in modern computers, machine code instructions and data were stored in the same loadable and modifiable memory.

The Computer Science Department at the University of Cape Town kindly provided me with access to the university's library and Internet facilities during the last three months of the editing process. Kathy Glidden of Stratford Publishing Services provided immense help and skill in transforming the manuscript into final copy. It was a delightful privilege to have her work on this volume.

Notes 1 Design is the activity of formulating an engineering solution to a problem in light of requirements, other pertinent design information, and technical and economic constraints. The interactive system design discussed here is different from the technical implementation design referred to as object-oriented design OOD. Interactive system design is discussed later in this preface, but, for now, this is mostly an activity that establishes both the high-level system design and the design of the user interface as perceived, used, and experienced by its future users.

Here efficiency refers to efficiency of interaction when used by users, rather than internal program efficiency. It is important to note that the ISO definition includes issues of system scope, contents, functionality, and impact on user work and leisure activities, as well as the more traditional notion of usability, namely, ease and efficiency in interactively invoking system functionality. This is in contrast to user interface design as practiced by software engineering professionals as an "add-on" activity that occurs after analysis as part of a subsequent implementation-centered OOD phase.

For example, the application of social science methods such as ethnography and ethnomethodology to extract design information from field studies of users and their environments is becoming more widespread within HCI practice. However, these methods are some way from being able to be closely integrated with mainstream software engineering approaches. Envisioning Work and Technology in System Development. Wiley and Sons, Goals and Use Cases.

Using Goal-Based Use Cases. Constantine and Lockwood L. Dumas and Redish J. A Practical Guide to Usability Testing. The Rational Unified Process. The Trouble with Computers. Newman and Lamming W. User Centered System Design. Lawrence Erlbaum Associates, Rational Software Corporation, Dynamic Systems Development Method: The Method in Practice.

Design, Specification and Verification. Would you like to tell us about a lower price? If you are a seller for this product, would you like to suggest updates through seller support? Learn more about Amazon Prime. 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: 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. Read more Read less. Customers who viewed this item also viewed. Page 1 of 1 Start over Page 1 of 1. Customers who bought this item also bought. Sponsored products related to this item What's this? Algorithms to Live By: The Computer Science of Human Decisions. Once Upon an Algorithm: Transform Your Space on Any Budget. This easy to use guide will help you navigate your way to becoming proficient with network fundamentals and technology.

Learn these tasks to use Google Classroom to its full potential. Let your students benefit from improved teaching today. Addison-wesley Object Technology Series Paperback: Addison-Wesley; 1st edition April 11, Language: Related Video Shorts 0 Upload your video.

Product details

Share your thoughts with other customers. Write a customer review. There was a problem filtering reviews right now. Please try again later. Nine different methods are presented by an international team of software experts like Larry Constantine and Philippe Kruchten. All the authors are trying to solve constraints or deficiencies in existing methods. 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.

Taxing Ourselves: A Citizens Guide to the Debate over Taxes?
Description of Paradise?
The Servant!
Incidents in the Life of a Slave Girl.
Gelenke und Gelenkwellen: Berechnung, Gestaltung, Anwendungen (German Edition).
Customers who bought this item also bought!

The editor repeats what is generally recognized: 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.

Pages with related products. See and discover other items: Dispatched from the UK in 4 business days When will my order arrive? Home Contact Us Help Free delivery worldwide. Description Domain Modelling for Interactive Systems Design brings together in one place important contributions and up-to-date research results in this fast moving area. Domain Modelling for Interactive Systems Design serves as an excellent reference, providing insight into some of the most challenging research issues in the field.

Product details Format Hardback 89 pages Dimensions x Bestsellers in Software Engineering. Clean Code Robert C. Creative Selection Ken Kocienda. Liftoff, 2e Ainsley Nies. Clean Architecture Robert C. Product Mastery Geoff Watts. Code Complete Steve McConnell.

OO Systems Analysis and Design - Domain Class Modeling (Part 5)

Design Patterns Erich Gamma. Building Microservices Sam Newman. User Story Mapping Jeff Patton. Test Driven Development Kent Beck. Practical Monitoring Mike Julian. Exercises for Programmers Brian P. Designing Distributed Systems Brendan Burns. Java Testing with Spock Konstantinos Kapelonis. Agile Testing Janet Gregory. More Agile Testing Janet Gregory.