Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.
Figure 1: Sample of ERD notation
Figure 2: Sample of UML notation
Figure 3: Many-to-many association
Figure 4: Many-to-many resolution
Figure 7: Simplified example of the Party/Role pattern
Figure 8: Some common assembly patterns – ready for integration
Figure 9: Sample objects for a land transaction scenario
Figure 10: Integration pattern / land transaction scenario
Figure 11: Simplified example of the Party/Role pattern
Figure 12: Party details – name, address, and identifier
Figure 13: Party contact rules
Figure 14: Specialization through inheritance
Figure 15: Party/Role sample objects for a school scenario
Figure 16: Party relationships – implied agreements, implied roles
Figure 17: Party relationships – implied agreements, explicit roles
Figure 18: Party relationships – explicit agreements, explicit roles
Figure 19: Generalization sets
Figure 20: Sample low-level generalization #1
Figure 21: Sample low-level generalization #2
Figure 22: Sample medium-level generalization
Figure 23: Sample high-level generalization
Figure 24: Specialization by inheritance
Figure 25: Specialization by association
Figure 26: Thinking outside the box – the problem
Figure 27: Thinking outside the box – a solution
Figure 28: Simplified bill-of-materials pattern
Figure 29: Generalized bill-of-materials pattern
Figure 30: Adapted bill-of-materials pattern
Figure 31: Integration pattern / land transaction scenario
Figure 32: Integration pattern palette
Figure 33: Integration pattern / mineral extraction scenario
Figure 34: Integration pattern / emergency response scenario
Figure 35: Integration pattern / banking scenario
Figure 36: Integration pattern / a pattern of patterns!
Figure 37: Delivery logistics for simple/atomic items
Figure 38: Delivery logistics for complex/composite items
Figure 39: The conceptual versus logical dilemma
Figure 40: Specific domain model
Figure 41: Generalized domain model
Figure 42: Applying the generalization to specialized domains
Figure 43: The 80/20 rule mirage
Figure 44: A model for a metadata-driven "Decision table"
Figure 45: Shower screen schematic
Figure 46: Computation rules-in-data
Figure 47: Simplified bill-of-materials pattern
Figure 48: Generalized bill-of-materials pattern
Figure 49: Shower screen bill-of-materials
Figure 50: Integration pattern / shower screen scenario
Figure 51: Logical context diagram / shower screen scenario
Figure 52: Logical domain (Agreement) model / shower screen scenario
Figure 53: UML – derivable attribute
Figure 55: UML – unique object ID?
Figure 56: UML – associations and "foreign keys"?
Figure 57: UML – attribute multiplicity (optionality, cardinality)
Figure 58: UML – attribute data types
Figure 59: UML – properties as associations
Figure 60: UML – properties as attributes
Figure 61: UML – data types with operations
Figure 62: UML – rich, user-defined data types
Figure 63: Traditional entities and relationships
Figure 64: Classes and associations
Figure 67: UML – many-to-many associations with no resolution
Figure 68: UML – inheritance of data