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: design

Computational Artefacts and Software Requirements

Posted on 2020 September 18 by modelpractice

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

Separation of Analysis & Design wrt. Abstraction

Posted on 2020 August 12 by modelpractice

Summing up separation of concerns of analysis and design wrt. abstraction, inspired by: Turner (2018) Computational Artifacts. Continue reading →

Posted in Software_Engineering | Tagged abstraction, analysis, computational artifact, Concerns, design, epistemology of engineering, Raymond Turner, Requirements, Requirements Analysis, Separation of Concerns, SoC, software engineering, Turner | Leave a comment
  • 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
Create a free website or 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