# 1 Introduction
[NULL]

## 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).

## 1.2 Scope
The System Administration Module is a software product designed to facilitate the management of every aspect of an Integrated Library System (ILS). It is intended to replace and enhance current capabilities of commercially available ILSes, as well as add new functionality. The application is specifically developed for the King County Library System, but its requirements are believed to be suitable for many large, urban, multiple-branch, centralized library systems. The specification focuses on requirements directly or indirectly related to management activities within an ILS, presupposing the general data structures and functionality of a full-fledged ILS.

## 1.3 Product overview
[NULL]

### 1.3.1 Product perspective
The System Administration Module is an integral part of a larger enterprise-level Library Automation System. It presupposes the general data structures and functionality of a full-fledged ILS and relies on the data structures and functionality of other modules within this system, including Acquisitions and Cataloging modules. The module is focused on functional characteristics related to system administration, with data structures and user interfaces requiring further specification and development using an iterative, prototype-oriented software development methodology.

#### System interfaces
The System Administration Module interfaces with:
*   A variety of vendor websites, via published APIs and/or automated transfer of standard-format data files (e.g., USMARC21, EDIFACT).
*   A patron interface, also known as an Online Public Access Catalog (OPAC).

#### User interfaces
The System Administration Module shall be accessible through a web-browser or a Windows-compatible client. If web-browser based, it shall be accessible through Microsoft Internet Explorer (v.6.0 and later) and Mozilla Firefox (v.2.0 and later). The system shall also be accessible with screen-reading software, screen-magnification software, and other software programs designed to increase accessibility. User interfaces will require further specification and development using an iterative, prototype-oriented software development methodology.

#### Hardware interfaces
The System Administration Module shall operate on a Linux or Solaris server.

#### Software interfaces
The System Administration Module requires and interfaces with the following software products and systems:
*   **Required Software Product:** A fully relational, SQL-based database system. This database must allow SQL queries against any table and be accessible as an ODBC source, with all data tables and data storage fully accessible.
*   **Interfacing Application Systems:**
    *   An enterprise-level Library Automation System, including its Acquisitions and Cataloging modules. The System Administration Module relies on the data structures and functionality provided by these components.
    *   Various vendor websites, for which the module will interface via published APIs and/or automated transfer of standard-format data files (e.g., USMARC21, EDIFACT).

#### Communications interfaces
The system supports secure protocols, including SFTP, SSL, and SSH. SFTP is supported in both active and passive modes, configurable per vendor.

#### Memory constraints
[N/A]

#### Operations
The System Administration Module supports various management activities, including:
*   Configuring the ILS to enable and support features and processes.
*   Monitoring, troubleshooting, and controlling server, database, application, services, ports, and API performance.
*   Managing user and group accounts and privileges.
*   Managing server and client software installation, upgrades, and updates.
*   Backing up databases, configuration files, log files, etc.
It is highly desirable that searches and reports can be processed during open hours without disrupting other system functions. The system provides capability to perform live incremental and full backups of data and transaction logs.

#### Site adaptation requirements
The System Administration Module is designed to support the needs of a large, multiple-branch library system, specifically one with 50 locations, 20 million circulations, and purchasing and processing over 500,000 items per year. While developed for King County Library System, the requirements are believed to be suitable for many large, urban, multiple-branch, centralized library systems, implying a degree of adaptability for different library system configurations.

#### Interfaces with services
[N/A]

### 1.3.2 Product functions
The System Administration Module facilitates the management of every aspect of the Integrated Library System. Specifically, it supports the following activities:
*   Configuring the ILS to enable and support features and processes required for management of the Library branches, patrons, collections, and circulation transactions.
*   Monitoring, troubleshooting, and controlling server performance.
*   Monitoring, troubleshooting, and controlling database and application performance.
*   Monitoring, troubleshooting, and controlling services, ports, and application programming interfaces.
*   Managing user and group accounts and privileges.
*   Managing server and client software installation, upgrades, and updates.
*   Backing up databases, configuration files, log files, etc.

### 1.3.3 User characteristics
This SRS is intended for both library managers and staff who may contribute additional requirements or commentary, and for software project managers and developers who will implement the requirements. It assumes a general understanding of Library services and processes.

