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.1. Atomic and Composite Parts2.3.1.2. Atomic Parts63• When we observe2.3.1.2 Atomic Parts– what we have decided, i.e., analysed, to be an endurant,– more specifically an atomic part, of a domain,– we are observing an instance of an atomic part.• When we describe those instances– we describe, not their values, i.e., the instances,– but their∗ type and∗ properties.A Precursor for Requirements Engineering 63 c○ Dines Bjørner 2012, DTU Informatics, Techn.Univ.of Denmark – July 20, 2012: 12:33
642. Domain Entities 2.3. Parts2.3.1. Atomic and Composite Parts2.3.1.2. Atomic Parts• In this section on endurant entitieswe shall unfold what these properties might be.• But, for now, we focus on the type of the observed atomic part.• So the situation is that we are observing a number of atomic parts– and we have furthermore decided that– they are all of “the same kind”.c○ Dines Bjørner 2012, DTU Informatics, Techn.Univ.of Denmark – July 20, 2012: 12:33 64 Domain Science & Engineering
- Page 1 and 2: 33NICE TO SEE YOU BACKA Precursor f
- Page 5 and 6: 36 2. Domain Entities• When we ob
- Page 7 and 8: 382. Domain Entities• Phenomena:
- Page 9 and 10: 402. Domain Entities• Domain Onto
- 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 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 62 and 63: 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.
2. Domain Entities 2.3. Parts2.3.1. Atomic and Composite Parts2.3.1.2. Atomic Parts63• When we observe2.3.1.2 Atomic Parts– what we have decided, i.e., analysed, to be an endurant,– more specifically an atomic part, of a domain,– we are observing an instance of an atomic part.• When we describe those instances– we describe, not their values, i.e., the instances,– but their∗ type and∗ properties.A Precursor for Requirements Engineering 63 c○ Dines Bjørner 2012, <strong>DTU</strong> <strong>Informatics</strong>, Techn.Univ.of Denmark – July 20, 2012: 12:33
Change language