SanFrancisco (TM) Design Patterns
Blueprints for Business Software
Published on 17. April 2000
Book
Mixed media product
400 pages
978-0-201-61644-6 (ISBN)
Description
IBM's SanFrancisco is a Java-based set of pre-constructed components that help developers quickly assemble server-side business applications. In developing SanFrancisco, IBM's Java developers discovered a wide range of patterns that are invaluable to all Java developers. This book documents them, in-depth. It follows the format used in the groundbreaking book Design Patterns. Beginning with a case study describing a typical set of business requirements for a hypothetical enterprise, successive chapters address each design pattern in turn, using an aspect of the case study to provide a concrete example that motivates the pattern. The patterns fall into five categories: foundational, behavioral, structural, process, and dynamic behavioral patterns. While some of them extend patterns originally identified elsewhere, many are entirely new -- and all of them offer powerful opportunities for more effective development.
More details
Language
English
Place of publication
Boston
United States
Publishing group
Pearson Education (US)
Target group
College/higher education
Dimensions
Height: 190 mm
Width: 235 mm
Thickness: 18 mm
Weight
626 gr
ISBN-13
978-0-201-61644-6 (9780201616446)
Copyright in bibliographic data and cover images is held by Nielsen Book Services Limited or by the publishers or by their respective licensors: all rights reserved.
Schweitzer Classification
Persons
James Carey is the Base Component (fine-grained component) architect for IBM's WebSphere Business Components. He previously served as a lead designer for the Common Business Objects and General Ledger Core Business Processes part of the IBM SanFrancisco frameworks.
Brent Carlson is Vice President of Technology for LogicLibrary, a provider of software asset management products and services. He previously served as the lead architect for the IBM SanFrancisco project and lead designer for its Warehouse and Order Management Core Business Processes.
Tim Graser is currently the business component architect for IBM Software Group's EJB-based business software component development. Previously he was the lead designer for SanFrancisco's Common Business Objects and contributed to the design for the Order Management Core Business Processes.
0201616440AB04172002
Brent Carlson is Vice President of Technology for LogicLibrary, a provider of software asset management products and services. He previously served as the lead architect for the IBM SanFrancisco project and lead designer for its Warehouse and Order Management Core Business Processes.
Tim Graser is currently the business component architect for IBM Software Group's EJB-based business software component development. Previously he was the lead designer for SanFrancisco's Common Business Objects and contributed to the design for the Order Management Core Business Processes.
0201616440AB04172002
Content
1. Introduction
Frameworks by San Francisco
Book Structure
What's Next
Summing Up
2. Case Study
Business Problem
General Application Requirements
Putting Our Example in Context
I. Foundational Patterns
3. Class Replacement.
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
4. Special Class Factory
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
5. Property Container
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
6. Business Process Command
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
II. Behavioral Patterns
7. Simple Policy
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
8. Chain of Responsibility-Driven Policy
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
9. Token-Driven Policy
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
III. Structural Patterns
10. Controller.
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
11. Key/Keyable.
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
12. Generic Interface
Intent
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
IV. Process Patterns.
13. Cached Aggregate
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
14. Keyed Attribute Retrieval.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
15. List Generation.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
V. Dynamic Behavioral Patterns.
16. Extensible Item.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
17. Hierarchical Extensible Item.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
18. Business Entity Lifecycle.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
19. Hierarchy Information.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
20. Decoupled Processes.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
Appendix A. UML Nomenclature.
UML Notation.
Objects and Collaboration Diagrams.
Appendix B. Project SanFrancisco.
History.
Mission.
Architecture.
Appendix C. The CD-ROM.
Installing the Software That Accompanies the Book.
CD-ROM Warranty.
Bibliography.
Index. 0201616440T04062001
Frameworks by San Francisco
Book Structure
What's Next
Summing Up
2. Case Study
Business Problem
General Application Requirements
Putting Our Example in Context
I. Foundational Patterns
3. Class Replacement.
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
4. Special Class Factory
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
5. Property Container
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
6. Business Process Command
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
II. Behavioral Patterns
7. Simple Policy
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
8. Chain of Responsibility-Driven Policy
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
9. Token-Driven Policy
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
III. Structural Patterns
10. Controller.
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
11. Key/Keyable.
Intent
Motivation
Applicability
Structure
Participants
Collaborations
Consequences
Implementation
Sample Code
Known Uses
Related Patterns
12. Generic Interface
Intent
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
IV. Process Patterns.
13. Cached Aggregate
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
14. Keyed Attribute Retrieval.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
15. List Generation.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
V. Dynamic Behavioral Patterns.
16. Extensible Item.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
17. Hierarchical Extensible Item.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
18. Business Entity Lifecycle.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
19. Hierarchy Information.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
20. Decoupled Processes.
Intent.
Motivation.
Applicability.
Structure.
Participants.
Collaborations.
Consequences.
Implementation.
Sample Code.
Known Uses.
Related Patterns.
Appendix A. UML Nomenclature.
UML Notation.
Objects and Collaboration Diagrams.
Appendix B. Project SanFrancisco.
History.
Mission.
Architecture.
Appendix C. The CD-ROM.
Installing the Software That Accompanies the Book.
CD-ROM Warranty.
Bibliography.
Index. 0201616440T04062001