The intended user classes include:
*   **Patron:** A customer of King County Library System, either possessing a library card or not, either on site of a community library or not, using either print materials, media materials, or electronic resources.
*   **Staff:** Includes managers, librarians, library technicians, library assistants, and library pages who are involved in designing and providing services for the Library.
*   **System Administrators:** Includes staff with responsibility for managing servers, databases, applications, services, ports, and APIs related to the ILS.
*   **Managers:** Includes management staff who oversee Library processes.
*   **Library Managers:** Includes Cluster and Site Managers who provide input to the design and implementation of Library services.
*   **Library Directors:** Includes members of the Library Executive Team who plan and direct Library services and priorities.

### 1.3.4 Limitations
The following items limit the supplier's options or define the scope of this specification:
*   **Hardware Limitations:** The system shall operate on a Linux or Solaris server.
*   **Software Limitations:** The System Administration Module shall use a fully relational database back-end.
*   **Interface Limitations:** The System Administration Module shall produce standards-compliant HTML.
*   **Development Process Limitations:** Data structures and user interfaces will require further specification and development using an iterative, prototype-oriented software development methodology.
*   **Control Functions:** User rights and privileges will be controlled through security groups and/or “roles” that allow access control for individuals, workgroups, and arbitrary staff groups.
*   **Audit Functions:** Individual staff logins shall allow for an audit trail.
*   **Parallel Operation:** The system must support simultaneous access and updates to patron and item records by multiple staff members and patrons, with record changes applied in a reasonable way, including prompts to warn when a record has been changed since it was displayed.
*   **Security Considerations:** Patron data must be secure in all transfers to and from the system.

## 1.4 Definitions
*   **ILS:** Integrated Library System
*   **OPAC:** Online Public Access Catalog
*   **Patron:** A customer of King County Library System, either possessing a library card or not, either on site of a community library or not, using either print materials, media materials, or electronic resources.
*   **Staff:** Includes managers, librarians, library technicians, library assistants, and library pages who are involved in designing and providing services for the Library.
*   **System Administrators:** Includes staff with responsibility for managing servers, databases, applications, services, ports, and APIs related to the ILS.
*   **Managers:** Includes management staff who oversee Library processes.
*   **Library Managers:** Includes Cluster and Site Managers who provide input to the design and implementation of Library services.
*   **Library Directors:** Includes members of the Library Executive Team who plan and direct Library services and priorities.
*   **SRS:** Software Requirements Specification

# 2 References
The following documents and standards are referenced in this SRS:

**Compliance:**
*   USMARC21 (standard format for data files)
*   EDIFACT (standard format for data files)
*   Specifications for Acquisitions and Serials Management modules (previously published by King County Library)
*   Specifications for Circulation module (previously published by King County Library)
*   Specifications for Cataloging module (previously published by King County Library)
*   Specifications for OPAC and web services (under development by King County Library)

**Guidance:**
*   Process flowcharts indicating the current approach to System Administration at King County Library System. These provide contextual information and do not prescribe or constrain new software development.

# 3 Requirements
[NULL]

## 3.1 Functions
### 3.1.1 General System Functions
*   **SQL-based database (Req ID: 6512):** The system shall run on a fully relational, SQL-based database system. It shall provide the ability to run SQL queries against any table in the database and access the database as an ODBC source. All data tables and data storage shall be fully accessible.
*   **Real-time processing (Req ID: 5615):** The system shall provide real-time processing, ensuring, for example, that pull lists are up to date at the time of viewing or printing, and supporting live shelf reading and weeding.
*   **Field and record sharing (Req ID: 5323):** The system shall allow multiple staff members and patrons to simultaneously access and update patron and item records, including on staff check-in and check-out terminals, self check-out stations, through SIP2/NCIP2 and similar protocols and APIs, and in the OPAC. Depending on assigned privileges, staff shall be able to view all patron and item fields, while patrons can access only selected fields. Record changes shall be applied in a reasonable way, with prompts to warn when a record has been changed since it was displayed.
*   **Record lock management (Req ID: 6513):** For any patron record or item record, staff shall be able to identify where it is in use (location, user, date and time placed).
*   **Individual and shared staff login accounts (Req ID: 2492):** The system shall support individual and shared staff login accounts. Access to modules shall be granted by use of "roles" or "privileges" that allow each account to access as many (or as few) modules as needed. Individual logins shall allow user-level preferences and an audit trail.
*   **System documentation (Req ID: 2428):** System documentation shall be library-specific and follow standard formats for technical documentation. Documentation shall be specific to the particular version of the software in use at the library, web-based, indexed, organized by function, and easily searchable.
*   **System upgrade guidelines (Req ID: 2431):** System upgrades and updates shall include written guidelines for updating servers and clients, including a list of new, changed, and removed features.
*   **Configuration file access (Req ID: 2479):** The system shall provide access to all configuration files.
*   **Log file access (Req ID: 2474):** The system shall provide 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.
*   **Root shell access (Req ID: 2470):** The system shall provide access to the root shell.

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

