-
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
- RT @EgbertRijke: The univalent hydrocarbons are premiering today at the Category Theory Octoberfest richardblute.ca/octoberfest-20… Time: 15:45 U… - 4 months ago
Tag Archives: engineering
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
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
Craftsman or Engineer?
A lot has been written on the differences between Craftsman and Engineer. Recently I came across a simple example by Hofstadter & Sander, that nicely shows the basic difference in thinking: Continue reading
Posted in Abstract Thinking, Software_Engineering
Tagged abstraction, analogy, craft, craftsman, craftsmanship, Douglas Hofstadter, Emmanuel Sander, engineer, engineering, Hofstadter, marking, model, Modelling, parallelogram, rectangle, rhombus, software engineering, square, surfaces and essences
4 Comments
Abstraction makes the Engineer
From my own experience I may say, what separates the engineer from the craftsman is clearly the ability to abstract. Continue reading
Posted in Abstract Thinking, Software_Engineering
Tagged abstraction, analogy, Douglas Hofstadter, education, Emmanuel Sander, engineer, engineering, Hofstadter, marking, model, Modelling, parallelogram, rectangle, rhombus, software engineering, square, surfaces and essences, thinking
Leave a comment
Every method works well on the scenarios its author publishes
An excerpt from John D. Cook’s Blog. Although this is actually about methods in Statistics and Simulation, it strongly reminded me to methods in Software Engineering … Continue reading
Humanities #fail
Basic hermeneutic ideas, like the influence of context on meaning and understanding of things seems to be a completely new idea for many contemporaries. Continue reading
Posted in Abstract Thinking
Tagged abstraction, business, conflict, dialectics, engineering, epistemology, hermeneutics, humanities, interpretation, psycology, rant, science, social, software
2 Comments
Just Who Plays, Obeys
Only a developer (or engineer) who may play is also willing to obey (QM). Continue reading
modelpractice 