SAIL Ontology

offering: context of learner interactions, instantiation of curnit
run: deprecated, see offering
curnit: top-level independent organization of content that is ready to run (mash of "curriculum unit")
unit: deprecated , see curnit
Pedagogical Object: composition of assets, other pedagogical objects, and the relations between them
asset: non-relational digital asset (with no pedagogical goal)
pod - Pedagogical Object Descriptor, the pedagogical object as it's represented before usage
POI - deprecated Pedagogical Object Instantiation, a use of the POD
POR - deprecated POI with runtime bindings (unique to a run)
rim - class of container for learner data so that code can describe what it wants to store
sock - instance of a container for learner data, in which their interactions are recorded. it is bound to a rim.

implicit assessment: assessments that are embedded and unapparent to the learner

assessment script: human-authored script that culls learner artifacts to report conceptual understanding to the instructor. (in simplest form, just shows all most-recent artifacts through rims that had a certain flag.)

Design Glossary

actions
Actions are functions, inputs or features that are allowed by the role.

actor
An actor is someone or something that interacts with the system. At any moment, an actor assumes a particular role. (eg. graduate student assumes role of instructor)

critical feature
requested functionality that affects the architecture fundamentally

data model
A data model is the structure in which a computer program stores persistent information. In a relational database, data models are built from tables.

requirement
A definition of a piece of functionality for a software system.

role
A mode of interaction with the system (eg. learner). Constrast with user (e.g. student) who is an actual person who may fulfill multiple roles (e.g. facilitator when TAing a course)

scenario
A mostly static description of the actor, the preconditions, and his goals. E.g. [Derivative unit SCENARIO]. Contrast with story.

story
A narrative of: user, starting conditions, elements to interact with, actions, and results. Constrast with scenario.

TELS eXtreme
TELS software development process that combines traditional software approaches with eXtreme programming.

unit test
Controlled evaluation performed by a system programmer in the Development step to ensure that a piece of program code performs as defined in the specification.

use case
A use-case model consists of actors, use cases, and relations among them. Actors represent everything that must exchange information with the system, including what are typically called users. When an actor uses the system, the system performs a use case. A good use case is a sequence of transactions that yields a measurable result of value for an actor. The collection of use cases is the system's complete functionality.

UML
Unified Modeling Language, an object-oriented design language.

EMF
Eclipse Modeling Framework - "The EMF project is a modeling framework and code generation facility for building tools and other applications based on a structured data model." from emf home
In SAIL it is being used a way to marshal user and teacher data.

Proposed Terms

athena - a type of spotted owl (refactored from Anthony Perritano's Athena page)
OSLO - SAIL Savvy Learning Objects (refactored from Nate Titterton's SAILSavvyObjects page)