2.   Use Case Overview

Presents the use case framework for APIP;

2.   The Key Use Cases

The descriptions for the set of summary use cases that are supported by the APIP.  These use case descriptions are documented using the Cockburn [Cockburn, 01] style.

Use Case

Supported in Version 1.0

Importing an APIP Item

Y

Exporting an APIP Item

Y

Importing an APIP Test

Y

Exporting an APIP Test

Y

Importing a Set of APIP Items

Y

Exporting a Set of APIP Items

Y

Importing a Set of APIP Tests

Y

Exporting a Set of APIP Tests

Y

Loading an APIP Test

Y

Loading an APIP Item

Y

Importing an APIP Database

-

Exporting an APIP Database

-

Importing APIP PNP Single or Bulk Records

Y

Exporting APIP PNP Single or Bulk Records

Y

Reading an APIP PNP

Y

Brief Description:

Upon request, the APIP Item and the associated asset files are imported in the form of the APIP interchange file from a source digital repository into either a target digital repository or an authoring tool.

Level:

Summary

Actors:

APIP Database, Authoring Tool

Trigger:

A user of an Authoring Tool or the APIP Database administrator request the import of an APIP Item.

Preconditions:

The APIP Item, and the associated asset files, are available for import in the form of an interchange file compliant with the APIP format.

Success Post-condition:

The APIP Item, and the associated set of asset files, are available in the new digital repository/authoring tool and available for editing, etc.

Failure Post-condition:

The APIP Item is not imported due to a problem in the interchange file. The problems may be in the availability of the asset files.

Main Success Scenario:

At receipt of the import request the system/application imports the interchange file into the target system/application (the manner of the import is outside the scope of this standard).  The APIP Item is identified and stored in a form appropriate for the local system/application.  All of the corresponding video, audio, image, etc. files are also stored appropriately.

Exception Conditions:

•         The APIP Item is invalid;

•         The APIP content packaging manifest is missing or invalid.

Brief Description:

Upon request the APIP Item, is exported from a source digital repository or an authoring tool into an independent APIP interchange file that is stored where appropriate, e.g., in a file store.

Level:

Summary

Actors:

APIP Database, Authoring Tool

Trigger:

A user of an Authoring Tool or the APIP Database administrator request the export of the APIP Item.

Preconditions:

The APIP Item is available for export in the form suitable to the system/application/tool that will perform the export operation.

Success Post-condition:

The APIP interchange file has been created and stored.

Failure Post-condition:

The APIP interchange file cannot be created.  This may be because one or more required asset files for the APIP Item cannot be located.

Main Success Scenario:

At receipt of the export request the system/application/tool responsible for the export identifies and collates the APIP Item and asset files. The APIP interchange file is then created and stored.

Exception Conditions:

•         The APIP manifest cannot be created;

•         APIP Item cannot be created.

Brief Description:

Upon request the APIP Test and the associated APIP Items, is imported in the form of the APIP interchange file from a source digital repository into either a target digital repository or an authoring tool.

Level:

Summary

Actors:

APIP Database, Authoring Tool

Trigger:

A user of an Authoring Tool or the APIP Database administrator request the import of an APIP Test.

Preconditions:

The APIP Test, and the associated APIP Items, is available for import in the form of an interchange file compliant with the APIP format.

Success Post-condition:

The APIP Test, and the associated set of APIP Items, are available in the new digital repository/authoring tool and available for editing, etc.

Failure Post-condition:

The APIP Test is not imported due to a problem in the interchange file. The problems may be in the availability of APIP Items and/or the asset files.

Main Success Scenario:

At receipt of the import request the system/application imports the interchange file into the target system/application (the manner of the import is outside the scope of this standard).  The APIP Test and the associated APIP Items are identified and stored in a form appropriate for the local system/application.  All of the corresponding video, audio, image, etc. files are also stored appropriately.

Exception Conditions:

N/A

Brief Description:

