Changeset 10742
- Timestamp:
- 14 Nov 2013, 07:46:13 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
main/eko-disco-specs/trunk/data.rst
r10738 r10742 50 50 51 51 Connected to: :ref:`label-customer` (1:1), 52 :ref:`label-contact-address` (1: |n0|), :ref:`label-contact-email`53 (1: |n0|), :ref:`label-contact-phone` (1:|n0|)52 :ref:`label-contact-address` (1:p), :ref:`label-contact-email` 53 (1:n), :ref:`label-contact-phone` (1:p) 54 54 55 55 Used in the following use cases: … … 64 64 addresses we store some timestamp that indicates when the respective 65 65 email address was last checked successfully (thus marking it a 'valid' 66 one). 67 68 Connected to: :ref:`label-contact-data` ( |n0|:1),69 :ref:`label-timestamp` (1: |m0|).66 one). No timestamp means, the email address has never been checked. 67 68 Connected to: :ref:`label-contact-data` (n:1), 69 :ref:`label-timestamp` (1:q) 70 70 71 71 Used in the following use cases: … … 79 79 Mobile phone number which is capable of receiving sms text messages. 80 80 81 Connected to: :ref:`label-contact-data` ( |n0|:1)81 Connected to: :ref:`label-contact-data` (n:1) 82 82 83 83 Used in the following use cases: … … 104 104 become due, a respective :ref:`label-transaction` is triggered. 105 105 106 Contracts can have multiple :ref:`label-contract-addon` .107 108 Connected to: :ref:`label-service` ( |n0|:1), :ref:`label-customer` (|n0|:1),109 :ref:`label-contract-addon` (1: |n0|), :ref:`label-transaction` (|n0|, |m0|)106 Contracts can have multiple :ref:`label-contract-addon`\ s. 107 108 Connected to: :ref:`label-service` (p:1), :ref:`label-customer` (p:1), 109 :ref:`label-contract-addon` (1:p), :ref:`label-transaction` (p:q) 110 110 111 111 Used in the following use cases: … … 121 121 parameters. Contract addons are created by :ref:`label-contract`\ s. 122 122 123 Connected to: :ref:`label-contract` ( |n0|:1)123 Connected to: :ref:`label-contract` (p:1) 124 124 125 125 … … 149 149 - get help if problems arise 150 150 151 - retrieve bills .152 153 - reset their passwords if forgotten.151 - retrieve bills 152 153 - change their passwords 154 154 155 155 Customers can order :ref:`label-service`\ s and pay these (kinds of … … 160 160 instance when postal addresses change), and by staff members. 161 161 162 Connected to: :ref:`label-contract` (1: |n0|),163 :ref:`label-contact-data` (1:1), :ref:`label-login-credentials` (1:1) .162 Connected to: :ref:`label-contract` (1:p), 163 :ref:`label-contact-data` (1:1), :ref:`label-login-credentials` (1:1) 164 164 165 165 … … 174 174 for instance describing a location in words. 175 175 176 Connected to: :ref:`label-meter` (1: 1)176 Connected to: :ref:`label-meter` (1:p) 177 177 178 178 … … 187 187 Passwords can be reset on request. 188 188 189 Connected to: :ref:`label-customer` 189 Connected to: :ref:`label-customer` (1:1) 190 190 191 191 … … 206 206 at a given time. 207 207 208 Connected to: :ref:`label-contract` ( |n0|:\ |m0|),209 :ref:`label-meter-value` (1: |m0|), :ref:`label-location` (1:n)208 Connected to: :ref:`label-contract` (b:1), 209 :ref:`label-meter-value` (1:n), :ref:`label-location` (p:1) 210 210 211 211 … … 238 238 prepared to collect meter data from external devices. 239 239 240 Connected to: :ref:`label-meter` ( |n0|:1), :ref:`label-timestamp` (1:1),241 :ref:`label-user` .240 Connected to: :ref:`label-meter` (p:1), :ref:`label-timestamp` (1:1), 241 :ref:`label-user` (p:1) 242 242 243 243 … … 274 274 Services also serve as factories for :ref:`label-contract`\ s. 275 275 276 Connected to: :ref:`label-contract` (1: |n0|),276 Connected to: :ref:`label-contract` (1:p) 277 277 278 278 Used in the following use cases: … … 292 292 293 293 Connected to: :ref:`label-meter-value` (1:1), 294 :ref:`label-contact-email` ( 1:1)294 :ref:`label-contact-email` (p:1) 295 295 296 296 … … 310 310 is consumed, purchased, or (pre-)paid by the respective customer. 311 311 312 Connected to: :ref:`label-customer` ( 1:|n0|), :ref:`label-service`313 ( |n0|:1)312 Connected to: :ref:`label-customer` (p:1), :ref:`label-service` 313 (p:1) 314 314 315 315 Used in the following use cases: … … 334 334 Users can be blocked or removed from the system. 335 335 336 Connected to: :ref:`label-login-credentials` .336 Connected to: :ref:`label-login-credentials` (1:1), :ref:`label-user-role` (p:q) 337 337 338 338 … … 344 344 A role assigned to a group of :ref:`label-user`\ s. 345 345 346 Connected to: :ref:`label-user` (1:|n0|). 347 348 349 .. [#] Relation types: (1:1): One-to-one, (1:n): One-to-many, (n:1): 350 many-to-one, (n:m): many-to-many. ``n`` and ``m`` mean some 351 value ``1..n``. To indicate zero or more (``0..n``) relations, 352 we use |n0| and |m0| respectively. 346 Connected to: :ref:`label-user` (p:q) 347 348 349 .. [#] Relation types: (1:1): one on one, (1:n): one on many, (n:1): 350 many on one, (n:m): many on many, (1:p): one on many or none, 351 (p:1): many or none on one, (p:q): many or none on many or none, 352 (1:b): one or none on one, (b:1): none or one on one 353 354 In mathematical terms: 355 356 n and m are elements of {1, 2, ...}, 357 p and q are elements of {0, 1, 2, ...}, 358 b is element of {0, 1} 359 360
Note: See TracChangeset for help on using the changeset viewer.