Ignore:
Timestamp:
20 Nov 2013, 14:55:54 (11 years ago)
Author:
Henrik Bettermann
Message:

A contract addon is now called 'supplementary contract' and a user data entity is called 'user account'.

Location:
main/eko-disco-specs/trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • main/eko-disco-specs/trunk/data.rst

    r10752 r10776  
    4949only based on one service.
    5050
    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.
     51p:q useraccount-userrole relation means that each user account can have no role
     52or several roles and each role can be assigned to no user account
     53or several user accounts.
    5354
    5455Relations can always be read in two directions.
     
    9394
    9495Connected 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)
    9698
    9799Used in the following use cases:
     
    130132become due, a respective :ref:`label-transaction` is triggered.
    131133
    132 Contracts can have multiple :ref:`label-contract-addon`\ s.
     134Contracts can have multiple :ref:`label-supp-contract`\ s.
    133135
    134136Connected 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),
    136138:ref:`label-meter` (1:b)
    137139
    138140Used in the following use cases:
    139 
    140 
    141 .. _label-contract-addon:
    142 
    143 Contract Addon
    144 --------------
    145 
    146 Kind of 'sub contract' that always belongs to some already existing
    147 :ref:`label-contract` but comes with an own set of
    148 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)
    153141
    154142
     
    158146--------
    159147
    160 Beneficiary of :ref:`label-contract`\ s.
     148A user data entity and beneficiary of :ref:`label-contract`\ s.
    161149
    162150Customers are added to the system by initial import (migration phase),
    163 being created by staff or can self-register themselves to the system.
     151being created by staff or can register themselves (self-registration)
     152to the system.
     153
     154Each customer has a :ref:`label-user-account`.
    164155
    165156Customers have to provide :ref:`label-contact-data` and get
     
    191182Connected to: :ref:`label-contract` (1:p),
    192183: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)
    194185
    195186
     
    213204-----------------
    214205
    215 A set of username/password assigned to system users. Passwords are
     206A set of username and password assigned to user accounts. Passwords are
    216207stored inside the system using strong cryptographic hash functions.
    217208
    218209Passwords can be reset on request.
    219210
    220 Connected to: :ref:`label-customer` (1:1)
     211Connected to: :ref:`label-customer` (1:1), :ref:`label-user-account` (1:1)
    221212
    222213
     
    247238
    248239The 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.
    251241
    252242It serves mainly for computing power consumption of
     
    270260
    271261Connected to: :ref:`label-meter` (n:1), :ref:`label-timestamp` (1:1),
    272 :ref:`label-user` (p:1)
     262:ref:`label-user-account` (p:1)
    273263
    274264
     
    278268-------
    279269
    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.
     270A user data entity of a staff member with certain permissions to manage
     271portal data.
     272
     273Each officer has a :ref:`label-user-account`.
     274
     275Actors are called :ref:`Manager <label-actors>`\ s if they are officers with
     276local managing permission.
    284277
    285278Connected to: :ref:`label-login-credentials` (1:1),
    286 :ref:`label-user` (b:1),
     279:ref:`label-user-account` (b:1),
    287280:ref:`label-user-role` (1:p)
    288281
     
    300293
    301294Reports are generated as PDF documents and are available for download
    302 by authorized :ref:`label-user`\ s.
     295by authorized users.
    303296
    304297Connected to: (almost everything else)
     
    326319
    327320
     321.. _label-supp-contract:
     322
     323Supplementary Contract
     324----------------------
     325
     326A supplementary contract always belongs to some already existing
     327:ref:`label-contract` but comes with an own set of
     328parameters. A typical supplementary contract materialises if a customer
     329orders an amount of electrical energy on the bases of a 'main' contract
     330achieved between the customer and the distribution company.
     331The parent contract for instance may guarantee a special price
     332per kilowatt hour of electrical energy.
     333
     334Supplementary contracts are created by :ref:`label-contract`\ s.
     335
     336Connected 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
    328341.. _label-timestamp:
    329342
     
    363376
    364377
    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
     380User Account
     381------------
     382
     383A user account is a set of user data and :ref:`label-login-credentials`
     384which allows a user (agent) to authenticate to the system and
     385let the system store some information required for user handling,
     386such 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
     388system to grant authorization for the various views of the portal.
     389Real-world officers (staff members) and customers are different to the
     390system as they will get different roles. Also anonymous users are
    375391accepted by the system to provide marketing pages, service offers,
    376392etc.
     
    383399Connected to: :ref:`label-login-credentials` (1:1),
    384400: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)
    386403
    387404
     
    391408---------
    392409
    393 A set of permissions assigned to a group of :ref:`label-user`\ s.
    394 
    395 Connected to: :ref:`label-user` (p:q)
    396 
     410A set of permissions assigned to a group of :ref:`label-user-account`\ s.
     411
     412Connected to: :ref:`label-user-account` (p:q)
     413
  • main/eko-disco-specs/trunk/use-cases/customer-add-by-mg.rst

    r10754 r10776  
    11.. _label-mg-customer-add:
    22
    3 Use-Case: Add a Customer by officer
     3Use-Case: Add a Customer by Officer
    44***********************************************************************
    55
Note: See TracChangeset for help on using the changeset viewer.