### Modelling:

- Applications (relevance) (47)
- Abstract Thinking (11)
- Software_Engineering (39)

- Foundations (rigour) (37)
- Epistemology (17)
- Mathematics (19)

- Series (38)
- Herbert Stachowiak (6)
- Model Thinking (8)
- Reflections on Abstractions (14)
- Requirements (13)

- Uncategorized (3)

- Applications (relevance) (47)
### Twitter

- RT @peoppenheimer: SEP: Emergent Properties ift.tt/2l9BuLF #philosophy - 21 hours ago

# Tag Archives: model theory

## 1 + x = 3 as a Query

Strongly reduced recap of basic software engineering concepts: Query, Result Set, Requirement. Continue reading

## Reflections on Abstractions: The Use Case trade-off

Based on the elementary terms of relational structures, this little example shows the basic trade-off of Use Cases: understandability vs redundancy. Continue reading

## Examples of Preterition and Abundance in Modelling

In addition to the earlier posting “Stachowiak on Preterition and Abundance in Modelling” here are some examples of Preterition and Abundance in Photography, Use Case Models, and Graph or Flow notations. Continue reading

Posted in Epistemology, Herbert Stachowiak, Software_Engineering
Tagged Abduction, abstraction, Actor, Allgemeine Modelltheorie, Definition, General Model Theory, Herbert Stachowiak, Homomorhism, Homomorphism preservation theorem, Labyrinth, Maze, model, model theory, Modelling, original, Preteritition, Stachowiak, Use Case, Use Case Model
5 Comments

## Stachowiak on Preterition and Abundance in Modelling

In his 1973 book “Allgemeine Modelltheorie” Herbert Stachowiak discusses the concepts of Preterition, Abundance and Contrastation of Original-Model mappings. This can be interpreted using homomorphism preservation and other logical concepts. Continue reading

Posted in Epistemology, Herbert Stachowiak
Tagged Abduction, abstraction, Allgemeine Modelltheorie, Contrastation, Definition, General Model Theory, Herbert Stachowiak, Homomorhism, Homomorphism preservation theorem, logic, Mapping, model, model theory, Modelling, original, Preteritition, Stachowiak
10 Comments

## Reflections on Abstractions: Correctness and Completeness

An earlier post on quality properties of models is compared to basic concepts of mathematical logic, in strive for rigour. What does a formal system of mathematical logic has in common with a modelling situation as in requirements analysis? It depends … Continue reading

Posted in Mathematics, Reflections on Abstractions
Tagged abstraction, axiom, Complete, completeness, consistency, Consistent, Correct, correctness, formal system, incomplete, incorrect, incosistent, logic, model, model quality, model theory, Modelling, Requirements, resolution, software requirements specification, specification, Unambiguous, venn diagram
Leave a comment

## Models: Correct, Complete, Consistent, Unambiguous

**How do you judge how ‘good’ or ‘bad’ a model is?** I mean models like we use them in **software requirements specification** or **business analysis**. On this, one can find criteria in literature like BABOK, Wikipedia, IEEE, research papers, or textbooks. However, for some reason these criteria sets are quite different in each case. I’ve tried to get the things a little straighter, starting with the ‘big four’ quality characteristics of software requirements specifications … Continue reading

Posted in Mathematics, Requirements
Tagged abstraction, Complete, completeness, consistency, Consistent, Correct, correctness, IEEE 830, incomplete, incorrect, incosistent, logic, model, model quality, model theory, Modelling, quality criteria, Requirements, software requirements specification, specification, Unambiguous, venn diagram
1 Comment

## Reflections on Abstractions: Cases vs Models

We describe by simple means of basic Finite Model Theory a very important principle in software engineering: modelling properties is more expressive than just collecting cases. This, for example, is the reason why test cases can be derived from specifications but not vice versa. Continue reading

Posted in Mathematics, Reflections on Abstractions
Tagged abstraction, abstraction awareness, axiomatizable, Case, Finite Model Theory, finite models, formal methods, intentional programming, model, model theory, modeling, modeling theory, refinement, reflections on abstractions, ROA, specification, Test
Leave a comment

## Stachowiak’s K-System of Modelling

Beyond the colloquial fundamental model properties Stachowiak gives a more formal definition of model: “Explication of the Concept of Model” … Continue reading

## General Model Theory by Stachowiak

In his 1973 book “Allgemeine Modelltheorie” (General Model Theory) Herbert Stachowiak describes the fundamental properties that make a Model: Mapping, Reduction, and Pragmatism. Continue reading

## Lazy Friday (and First Order Logic)

Can “the company has 3 problems” be formalized in First Order language? Picture the sentence in the context of a management presentation … Continue reading