Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Current »

Actors

  • User
  • Database
  • OpenRegistry

Pre-Conditions

  • PRE1: User is authenticated and authorized.
  • PRE2: Calculated Person has been created and chosen.
  • PRE3: There are 0 or 1 activation keys already in existence.
  • PRE4: Validity Length for Activation Keys is configured outside of use case (start and end validity).

Flow

  1. If there is already a valid activation key, the key is deleted.
  2. An activation key is randomly generated and associated with the calculated person.

Post Conditions

  1. Key is available to user who initiated key creation.

Business Rules

  • BR1: Activation Keys are valid as defined in PRE4.
  • BR2: Activation Keys are of the following format: 10 characters in length, consisting of characters [abcdefghijkmnopqrstuvwxyzABCDEFGHJKLMNPQRSTUVWXYZ2345679]
  • BR3: Activation Keys cannot be changed. They can only be removed per the Delete Activation Key Use Case or expired naturally.
  • BR4: An activation key is generated when a Calculated Person is first created. This activation key is generated with a maximum date range of 10 days which is the maximum length of time a key of this size should exist. Subsequent calls to Generate Activation Key can provide their own date range.

Exceptions

  • No labels