-
Join 35 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: Software_Engineering
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
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
Practical Software Analysis vs. Design Modelling
Practical modelling in software analysis differs significantly from design. The IMHO main differences are highlighted here. Continue reading
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
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 ACM, BPM, Case Management, chaos, chaotic, cynefin, cynefin framework, dave snowden, decision making, Deputy Chief Walter Gasior, informatics, information system, knowledge management, Mary Boone, Process Management, sense-making, software development, software engineering, software requirements
Leave a comment
A simple relational Model
Modelling foundations: What does a simple diagram ‘thing – relation – thing’ say, in terms of logic? Continue reading
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
Modeling for Understanding and/xor/etc Execution
Executable models have a great potential for achieving real separation of concerns. However, some practical modeling aspects on the business side deserve closer attention. Continue reading
What kind of Computer Science matters?
Just came across Why Computer Science Matters? by Vugranam Sreedhar. He observes a decline in real computer scientists in favour of ‘commodity programmers’. Basically, I have to (sad but true) agree here, and would like to take a closer look … Continue reading
Modeling & Abstraction at the very heart of Business Requirements Analysis
From industrial practice we know a BA definitely adds a lot of value to an IT project. So, now we try to conceptualise this in contrast to the Biz Engineer’s and IT Architect’s role. As we’ll see, a BA’s special benefit is mainly based on abstraction (and thus modeling). Continue reading
modelpractice 