Tag Archives: Diagram

A simple relational Model

Modelling foundations: What does a simple diagram ‘thing – relation – thing’ say, in terms of logic? Continue reading

Posted in Foundations (rigour), Software_Engineering | Tagged , , , , , , , , , , , , , , | Leave a comment

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

Posted in Mathematics, Reflections on Abstractions, Requirements, Software_Engineering | Tagged , , , , , , , , , , , , , , , | 1 Comment

Software Modelling – a Rhino’s Perspectice

Got carried away by this little picture, I recently found in a tweet, and its correspondence to modelling. So I started fooling around a bit on blind spots, redundancy and how to handle it in software modelling. Continue reading

Posted in Epistemology | Tagged , , , , , , , , , , , , , , , | 1 Comment

Meanings of “Model”

On the different usages of ‘model’ in the sense of Business Process Model or Entity Relationship Model, and in mathematical Model Theory.

Continue reading

Posted in Epistemology | Tagged , , , , , , , , , , , | 8 Comments

Reader Acceptance of Models

Modeling trade-off: new language to learn, but easy to use the power of graphical notation. Continue reading

Posted in Software_Engineering | Tagged , , , , , , , , , , , , , , , | Leave a comment

UML and Complexity aware modeling

I believe that applying complexity classes to UML can provide a substantial benefit, if it can support the controlled (complexity aware) use of language. Continue reading

Posted in Software_Engineering | Tagged , , , , , , , , , , , , | 6 Comments