/
Use Cases - UC-05 Customers

Use Cases - UC-05 Customers

Owned by David Castro Aguilar (Deactivated)
Last updated: jul 19, 2018 by Francisco Cilleruelo Trotter (Deactivated)

UC-05a

CustomerManagement - Add customer

Versión1.0
DependenciesNone
Preconditions
  • User must be logged
  • User must have ROLE_ADMINISTRATIVE
DescriptionFunctionality to add new customers
Secuence
  1. User request to add a customer
  2. System returns customer creation form
  3. User add customer data.
  4. System requests for an initial user (default contact person)
  5. System saves created customer.
  6. User adds a new user (@see UC-06a UserManagement-addUser) with ROLE_USER as default contact person.
  7. UI offers to license products for new user (@see UC-07a LicenseManagement-addProductLicenses)
PostconditionsAudit fields must save who created that customer.
ExceptionsSystem must reject customer creation if customer cif just exists.
CommentsNone

UC-05b

CustomerManagement - Update customer

Versión1.0
DependenciesNone
Preconditions
  • User must be logged
  • User must have ROLE_ADMINISTRATIVE
DescriptionFunctionality to update a customer
Secuence
  1. User request to obtain a customer by primary key.
  2. System returns customer detailed model.
  3. User updates general customer information.
  4. System may offer the option to update the users associated to customer (@see UC-06b UserManagement-updateUser)
  5. System may offer the option to update the products licensed to current customer (@see UC-07b LicenseManagement-updateProductLicense)
  6. System save customer information.
PostconditionsAudit fields must save who modified that customer.
Exceptions

System will raise and exception if primarey key does not exist.

CommentsNone


UC-05c

CustomerManagement - Remove customer

Versión1.0
DependenciesNone
Preconditions
  • User must be logged
  • User must have ROLE_ADMINISTRATIVE
DescriptionFunctionality to remove a customer
Secuence
  1. User request to remove a customer by primary key.
  2. System will check for associated licenses and warn the user about:
    1. Number of licenses associated to the customer.
    2. Double check to remove that customer
  3. User accepts to remove the customer.
  4. System removes associated users (@see UC-06c UserManagement-removeUser) forcing to ignore customer relation restrictions.
  5. System removes customer licenses and keys (@see UC-07b LicenseManagement-removeLicense)
  6. System finally removes the customer.
PostconditionsNone
Exceptions

System will raise and exception if primary key does not exist.

CommentsNone


UC-05d

CustomerManagement - Find customers

Versión1.0
DependenciesNone
Preconditions
  • User must be logged
  • User could have ROLE_ADMINISTRATIVE or ROLE_PRODUCT_MANAGER
DescriptionFunctionality to search for customers
Secuence
  1. User request for a list of customers.
  2. System will query database using provided parameters:
    1. If user details are requested then it will be included in response
    2. If license details are requested then it will be included in response. License i18N fields must be returned in all the configured languages.
PostconditionsNone
Exceptions

None

CommentsNone



Avvale 2024