Upon request the APIP Test, and the associated APIP Items, is exported from a source digital repository or an authoring tool into an independent APIP interchange file that is stored where appropriate e.g. in a file store.

Level:

Summary

Actors:

APIP Database, Authoring Tool

Trigger:

A user of an Authoring Tool or the APIP Database administrator request the export of an APIP Test.

Preconditions:

The APIP Test, and the associated APIP Items, are available for export in the form suitable to the system/application/tool that will perform the export operation.

Success Post-condition:

The APIP interchange file has been created and stored.

Failure Post-condition:

The APIP interchange file cannot be created.  This may be due to size constraints or because one or more required APIP Items for the APIP Tests cannot be located.

Main Success Scenario:

At receipt of the export request the system/application/tool responsible for the export identifies and collates the APIP Test, the associated APIP Items and asset files.  The APIP interchange file is then created and stored.

Exception Conditions:

N/A

Brief Description:

Upon request a set of APIP Items, and the associated asset files, is imported in the form of the APIP interchange file from a source digital repository into either a target digital repository or an authoring tool.

Level:

Summary

Actors:

APIP Database, Authoring Tool

Trigger:

A user of an Authoring Tool or the APIP Database administrator requests the import of a set of APIP Items.

Preconditions:

The set of APIP Items, and the associated asset files, are available for import in the form of an interchange file compliant with the APIP format.

Success Post-condition:

The set of APIP Items, and the associated set of asset files, are available in the new digital repository/authoring tool and available for editing, etc.

Failure Post-condition:

The set of APIP Items are not imported due to a problem in the interchange file.  Some of the Items may be successfully imported.  The problems may be in the APIP Items and/or the asset files.

Main Success Scenario:

At receipt of the import request the system/application imports the interchange file into the target system/application (the manner of the import is outside the scope of this standard).  The set of APIP Items are identified and stored in a form appropriate for the local system/application.  All of the corresponding video, audio, image, etc. files are also stored appropriately.

Exception Conditions:

•         One of more APIP Item(s) are invalid;

•         The APIP content packaging manifest is missing or invalid.

Brief Description:

Upon request the set of APIP Items, is exported from a source digital repository or an authoring tool into an independent APIP interchange file that is stored where appropriate, e.g., in a file store.

Level:

Summary

Actors:

APIP Database, Authoring Tool

Trigger:

A user of an Authoring Tool or the APIP Database administrator requests the export of a set of APIP Items.

Preconditions:

The set of APIP Items are available for export in the form suitable to the system/application/tool that will perform the export operation.

Success Post-condition:

The APIP interchange file has been created and stored.

Failure Post-condition:

The APIP interchange file cannot be created.  This may be due to size constraints or because one or more required asset files for the APIP Items cannot be located.

Main Success Scenario:

At receipt of the export request the system/application/tool responsible for the export identifies and collates all of the appropriate APIP Items and asset files.  The APIP interchange file is then created and stored.

Exception Conditions:

•         The APIP manifest cannot be created;

•         APIP Item(s) cannot be created.

Brief Description:

Upon request a set of APIP Tests, and the associated APIP Items, is imported from a source digital repository into either a target digital repository or an authoring tool.

Level:

Summary

Actors:

APIP Database, Authoring Tool

Trigger:

A user of an Authoring Tool or the APIP Database administrator requests the import of a set of APIP Tests.

Preconditions:

The set of APIP Tests, and the associated APIP Items, are available for import in the form of an interchange file compliant with the APIP format.

Success Post-condition:

The set of APIP Tests, and the associated set of APIP Items, are available in the new digital repository/authoring tool and available for editing, etc.

Failure Post-condition:

The set of APIP Tests are not imported due to a problem in the interchange file.  Some of the Tests may be successfully imported.  The problems may be in the APIP Tests and/or the APIP Items.

Main Success Scenario:

At receipt of the import request the system/application imports the interchange file into the target system/application (the manner of the import is outside the scope of this standard).  The set of APIP Tests and Items are identified and stored in a form appropriate for the local system/application.  All of the corresponding video, audio, image, etc. files are also stored appropriately.

Exception Conditions:

N/A

Brief Description:

Upon request the set of APIP Tests, and the associated APIP Items, is exported from a source digital repository or an authoring tool into an independent APIP interchange file that is stored where appropriate e.g. in a file store.

Level:

Summary

Actors:

APIP Database, Authoring Tool

Trigger:

A user of an Authoring Tool or the APIP Database administrator requests the export of a set of APIP Tests.

Preconditions:

The set of APIP Tests, and the associated APIP Items, are available for export in the form suitable to the system/application/tool that will perform the export operation.

Success Post-condition:

The APIP interchange file has been created and stored.

Failure Post-condition:

The APIP interchange file cannot be created.  This may be due to size constraints or because one or more required APIP Items for the APIP Tests cannot be located.

Main Success Scenario:

At receipt of the export request the system/application/tool responsible for the export identifies and collates all of the appropriate APIP Tests, the associated APIP Items and asset files.  The APIP interchange file is then created and stored.

Exception Conditions:

N/A

Brief Description:

When a test taker activates an assessment, the assessment system loads in the APIP Test and configures it according to the learning and accessibility preferences of the test taker.  The assessment system selects the parts of the APIP Test that support the learning and accessibility preferences of the test taker.

Level:

Summary

Actors:

Assessment System

Trigger:

A test taker activates an assessment sessions while working with their LMS, local assessment system, or external assessment system.

Preconditions:

The APIP Test, and the associated APIP Items, is available for loading in the form of an interchange file compliant with the APIP format.

Success Post-condition:

The APIP Test has been loaded into the assessment system.  The start of the APIP Test is presented to the test taker and the set of related APIP Items have been identified and marked for loading into the assessment systems.

Failure Post-condition:

The APIP Test becomes marked as unavailable. The problems may be in the availability of APIP Items and/or the asset files.

Main Success Scenario:

At receipt of the APIP Test launch request by the test taker, the APIP Test is loaded from the repository.  This APIP file contains only the description of the test and the links to the set of related APIP Items, i.e., the APIP Items are not loaded into the assessment system as part of the load APIP Test call.

Exception Conditions:

N/A

Brief Description:

When a test taker activates an assessment, the assessment system loads the APIP Test and configures it according to the learning and accessibility preferences of the test taker.  The assessment system loads the relevant APIP Items (it is the assessment system that determines when the APIP Items are to be loaded and this may be implementation specific).

Level:

Summary

Actors:

Assessment System

Trigger:

A test taker activates an assessment sessions while working with their LMS, local assessment system, or external assessment system. The assessment system selects the APIP Items that need to be loaded.

Preconditions:

The APIP Test has been previously loaded into the assessment system.  The associated APIP Items are available for loading in the form of an interchange file compliant with the APIP format.

Success Post-condition:

The APIP Item(s) have been loaded into the assessment system.  Pre-rendering construction has been completed in response to the learning and accessibility preferences of the test taker.

Failure Post-condition:

The APIP Items are unavailable.  The problems may be due either to the failure to access/retrieve the associated asset files or it proves impossible to configure the Item as required by the test taker's accessibility and learning preferences.

Main Success Scenario:

Once the APIP test has been loaded the associated APIP Items are loaded according to the implementation approach of the assessment system.  For example, the assessment system may use on-demand loading of APIP Items in real-time as required by the test being presented to the test taker, or pre-caching of APIP Items may be used to ensure performance requirements, etc.  Once loaded the APIP Item is processed to prepare its rendered form to reflect the test taker's accessibility and learning preferences.

Exception Conditions:

•         The APIP Item is invalid;

•         The APIP content packaging manifest is missing or invalid.

Brief Description:

Upon request a complete APIP Database is imported from a source digital repository into the target digital repository.

Level:

Summary

Actors:

APIP Database

Trigger:

A Database Administrator is requested to make a new APIP Database available in a local repository.

Preconditions:

The APIP Database is available for import in the form of an interchange file compliant with the APIP format.

Success Post-condition:

The APIP Database is available in the new digital repository and available for use by APIP-complaint systems.

Failure Post-condition:

The APIP Database is not imported into the new target database system.

Main Success Scenario:

At receipt of the import request the digital repository issues an import request identifying the required APIP Database.  The APIP Database interchange file is imported into the new repository that unpacks the APIP information and stores it in the appropriate local database form in the local repository (the manner of the import is outside the scope of this standard).  The interchange must contain all of the files associated with the APIP Tests and APIP Items, i.e., any video, audio, image, etc. files.

Exception Conditions:

N/A

Brief Description:

Upon request a complete APIP Database is exported to the APIP interchange format.

Level:

Summary

Actors:

APIP Database

Trigger:

A Database Administrator is requested to export an APIP Database in the APIP interchange format.

Preconditions:

The APIP Database is available for export.

Success Post-condition:

The APIP interchange file is ready for use and/or import to some external digital repository.

Failure Post-condition:

The APIP interchange file has not been created.  This may be due to size constraints on the target storage system.

Main Success Scenario:

At receipt of the export request the digital repository processes the identified APIP Database and creates the APIP interchange file. Each APIP Database is contained in its own APIP interchange file.  If the interchange file is copied then either copy can be used to recreate one or more copies of the original APIP Database.

The interchange will contain all of the files associated with the tests, i.e., any video, audio, image, etc. files.  The relationships between these asset files and the actual test descriptions must be maintained within the new repository.

Exception Conditions:

N/A

Brief Description:

Upon request PNP file (containing a single test takers profile) or a bulk PNP records file (containing multiple test takers profiles).

Level:

Formative, Summary

Actors:

Student Information System (SIS), or any system that stores student records.

Trigger:

A user or administrator of an SIS or records system requests the import of a single PNP file, multiple PNP files, or single file containing multiple PNP records.

Preconditions:

The single or set of PNP files is/are available for import in the form of a/an interchange file(s) compliant with the APIP format.

Success Post-condition:

The SIS or records system records the information contained within the PNP file(s) at the level for which the system has been certified (Entry, Core, Elective, or any future level/profile). The profile information is properly assigned to the correct test taker.

Failure Post-condition:

The records system fails to receive the PNP information, or loses portions of information contained within the PNP file(s) for which the system has been certified (Entry, Core, Elective, or any future level/profile), or fails to assign the information to the correct test taker.

Main Success Scenario:

For a single PNP file, the user of a records system identifies the test taker for whom the PNP file pertains to, and chooses to import the PNP file (identifying the test taker could also be done after choosing to import the file). The PNP files data is imported, and is now associated with that test taker. If the records system is certified at the Entry Level, all Entry Level features will be recorded without losing any information. If the system is certified at the Core Level, then all Core information is recorded. Optionally, a system can retain any further Elective features. A system is required to record any features for which it has been certified, but can optionally retain any other features.

For multiple PNP files, or for a single bulk records file, the system user chooses the file(s) to import, and all the information contained within the files is accurately recorded in the system, assigning the features to the correct test takers. Any errors or duplications would be provided to the system user, and allow them to accept or reject the file. The system may optionally allow the system user to accept or reject portions of the information contained within the PNP file(s) to ignore or replace information already contained within the records system.

Exception Conditions:

•         One or more PNP file(s) are invalid

•         Information within the PNP file(s) conflicts with information already supplied within a records system.

Brief Description:

Upon request, a PNP file, or files, or a single file with multiple PNP records will be exported in the APIP PNP interchange format.

Level:

Formative, Summary

Actors:

Student Information System (SIS), or any system that stores student records

Trigger:

