1. Three dimensions of formal languages Arve Meisingset Telenor R&D

2. Dimensions 1. Denotation 2. Instantiation 3. Implementation But first, the language itself

3. The language as a syntax tree Population Name 1 Company Name Telenor Employee Number 017976 <> Employee ’ Company ’ Population Person Name Arve Meisingset Person Name Arve Meisingset Labels are local to the superior node Superior nodes provide the context in an attachment grammar

4. Graphic notation isomorphic to alphanumerical notation Population Emplyee Company Person Company Person Emplyee Simplification

5. Even labels and tokens are syntax trees Population Name 1 Company Name : T e l e n o r Provides lists of significant duplicates

6. Algorithmic and navigating functions are subordinate to data ref. UML class diagrams Population Company Name Telenor Employee Number 017976 <> Employee ’ Company ’ Population Person Name Example Arve Meisingset PS. Subordinate, Sequence and Operator form a threedimensional tree; ie. <> and ’ are not needed with navigating references between the nodes – as an alternative to the Turing tape

7. 1. Denotations Population English Company Name Telenor Denotation <> Denotation ’ Company ’ English ’ Population Phenomena Bedrift Phenomena Bedrift Explisit Isomorphic mapping from Terminologies to Phenomena The isomorphic mapping is made between inscriptions ; there is no need for strings Phenomena are themselves data inside some observer

8. Note on modelling Cir. group Circuit Cable pair Is a Cable pair a physical entity? Is a Circuit a physical entity Is Circuit group a physical entity? Or are they just data providing overview of other data – to serve some tasks? Do most data model nothing? Provides overview of Circuits terminated in the same two Exchanges 1

9. 2. Instatiations System Schema P <> ’ System (Population Company Name Population S <> ’ System (Schema Company Name Telenor Company Name Telia Enforced implicit Homomorphic mapping from Instances to Classes Schema and Population references Mappings from instances to classes

10. Graphic notation with recursion System Schema Company Population Company S S Note that class labels are copied into every instance, but not every (subordinate) detail needs be instantiated Homomorphic dotted implicit moppings

11. Detailed Graphic notation System Schema Company Population Company S S The syntax tree is made up of lists of lists with significant duplicates

12. Note on homomorphism CompanycOMPANY Company Languages not satisfying the homomorphism requirement are translated to implementations before instantiation Ie. Not Class Company BetterCompany Class BestCompany Instantiation Implementation

13. Note on Subclasses CompanyEmployeePerson Phenomena acting as roles of other phenomena is replacing the subclass notion The Schema-Population references are more generic than and replacing nheritance Also Contents schemata providing views of Application schemata, have a similar effect Also Access control must be much more powerfull than hiding by classes

14. 3. Implementation by the Data transformation architecture Compiler architecture The Application schema provides the domain model inside the implementation; implementation specifications are added and do not replace the Application schema LSCSETSOSITSDSPS External schemataApplication schemaInternal schemata DBHCI Processes state abstract implementations Schemata and mappings between schemata state the rules for transformation of data between two media

15. Implementation System schema External schema LSLayout schema CSContents schema Application schema ETSExternal terminology schema OSConcept schema ITSInternal terminology schema Internal schema DSDistribution schema PSPhysical schema

16. Implementation on multiple media DBAlfa ProcessTele Graphic Tape SG10 ? Reports

17. Implementation Note on partial reuse of more central schemata DBAlfa ProcessTele Graphic Tape Reports

18. Implementation Mapping from External terminology schemata to Internal terminology schemata CompanyC1-record C2-record C1-C2-set If a Specification is a Model of an Implementation, then the Specification has to be Isomorphic to the Implementation Only change of labels and details are permitted. Often, as examplified, the mapping is not isomorphic. We do not require an isomorphic mapping from Application schemata to Internal schemata, but the Application schema must itself be in the running implementation

19. Schemata can themselves be stored in a database. Hence, you can have external and internal forms of each schema Internal executable form External form, presented to developers and users LS CS ETS CS ITS DS PS SG10 ?

20. Conclusions UML does neither Model implementations nor anything else SG10 languages are neither Description techniques for implementations nor of anything else Process and Block are internal implementation notions External HCI aspects are not addressed by SG10 Data(base) aspects are not addressed by SG10 Will competition come from these domains, and is UML such an approach?