Metapattern invites the modeler to generate (more) flexible models.

in: Metapattern as context orientation: meeting Odell's challenge of object orientation

 

Rigorously combining time with context[, …] Metapattern supports the designer's art to the extent that a. (s)he doesn't have to worry about temporal differentiation and b. behavioral differentiation can be modeled unambiguously, that is contextually.

in: Notes on Metapattern, part 1

 

It should be clear that the assumption of behavioral relativity or, in other words, interdependency, involves a departure from modeling as analysis. Modeling at the scale of behavioral variety is not a matter of taking objects for granted in the sense of logical atomism, with analysis limited to just sticking equally absolutely valid labels on. Instead, in the open information space contingency rules. Modeling must be practiced as design.

in: Open conceptual modeling with Metapattern

 

It makes nine terms available for dialogically structural attribution of each participant’s involvement. More consistent precision is always an improvement, I would say. And, most practically, it serves to arrive at unambiguous design models for information systems regardless of — scope and — variety. This might not be your goal, but it certainly is mine and being able to confirm alignment with dialogicality is for me a sure sign (!) that I am on the right track.

in: note 53.43

 

I can imagine that modeling for integration initially comes across as counterintuitive. You often need to consider and order concepts upside-down (actually: downside-up) when compared to modeling for a separate, small-scale application. […] What needs to be included for disambiguation, not only across all currently relevant systems, bur for what you expect for the future, too? Don’t try to be exhaustive, though. [… F]rom one concept comes another, and so on. You’ll quickly see an overview developing …

in: note 71.19

 

Of course, you cannot do conceptual modeling without deep understanding of what both is and is not impossible for making ‘it’ into a tool. But then, conceptual modeling is about acquiring — and documenting — a deep understanding of reality first. Such a model explains what the relevant information is and/or should be unambiguously about. Understanding is served by as much as possible abstracting from whatever technology might be applied for actual information management. In fact, the choice of technology/-gies can only be responsibly made on the basis of the conceptual model, that is, later.

in: note 71.36

 

You cannot arrive at a conceptual model for integrated order through addition of separately drawn-up models. Integrity of design requires focused design.

in: note 71.40

 

Metapattern doesn ’t entail whatever logic for ‘calculating ’ additional contexts, et cetera. What you see is what you get. :-) The modeller (also read: human designer) does the modelling.

in: note 80.10