Preface. Who This Book Is For. Acknowledgements. Colophon. Introduction. Architecture. Enterprise Applications. Kinds of Enterprise Application. Thinking About Performance. Patterns. The Structure of the Patterns. Limitations of These Patterns. I. THE NARRATIVES. 1. Layering. The Evolution of Layers in Enterprise Applications. The Three Principal Layers. Choosing Where to Run Your Layers. 2. Organizing Domain Logic. Making a Choice. Service Layer. 3. Mapping to Relational Databases. Architectural Patterns. The Behavioral Problem. Reading in Data Structural Mapping Patterns. Mapping Relationships. Inheritance. Building the Mapping. Double Mapping. Using Metadata. Database Connections. Some Miscellaneous Points. Further Reading. 4. Web Presentation. View Patterns. Input Controller Patterns. Further Reading. 5. Concurrency (by Martin Fowler and David Rice). Concurrency Problems. Execution Contexts. Isolation and Immutability. Optimistic and Pessimistic Concurrency Control. Preventing Inconsistent Reads. Deadlocks. Transactions. ACID. Transactional Resources. Reducing Transaction Isolation for Liveness. Business and System Transactions. Patterns for Offline Concurrency Control. Application Server Concurrency. Further Reading. 6. Session State. The Value of Statelessness. Session State. Ways to Store Session State. 7. Distribution Strategies. The Allure of Distributed Objects. Remote and Local Interfaces. Where You Have to Distribute. Working with the Distribution Boundary. Interfaces for Distribution. 8. Putting it all Together. Starting With the Domain Layer. Down to the Data Source. Data Source for Transaction Script. Data Source Table Module (125). Data Source for Domain Model (116). The Presentation Layer. Some Technology-Specific Advice. Java and J2EE. .NET. Stored Procedures. Web Services. Other Layering Schemes. II. THE PATTERNS. 9. Domain Logic Patterns. Transaction Script. How It Works. When to Use It. The Revenue Recognition Problem. Example: Revenue Recognition (Java). Domain Model. How It Works. When to Use It. Further Reading. Example: Revenue Recognition (Java). Table Module. How It Works. When to Use It. Example: Revenue Recognition with a Table Module (C#). Service Layer(by Randy Stafford). How It Works. When to Use It. Further Reading. Example: Revenue Recognition (Java). 10. Data Source Architectural Patterns. Table Data Gateway. How It Works. When to Use It. Further Reading. Example: Person Gateway (C#). Example: Using ADO.NET Data Sets (C#). Row Data Gateway. How It Works. When to Use It. Example: A Person Record (Java). Example: A Data Holder for a Domain Object (Java). Active Record. How It Works. When to Use It. Example: A Simple Person (Java). Data Mapper. How It Works. When to Use It. Example: A Simple Database Mapper (Java). Example: Separating the Finders (Java). Example: Creating an Empty Object (Java). 11. Object-Relational Behavioral Patterns. Unit of Work. How It Works. When to Use It. Example: Unit of Work with Object Registration (Java) (by David Rice). Identity Map. How It Works. When to Use It. Example: Methods for an Identity Map (Java). Lazy Load. How It Works. When to Use It. Example: Lazy Initialization (Java). Example: Virtual Proxy (Java). Example: Using a Value Holder (Java). Example: Using Ghosts (C#). 12. Object-Relational Structural Patterns. Identity Field. How It Works. When to Use It. Further Reading. Example: Integral Key (C#). Example: Using a Key Table (Java). Example: Using a Compound Key (Java). Foreign Key Mapping. How It Works. When to Use It. Example: Single-Valued Reference (Java). Example: Multitable Find (Java). Example: Collection of References (C#). Association Table Mapping. How It Works. When to Use It. Example: Employees and Skills (C#). Example: Using Direct SQL (Java). Example: Using a Single Query for Multiple Employees (Java) (by Matt Foemmel and Martin Fowler). Dependent Mapping. How It Works. When to Use It. Example: Albums and Tracks (Java). Embedded Value. How It Works. When to Use It. Further Reading. Example: Simple Value Object (Java). Serialized LOB. How It Works. When to Use It. Example: Serializing a Department Hierarchy in XML (Java). Single Table Inheritance. How It Works. When to Use It. Example: A Single Table for Players (C#). Loading an Object from the Database. Class Table Inheritance. How It Works. When to Use It. Further Reading. Example: Players and Their Kin (C#). Concrete Table Inheritance. How It Works. When to Use It. Example: Concrete Players (C#). Inheritance Mappers. How It Works. When to Use It. 13. Object-Relational Metadata Mapping Patterns. Metadata Mapping. How It Works. When to Use It. Example: Using Metadata and Reflection (Java). Query Object. How It Works. When to Use It. Further Reading. Example: A Simple Query Object (Java). Repository (by Edward Hieatt and Rob Mee). How It Works. When to Use It. Further Reading. Example: Finding a Person's Dependents (Java). Example: Swapping Repository Strategies (Java). 14. Web Presentation Patterns. Model View Controller. How It Works. When to Use It. Page Controller. How It Works. When to Use It. Example: Simple Display with a Servlet Controller and a JSP View (Java). Example: Using a JSP as a Handler (Java). Example: Page Handler with a Code Behind (C#). Front Controller. How It Works. When to Use It. Further Reading. Example: Simple Display (Java). Template View. How It Works. When to Use It. Example: Using a JSP as a View with a Separate Controller (Java). Example: ASP.NET Server Page (C#). Transform View. How It Works. When to Use It. Example: Simple Transform (Java). Two Step View. How It Works. When to Use It. Example: Two Stage XSLT (XSLT). Example: JSP and Custom Tags (Java). Application Controller. How It Works. When to Use It. Further Reading. Example: State Model Application Controller (Java). 15. Distribution Patterns. Remote Facade. How It Works. When to Use It. Example: Using a Java Session Bean as a Remote Facade (Java). Example: Web Service (C#). Data Transfer Object. How It Works. When to Use It. Further Reading. Example: Transferring Information about Albums (Java). Example: Serializing Using XML (Java). 16. Offline Concurrency Patterns. Optimistic Offline Lock (by David Rice). How It Works. When to Use It. Example: Domain Layer with Data Mappers (165) (Java). Pessimistic Offline Lock (by David Rice). How It Works. When to Use It. Example: Simple Lock Manager (Java). Coarse-Grained Lock (by David Rice and Matt Foemmel). How It Works. When to Use It. Example: Shared Optimistic Offline Lock (416) (Java). Example: Shared Pessimistic Offline Lock (426) (Java). Example: Root Optimistic Offline Lock (416) (Java). Implicit Lock (by David Rice). How It Works. When to Use It. Example: Implicit Pessimistic Offline Lock (426) (Java). 17. Session State Patterns. Client Session State. How It Works. When to Use It. Server Session State. How It Works. When to Use It. Database Session State. How It Works. When to Use It. 18. Base Patterns. Gateway. How It Works. When to Use It. Example: A Gateway to a Proprietary Messaging Service (Java). Mapper. How It Works. When to Use It. Layer Supertype. How It Works. When to Use It. Example: Domain Object (Java). Separated Interface. How It Works. When to Use It. Registry. How It Works. When to Use It. Example: A Singleton Registry (Java). Example: Thread-Safe Registry (Java) (by Matt Foemmel and Martin Fowler). Value Object. How It Works. When to Use It. Money. How It Works. When to Use It. Example: A Money Class (Java) (by Matt Foemmel and Martin Fowler). Special Case. How It Works. When to Use It. Further Reading. Example: A Simple Null Object (C#). Plugin (by David Rice and Matt Foemmel). How It Works. When to Use It. Example: An Id Generator (Java). Service Stub (by David Rice). How It Works. When to Use It. Example: Sales Tax Service (Java). Record Set. How It Works. When to Use It. References Index. 0321127420T10162002

/pdf/patterns-of-enterprise-application-architecture-1kqa9p9kfu.pdf

Patterns of Enterprise Application Architecture

Cognitive engineering

Usability Engineering: Scenario-Based Development of Human-Computer Interaction is a radical departure from traditional books that emphasize theory and address experts. This book focuses on the realities of product development, showing how user interaction scenarios can make usability practices an integral part of interactive system development. As you'll learn, usability engineering is not the application of inflexible rules; it's a process of analysis, prototyping, and problem solving in which you evaluate tradeoffs, make reasoned decisions, and maximize the overall value of your product.

Usability Engineering: Scenario-Based Development of Human-Computer Interaction

This article describes the Quest Atlantis (QA) project, a learning and teaching project that employs a multiuser, virtual environment to immerse children, ages 9–12, in educational tasks. QA combines strategies used in commercial gaming environments with lessons from educational research on learning and motivation. It allows users at participating elementary schools and after-school centers to travel through virtual spaces to perform educational activities, talk with other users and mentors, and build virtual personae. Our work has involved an agenda and process that may be called socially-responsive design, which involves building sociotechnical structures that engage with and potentially transform individuals and their contexts of participation. This work sits at the intersection of education, entertainment, and social commitment and suggests an expansive focus for instructional designers. The focus is on engaging classroom culture and relevant aspects of student life to inspire participation consistent with social commitments and educational goals interpreted locally.

/pdf/making-learning-fun-quest-atlantis-a-game-without-guns-afyyuz0yom.pdf

Making Learning Fun: Quest Atlantis, A Game Without Guns.

The effects of utilitarian and hedonic online shopping value on consumer preference and intentions

From the Book:
PREFACE: 
Two technological advances in recent years have radically altered the nature of computing for most computer users The first is mobility Laptop computers now represent the fastest growing segment of the computer market Most observers expect that laptop computers, palmtop computers, networked personal digital assistants, and other such mobile computers will eventually represent the majority of the stations connected to the Internet The advantage of mobile computing is that users may access all their applications from any location, whether they are in another building or a different state The second advance is the widespread use of the Internet for communication, file transfer, and World Wide Web connectivity This book describes how to make a mobile computer user a citizen of the Internet and how to access everything the information superhighway has to offer The goal of this book is to provide you with an introduction to the design and implementation of Internet protocols that are useful for maintaining network connections even while moving from place to place We look at several protocols including Mobile IP, route optimization, IP version 6, the Dynamic Host Configuration Protocol, encapsulation, source routing, and some related miscellaneous topics still under development

To take full advantage of the information in this book, you should be familiar with basic Internet protocols, such as the Transmission Control Protocol (TCP)/IP Rich Stevens' book TCP/IP Illustrated, Volume 1: The Protocols and Douglas Comer's Internetworking with TCP/IP both provide excellent introductions to TCP/IP As a developer of hardware and softwareproductsfor the Internet, you should have these books on your shelves

By the time you finish Mobile IP: Design Principles and Practices, you will be able to implement Mobile IP, and will have a clear understanding of the system impact of mobility You will also understand the relevant protocols, and the traps and pitfalls that you are likely to encounter along the way

As you read the book, you will notice many italicized terms, some of which have conventional meanings that may be different than one's first impression (for example, foreign agent) These terms are defined in the Glossary: Please check definitions there, and be sure that you understand a term's meaning before moving on in the text 

0201634694P04062001

Mobile IP : design principles and practices

The most valuable tools or methodologies supporting the design of interactive systems are those that simultaneously ease the process of design and improve the usability of the resulting system. We consider the potential of the object-oriented paradigm in providing this dual function. After briefly reviewing what is known about the design process and some important characteristics of object-oriented programming and design, we speculate on the possible cognitive consequences of this paradigm for problem understanding, problem decomposition, and design result. We conclude with research issues raised by our analysis.

The cognitive consequences of object-oriented design

Despite an abundance of recommendations by researchers and more recently by commercial enterprises for adaptive interaction techniques and technologies, there exists little experimental validation of the value of such approaches to users. We have conducted user studies focussed on the perceived value of a variety of personalization features for an eCommerce Web site for computing machinery sales and support. Our study results have implications for the design of user-adaptive applications. Interesting findings include unenthusiastic user attitudes toward system attempts to infer user needs, goals, or interests and to thereby provide user-specific adaptive content. Users also expressed equivocal opinions of collaborative filtering for the specific eCommerce scenarios we studied; thus personalization features popular in one eCommerce environment may not be effective or useful for other eCommerce domains. Users expressed their strong desire to have full and explicit control of data and interaction. Lastly, users want readily to be able to make sense of site behavior, that is, to understand a site's rationale for displaying particular content.

/pdf/user-attitudes-regarding-a-user-adaptive-ecommerce-web-site-39xe8qwvox.pdf

User Attitudes Regarding a User-Adaptive eCommerce Web Site

We describe the conversion of a standalone intelligent tutoring system (ITS) to one that operates on the World Wide Web. First, we focus on one product of this effort, a Web- enabled architecture as extension of a widely-used standalone ITS architecture. The advantages of the architecture we have chosen are discussed. We then describe the specific Web-based ITS that uses this architecture, highlighting features of the tutor for supporting and enhancing problem solving. Both the architecture and many features of the tutor that support students' problem solving activities should be generalizable to other ITSs.

/pdf/deploying-intelligent-tutors-on-the-web-an-architecture-and-2mm9hq5avr.pdf

Deploying Intelligent Tutors on the Web: An Architecture and an Example

A method and apparatus are disclosed for ranking the results of a document search by identifying a prior, similar search and assigning a weight to each document based on whether the document was selected by a user of the prior search. The assigned weights are utilized to rank the documents identified by the document search in order of their relevance to the search terms. The search terms of the document search and information describing the selections made by a user of the document search are then stored to facilitate the assignment of weights to documents in future searches. According to another aspect of the invention, the weight assigned to a document is correlated to a degree of closeness of search terms of a prior search and search terms of a new document search. For example, a degree of closeness measurement is defined that correlates to a number of synonyms common between the search terms of a prior search and the search terms of a new document search.

Sherman R. Alpert

Papers

Mobile IP : design principles and practices

The cognitive consequences of object-oriented design

User Attitudes Regarding a User-Adaptive eCommerce Web Site

Deploying Intelligent Tutors on the Web: An Architecture and an Example

System and method for user rank search