source: main/eko-disco-specs/trunk/data.rst @ 10717

Last change on this file since 10717 was 10717, checked in by uli, 11 years ago

Update data.

File size: 2.8 KB
Line 
1.. _label-data-entities:
2
3Data Entities
4=============
5
6These are the data entities the new system is supposed to model. Each
7of these entities should be addable, editable, and removable as
8covered in more detail in :ref:`label-use-cases`.
9
10For each entity we give a short description to tell what it means,
11what its purpose is and in what regards (and how) it should be handled
12by the system. Again the more detailed actions on these entities
13provided by the system are described in the :ref:`label-use-cases`
14section.
15
16The data entities are sorted alphabetically, not by importance or
17similar. Used description terms should link to other respective
18entities/terms where possible.
19
20Each data entitiy description provides a list of use cases and other
21data entities connected. Connections to other data entities contain a
22relationship telling how many instances of the described entity are
23connected to how many instances of the related entity [#]_.
24
25.. _label-account:
26
27Account
28-------
29
30A customer account contains the assets/debts of a :ref:`customer
31<label-customer>`. It is *not* a system account (see
32:ref:`label-login-credentials` for that) but a virtual financial
33account kept by the system. Basically it tells, how much money a
34certain :ref:`customer <label-customer>` owes or is eligible for. Each
35account is connected to exactly one customer.
36
37Connected to: :ref:`label-customer` (1:1), :ref:`label-payment` (1:n),
38:ref:`label-consumption` (1:n)
39
40Used in the following use cases: :ref:`label-uc-account-add`
41
42
43.. _label-contact-address:
44
45Contact Address
46---------------
47
48A postal address.
49
50Connected to: :ref:`label-contact-data` (n:1)
51
52Used in the following use cases:
53
54
55.. _label-contact-data:
56
57Contact Data
58------------
59
60The data neccessary to contact some customer, staff person or similar
61entity. Contact data might contain several addresses, phone numbers,
62emails, etc.
63
64Connected to: :ref:`label-customer` (1:1),
65:ref:`label-contact-address` (n:1)
66
67Used in the following use cases:
68
69
70.. _label-contract:
71
72Contract
73--------
74
75.. _label-contract-types:
76
77Contract Types
78--------------
79
80.. _label-contract-termination:
81
82Contract Termination
83--------------------
84
85.. _label-consumption:
86
87Consumption
88-----------
89
90.. _label-customer:
91
92Customer
93--------
94
95Beneficiary of a contract
96
97.. _label-login-credentials:
98
99Login Credentials
100-----------------
101
102.. _label-meter:
103
104Meter
105-----
106
107.. _label-meter-status:
108
109Meter Status
110------------
111
112.. _label-meter-value:
113
114Meter Value
115-----------
116
117.. _label-meter-reader:
118
119Meter Reader
120------------
121
122.. _label-payment:
123
124Payment
125-------
126
127.. _label-point-of-consumption:
128
129Point of Consumption
130--------------------
131
132.. _label-report:
133
134Report
135------
136
137.. _label-timestamp:
138
139Timestamp
140---------
141
142.. [#] Relation types: (1:1): One-to-one, (1:n): One-to-many, (n:1):
143       many-to-one, (n:m): many-to-many.
Note: See TracBrowser for help on using the repository browser.