Which Modeling Language?
<-- ^
-->
Modeling language needs to
support at least the following capabilities
-
Execution (Simulation)
-
Hierarchical, networked composition
of submodels
-
Formal validation techniques
-
Source coverage measurement and
reporting
-
Property verification (e.g. model
checking, theorem proving)
Must allow incorporating shared,
domain-relevant function/object theories
-
(Human) validators want to think
about domain-meaningful objects, not bit-encodings of them
-
Must standardize theories
to allow composition of models from different servers
-
e.g. submodels must agree on what
an "email message" is
-
Similar to Semantic Web ontologies,
but including reasoning knowledge as well as E-R info
-
These constrain (and hence guide)
the "level of abstraction"
Some other requirements
-
Models should support single-node
validation as well as OpenModel validation (to get 2 for 1)
-
Abstract state model (and interface
to it) must be first class to enable behavior sampling
-
Abstraction map (A) must
be expressible, computable, and required