source: main/eko-disco-specs/trunk/use-cases.rst @ 10749

.. _label-use-cases:

Use Cases
*********

Here we collect all use-cases identified to occur with regard to the
Eko Disco Portal. Use-cases are important to check which
:ref:`label-actors` interact with the system in what way.

In use case titles we distinguish between 'manage' and 'edit'.
The first verb refer to manager actions and the second to
customer actions respectively. Actually 'managing' means
editing by Manager.

.. toctree::
   :maxdepth: 1

   use-cases/customer-add-by-mg
   use-cases/customer-add-by-anon
   use-cases/customer-edit-basedata
   use-cases/customer-remove
   use-cases/contract-add
   use-cases/contract-manage
   use-cases/contract-remove
   use-cases/service-add
   use-cases/service-manage
   use-cases/service-remove
..   use-cases/meter-reading
..   use-cases/mg-customer-add


Identified use cases:

* Import legacy data into new system

  Convert legacy data suitable for new system before.

* Add customer by manager

* Add customer by anonymous (self-registration)

* Edit customer base data (contact data and password)

* Remove customer

* Add contract

* Manage contract

* Remove contract

* Add service

* Manage service

* Remove service

* Add subcontract

* Manage subcontract

* Remove subcontract

* Add transaction

* Remove transaction

* Add meter

* Manage meter

* Remove meter

* Read meter

* Add user and assign roles

  Depending on the role, different user data entities (Officer, Customer,
  Accountant) are automatically created.

* Add service

* Manage service

* Remove service