A system user or administrator logs into a records system.  The user chooses a single, or multiple test takers for whom they wish to export PNP data. Depending on the export needs, the system exports valid instances of a single PNP file with a single record, multiple PNP files where each file has a single record, or a single PNP file with multiple records.

Preconditions:

The records system contains assessment accessibility data for test taker(s).

Success Post-condition:

The APIP PNP file(s) is/are ready for use and/or import to some external records system.

Failure Post-condition:

The APIP PNP file(s) are not created.

For a bulk records PNP file, the file does not contain test taker identifying information for each record.

The record data is not in the valid APIP interchange format.

Main Success Scenario:

The system user logs into a records system. The user then chooses which test takers for which PNP records need to be exported. The user chooses to EXPORT APIP PNP records from within the system. PNP file(s) are exported to a location which the user has chosen. The information contained within each instance reflects the records system's certification level (Entry, Core, Elective, or any future level/profile). A system is required to export any features for which it has been certified, but can optionally export any other features.

Exception Conditions:

•         The XML instance is invalid.

•         Stored information is incorrectly exported to the PNP file(s).

Brief Description:

This is the mechanism by which an assessment system is configured to match the accessibility and learning preferences for each and every test taker.

Level:

Formative, Summative

Actors:

Delivery Assessment System

Trigger:

A test taker logs into an Assessment System.  Therefore, the Assessment System must query the 'Preferences Server' to acquire the test taker's accessibility needs & preferences.

Preconditions:

The assessment accessibility needs  & preferences for the test taker are available to the Assessment System via a known Preferences Server.

Success Post-condition:

The Assessment System has received the accessibility and learning preferences that were provided in an APIP PNP profile.  The Assessment System environment for the test taker has been configured to reflect those preferences.  The Assessment System will be able to tailor any presented tests in an appropriate manner. The system is required to provide any features for which it has been certified (Entry, Core, Elective, or any future level/profile), but can optionally provide any other features. However, a system should only provide features to students for which have been approved by the assessment administrators, or supplied in their PNP profile.

If a system is Core Certified (or certified for any level or profile that uses APIP accessibility information provided within the APIP content), the system delivers the accessible content in the prescribed order provided in the inclusion order applicable to the audience for whom it is intended.

Failure Post-condition:

The Assessment System fails to receive the accessibility & needs preferences information.  Consequently, the test taker must be asked to provide an alternative source for those preferences.

Main Success Scenario:

The test taker logs into the Assessment System.  During the login process, the Assessment System requires its Preferences Server to obtain the assessment accessibility and needs preferences for the test taker.  Once obtained, these preferences are used to configure the Assessment System and any subsequent assessments/tests appropriately (the latter will also require real-time rendering of the APIP Tests and Items to facilitate the accessibility preferences).  The preferences are supplied in the form of an APIP Personal Needs and Preferences (PNP) data file.

Exception Conditions:

•         The XML instance is invalid.

Rob Abel, 1EdTech (USA)

Justin Marks, NWEA (USA)

Michael Aumock, Pacific Metrics (USA)

Mark McKell, 1EdTech (USA)

Marty Christensen, ACT (USA)

Sue Milne, JISC (UK)

Jason Craft, Pearson (USA)

Wayne Ostler, Pearson (USA)

Gary Driscoll, ETS (USA)

Zack Pierce, Measured Progress (USA)

Eric Hansen, ETS (USA)

Michelle Richard, Pearson (USA)

Regina Hoag, ETS (USA)

Mike Russell, Measured Progress (USA)

Thomas Hoffmann, Measured Progress (USA)

Farhat Siddiqui, ETS (USA)

Wilbert Kraan, JISC (UK)

Colin Smythe, 1EdTech (UK)

Devin Loftis, McGraw-Hill/CTB (USA)

Wyatt VanderStucken, ETS (USA)

Version No.

Release Date

Comments

v1.0 Candidate Final

26 March 2012

The first formal release of the Candidate Final version of this document.

v1.0 Final Specification

31 March 2014

The Final Specification version of this document.