# 1 Introduction

## 1.1 Purpose
This Software Requirements Specification (SRS) describes the functional and nonfunctional requirements for the System Administration Module of an Integrated Library System (ILS). The module replaces and enhances the current capabilities of commercially available ILSes and adds new functionality to support management activities.

## 1.2 Scope
- Product name: System Administration Module of an Integrated Library System (ILS).
- What it will do:
  - Configure the ILS to support features and processes for managing library branches, patrons, collections, and circulation transactions.
  - Monitor, troubleshoot, and control server, database, application, services, ports, and API performance.
  - Manage user and group accounts and privileges.
  - Manage server and client software installation, upgrades, and updates.
  - Provide backup and recovery (databases, configuration files, log files, etc.).
  - Provide dashboards, consoles, job scheduling, and reporting.
- Application and benefits:
  - Designed for a large, urban, multiple-branch, centralized library system.
  - Supports high-volume operations (e.g., 50 locations, ~20 million circulations per year; purchasing/processing over 500,000 items per year).
  - Enables real-time processing and administration without disrupting core services during open hours.
- Consistency:
  - Presupposes general data structures and functionality of a full-fledged ILS and aligns with separate module specifications (e.g., Acquisitions and Serials, Circulation, Cataloging).

## 1.3 Product overview

### 1.3.1 Product perspective
The System Administration Module is part of an enterprise-level ILS. It provides administration and management functions that interface with other ILS modules (e.g., Acquisitions, Cataloging, Circulation) and the public patron interface (OPAC), as well as external vendor services via published APIs and/or standard-format data exchanges.

#### System interfaces
- Interfaces with:
  - Acquisitions, Cataloging, and Circulation modules.
  - Patron interface (OPAC).
  - Vendor websites and services via published APIs and standard-format data files (e.g., USMARC21, EDIFACT).
  - Protocols and APIs such as SIP2/NCIP2 for self-check and related services.
  - Monitoring systems via SNMP.
  - Email transport via SMTP.

#### User interfaces
- Accessible via a web browser or a Windows-compatible client.
- If web-based, compatible with Microsoft Internet Explorer (v6.0 and later) and Mozilla Firefox (v2.0 and later).
- Accessible with screen-reading software, screen-magnification software, and other assistive technologies.
- Provides administrative dashboards and consoles for monitoring, configuration, and job scheduling.
- Provides online, hierarchical, cross-linked HTML help describing all system functions.

#### Hardware interfaces
- Operates on Linux or Solaris servers.
- Supports Windows printers (receipt, standard, label, forms).

#### Software interfaces
- Fully relational, SQL-based database backend; ODBC-accessible.
- Standards-compliant HTML output.
- Supports secure protocols including SFTP (active and passive), SSL, and SSH.
- Supports SNMP for system monitoring.
- Supports import/export of MARC bibliographic and authority records, including integration with vendors such as OCLC.

#### Communications interfaces
- SMTP for email transport.
- SFTP for file transfer (active and passive modes, configurable per vendor).
- SSL/SSH for secure communications.
- SNMP for monitoring.
- SIP2/NCIP2 and similar protocols/APIs for circulation/self-check integrations.

#### Memory constraints
[N/A]

#### Operations
- Modes of operation include:
  - User-initiated administration through dashboards and consoles.
  - Scheduled and unattended operations (e.g., backups, imports/exports, reports, software updates).
- Supports real-time processing (e.g., pull lists current at time of viewing/printing; live shelf reading and weeding).
- Backup and recovery operations for data and transaction logs, including incremental and full backups.
- Supports job sequencing and management by administrative staff.

#### Site adaptation requirements
- Provides development and training environments with the ability to migrate configurations to production.
- Business rules, loan and requesting rules, and suppression rules are site-configurable.
- Configurable templates for staff and patron account creation.
- Centrally managed client configurations; configurations exportable/importable between clients.

#### Interfaces with services
- Interfaces with vendor sites and services via APIs and standard data exchanges (USMARC21, EDIFACT).
- Integrates with OCLC for MARC authority and bibliographic records.

