Tag Archives: Diagram

A simple relational Model

Posted on 2016 October 1 by modelpractice

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

Posted in Foundations (rigour), Software_Engineering | Tagged , , , , , , , , , , , , , , | 1 Comment

Reflections on Abstractions: The Use Case trade-off

Posted on 2013 July 22 by modelpractice

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 , , , , , , , , , , , , , , , | 2 Comments

Software Modelling – a Rhino’s Perspectice

Posted on 2011 October 26 by modelpractice

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”

Posted on 2011 March 27 by modelpractice

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

Posted on 2011 March 21 by modelpractice

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

Posted on 2011 February 2 by modelpractice

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