### 3.1.3 Business Rules
*   **Business rules (Req ID: 2445):** The system shall support restrictions based on business rules, e.g., restrictions on deleting item records that are in checked-out status, or restrictions on deleting bibliographic records with existing holds.
*   **Suppression rules (Req ID: 5278):** The system shall provide customizable 'Rules of Suppression' that specify whether patrons and staff can view 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.
*   **Requesting rules (Req ID: 5190):** The system shall allow creation and modification of requesting rules that determine whether a patron can place a hold on an item. Requesting rules may evaluate patron type, current number of holds, current patron account balance, item type, item status, owning location code, and other criteria. Requesting rules shall also specify whether staff with specific privileges or roles can override specific criteria.
*   **Loan rules (Req ID: 5057):** The system shall allow creation and modification of loan rules that allow or disallow check-out of items, calculate loan periods, and determine renewal limits. Loan rules may evaluate patron type, current number of items checked out, current patron account balance, item type, item status, owning location code, check-out location code, and other criteria. Loan rules can access check-out location open/closed schedule in calculating due date. Loan rules shall also specify whether a specific criteria may be overridden by staff with specific privileges or roles.
*   **Data validation (Req ID: 5328):** The system shall provide the ability to specify default value, data validation, automatic formatting, and required status for any field.

### 3.1.4 Data Recovery
*   **System backup (Req ID: 6502):** The system shall provide capability to perform live incremental and full backups of data and transaction logs. The system shall support the use of third-party backup software such as EMC NetWorker.
*   **Data rollback (Req ID: 6505):** The system shall log data changes (such as record deletions) and provide "undo" functionality. Ideally, the system shall provide revision control.
*   **Server clustering (Req ID: 2462):** The system shall provide the ability to cluster servers for failover capability.

### 3.1.5 Security
*   **Patron data security (Req ID: 6510):** Patron data shall be secure in all transfers to and from the system.
*   **User account privileges (Req ID: 6509):** System administrative staff shall have full visibility and control of user privileges.
*   **Secure protocol support (Req ID: 6511):** The system shall support secure protocols, including SFTP, SSL, and SSH. SFTP is supported in both active and passive modes, configurable per vendor.

### 3.1.6 Maintenance
*   **MARC import/export (Req ID: 1716):** 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 and manipulated as selection lists.
*   **Record sets (Req ID: 6518):** The system shall support an unlimited number of record sets, with the ability to import and export set members in batch. Record sets can be the basis for batch field updates; can be used as a limiting scope for queries; can be used to delete original records with the ability to review prior to deletion, write errors to a log file, and undo one or more deletions.
*   **Staff account setup (Req ID: 2420):** The system shall provide a dedicated interface for creating new staff accounts. The new staff account creation process shall provide configurable templates for account administrator use; provide granular privileges for account creation, modification, and deletion.
*   **Patron account setup (Req ID: 2419):** The system shall provide a dedicated interface for creating new patron accounts. The patron account creation process shall provide configurable templates for staff use; support field validation and required fields; and provide configurable defaults.
*   **Job scheduling (Req ID: 6507):** The system shall support scheduling of maintenance tasks, reports, and data exports. Jobs can be scheduled in sequence ("start job B when job A finishes") and can be modified or cancelled at any time prior to starting.
*   **Job scheduling: management (Req ID: 6508):** Staff can be given permission to schedule tasks, reports, and data exports. System administration staff can view and manage jobs scheduled by other staff.
*   **Keyboard macros and shortcuts (Req ID: 2220):** The system shall support administrator-programmable and user-programmable macros and/or keyboard shortcuts. Shortcut keys may be assigned to macros (e.g., 'Insert Field') or to text strings. Macros are centrally managed on the server, can be imported from and exported to individual users, and can be restricted for use and/or editing through centrally-managed permissions.

### 3.1.7 Client Management
*   **Accounts independent from workstation (Req ID: 6514):** Staff and group accounts shall be independent from workstations; client install should not be tied to a specific location.
*   **Client software updates (Req ID: 6504):** Client software installation and updates must be centrally managed, using standard or proprietary network management tools, allowing streaming updates from the server. The system shall provide the ability to specify specific clients to be updated. Client software can be managed with VNC and Remote Desktop.
*   **Client configurations (Req ID: 6519):** All client configuration files shall be server based; configurations can be exported and imported between clients.