### 1.3.2 Product functions
- Configuration and control of servers, services, ports, APIs, and applications.
- Performance monitoring dashboards (system, application, circulation).
- Business rules management (loan rules, requesting rules, suppression rules, data validation).
- Security management (roles/privileges, patron data security, secure protocols).
- Data recovery (backups, rollback, revision control if available) and high availability (server clustering).
- Maintenance workflows (staff/patron account setup, job scheduling and management, record sets, MARC import/export).
- Client management (centralized client software updates, independent accounts, server-based configurations).
- Queries and reporting (query tool, templates, permissions, formats/outputs, printer support).
- Documentation and upgrade guidance; access to configuration and log files; root shell access where required by administrators.

### 1.3.3 User characteristics
- Patrons: Customers of the library system using print, media, or electronic resources, on-site or remote, with or without library cards.
- Staff: Managers, librarians, library technicians, assistants, and pages involved in service delivery.
- System Administrators: Staff managing servers, databases, applications, services, ports, and APIs related to the ILS.
- Managers: Management staff overseeing library processes.
- Library Managers: Cluster and Site Managers providing input on design and implementation of services.
- Library Directors: Executive team members planning and directing services and priorities.
- Assumptions: Users are generally familiar with library services and terminology; development will be collaborative and iterative with end-user participation and prototype reviews.

### 1.3.4 Limitations
- The specification focuses on functional characteristics; detailed data structures and user interfaces require further iterative specification and prototyping.
- User rights and privileges are controlled through security groups/roles for individuals and workgroups.
- Regulatory and policy constraints are not specified here.
- Quality attributes such as accessibility and non-disruptive operation during open hours are required.
- Interfaces to other modules and services must follow published standards/protocols (e.g., USMARC21, EDIFACT, SIP2/NCIP2).

## 1.4 Definitions
- Patron: A customer of the library system, regardless of card status or location, using print, media, or electronic resources.
- Staff: Library personnel including managers, librarians, technicians, assistants, and pages.
- System Administrator: Staff responsible for servers, databases, applications, services, ports, and APIs related to the ILS.
- Manager: Management staff overseeing library processes.
- Library Manager: Cluster and Site Managers who contribute to design and implementation of services.
- Library Director: Executive team members guiding services and priorities.
- ILS (Integrated Library System): Enterprise-level library automation system supporting acquisitions, cataloging, circulation, OPAC, and administration.
- OPAC (Online Public Access Catalog): Patron-facing interface for searching and managing library resources.

# 2 References
[N/A]

# 3 Requirements

## 3.1 Functions
The following functional requirements are organized by capability area. Each item retains its original identifier, priority, and source.

- Systems: General
  - Priority: 3; Req ID: 6512; Name: SQL-based database
    - Description: System runs on a fully relational, SQL-based database system. Ability to run SQL queries against any table in the database. Ability to access database as an ODBC source. All data tables and data storage are fully accessible.
    - Related Reqs: 2456, 2475; Source: ITS
  - Priority: 3; Req ID: 5615; Name: Real-time processing
    - Description: The system provides real-time processing. Examples: pull lists are up to date at time of viewing or printing; system supports live shelf reading and weeding.
    - Related Reqs: [N/A]; Source: MGT
  - Priority: 3; Req ID: 5323; Name: Field and record sharing
    - Description: Ability for multiple staff members and patrons to simultaneously access and update patron and item records, including on staff check-in and check-out terminals, on self check-out stations, through SIP2/NCIP2 and similar protocols and APIs, and in OPAC. Depending on assigned privileges, staff can view all patron and item fields; patrons can access only selected fields. Record changes are applied reasonably, with prompts to warn when a record has been changed since it was displayed.
    - Related Reqs: [N/A]; Source: CIR
  - Priority: 3; Req ID: 6513; Name: Record lock management
    - Description: For any patron or item record, staff can identify where it is in use (location, user, date and time placed).
    - Related Reqs: 6501, 7302; Source: ITS
  - Priority: 2; Req ID: 2492; Name: Individual and shared staff login accounts
    - Description: Support individual and shared staff login accounts; access to modules is granted by roles or privileges allowing each account to access necessary modules. Individual logins allow user-level preferences and audit trail.
    - Related Reqs: 5514; Source: ACQ
  - Priority: 3; Req ID: 2428; Name: System documentation
    - Description: System documentation is library-specific, web-based, indexed, organized by function, easily searchable, and specific to the installed version; follows standard technical documentation formats.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2431; Name: System upgrade guidelines
    - Description: System upgrades and updates include written guidelines for updating servers and clients, including lists of new, changed, and removed features.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2479; Name: Configuration file access
    - Description: System provides access to all configuration files.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2474; Name: Log file access
    - Description: System provides full access to all log files. Log files can be reviewed without stopping the system. Logs can be enabled, disabled, and set to a specific retention threshold.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2470; Name: Root shell access
    - Description: System provides access to root shell.
    - Related Reqs: [N/A]; Source: ITS

