I am talking about a domain model of the problem under consideration. That model is the same thing from analysis/design to code. It is independent of technical concerns and plumbing. Independent of a particular interface or mechanism for persistence. I'm talking about using standard programming language features, rather than yet another (diagrammatic) language that requires translation to executable code.
Those technical concerns are dependent on the non-functional requirements of the particular required solution. This includes aspects of concurrency.
I suspect your interested in a "framework" that supports both problem domain modeling and specific technical circumstances?
Those technical concerns are dependent on the non-functional requirements of the particular required solution. This includes aspects of concurrency.
I suspect your interested in a "framework" that supports both problem domain modeling and specific technical circumstances?