| List of Figures | p. xi |
| List of Tables | p. xvii |
| Contributing Authors | p. xxi |
| Human-Centered Software Engineering: Software Engineering Architectures, Patterns, and Models for Human Computer Interaction | p. 1 |
| Scope | p. 1 |
| Specific Objectives of the CHISE Volume II | p. 2 |
| Overview | p. 2 |
| Chapter Summaries | p. 3 |
| References | p. 6 |
| User Experiences, Usability Requirements, and Design | |
| What Drives Software Development: Bridging the Gap Between Software and Usability Engineering | p. 9 |
| Introduction | p. 9 |
| Use Case Driven Software Development | p. 11 |
| Architecture Centric | p. 14 |
| From Essential Use Cases to the Conceptual Architecture | p. 17 |
| Tool Issues | p. 20 |
| Conclusion | p. 23 |
| References | p. 24 |
| Human Activity Modeling: Toward a Pragmatic Integration of Activity Theory and Usage-Centered Design | p. 27 |
| Introduction | p. 28 |
| Activity Theory | p. 29 |
| Usage-Centered Design | p. 31 |
| Toward Integration | p. 33 |
| Human Activity Modeling | p. 35 |
| Design Implications | p. 43 |
| Process Implications | p. 44 |
| Application | p. 45 |
| Discussion | p. 47 |
| References | p. 50 |
| A User-Centered Framework for Deriving a Conceptual Design from User Experiences: Leveraging Personas and Patterns to Create Usable Designs | p. 53 |
| Introduction | p. 54 |
| A First Look at the Proposed Framework | p. 55 |
| Modeling User Experiences with Personas | p. 56 |
| Creating a Conceptual Design Using Patterns | p. 57 |
| An Illustrative Case Study | p. 61 |
| A Detailed Description of UX-process | p. 70 |
| Further Investigation: The P2P Mapper Tool | p. 74 |
| Conclusion | p. 76 |
| References | p. 79 |
| XML-Based Tools for Creating, Mapping, and Transforming Usability Engineering Requirements | p. 83 |
| Introduction | p. 83 |
| Toolset Overview | p. 85 |
| Using XML to Structure UE Specifications | p. 89 |
| Mapping Between XML-based UE and SE Specifications | p. 92 |
| Translating Between XML-based UE Requirements Into SE Specifications | p. 99 |
| Conclusion | p. 102 |
| References | p. 102 |
| Modeling and Model-Driven Engineering | |
| MultiPath Transformational Development of User Interfaces with Graph Transformations | p. 107 |
| Introduction | p. 108 |
| Related Work | p. 110 |
| Expressing the UI Development Cycle with Graph Transformations | p. 111 |
| Development Paths | p. 118 |
| Conclusion | p. 134 |
| References | p. 135 |
| Human-Centered Engineering with UIML | p. 139 |
| Introduction | p. 140 |
| UIML: An Overview | p. 141 |
| Tools for and Extensions of UIML | p. 148 |
| Improvements to UIML for Version 4.0 | p. 156 |
| UIML-Related Standards | p. 166 |
| Conclusion | p. 169 |
| References | p. 170 |
| Megamodeling and Metamodel-Driven Engineering for Plastic User Interfaces: Mega-UI | p. 173 |
| Introduction | p. 174 |
| Plasticity: Case Study and Engineering Issues | p. 175 |
| Modeling, Metamodeling, and Megamodeling | p. 182 |
| MDE for Plasticity | p. 190 |
| Conclusions and Perspectives | p. 196 |
| References | p. 197 |
| Cause and Effect in User Interface Development | p. 201 |
| Introduction | p. 201 |
| Research Study | p. 205 |
| Eliciting Needs and Context | p. 209 |
| Design | p. 210 |
| Evaluation in Context | p. 214 |
| Foundation and Context of an Evaluation Model | p. 215 |
| Conclusion | p. 218 |
| References | p. 219 |
| Interactive Systems Architectures | |
| From User Interface Usability to the Overall Usability of Interactive Systems: Adding Usability in System Architecture | p. 225 |
| Introduction | p. 226 |
| Background and Related Work | p. 227 |
| Identifying and Categorizing Typical Scenarios | p. 228 |
| Patterns as Solutions to the Problems Documented as Scenarios | p. 230 |
| Modeling Cause-Effect Relationships Between Software Elements and Usability | p. 237 |
| Conclusion and Future Investigations | p. 242 |
| References | p. 243 |
| Toward a Refined Paradigm for Architecting Usable Systems | p. 245 |
| Introduction | p. 245 |
| An Overview of Previous Work | p. 246 |
| Usability at the Requirements Definition Stage | p. 248 |
| Usability-Centered Software Development Process | p. 251 |
| Conclusion | p. 253 |
| References | p. 254 |
| Trace-Based Usability Evaluation Using Aspect-Oriented Programming and Agent-Based Software Architecture | p. 257 |
| Introduction | p. 257 |
| First Approach for Early Usability Evaluation: Injection of the Mechanism of Traces by Aspect-Oriented Programming | p. 258 |
| Second Approach: Interactive Agent-Based Architecture and Evaluation Module | p. 263 |
| Towards an Assistance System for the Evaluation of Agent-Based Interactive Systems | p. 266 |
| Comparison Between the two Approaches | p. 268 |
| Conclusion | p. 273 |
| References | p. 274 |
| Achieving Usability of Adaptable Software: The AMF-Based Approach | p. 277 |
| Introduction | p. 277 |
| State-of-the-art | p. 278 |
| AMF and Its Relationships With Other Models | p. 281 |
| A Method for Designing Adaptable Applications | p. 289 |
| Future Developments and Conclusion | p. 294 |
| References | p. 295 |
| Reengineering, Reverse Engineering, and Refactoring | |
| The Gains Design Process: How to do Structured Design of User Interfaces in any Software Environment | p. 301 |
| The Costs of Changing User Interfaces | p. 302 |
| Overview of the Gains Process | p. 304 |
| Overview of XP's Planning Levels | p. 305 |
| Evaluations of Usability | p. 313 |
| Difficulties With Two XP Assumptions | p. 314 |
| Conclusions | p. 315 |
| References | p. 315 |
| Legacy Systems Interaction Reengineering | p. 317 |
| Introduction | p. 318 |
| Motivation for Interaction Engineers | p. 318 |
| Generic Methodology | p. 319 |
| Applications of Interaction Reengineering | p. 323 |
| From Websites to Web Services | p. 325 |
| Advantages and Limitations | p. 331 |
| References | p. 332 |
| Reverse Engineering for Usability Evaluation | p. 335 |
| Introduction | p. 335 |
| GUI Model | p. 338 |
| Design of the GUI Ripper | p. 345 |
| Implementation | p. 347 |
| Empirical Evaluation | p. 349 |
| Related Work | p. 351 |
| Conclusions and Future Work | p. 352 |
| References | p. 353 |
| Task Models and System Models as a Bridge between HCI and SE | p. 357 |
| Introduction | p. 358 |
| Related Work | p. 359 |
| Why a Task Model is Not Enough | p. 359 |
| A Classical System Model | p. 361 |
| The Improved System Model | p. 362 |
| Scenarios as a Bridge Between Tasks and System Models | p. 363 |
| A Case Study | p. 365 |
| The Integration of the Models: CTT-ICO | p. 375 |
| Conclusions | p. 382 |
| References | p. 384 |
| Authors Index | p. 387 |
| Subject Index | p. 395 |
| Table of Contents provided by Ingram. All Rights Reserved. |