NICE TO SEE YOU BACK - DTU Informatics
NICE TO SEE YOU BACK - DTU Informatics NICE TO SEE YOU BACK - DTU Informatics
2. Domain Entities 2.3. Parts2.3.2. Properties2.3.2.2. Mereology93Concrete Models of MereologyThe concrete mereology example models above illustrated maps and sequences assuch models.• In general we can model mereologies in terms of– (i) sets: A-set,– (ii) Cartesians: A 1 ×A 2 ×...×A m ,– (iii) lists: A ∗ , and– (iv) maps: A → m B,where A, A 1 , A 2 ,...,A m and B are types [we assume that they are type names] andwhere the A 1 , A 2 ,...,A m type names need not be distinct.• Additional concrete types, say D, can be defined by concrete type definitions,D=E, where E is either of the type expressions (i–iv) given above or (v) E i |E j , or(vi) (E i ). where E k (for suitable k) are either of (i–vi).• Finally it may be necessary to express well-formedness predicates for concretelymodelled mereologies.A Precursor for Requirements Engineering 93 c○ Dines Bjørner 2012, DTU Informatics, Techn.Univ.of Denmark – July 20, 2012: 12:33
942. Domain Entities 2.3. Parts2.3.2. Properties2.3.2.2. MereologyAbstract Models of MereologyAbstractly modelling mereology of parts, to us, means the following.• With part types P 1 , P 2 , . . . , P n– is associated the unique part identifier types, Π 1 , Π 2 , . . . , Π n ,– that is uid Π i : P i →Π i for i ∈ {1..n},• and with each part type, P i ,– is then associated a mereology observer,– mereo P i : P i → Π j -set×Π k -set×...×Π l -set,• such that for all p:Pi we have that– if mereo P i (p) = ({..., π ja , ...},{..., π kb , ...},...,{..., π lc , ...})– for i,j,k,...l ∈ {1..n}– then part p:P i is connected (related) to the parts identified by..., π ja , ... π kb , ..., π lc , ....• Finally it may be necessary to express axioms for abstractly modelled mereologies.c○ Dines Bjørner 2012, DTU Informatics, Techn.Univ.of Denmark – July 20, 2012: 12:33 94 Domain Science & Engineering
- Page 11 and 12: 422. Domain Entities 2.1. Entities2
- Page 13 and 14: 442. Domain Entities 2.1. Entities2
- Page 15 and 16: 462. Domain Entities 2.1. Entities2
- Page 17 and 18: 482. Domain Entities 2.1. Entities2
- Page 19 and 20: 502. Domain Entities 2.2. Endurants
- Page 21 and 22: 522. Domain Entities 2.2. Endurants
- Page 23 and 24: 542. Domain Entities 2.3. Parts•
- Page 25 and 26: 562. Domain Entities 2.3. Parts2.3.
- Page 27 and 28: 582. Domain Entities 2.3. Parts2.3.
- Page 30 and 31: 2. Domain Entities 2.3. Parts2.3.1.
- Page 32 and 33: 2. Domain Entities 2.3. Parts2.3.1.
- Page 34 and 35: 2. Domain Entities 2.3. Parts2.3.1.
- Page 36 and 37: 2. Domain Entities 2.3. Parts2.3.1.
- Page 38 and 39: 2. Domain Entities 2.3. Parts2.3.1.
- Page 40 and 41: 2. Domain Entities 2.3. Parts2.3.1.
- Page 42 and 43: 2. Domain Entities 2.3. Parts2.3.1.
- Page 44 and 45: 2. Domain Entities 2.3. Parts2.3.1.
- Page 46 and 47: 2. Domain Entities 2.3. Parts2.3.1.
- Page 48 and 49: 2. Domain Entities 2.3. Parts2.3.2.
- Page 50 and 51: 2. Domain Entities 2.3. Parts2.3.2.
- Page 52 and 53: 2. Domain Entities 2.3. Parts2.3.2.
- Page 54 and 55: 2. Domain Entities 2.3. Parts2.3.2.
- Page 56 and 57: 2. Domain Entities 2.3. Parts2.3.2.
- Page 58 and 59: 2. Domain Entities 2.3. Parts2.3.2.
- Page 60 and 61: 2. Domain Entities 2.3. Parts2.3.2.
- Page 64 and 65: 2. Domain Entities 2.3. Parts2.3.2.
- Page 66 and 67: 2. Domain Entities 2.3. Parts2.3.2.
- Page 68 and 69: 2. Domain Entities 2.3. Parts2.3.2.
- Page 70 and 71: 2. Domain Entities 2.3. Parts2.3.2.
- Page 72 and 73: 2. Domain Entities 2.3. Parts2.3.2.
- Page 74 and 75: 2. Domain Entities 2.3. Parts2.3.2.
- Page 76 and 77: 2. Domain Entities 2.3. Parts2.3.2.
- Page 78 and 79: 2. Domain Entities 2.3. Parts2.3.3.
- Page 80 and 81: 2. Domain Entities 2.3. Parts2.3.3.
- Page 82 and 83: 2. Domain Entities 2.3. Parts2.3.3.
- Page 84 and 85: 2. Domain Entities 2.3. Parts2.3.4.
- Page 86 and 87: 2. Domain Entities 2.3. Parts2.3.4.
- Page 88: 118LONG BREAKc○ Dines Bjørner 20
942. Domain Entities 2.3. Parts2.3.2. Properties2.3.2.2. MereologyAbstract Models of MereologyAbstractly modelling mereology of parts, to us, means the following.• With part types P 1 , P 2 , . . . , P n– is associated the unique part identifier types, Π 1 , Π 2 , . . . , Π n ,– that is uid Π i : P i →Π i for i ∈ {1..n},• and with each part type, P i ,– is then associated a mereology observer,– mereo P i : P i → Π j -set×Π k -set×...×Π l -set,• such that for all p:Pi we have that– if mereo P i (p) = ({..., π ja , ...},{..., π kb , ...},...,{..., π lc , ...})– for i,j,k,...l ∈ {1..n}– then part p:P i is connected (related) to the parts identified by..., π ja , ... π kb , ..., π lc , ....• Finally it may be necessary to express axioms for abstractly modelled mereologies.c○ Dines Bjørner 2012, <strong>DTU</strong> <strong>Informatics</strong>, Techn.Univ.of Denmark – July 20, 2012: 12:33 94 Domain Science & Engineering