-
Join 34 other subscribers
Modelling:
- Applications (relevance) (50)
- Abstract Thinking (11)
- Software_Engineering (40)
- Foundations (rigour) (42)
- Epistemology (20)
- Mathematics (19)
- Series (42)
- Herbert Stachowiak (6)
- Model Thinking (8)
- Reflections on Abstractions (14)
- Requirements (16)
- Uncategorized (3)
- Applications (relevance) (50)
Twitter
Tweets by modelpractice
Category Archives: Foundations (rigour)
Modelling the World …
Overview of blog posts on Modelling Theory, Practical Software Modelling, Epistemology of Engineering, Abstraction, … Continue reading
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
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 computational artefact, computer science, concrete computation, engineering, epistemology, Gualtiero Piccinini, lighweight formal metrhods, Ontology, pancomputation, propositional logic, Raymond Turner, Requirements Engineering, requirements specification, software design, Spichkova, Technical Artefact, Toaster, Zamansky
2 Comments
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 analysis, computational artefact, computer science, design, Elements of Software RequirementsEngineering, engineering, epistemology, mind-body problem, Peter Kroes, Raymond Turner, Requirements, Requirements Engineering, software, software engineering, specification, Technical Artefact
5 Comments
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 abstraction, Bernhard Ganter, Bob Hale, computational artifact, concept analysis, Crispin Wright, David Lewis, epistemology, epistemology of engineering, formal concept analysis, Gideon Rosen, John Burgess, Raymond Turner, software engineering, technical artifact, Turner
1 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 computer science, Elements of Software RequirementsEngineering, engineering, epistemology, Herbert Simon, mind-body problem, Nicola Angius, Peter Kroes, Raymond Turner, Requirements, Requirements Engineering, software, software engineering, specification, Technical Artefact, Teleology
4 Comments
A simple relational Model
Modelling foundations: What does a simple diagram ‘thing – relation – thing’ say, in terms of logic? Continue reading
Categories of semantic Models by Stachowiak
Categorisation by example of semantic models, i.e. models as we use them in software engineering etc, according to Herbert Stachowiak. Continue reading
Posted in Epistemology, Herbert Stachowiak, Requirements
Tagged abstraction, Allgemeine Modelltheorie, empirical models, Finite Model Theory, formal models, General Model Theory, Herbert Stachowiak, Modelling, modelling theory, Requirements Modeling, scientific models, semantic model, semantics, Semiology, Semiotics, Semology, Stachowiak
Leave a comment
1 + x = 3 as a Query
Strongly reduced recap of basic software engineering concepts: Query, Result Set, Requirement. Continue reading
modelpractice 