Figure 1-1 Raising the level of abstraction
Figure 1-2 Raising the level of reuse
Figure 1-3 The difficulty of reusing applications
Figure 2-1 Models, metamodels, and platforms
Figure 2-2 Platforms and platform realizations
Figure 2-3 Mappings, mapping functions, and mapping rules
Figure 2-4 Marks and marking models
Figure 2-5 From PIMs to PSMs
Figure 3-1 Abstraction, classification, and generalization
Figure 3-2 Domain-level class diagram for banking model
Figure 3-3 Domain-level class diagram for security domain
Figure 3-4 Subject matter and modeling language abstraction levels
Figure 3-5 Design-level class diagram for banking model
Figure 4-1 Excerpt from the UML metamodel
Figure 4-2 Metamodel in relation to developer models
Figure 4-3 Banking model as instances of metamodel classes
Figure 4-4 Four-level metamodel hierarchy
Figure 5-1 Merging mapping
Figure 6-1 A very simple marking model
Figure 7-1 Excerpt of UML metamodel in MOF
Figure 7-2 Stereotype persistent applied to elements of type Class
Figure 7-3 Defining an attribute for a stereotype
Figure 7-4 Showing values of stereotypes and corresponding instance object) specifications
Figure 7-5 A graphical representation of a network
Figure 7-6 Metamodel for network
Figure 7-7 UML rendition of metamodel for network
Figure 7-8 Mapping between network and UML metamodels
Figure 7-9 Marking stereotype as mandatory
Figure 8-1 Porting models
Figure 9-1 Essential elements of Executable UML
Figure 9-2 Domain-level class diagram for security domain
Figure 9-3 Relation between application and model compiler
Figure 10-1 A design-time interoperability bus
Figure 11-1 Example domain chart