### 3.1.8 Queries and Reports
*   **Report format and output (Req ID: 2197):** The system shall provide the ability to fully customize the layout and appearance of reports. It shall provide the ability to display, print, email, or save reports to standard formats including CSV and Excel, as well as to customizable formats.
*   **Query tool (Req ID: 5624):** The system shall provide a user-friendly interface for designing queries against all record types. Staff can select fields to query; select values from a picklist of possible values; select regular expressions from a drop-down menu, and use a full range of Boolean operators. Administrators shall control staff access to tables and fields.
*   **Report templates (Req ID: 5607):** System administrators can create report templates that are available to front-line staff, and can be run as is or modified to the staff person's particular needs.
*   **Reports permissions (Req ID: 5617):** The system shall provide fine-grained permissions to allow or disallow staff to run specific reports, and/or to run ad hoc reports on specific sets of data.
*   **Record number report (Req ID: 2465):** The system shall report for each record type (patron, bibliographic, item, order, invoice, etc.): current record number, current number of records, number deleted, and number purged. Access to record numbers shall be controlled at the user/group level.
*   **Printer support (Req ID: 2441):** The system shall provide the ability to define and select four types of printers: receipt printer, standard printer, label printer, and forms printer. All Windows printers are supported.
*   **Multiple print output options (Req ID: 2439):** The system shall provide the ability to print to a file on the server, ftp, email, or printer from any part of the application. When applicable, the ability to select record fields and control the order of fields when printing.

## 3.2 Performance requirements
*   **Capacity (OE-1):** The system must support a library system with 50 locations, 20 million circulations, and purchasing and processing over 500,000 items per year.
*   **Response Time (OE-1):** It is highly desirable that searches and reports can be processed during open hours without disrupting other system functions.
*   **Real-time Processing (Req ID: 5615):** The system shall provide real-time processing, ensuring, for example, that pull lists are up to date at the time of viewing or printing; system supports live shelf reading and weeding.
*   **Concurrency (Req ID: 5323):** Record changes shall be applied in a reasonable way, with prompts to warn when a record has been changed since it was displayed.

## 3.3 Usability requirements
*   **Accessibility (OE-5):** The System Administration Module shall be accessible with screen-reading software, screen-magnification software, and other software programs designed to increase accessibility.
*   **User Interface Design (1.3 Intended Audience):** The software development process will occur in a highly collaborative and iterative environment in which end-users have multiple opportunities to review prototypes and refine the user interface and software functionality.
*   **Documentation Usability (Req ID: 2428, UD-3):** System documentation shall be web-based, indexed, organized by function, and easily searchable. The system shall provide an online, hierarchical, and cross-linked help system in HTML that describes and illustrates all system functions.
*   **Query Tool Usability (Req ID: 5624):** The system shall provide a user-friendly interface for designing queries against all record types.

## 3.5 Logical database requirements
*   **Database Type (CO-1, Req ID: 6512):** The System Administration Module shall use a fully relational, SQL-based database back-end.
*   **Accessing Capabilities (Req ID: 6512):** The system shall provide the ability to run SQL queries against any table in the database and access the database as an ODBC source. All data tables and data storage shall be fully accessible.
*   **Integrity Constraints (Req ID: 2445):** The system shall support restrictions based on business rules, such as prohibiting deletion of checked-out item records or bibliographic records with existing holds.
*   **Security (Req ID: 6510):** Patron data shall be secure in all transfers to and from the system.
*   **Data Retention (Req ID: 2474):** Log files can be enabled, disabled, and set to a specific retention threshold.
*   **Data Entities (UD-1):** The software developer shall provide complete data specifications for authority records, bibliographic records, order records, item records, hold/request records, and other records maintained or accessed by the System Administration Module.

## 3.6 Design constraints
*   **Database Technology (CO-1):** The System Administration Module shall use a fully relational database back-end.
*   **Output Standards (CO-2):** The System Administration Module shall produce standards-compliant HTML.
*   **Environment Provision (CO-3):** The System Administration Module shall provide a development and training environment with the ability to migrate configurations to a production environment.
*   **Access Control Mechanism (CO-4):** User rights and privileges will be controlled through security groups and/or “roles” that allow access control for individuals, workgroups, and arbitrary staff groups.
*   **Operating System (OE-2):** The System Administration Module shall operate on a Linux or Solaris server.
*   **Development Methodology (1.2 Product Scope and Features):** Data structures and user interfaces will require further specification and development using an iterative, prototype-oriented software development methodology.