- Systems: Consoles and Dashboards
  - Priority: 3; Req ID: 6520; Name: Dashboard configuration
    - Description: Supports creation of custom dashboards displaying current and historical data about system performance, record creation and modification, circulation transactions, etc. Administrators can create dashboards and grant access to selected users and groups.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 6501; Name: System monitoring
    - Description: Full support for SNMP and monitoring of system resources (disk space, CPU load, memory load, processes, interfaces, ports). Alert thresholds are configurable. Alerts can be sent via dashboards, email, and text messages to an unlimited number of recipients via any/all methods.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 7302; Name: Record lock administration
    - Description: Ability to set thresholds on record lock durations and list records in sustained use/locked condition for all record types. Ability to unlock one or more records from the same console.
    - Related Reqs: 6513; Source: ITS
  - Priority: 3; Req ID: 2467; Name: System performance dashboard
    - Description: Provides dashboard of performance monitoring and management tools. Identifies processes with process ID, owner username, IP address (if applicable), CPU/memory utilization, run time. Identifies runaway processes. System status shown with visual indicators (e.g., green/red lights).
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2466; Name: Server console
    - Description: Provides server management console including: software shutdown/startup, server shutdown/restart utilities.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2464; Name: Application dashboard
    - Description: Displays last full and incremental backup; last planned/unplanned reboot; last software upgrade; current software version; transactions waiting; size of log files; current count of records by type (item, bibliographic, patron, etc.); database utilization (size, running processes).
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2430; Name: Client management console
    - Description: Displays workstations running client software; workstation name and IP address; includes utilities for managing and killing client sessions.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 6503; Name: Circulation dashboard
    - Description: Shows key performance indicators such as check-outs/hour, check-ins/hour, holds placed/hour, holds paged/day. Indicators can be limited to a single branch or set to systemwide.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 6517; Name: Configuration file console
    - Description: Provides a single console with access to all configuration files. Read/write permissions to individual configuration files can be assigned to users and groups.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2433; Name: Log-file dashboard
    - Description: Provides a dashboard for locating and viewing log files.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 6521; Name: Job scheduling console
    - Description: Provides a single interface for reviewing and controlling scheduled tasks, including staff-scheduled tasks, automated reports, scheduled imports/exports, software updates, etc.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 6515; Name: Email configuration
    - Description: Ability to access and edit email configuration, including a quick menu of common settings (e.g., masquerading, log retention, bounce management).
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 6516; Name: SMTP support
    - Description: System supports SMTP for email transport.
    - Related Reqs: [N/A]; Source: ITS

- Systems: Business Rules
  - Priority: 3; Req ID: 2445; Name: Business rules
    - Description: Supports restrictions based on business rules (e.g., restrict deletion of checked-out items or bibliographic records with existing holds).
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 5278; Name: Suppression rules
    - Description: Customizable Rules of Suppression specify visibility of authority, bibliographic, order, and item records in staff and public (OPAC) interfaces. Records may be visible to specific workgroups only; to all staff and patrons at specific locations; or to all staff and all patrons.
    - Related Reqs: 5057, 5190, 580; Related Process: CAT180; Source: CIR
  - Priority: 3; Req ID: 5190; Name: Requesting rules
    - Description: Allows creation and modification of requesting rules determining whether a patron can place a hold on an item. Rules may evaluate patron type, current number of holds, account balance, item type/status, owning location code, and other criteria. Rules may prohibit holds on specific on-order materials while allowing others. Rules also specify whether staff with certain roles can override criteria.
    - Related Reqs: 5057, 5278; Related Process: HOL-011; Source: CIR
  - Priority: 3; Req ID: 5057; Name: Loan rules
    - Description: Allows creation and modification of loan rules to allow/disallow check-out, calculate loan periods, and determine renewal limits. Rules may evaluate patron type, items checked out, account balance, item type/status, owning and check-out location codes, and other criteria. Rules can access check-out location open/closed schedules when calculating due dates and specify staff override permissions.
    - Related Reqs: 5190; Related Process: HOL-131; Source: CIR
  - Priority: 3; Req ID: 5328; Name: Data validation
    - Description: Ability to specify default values, data validation, automatic formatting, and required status for any field.
    - Related Reqs: [N/A]; Source: CIR

