### Modelling:

### Tweets

- RT @TimWeilkiens: SysML 1.5 officially published! model-based-systems-engineering.com/2017/05/16/sys… 1 week ago
- RT @seidewitz: The most pointed critique I have seen on #UML in years! I shall introduce an issue to the UML Revision Task Force to fix it… 1 week ago

# Tag Archives: specification

## Reflections on Abstractions: Correctness and Completeness

An earlier post on quality properties of models is compared to basic concepts of mathematical logic, in strive for rigour. What does a formal system of mathematical logic has in common with a modelling situation as in requirements analysis? It depends … Continue reading

Posted in Mathematics, Reflections on Abstractions
Tagged abstraction, axiom, Complete, completeness, consistency, Consistent, Correct, correctness, formal system, incomplete, incorrect, incosistent, logic, model, model quality, model theory, Modelling, Requirements, resolution, software requirements specification, specification, Unambiguous, venn diagram
Leave a comment

## Models: Correct, Complete, Consistent, Unambiguous

**How do you judge how ‘good’ or ‘bad’ a model is?** I mean models like we use them in **software requirements specification** or **business analysis**. On this, one can find criteria in literature like BABOK, Wikipedia, IEEE, research papers, or textbooks. However, for some reason these criteria sets are quite different in each case. I’ve tried to get the things a little straighter, starting with the ‘big four’ quality characteristics of software requirements specifications … Continue reading

Posted in Mathematics, Requirements
Tagged abstraction, Complete, completeness, consistency, Consistent, Correct, correctness, IEEE 830, incomplete, incorrect, incosistent, logic, model, model quality, model theory, Modelling, quality criteria, Requirements, software requirements specification, specification, Unambiguous, venn diagram
1 Comment

## Reflections on Abstractions: Cases vs Models

We describe by simple means of basic Finite Model Theory a very important principle in software engineering: modelling properties is more expressive than just collecting cases. This, for example, is the reason why test cases can be derived from specifications but not vice versa. Continue reading

Posted in Mathematics, Reflections on Abstractions
Tagged abstraction, abstraction awareness, axiomatizable, Case, Finite Model Theory, finite models, formal methods, intentional programming, model, model theory, modeling, modeling theory, refinement, reflections on abstractions, ROA, specification, Test
Leave a comment

## Models and Cases

What are the next letters in this sequence?

O O T T F F S S E

Continue reading

Posted in Mathematics
Tagged 0123456789, abstraction, Bertrand Meyer, Case, emergence, model based, modeling, Principle, sequence, specification, supervenience, Test, test driven, what are the next
1 Comment