## 3.7 Software system attributes
*   **Reliability:**
    *   **Failover Capability (Req ID: 2462):** The system shall provide the ability to cluster servers for failover capability.
    *   **Operational Stability (OE-1):** Searches and reports should be processed during open hours without disrupting other system functions.
*   **Availability:**
    *   **Server Clustering (Req ID: 2462):** The system shall provide the ability to cluster servers for failover capability.
*   **Security:**
    *   **Access Control (CO-4, Req ID: 2492, Req ID: 6509):** User rights and privileges will be controlled through security groups and/or “roles” that allow access control for individuals, workgroups, and arbitrary staff groups. System administrative staff shall have full visibility and control of user privileges. Access to modules is granted by use of "roles" or "privileges".
    *   **Data Protection (Req ID: 6510):** Patron data shall be secure in all transfers to and from the system.
    *   **Protocol Support (Req ID: 6511):** The system shall support secure protocols, including SFTP, SSL, and SSH.
    *   **Audit Trail (Req ID: 2492):** Individual logins shall allow for an audit trail.
*   **Maintainability:**
    *   **Upgrade Guidelines (Req ID: 2431):** System upgrades and updates shall include written guidelines for updating servers and clients, including a list of new, changed, and removed features.
    *   **Configuration Access (Req ID: 2479, Req ID: 6517):** The system shall provide access to all configuration files, with a single console for access and assignable read/write permissions.
    *   **Log Access (Req ID: 2474, Req ID: 2433):** The system shall provide full access to all log files, which can be reviewed without stopping the system. Logs can be enabled, disabled, and set to a specific retention threshold. A dashboard for locating and viewing log files shall be provided.
    *   **Root Access (Req ID: 2470):** The system shall provide access to the root shell.
    *   **Scheduled Tasks (Req ID: 6507, Req ID: 6508):** The system shall support scheduling of maintenance tasks, reports, and data exports, with management capabilities for system administration staff.
*   **Portability:**
    *   **Operating System (OE-2):** The System Administration Module shall operate on a Linux or Solaris server.

## 3.8 Supporting information
*   **Process Flowcharts (1.4 Document Conventions):** Process flowcharts, where appropriate, are included to provide contextual information regarding the current approach to System Administration at King County Library System. These are not prescriptive or constraining for new software development.
*   **Product Documentation Requirements (UD-1, UD-2):**
    *   The software developer shall provide complete data specifications for authority records, bibliographic records, order records, item records, hold/request records, and other records maintained or accessed by the System Administration Module.
    *   The software developer shall provide a thorough high-level description of major processes, including bibliographic record import and export, validation of bibliographic records against internal and external authority sources, and standard reports.

# 4 Verification
[NULL]

## 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
[NULL]

## 5.1 Assumptions and dependencies
*   **AS-1:** The System Administration Module is part of an enterprise-level Library Automation System.
*   **AS-2:** System Administration processes are consolidated at a central location, and accept input and provide services to multiple locations.
*   **DE-1:** The System Administration Module relies on the data structures and functionality of an enterprise-level Library Automation System, including Acquisitions and Cataloging modules.
*   **DE-2:** The System Administration Module interfaces with a variety of vendor websites, via published APIs and/or automated transfer of standard-format data files (e.g., USMARC21, EDIFACT).
*   **DE-3:** The System Administration Module interacts with a patron interface, also known as an Online Public Access Catalog (OPAC).

## 5.2 Acronyms and abbreviations
*   **API:** Application Programming Interface
*   **CPU:** Central Processing Unit
*   **CSV:** Comma Separated Values
*   **EDIFACT:** Electronic Data Interchange For Administration, Commerce and Transport
*   **HTML:** HyperText Markup Language
*   **ILS:** Integrated Library System
*   **IP:** Internet Protocol
*   **MARC:** Machine-Readable Cataloging
*   **ODBC:** Open Database Connectivity
*   **OPAC:** Online Public Access Catalog
*   **SFTP:** SSH File Transfer Protocol
*   **SIP2/NCIP2:** Standard Interchange Protocol (versions 2 and NISO Circulation Interchange Protocol 2)
*   **SNMP:** Simple Network Management Protocol
*   **SRS:** Software Requirements Specification
*   **SQL:** Structured Query Language
*   **SSH:** Secure Shell
*   **SSL:** Secure Sockets Layer
*   **VNC:** Virtual Network Computing