- Systems: Data Recovery
  - Priority: 3; Req ID: 6502; Name: System backup
    - Description: Capability to perform live incremental and full backups of data and transaction logs. Supports use of third-party backup software such as EMC NetWorker.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 6505; Name: Data rollback
    - Description: Logs data changes (such as record deletions) and provides undo functionality. Ideally provides revision control.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2462; Name: Server clustering
    - Description: Ability to cluster servers for failover capability.
    - Related Reqs: [N/A]; Source: ITS

- Systems: Security
  - Priority: 3; Req ID: 6510; Name: Patron data security
    - Description: Patron data is secure in all transfers to and from the system.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 6509; Name: User account privileges
    - Description: System administrative staff has full visibility and control of user privileges.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 6511; Name: Secure protocol support
    - Description: Supports secure protocols, including SFTP, SSL, and SSH. SFTP is supported in both active and passive modes, configurable per vendor.
    - Related Reqs: [N/A]; Source: ITS

- Systems: Maintenance
  - Priority: 3; Req ID: 1716; Name: MARC import/export
    - Description: MARC bibliographic and authority records can be imported and exported, singly and in batch, all fields or selected fields, to and from vendors including OCLC. Imported records can overlay existing short or full bibliographic records. Imported batches can be maintained/manipulated as selection lists.
    - Related Reqs: 3004; Related Process: CAT180; Source: CAP
  - Priority: 3; Req ID: 6518; Name: Record sets
    - Description: Supports an unlimited number of record sets, with ability to import and export set members in batch. Record sets can be used for batch field updates, as limiting scopes for queries, and to delete original records with pre-review, error logging, and undo of one or more deletions.
    - Related Reqs: 2204; Source: ITS
  - Priority: 3; Req ID: 2420; Name: Staff account setup
    - Description: Dedicated interface for creating new staff accounts. Provides configurable templates for account administrators; granular privileges for account creation, modification, and deletion.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2419; Name: Patron account setup
    - Description: Dedicated interface for creating new patron accounts. Provides configurable templates; supports field validation and required fields; configurable defaults.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 6507; Name: Job scheduling
    - Description: Supports scheduling of maintenance tasks, reports, and data exports. Jobs can be sequenced (e.g., start job B when job A finishes) and modified or cancelled any time prior to starting.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 6508; Name: Job scheduling: management
    - Description: Staff can be permitted to schedule tasks, reports, and data exports. System administration staff can view and manage jobs scheduled by other staff.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2220; Name: Keyboard macros and shortcuts
    - Description: Supports administrator- and user-programmable macros and/or keyboard shortcuts. Shortcut keys may be assigned to macros (e.g., Insert Field) or text strings. Macros are centrally managed on the server, can be imported/exported to individual users, and can be restricted for use and/or editing through centrally-managed permissions.
    - Related Reqs: [N/A]; Source: ACQ

- Systems: Client Management
  - Priority: 3; Req ID: 6514; Name: Accounts independent from workstation
    - Description: Staff and group accounts are independent from workstations; client install should not be tied to a specific location.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 6504; Name: Client software updates
    - Description: Client software installation and updates are centrally managed using standard or proprietary network management tools, allowing streaming updates from server. Ability to specify specific clients to be updated. Client software can be managed with VNC and Remote Desktop.
    - Related Reqs: 2430; Source: ITS
  - Priority: 3; Req ID: 6519; Name: Client configurations
    - Description: All client configuration files are server-based; configurations can be exported and imported between clients.
    - Related Reqs: [N/A]; Source: ITS

