Changeset 10776 for main/eko-disco-specs/trunk
- Timestamp:
- 20 Nov 2013, 14:55:54 (11 years ago)
- Location:
- main/eko-disco-specs/trunk
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
main/eko-disco-specs/trunk/data.rst
r10752 r10776 49 49 only based on one service. 50 50 51 p:q user-userrole relation means that each user can have no role or 52 several roles and each role can be assigned to no user or several users. 51 p:q useraccount-userrole relation means that each user account can have no role 52 or several roles and each role can be assigned to no user account 53 or several user accounts. 53 54 54 55 Relations can always be read in two directions. … … 93 94 94 95 Connected to: :ref:`label-contact-data` (n:1), 95 :ref:`label-timestamp` (1:q) 96 :ref:`label-timestamp` (1:q), 97 :ref:`label-user-account` (1:b) 96 98 97 99 Used in the following use cases: … … 130 132 become due, a respective :ref:`label-transaction` is triggered. 131 133 132 Contracts can have multiple :ref:`label- contract-addon`\ s.134 Contracts can have multiple :ref:`label-supp-contract`\ s. 133 135 134 136 Connected to: :ref:`label-service` (p:1), :ref:`label-customer` (p:1), 135 :ref:`label- contract-addon` (1:p), :ref:`label-transaction` (1:p),137 :ref:`label-supp-contract` (1:p), :ref:`label-transaction` (1:p), 136 138 :ref:`label-meter` (1:b) 137 139 138 140 Used in the following use cases: 139 140 141 .. _label-contract-addon:142 143 Contract Addon144 --------------145 146 Kind of 'sub contract' that always belongs to some already existing147 :ref:`label-contract` but comes with an own set of148 parameters. Contract addons are created by :ref:`label-contract`\ s.149 150 Connected to: :ref:`label-contract` (p:1),151 :ref:`label-service` (p:1), :ref:`label-customer` (p:1),152 :ref:`label-transaction` (1:p)153 141 154 142 … … 158 146 -------- 159 147 160 Beneficiary of :ref:`label-contract`\ s.148 A user data entity and beneficiary of :ref:`label-contract`\ s. 161 149 162 150 Customers are added to the system by initial import (migration phase), 163 being created by staff or can self-register themselves to the system. 151 being created by staff or can register themselves (self-registration) 152 to the system. 153 154 Each customer has a :ref:`label-user-account`. 164 155 165 156 Customers have to provide :ref:`label-contact-data` and get … … 191 182 Connected to: :ref:`label-contract` (1:p), 192 183 :ref:`label-contact-data` (1:1), :ref:`label-login-credentials` (1:1), 193 :ref:`label-user ` (b:1)184 :ref:`label-user-account` (b:1) 194 185 195 186 … … 213 204 ----------------- 214 205 215 A set of username /password assigned to system users. Passwords are206 A set of username and password assigned to user accounts. Passwords are 216 207 stored inside the system using strong cryptographic hash functions. 217 208 218 209 Passwords can be reset on request. 219 210 220 Connected to: :ref:`label-customer` (1:1) 211 Connected to: :ref:`label-customer` (1:1), :ref:`label-user-account` (1:1) 221 212 222 213 … … 247 238 248 239 The value of a :ref:`label-meter` at a certain point in time 249 (providing a :ref:`label-timestamp`) authorized by some 250 :ref:`label-user` or device. 240 (providing a :ref:`label-timestamp`) authorized by some user or device. 251 241 252 242 It serves mainly for computing power consumption of … … 270 260 271 261 Connected to: :ref:`label-meter` (n:1), :ref:`label-timestamp` (1:1), 272 :ref:`label-user ` (p:1)262 :ref:`label-user-account` (p:1) 273 263 274 264 … … 278 268 ------- 279 269 280 Officers are staff members with certain permissions to manage portal data. 281 282 Actors are called :ref:`Manager <label-actors>` if they are officers with local 283 managing permission. 270 A user data entity of a staff member with certain permissions to manage 271 portal data. 272 273 Each officer has a :ref:`label-user-account`. 274 275 Actors are called :ref:`Manager <label-actors>`\ s if they are officers with 276 local managing permission. 284 277 285 278 Connected to: :ref:`label-login-credentials` (1:1), 286 :ref:`label-user ` (b:1),279 :ref:`label-user-account` (b:1), 287 280 :ref:`label-user-role` (1:p) 288 281 … … 300 293 301 294 Reports are generated as PDF documents and are available for download 302 by authorized :ref:`label-user`\s.295 by authorized users. 303 296 304 297 Connected to: (almost everything else) … … 326 319 327 320 321 .. _label-supp-contract: 322 323 Supplementary Contract 324 ---------------------- 325 326 A supplementary contract always belongs to some already existing 327 :ref:`label-contract` but comes with an own set of 328 parameters. A typical supplementary contract materialises if a customer 329 orders an amount of electrical energy on the bases of a 'main' contract 330 achieved between the customer and the distribution company. 331 The parent contract for instance may guarantee a special price 332 per kilowatt hour of electrical energy. 333 334 Supplementary contracts are created by :ref:`label-contract`\ s. 335 336 Connected to: :ref:`label-contract` (p:1), 337 :ref:`label-service` (p:1), :ref:`label-customer` (p:1), 338 :ref:`label-transaction` (1:p) 339 340 328 341 .. _label-timestamp: 329 342 … … 363 376 364 377 365 .. _label-user: 366 367 User 368 ---- 369 370 A system user. 371 372 Users can have :ref:`label-user-role`\ s managed by the 373 system. Real-world officers (staff members) and customers are different to the 374 system as they will have different roles. Also anonymous users are 378 .. _label-user-account: 379 380 User Account 381 ------------ 382 383 A user account is a set of user data and :ref:`label-login-credentials` 384 which allows a user (agent) to authenticate to the system and 385 let the system store some information required for user handling, 386 such as real name, email address and/or mobile phone number. 387 :ref:`label-user-role`\s are assigned to user accounts and managed by the 388 system to grant authorization for the various views of the portal. 389 Real-world officers (staff members) and customers are different to the 390 system as they will get different roles. Also anonymous users are 375 391 accepted by the system to provide marketing pages, service offers, 376 392 etc. … … 383 399 Connected to: :ref:`label-login-credentials` (1:1), 384 400 :ref:`label-customer` (1:b), 385 :ref:`label-user-role` (p:q) 401 :ref:`label-user-role` (p:q), 402 :ref:`label-contact-email` (b:1) 386 403 387 404 … … 391 408 --------- 392 409 393 A set of permissions assigned to a group of :ref:`label-user `\ s.394 395 Connected to: :ref:`label-user ` (p:q)396 410 A set of permissions assigned to a group of :ref:`label-user-account`\ s. 411 412 Connected to: :ref:`label-user-account` (p:q) 413 -
main/eko-disco-specs/trunk/use-cases/customer-add-by-mg.rst
r10754 r10776 1 1 .. _label-mg-customer-add: 2 2 3 Use-Case: Add a Customer by officer3 Use-Case: Add a Customer by Officer 4 4 *********************************************************************** 5 5
Note: See TracChangeset for help on using the changeset viewer.