-
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: Requirements 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
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 Business Analyst, customer collaboration, IIBA, IREB, managing complexity, model, Modelling, Requirements, Requirements Analysis, Requirements Engineering, Requirements Modeling, software development, software modelling, software requirements
1 Comment
Unambiguous Requirements Models
We’ll see that the concept of ambiguity of (requirements in software engineering) models comprises structural as well as material aspects, on all model levels (top to bottom). Continue reading
Henry Ford and Business Analysts
“If I had asked people what they wanted, they would have said faster horses.” – Henry Ford –
Isn’t this a nice litte example to show what Business Analysts are good for? Continue reading
Word Problems they don’t teach you in School
You are in school or university, and wanna know how real life biz looks like? Here’s a little impression by the means of word problems: say you have a little business that offers solving word problems … Continue reading
Complexity Aware Modelling I
Wow – I discovered that beyond the actual technology there is something called business logic, and – most surprising – it was not trivial! (on Complexity Aware Modelling) Continue reading
modelpractice 