Technical Requirements

Owned by Benn Oshrin
Last updated: Dec 14, 2008Version comment

Technical requirements are derived from Functional Requirements, which are referenced after each requirement.

  • TR1: Core registry function to add an SOR-based role record to a person, reconciling against existing person records, and optionally records in external systems, so that multiple source records for the same person are linked. (FR1,2,3,4)
  • TR2: Core registry function to modify an SOR-based role record for a person, including appropriate update of person data derived from role records (eg: name). (FR1,2,3; see also TR5)
  • TR3: Core registry function to remove an SOR-based role record for a person, including appropriate update of person data derived from role records (eg: name). (FR1,2,3; see also TR5)
  • TR4: For newly identified individuals, assign one or more identifiers for internal and/or external use according to predefined algorithms, optionally relying on external systems that are canonical for one or more identifiers. (FR5,17)
  • TR5: Attach biodemographic data to an individual's person record using the oldest, still valid SOR role record, unless the person requests otherwise. (FR6)
  • TR6: Attach role data and attributes to an individual's person record, linked by SOR role record. (FR6)
  • TR7: Batch interface to person operations. (FR1)
  • TR8: Web interface to person operations. (FR2)
  • TR9: Real-time programmatic interface to person operations. (FR3)
  • TR10: Allow a System of Record to be paired with a provisional record source such that the provisional data is hidden or removed when corresponding SOR is received. (FR7)
  • TR11: Permit linking of person role records to sponsors. (FR8)
  • TR12: Batch update mechanism via web interface, including support for file uploads (xls, csv). (FR9)
  • TR13: Extract registry data into LDIF (and other arbitrary) format. (FR10, FR13)
  • TR14: Provide incremental updates via LDAP. (FR11)
  • TR15: Core registry functions to add, modify, and remove groups and group members. (FR12)
  • TR16: Web interface to group operations. (FR12)
  • TR17: Real-time programmatic interface to group operations. (FR12)
  • TR18: Support for rules-based provisioning and deprovisioning via XML-based protocol. (FR13)
  • TR19: Support for rules-based provisioning and deprovisioning via callouts. (FR13)
  • TR20: Attribute definitions have versions. (FR14)
  • TR21: Establish a data dictionary of defined attributes. (FR15)
  • TR22: Support calculation of appropriate portions of NIST LoA (SP 800-63). (FR16)
  • TR23: Allow the use of activation keys for linking new and reset credentials to persons. (FR18)
  • TR24: Support the storage of persistent role data with transiently attached persons. (FR19)
  • TR25: Normalize data by executing local routines on all input data regardless of source. (FR20)
  • TR26: Support the storage of credential metadata. (FR21)
  • TR27: Web interface to credential management operations. (FR22)
  • TR28: Define a permission model that covers all data that is capable of being provided in an extract from the registry. (FR23)
  • TR29: Easily searchable history records of all changes. (FR24)

Technical requirements targeted for R1: 1, 2, 3, 4, 5, 6, 7, 8, 11, 12, 13, 14, 20, 21, 25, 29