A discussion of architectural patterns from a modeling perspective. How modeling can help the organization of your information system? How (bad) modeling practices can damage it?
Models need to represent the reality as accurately as possible. Nevertheless, complex systems are subject to uncertainty something difficult to express with plain UML. We propose a way to represent uncertainty on software models. Our uncertainty values can then be propagated through model transformations to evaluate the impact on other parts of the system.
Washing symbols are a universal way to quickly explain key properties of a piece of cloth and how you should handle it. A similar approach for models would help designers to understand the context, goal, quality,… of a model they just ran into.
Continuity is a drawing and a modeling tool at the same time and tries to combine the best of both worlds to help you create beautiful formal models
TemporalEMF adds native temporal support for models. Models are automatically treated as temporal models and can be subjected to temporal queries to retrieve the model contents at different points in time. Behind the scenes, the history of a model is transparently stored in a NoSQL database.
The first step in refactoring modeling technology is to understand and tame language complexity. This post proposes several solutions for that, for instnace, the definition of alternative notations for the same conceptual language.
