book

Analysis Patterns: Reusable Object Models

Name: Analysis Patterns: Reusable Object Models
Author: Martin Fowler
ISBN: 9780134271453

by Martin Fowler

May 2015

Beginner to intermediate

384 pages

10h 35m

English

Addison-Wesley Professional

Read now

Unlock full access

About This eBook
Title Page
Copyright Page
The Addison-Wesley Object Technology Series
Foreword by Ralph Johnson
Foreword by Ward Cunningham
Contents
Preface
Structure of this BookHow to Read this BookWho Should Read this BookA Living BookAcknowledgmentsReferences
1. Introduction
1.1 Conceptual Models1.2 The World of Patterns1.2.1 Christopher Alexander1.2.2 The Literary Form1.2.3 The Author’s Level of Abstraction1.3 The Patterns in this Book1.3.1 Examples for Modeling1.3.2 Origins of the Patterns1.3.3 Patterns Across Domains1.4 Conceptual Models and Business Process Reengineering1.5 Patterns and Frameworks1.6 Using the PatternsReferences
Part 1: Analysis Patterns

2. Accountability
2.1 Party2.2 Organization Hierarchies2.3 Organization Structure2.4 Accountability2.5 Accountability Knowledge Level2.6 Party Type Generalizations2.7 Hierarchic Accountability2.8 Operating Scopes2.9 PostReferences
3. Observations and Measurements
3.1 Quantity3.2 Conversion Ratio3.3 Compound Units3.4 Measurement3.5 Observation3.6 Subtyping Observation Concepts3.7 Protocol3.8 Dual Time Record3.9 Rejected Observation3.10 Active Observation, Hypothesis, and Projection3.11 Associated Observation3.12 Process of ObservationReferences
4. Observations for Corporate Finance
4.1 Enterprise Segment4.1.1 Defining the Dimensions4.1.2 Properties of Dimensions and Enterprise Segments4.2 Measurement Protocol4.2.1 Holding the Calculations4.2.2 Comparative and Causal Measurements Protocols4.2.3 Status Type: Defining Planned and Actual Status4.2.4 Creating a Measurement4.2.5 Dimension Combinations4.3 Range4.4 Phenomenon with Range4.4.1 Phenomenon with Range Attribute4.4.2 Range Function4.5 Using the Resulting FrameworkReferences
5. Referring to Objects
5.1 Name5.2 Identification Scheme5.3 Object Merge5.3.1 Copy and Replace5.3.2 Superseding5.3.3 Essence/Appearance5.4 Object EquivalenceReferences
6. Inventory and Accounting
6.1 Account6.2 Transactions6.2.1 Multilegged Transactions6.3 Summary Account6.4 Memo Account6.5 Posting Rules6.5.1 Reversibility6.5.2 Abandoning Transactions6.6 Individual Instance Method6.6.1 Implementation with a Singleton Class6.6.2 Implementation with the Strategy Pattern6.6.3 Implementation with an Internal Case Statement6.6.4 Implementation with a Parameterized Method6.6.5 Implementation with an Interpreter6.6.6 Choosing an Implementation6.7 Posting Rule Execution6.7.1 Eager Firing6.7.2 Account-based Firing6.7.3 Posting-rule-based Firing6.7.4 Backward-chained Firing6.7.5 Comparing the Firing Approaches6.8 Posting Rules for Many Accounts6.9 Choosing Entries6.10 Accounting Practice6.11 Sources of an Entry6.12 Balance Sheet and Income Statement6.13 Corresponding Account6.14 Specialized Account Model6.15 Booking Entries to Multiple Accounts6.15.1 Using Memo Entries6.15.2 Derived AccountsFurther ReadingReferences
7. Using the Accounting Models
7.1 Structural Models7.2 Implementing the Structure7.3 Setting Up New Phone Services7.4 Setting Up Calls7.5 Implementing Account-based Firing7.6 Separating Calls into Day and Evening7.7 Charging for Time7.8 Calculating the Tax7.9 Concluding Thoughts7.9.1 The Structure of the Posting Rules7.9.2 When Not to Use the Framework7.9.3 Accounting Practice DiagramsReferences
8. Planning
8.1 Proposed and Implemented Action8.2 Completed and Abandoned Actions8.3 Suspension8.4 Plan8.5 Protocol8.5.1 Plans and Protocols as Graphs8.6 Resource Allocation8.7 Outcome and Start FunctionsReferences
9. Trading
9.1 Contract9.2 Portfolio9.3 Quote9.4 Scenario9.4.1 Defining How to Build a ScenarioReferences
10. Derivative Contracts
10.1 Forward Contracts10.2 Options10.2.1 Longs, Shorts, Calls, and Puts: Representing a Tricky Vocabulary10.2.2 To Subtype or Not to Subtype10.3 Product10.3.1 Should a Product Always Be There?10.4 Subtype State Machines10.4.1 Ensuring Conformance of State Charts10.4.2 The Problems with Using Conformance10.5 Parallel Application and Domain Hierarchies10.5.1 Type Checking in the Application Facade10.5.2 Giving the Supertype an Encompassing Interface10.5.3 Using a Run-Time Attribute10.5.4 Making the Application Facade Visible to the Domain Model10.5.5 Using Exception HandlingReferences
11. Trading Packages
11.1 Multiple Access Levels to a Package11.2 Mutual Visibility11.3 Subtyping Packages11.4 Concluding ThoughtsReferences
Part 2: Support Patterns
12. Layered Architecture for Information Systems
12.1 Two-Tier Architecture12.2 Three-Tier Architecture12.2.1 The Location of the Domain Tier12.3 Presentation and Application Logic12.3.1 Advantages of the Presentation/Application Logic Split12.3.2 Stretching Facades in Client/Server Environments12.4 Database Interaction12.4.1 Linking the Domain Tier to Data Sources12.4.2 Database Interface Tier12.5 Concluding ThoughtsReferences
13. Application Facades
13.1 A Health Care Example13.2 Contents of a Facade13.2.1 Types of Methods13.2.2 Sample Methods13.3 Common Methods13.4 Operations13.5 Type Conversions13.6 Multiple FacadesReferences
14. Patterns for Type Model Design Templates
14.1 Implementing Associations14.1.1 Bidirectional and Unidirectional Associations14.1.2 Interface for Associations14.1.3 Fundamental Types14.1.4 Implementing a Unidirectional Association14.1.5 Bidirectional Implementation by Pointers in Both Directions14.1.6 Bidirectional Implementation by Pointers in One Direction14.1.7 Bidirectional Implementation by Association Objects14.1.8 Comparison of Bidirectional Implementations14.1.9 Derived Mappings14.1.10 Nonset Mappings14.2 Implementing Generalization14.2.1 Implementation by Inheritance14.2.2 Implementation by Multiple Inheritance Combination Classes14.2.3 Implementation by Flags14.2.4 Implementation by Delegation to a Hidden Class14.2.5 Implementation by Creating a Replacement14.2.6 Interface for Generalization14.2.7 Implementing the hasType Operation14.3 Object Creation14.3.1 Interface for Creation14.3.2 Implementation for Creation14.4 Object Destruction14.4.1 Interface for Destruction14.4.2 Implementation for Destruction14.5 Entry Point14.5.1 Interface for Finding Objects14.5.2 Implementation of Find Operations14.5.3 Using Classes or Registrar Objects14.6 Implementing Constraints14.7 Design Templates for Other TechniquesReferences
15. Association Patterns
15.1 Associative Type15.2 Keyed Mapping15.3 Historic Mapping15.3.1 Two-Dimensional HistoryReferences
16. Afterword
References
Part 3: Appendix
A. Techniques and Notations
A.1 Type DiagramsA.1.1 Type and ClassA.1.2 Associations, Attributes, and AggregationA.1.3 GeneralizationA.1.4 Rules and Semantic StatementsA.1.5 Fundamental TypesA.2 Interaction DiagramsA.3 Event DiagramsA.4 State DiagramsA.5 Package DiagramsReferences
B. Table of Patterns
Index
Code Snippets

Content preview from Analysis Patterns: Reusable Object Models

A. Techniques and Notations

To write a book like this, I need to use some modeling techniques, but I don’t want to spend too much time discussing them. After all, this is a book about patterns, not a book about modeling techniques (there are plenty of books on that subject). There are, as yet, no standards for techniques, so I am forced to choose something that I feel is appropriate and not too alien. I find that no method has everything and that I like to mix techniques from different methods. In this appendix I will discuss the techniques I use and the notation for them.

A.1 Type Diagrams

The type diagram shows a structural view of a system. It concentrates on describing the types of objects in the system and various kinds of static relationships ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9780134271453Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Analysis Patterns: Reusable Object Models

by Martin Fowler