Changeset 10732 for main/eko-disco-specs


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

Update/fix existing types.

File:
1 edited

Legend:

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

    r10730 r10732  
    4545------------
    4646
    47 The data neccessary to contact some customer, staff person or similar
    48 entity. Contact data might contain several addresses, phone numbers,
    49 emails, etc.
     47The data neccessary to contact some :ref:`label-customer`, staff
     48person or similar entity. Contact data might contain several
     49addresses, phone numbers, emails, etc.
    5050
    5151Connected to: :ref:`label-customer` (1:1),
    52 :ref:`label-contact-address` (1:|n0|), :ref:`label-contact-email` (1:|n0|)
     52:ref:`label-contact-address` (1:|n0|), :ref:`label-contact-email`
     53(1:|n0|), :ref:`label-contact-phone` (1:|n0|)
    5354
    5455Used in the following use cases:
     
    9899of :ref:`label-service` ordered.
    99100
     101Contracts can trigger :ref:`label-transaction`\ s. For instance if some
     102:ref:`label-customer` orders a service. When the service charges
     103become due, a respective :ref:`label-transaction` is triggered.
     104
    100105Contracts can have multiple :ref:`label-contract-addon`.
    101106
    102107Connected to: :ref:`label-service` (|n0|:1), :ref:`label-customer` (|n0|:1),
    103 :ref:`label-contract-addon` (1:|n0|)
     108:ref:`label-contract-addon` (1:|n0|), :ref:`label-transaction` (|n0|, |m0|)
    104109
    105110Used in the following use cases:
     
    112117
    113118Kind of 'sub contract' that always belongs to some already existing
    114 contract but comes with an own set of parameters. Contract addons are
    115 created by contracts.
     119:ref:`label-contract` but comes with an own set of
     120parameters. Contract addons are created by :ref:`label-contract`\ s.
    116121
    117122Connected to: :ref:`label-contract` (|n0|:1)
     
    186191-------
    187192
    188 The system will provide different services to customers. These can
    189 have arbitrary forms, including one-time services (like installation
    190 of meters) and open-ended long-time services (like delivering power
    191 based on contract). Services are managable by staff like goods offered
    192 in a shop.
     193The system will provide different services to
     194:ref:`label-customer`\ s. These can have arbitrary forms, including
     195one-time services (like installation of meters) and open-ended
     196long-time services (like delivering power based on contract). Services
     197are managable by staff like goods offered in a shop.
    193198
    194199Services define the conditions under which they can be ordered by
    195 customers, including prices, runtimes, etc.
    196 
    197 Services also serve as factories for contracts.
    198 
    199 Services can trigger transactions. For instance if some customer
    200 orders a service. When the service charges become due, a respective
    201 transaction is triggered.
    202 
    203 Connected to: :ref:`label-contract` (1:|n0|)
     200:ref:`label-customer`\ s, including prices, runtimes, etc.
     201
     202Services also serve as factories for :ref:`label-contract`\ s.
     203
     204Connected to: :ref:`label-contract` (1:|n0|),
    204205
    205206Used in the following use cases:
Note: See TracChangeset for help on using the changeset viewer.