modelpractice
Modelling the world to improve it through software. In strive for rigour of science and relevance to engineering.
Skip to content
  • |=
  • Stachowiak
  • Requirements
  • …
    • Inspirations
    • Readings
    • About

Tag Archives: software design

Artefacts of logic Intention

Posted on 2020 November 4 by modelpractice

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

Practical Software Analysis vs. Design Modelling

Posted on 2017 October 2 by modelpractice

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

Posted in Requirements, Software_Engineering | Tagged BPMN, domain model, DSL, ERM, model, Modelling, modelling language, modelling tool, Requirements Analysis, requirements modelling, software analysis, software analysis modelling, software design, UML | 2 Comments
  • 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)
  • Twitter

    Tweets by modelpractice
  • Blogroll

    • Jordi Cabot
    • T.Y.
    • Bertrand Meyer
    • Richard Zach
    • Vincent Hanniet
    • Camiano's Ways
    • xkcd
  • Tags

    • abstraction
    • abstraction awareness
    • analysis
    • BPMN
    • Business Analysis
    • Complexity
    • computational thinking
    • computer science
    • Diagram
    • engineering
    • epistemology
    • Finite Model Theory
    • General Model Theory
    • Graph Theory
    • Herbert Stachowiak
    • Language
    • logic
    • model
    • modeling
    • Modelling
    • modelling theory
    • model theory
    • model thinking
    • reflections on abstractions
    • Requirements
    • Requirements Analysis
    • Requirements Engineering
    • Requirements Modeling
    • ROA
    • software
    • software engineering
    • software modelling
    • Stachowiak
    • thinking
    • UML
  • On Modelling Theory, Abstraction Awareness and Complexity aware Modelling.

    Modelling theory is about the mapping from real world to models with main focus on software engineering and related areas like Business Process Modelling. Abstraction is seen as the core of modelling, thus Abstraction Awareness is closely related to Modelling Theory. Also Complexity Aware Modelling is close to Abstraction Awareness and Modelling Theory, since it it about applying results of complexity theory and finite model theory to software modelling, business modelling, systems engineering and software engineering.
  • Meta

    • Create account
    • Log in
    • Entries feed
    • Comments feed
    • WordPress.com
  • Unknown's avatar

modelpractice
Blog at WordPress.com.
  • Subscribe Subscribed
    • modelpractice
    • Join 34 other subscribers
    • Already have a WordPress.com account? Log in now.
  • Privacy
    • modelpractice
    • Subscribe Subscribed
    • Sign up
    • Log in
    • Report this content
    • View site in Reader
    • Manage subscriptions
    • Collapse this bar
Design a site like this with WordPress.com
Get started