View Complete Person

Owned by ScottS
Last updated: Jan 08, 2010 by Nancy MondVersion comment
1 min read

Actors

  • User
  • OpenRegistry
  • Database

Pre-Conditions

  • PRE1: User is authenticated and authorized to use system.
  • PRE2: User has chosen a Person to view (most likely via Search Person Use Case).
  • PRE3: User has permissions to view complete person.

Flow

  1. All information about a person is returned to the user. This includes:
    • Calculated Person
    • Calculated Roles
    • SoR Person and Role Information
    • Calculated Attributes
    • Audit History (future capability)
    • Provide information to determine how calculated values were determined, such as providing SoR color coded values to indicate source for values (future capability)

Post-Conditions

  • None

Business Rules

  • The actual fields, SoR Information, etc. that can be seen is controlled by authorization rules.

Exceptions