Semantic Integration of Heterogeneous Software Specifications

Grosse-Rhode

software specification development model semantic integration

@book{grosse:specification-integration2004,
  title={Semantic Integration of Heterogeneous Software Specifications},
  author={Gro\ss e-Rhode, M.},
  year={2004},
  publisher={Springer}
}

Software development entails many construction of many different models

• Class diagrams model static structure
• Use cases model main functionality but not structure or implementation
• Process calculi model temporal ordering of actions

Semantic integration of those can be used to keep them in sync, verify models and connections, etc

Models might provide different information, or a different view on the same information

A set of specifications is consistent if there is a common model of all specifications

www.cs.ukc/research/groups/tcs/openview

Reference model serves as common semantic domain interpreting all specs of all languages

Sets of admissible interpretations

Reference model

• Must be formal
  • Should have flexible granularity
• Must be able to capture developments, record modelling decisions
• Permit composition of models
  • Build larger, more complex models
    • Define how models connect
    • Define result of composition
      • Must be able to be considered a single model

Presents a formalism for such a reference model

• Transition graphs, data signatures, and so on...