Author Archives: modelpractice

About modelpractice

Modeling Theory and Abstraction Awareness in strive for scientific rigour and relevance to information systems engineering.

Artefacts in Technical and Social Contexts

A Computational Artefact in a human context is not just an embedded system from a machine context with a cuter interface. Continue reading

Posted in Epistemology, Requirements | Tagged , , , , , , , , , , , , | Leave a comment

The Beauty of Theories and Wittgenstein’s Grief

Scientific theories have the capacity to cause passion, or said and judged to be beautiful (or not). They can be subject to aesthetic judgements, have the capacity to trigger aesthetic experiences and are challenging, both for the artist and the observer. Continue reading

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

Artefacts of logic Intention

What are the advantages of stating the intention of a software in a language over expressing it as cases? “Understanding”? Continue reading

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

Computational Artefacts and Software Requirements

What if the intention of a technical artefact is not at all physical, but solely logical? Continue reading

Posted in Epistemology, Requirements | Tagged , , , , , , , , , , , , , , , | 4 Comments

Separation of Analysis & Design wrt. Abstraction

Summing up separation of concerns of analysis and design wrt. abstraction, inspired by: Turner (2018) Computational Artifacts. Continue reading

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

A New Account of Abstraction?

Software engineering could benefit from a more rigorous grounding in epistemology, e.g., for the account of abstraction. So, let’s see what we can learn from: Raymond Turner (2018) Computational Artifacts Continue reading

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

Technical Artefacts and Software Requirements

The epistemic concept of “Technical Artefact” may prove useful for studying requirements engineering. It brings together the notions of the world as physical objects with the world of intentionally acting agents. Continue reading

Posted in Epistemology, Requirements, Software_Engineering | Tagged , , , , , , , , , , , , , , , | 3 Comments

Practical Software Analysis vs. Design Modelling

Practical modelling in software analysis differs significantly from design. The IMHO main differences are highlighted here. Continue reading

Posted in Requirements, Software_Engineering | Tagged , , , , , , , , , , , , , | 1 Comment

The Killer Application of Software Modelling

From my experience as a business analyst (BA) I would say: checking or transforming models is interesting and important, but the real killer application of a model in software development is (simply) talking about it. Continue reading

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

Software for Managing Chaos

Workers in highly volatile contexts are best supported by software that implements generic communication or selfmanagement functionality. Like ACM systems do. Continue reading

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