Statement of Requirements_Xyleme_CHUNK LCMS_Amendment A00001.pdf

Office of Contracting and Logistics Management

Revised 05 Mar 2015

Amendment A00001

Statement of Requirements

Curated Heuristic Using a Network of Knowledge (CHUNK)

Learning Content Management System (LCMS)

Graduate Education Advancement Center (GEAC)

Naval Postgraduate School (NPS)

1.0 Background/Introduction:

CHUNK Learning is an adaptive learning initiative at NPS aimed at augmenting student classroom experiences through the use of a flexible web-based application that provides access to relevant learning content based on academic curricula, knowledge and skill needs, and personal learning preferences. Students should be able to access curated knowledge content developed by faculty subject matter experts (SME) and organized by instructional designers (IDs), regardless of geographic location. A crucial part of this system is the authoring and content management capability for the preparation and delivery of content to learners. This capability will be provided by CHUNK LCMS, the supporting authoring and content management tool, as described in the statement of requirements.

SCORM 1.2 is the required output format for content.

NPS envisions that CHUNK Learning integrated with CHUNK LCMS, will support remedial education to increase student success, for courses taught in residence in addition to courses taught in the hybrid/blended environments.

2.0 Minimal Technical Requirements/Salient Characteristics:

The CHUNK LCMS will support authoring, publishing, management of content, and must interface to CHUNK Learning, the in-house developed system. The interaction between both CHUNK LCMS and CHUNK Learning will be done through a representational state transfer (REST) application-programming interface (API). CHUNK LCMS must be

Sharable Content Object Reference Model (SCORM)-compliant and provide learning experience records via Experience API (xAPI), in terms of operability. In addition, the

CHUNK LCMS must interface with the open-source Sakai Leaning Management System

(LMS) to provide a seamless experience for faculty and students. The CHUNK LCMS must be able to establish objects in at least five levels: Activities (content files such as .doc, .pdf, .mp4, etc.), CHUNKlet (e.g., assembly of activities), CHUNK (e.g., assembly of

CHUNKlets), Units (e.g., assembly of CHUNKs), and Topics (assembly of units).

Table 1 specifies the minimum set of technical requirements, which details the essential operational and functional features required. , considering that most of the LCMS tools available in market will already offer the common required features for authoring and managing content.

Office of Contracting and Logistics Management

Revised 05 Mar 2015

Table 1: Minimum Technical Requirements

ID Description

T01 Provide centralization and organization of all related functions into one system

T02 Provide the capability to store all source, in-progress, and final learning content in one repository

T02 Allow access security based on users’ profiles

T03 Provide a log for all system actions taken in the repository

T04 Allow audit of data movement in and out of the repository (e.g., “process viewer”)

T05 Allow caching of media contained in the repository

T05 Provide SCORM Compliance interoperability

T06 Provide xAPI Compliance interoperability

T07 Allow delivery of HTML5 files (content must be adapted to mobile learning

T08 Integration features with other systems/applications (communicate and exchange data) via API

T09 Exports data from the repository into a packaged XML or JSON format

T10 Provide support for LDAP, SAML2 and Active directory or other single sign on identity management system

T11 Provide remote access (e.g. web API) to query, update, and download all pertinent content such as learner’s profile information, course content, and course metadata.

T12 Provide integration with SAKAI (LTI) and other LMS platform (IAW with IMS Global

Learning Standards)

T13 Provide a scalable solution

T14 Content created must be in a non-proprietary format and allowed to be easily exported

A rough estimate of the Initial Operational Capability (IOC) for CHUNK Learning System include:

- 500 faculty users (*)

- 10,000 student users (only access through CHUNK UI and Sakai LMS)

- 12,000 activities

- 1,500 CHUNKlets

- 300 Courses

- 100 Curricula

(*) this estimate is for faculty access to CHUNK Learning, not for the simultaneous use of the authoring feature of CHUNK LCMS.