What this is:  Modern institution-scale systems incorporate a number of common infrastructure features that enable them to be integrated into an institution-wide (or even federation-wide) ecosystem.  These features are independent of the functionality provided by a particular system but help that system to do its job.  This page describes these features so each subgroup doesn't have to; subgroups may still want to document requirements around distinctive uses of common infrastructure services (e.g. the use of workflow in identity registries).

Institutional Enablement Components

Service interfaces

Service interfaces support access to system functions by external processes, using industry-standard methods such as SOAP and REST.  These interfaces may be used by peer systems to automate access to data or transactions, or to support alternate user interfaces.

Workflow

Workflow services automate the flow of documents through business processes.

Event/message bus

Event services support the real-time distribution of system transition records to interested peer systems.  An event-enabled system both emits events and consumes events.

Notification

Notification services support announcements of system events to people via various communication methods:  email, IM, phone, etc.

End-user self-service

A self-service-enabled system supports access by casual users to system functions.  Successful self-service interfaces are easy to use, self-documenting, fault-tolerant, web-based, etc.

Management/helpdesk

Management functions enable access to detailed, often low-level, system setup, reporting, and diagnostic features by dedicated system management staff and helpdesk personnel.

Access control/federation

Access control services enable institutionally-driven control of access to system functions, for people and processes.

Reporting/auditing

...

Storage/archiving/history

Storage services enable persistent, scalable, high-performance storage and retrieval of system data.  Services include long-term archiving and purging of system data according to institutional policies.  Access to historical data and transaction logs is also supported.

  • No labels