- Systems: Queries and Reports
  - Priority: 2; Req ID: 2197; Name: Report format and output
    - Description: Ability to fully customize layout and appearance of reports. Ability to display, print, email, or save reports to standard formats including CSV and Excel, as well as customizable formats.
    - Related Reqs: [N/A]; Source: ACQ
  - Priority: 3; Req ID: 5624; Name: Query tool
    - Description: User-friendly interface for designing queries against all record types. Staff can select fields to query, values from picklists, regular expressions from a drop-down menu, and use full Boolean operators. Administrators control staff access to tables and fields.
    - Related Reqs: [N/A]; Source: MGT
  - Priority: 3; Req ID: 5607; Name: Report templates
    - Description: System administrators can create report templates available to front-line staff, to be run as-is or modified to specific needs.
    - Related Reqs: [N/A]; Source: MGT
  - Priority: 3; Req ID: 5617; Name: Reports permissions
    - Description: Provides fine-grained permissions to allow or disallow staff to run specific reports and/or to run ad hoc reports on specific data sets.
    - Related Reqs: [N/A]; Source: MGT
  - Priority: 3; Req ID: 2465; Name: Record number report
    - Description: Reports for each record type: current record number, current number of records, number deleted, and number purged. Record types include patron, bibliographic, item, order, invoice, etc. Access to record numbers is controlled at the user/group level.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2441; Name: Printer support
    - Description: Ability to define and select printer types: receipt, standard, label, and forms. All Windows printers are supported.
    - Related Reqs: [N/A]; Source: ITS
  - Priority: 3; Req ID: 2439; Name: Multiple print output options
    - Description: Ability to print to a file on the server, FTP, email, or printer from any part of the application. When applicable, ability to select record fields and control order of fields when printing.
    - Related Reqs: [N/A]; Source: ITS

## 3.2 Performance requirements
- Capacity and scale
  - Support a large, multiple-branch library system with approximately 50 locations and 20 million circulations annually; purchasing/processing over 500,000 items per year. (OE-1)
- Real-time responsiveness
  - Provide real-time processing for operational lists and tasks (e.g., pull lists up to date upon viewing/printing; live shelf reading/weeding). (Req 5615)
- Monitoring and alerting
  - Monitor system resources via SNMP with configurable thresholds; provide alerts via dashboards, email, and text to an unlimited number of recipients. (Req 6501)
- Non-disruptive operations
  - It is highly desirable that searches and reports can be processed during open hours without disrupting other system functions. (OE-1)

## 3.3 Usability requirements
- Accessibility
  - Accessible via screen readers, screen magnification, and other assistive technologies. (OE-5)
- Help and documentation
  - Provide an online, hierarchical, cross-linked HTML help system describing and illustrating all functions. (UD-3)
  - System documentation is web-based, indexed, organized by function, easily searchable, and version-specific. (Req 2428)
- Efficiency aids
  - Support administrator- and user-programmable macros and keyboard shortcuts; centrally managed with permissions. (Req 2220)
- Printing usability
  - Support multiple printer types and output options, with selection of record fields and order when applicable. (Reqs 2441, 2439)

## 3.5 Logical database requirements
- Data entities and scope
  - Authority, bibliographic, order, item, patron, hold/request, invoice, and related records. (UD-1; Req 2465)
- Accessing capabilities
  - Fully relational, SQL-based database; ability to run SQL against any table; ODBC access. (Req 6512)
  - All data tables and storage are fully accessible (with administrative control). (Req 6512)
- Concurrency and integrity
  - Simultaneous access and updates to patron and item records by multiple users with appropriate prompts on concurrent changes. (Req 5323)
  - Record lock visibility; lock duration thresholds; administrative unlocking. (Reqs 6513, 7302)
  - Data validation, defaults, formatting, and required field configuration. (Req 5328)
- Security
  - Patron data secure in all transfers; secure protocols (SFTP, SSL, SSH). (Reqs 6510, 6511)
  - Fine-grained user/group permissions across data access and reporting. (Reqs 2492, 5617)
- Retention and logging
  - Log files configurable for enable/disable and retention thresholds; viewable without system stop. (Req 2474)
  - Data changes logged; undo functionality; ideally revision control. (Req 6505)
- Import/export
  - MARC bibliographic/authority import/export (single and batch; overlay existing records; selection list management); vendor integration (e.g., OCLC). (Req 1716)

