The OOIE meta-model is notated in a small subset of OOIE. The first four diagrams are the object model. The next two begin the dynamic model, concerning operations and event diagrams, and the last three diagrams are the state models. Class boxes and relation lines in all diagrams are clickable to see comments.
This diagram covers the model of "things" and their connections. It is an analysis model, to be filled out at design-time using the Mapping Model. Start at Object and Object Type, then follow the Read Next links from Object Type. Also see summary with an example at Place Relation. Attributes are not included in the meta-model. See discussion at Mapping.
This diagram covers how relations are implemented during design. Specific mappings are chosen to implement the relations defined during analysis. Also see summary an example at Place Relation.
This diagram covers how "things" are grouped into types of things.
See Object Type Partition.
This diagrams covers: 1) the "interface" to operations, that is, information about operations that is independent of how they are carried out. 2) the linkage between an operation and the way it is carried out. 3) polymorphism. Start at Operation, then follow the Read Next links from there.
This diagram covers a particular way of writing methods for operations provided in OOIE. Technically this should be called the Event Schema Model, because it does not cover how the model is displayed (the "diagram")..
This diagram covers the static aspects of states. Start at State and follow the Read Next links.
This diagram shows the connection between states and events and how they are typed. Start at State Change and follow the Read Next links.
This model uses the other state concepts to model finite state machines. Start at State Machine and follow the Read Next links.
This diagram is for modelling part structure of objects. Part structure refers to the types of parts that an object will have and the way they are connected together. For example, companies may be modelled as having various departments with communication connections between them. Since relations are object types in OOIE, relations can have parts, just like objects can. For example, when one person calls another on the telephone, they are related by a composite relationship containing receivers, switches, the various wires connecting them. More about this at Relation Part Specification. Start at Part Specification and follow the Read Next links. See also A User-Level Model of Composition and An Html Demo of Inheriting Part Information.