Changeset 10730 for main


Ignore:
Timestamp:
9 Nov 2013, 17:35:17 (11 years ago)
Author:
uli
Message:

Remove Account data type and update others.

File:
1 edited

Legend:

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

    r10729 r10730  
    2727connected to how many instances of the related entity [#]_.
    2828
    29 .. _label-account:
    30 
    31 Account
    32 -------
    33 
    34 A customer account contains the assets/debts of a :ref:`customer
    35 <label-customer>`. It is *not* a system account (see
    36 :ref:`label-login-credentials` for that) but a virtual financial
    37 account kept by the system. Basically it tells, how much money a
    38 certain :ref:`customer <label-customer>` owes or is eligible for. Each
    39 account is connected to exactly one customer.
    40 
    41 Connected to: :ref:`label-customer` (1:1), :ref:`label-payment` (1:n),
    42 :ref:`label-consumption` (1:n)
    43 
    44 Used in the following use cases: :ref:`label-uc-account-add`
    45 
    4629
    4730.. _label-contact-address:
     
    10487--------
    10588
    106 A contract is created whenever a customer orders some service from the
    107 system. It is always connected to a customer and a service.
     89A contract is created whenever a :ref:`label-customer` orders some
     90:ref:`label-service` from the system. It is always connected to a
     91:ref:`label-customer` and a :ref:`label-service` .
    10892
    10993A contract is not necessarily written on paper and signed by
    11094people. Instead it is an abstraction used inside the system.
    11195
    112 It is always created from a service, which tells about the basic data,
    113 with additional parameters set that depend on the type of service
    114 ordered.
    115 
    116 Contracts can have contract additions.
    117 
    118 Connected to: :ref:`label-service` (1:1), :ref:`label-customer`
    119 
    120 Used in the following use cases:
     96It is always created from a :ref:`label-service` , which tells about
     97the basic data, with additional parameters set that depend on the type
     98of :ref:`label-service` ordered.
     99
     100Contracts can have multiple :ref:`label-contract-addon`.
     101
     102Connected to: :ref:`label-service` (|n0|:1), :ref:`label-customer` (|n0|:1),
     103:ref:`label-contract-addon` (1:|n0|)
     104
     105Used in the following use cases:
     106
     107
     108.. _label-contract-addon:
     109
     110Contract Addon
     111--------------
     112
     113Kind of 'sub contract' that always belongs to some already existing
     114contract but comes with an own set of parameters. Contract addons are
     115created by contracts.
     116
     117Connected to: :ref:`label-contract` (|n0|:1)
    121118
    122119
     
    200197Services also serve as factories for contracts.
    201198
     199Services can trigger transactions. For instance if some customer
     200orders a service. When the service charges become due, a respective
     201transaction is triggered.
     202
    202203Connected to: :ref:`label-contract` (1:|n0|)
    203204
     
    225226also contain some amount of money which is thereby transfered to or
    226227from a customer's account. They also always reference a service which
    227 is consumed or purchased by the respective customer.
    228 
    229 .. todo:: this is an initial draft, by no means the final version
     228is consumed, purchased, or (pre-)paid by the respective customer.
    230229
    231230Connected to: :ref:`label-customer` (1:|n0|), :ref:`label-service`
Note: See TracChangeset for help on using the changeset viewer.