## 3.6 Design constraints
- Platform and client
  - Operate on Linux or Solaris servers. (OE-2)
  - Accessible via web browser or Windows-compatible client; if web-based, support IE 6.0+ and Firefox 2.0+. (OE-3, OE-4)
- Database and web standards
  - Use a fully relational database backend. (CO-1)
  - Produce standards-compliant HTML. (CO-2)
- Environments
  - Provide development/training environments with migration to production. (CO-3)
- Security model
  - User rights and privileges controlled through security groups/roles for individuals, workgroups, and arbitrary staff groups. (CO-4)
- Accessibility
  - Accessible with assistive technologies. (OE-5)

## 3.7 Software system attributes
- Reliability
  - Support live backups (incremental/full) of data and transaction logs; changes logged with undo/revision control where available. (Reqs 6502, 6505)
- Availability
  - Support server clustering for failover capability. (Req 2462)
  - Non-disruptive processing of searches/reports during open hours is highly desirable. (OE-1)
- Security
  - Patron data secure in transit; support SFTP (active/passive), SSL, SSH; administrative visibility/control of user privileges. (Reqs 6510, 6511, 6509)
  - Access to configuration and log files controlled; root shell access available to authorized administrators. (Reqs 2479, 2474, 2470)
- Maintainability
  - Centralized dashboards and consoles for monitoring, configuration, logs, and jobs. (Reqs 6520, 6501, 2467, 2466, 2464, 6517, 2433, 6521, 6515)
  - Centralized client software installation/updates with targeting of specific clients; server-based configurations exportable/importable. (Reqs 6504, 6519)
  - Written upgrade guidelines including feature change lists. (Req 2431)
- Portability
  - Works with standard browsers and Windows-compatible clients; supports Windows printers. (OE-3, OE-4, Req 2441)

## 3.8 Supporting information
- Document conventions
  - Requirements may reference process flowcharts to provide context; these reflect current approaches and are not prescriptive constraints.
- Intended audience
  - For library managers/staff and software project managers/developers; readable to non-technical audiences with sufficient specificity for developers; assumes iterative, collaborative development with user reviews of prototypes.
- User documentation
  - Provide complete data specifications for all record types accessed/maintained by the module. (UD-1)
  - Provide high-level descriptions of major processes (e.g., bibliographic import/export, validation against authority sources, and standard reports). (UD-2)
  - Provide online HTML help as described in 3.3. (UD-3)

# 4 Verification

## 4.1 Functions
[N/A]

## 4.2 Performance requirements
[N/A]

## 4.3 Usability requirements
[N/A]

## 4.5 Logical database requirements
[N/A]

## 4.6 Design constraints
[N/A]

## 4.7 Software system attributes
[N/A]

# 5 Appendices

## 5.1 Assumptions and dependencies
- Assumptions
  - The System Administration Module is part of an enterprise-level Library Automation System. (AS-1)
  - System Administration processes are centralized, serving multiple locations. (AS-2)
- Dependencies
  - Relies on data structures and functionality of other ILS modules (e.g., Acquisitions and Cataloging). (DE-1)
  - Interfaces with vendor websites via published APIs and/or automated transfer of standard-format data files (e.g., USMARC21, EDIFACT). (DE-2)
  - Interacts with the patron interface (OPAC). (DE-3)

## 5.2 Acronyms and abbreviations
- ACQ: Acquisitions
- API: Application Programming Interface
- CAP: [N/A]
- CAT: Cataloging
- CSV: Comma-Separated Values
- EDIFACT: Electronic Data Interchange for Administration, Commerce and Transport
- HTML: HyperText Markup Language
- ILS: Integrated Library System
- IP: Internet Protocol
- KCLS: King County Library System
- MARC: MAchine-Readable Cataloging
- MGT: Management
- NCIP: NISO Circulation Interchange Protocol
- ODBC: Open Database Connectivity
- OCLC: Online Computer Library Center
- OPAC: Online Public Access Catalog
- SIP: Standard Interchange Protocol (SIP2)
- SMTP: Simple Mail Transfer Protocol
- SNMP: Simple Network Management Protocol
- SFTP: Secure File Transfer Protocol
- SSL: Secure Sockets Layer
- SSH: Secure Shell
- USMARC21: United States MARC 21 Format
- VNC: Virtual Network Computing
- Windows: Microsoft Windows Operating System