1 / 16

Itembanking Infrastructure: A Proposal for a Decoupled Architecture Brendan Tierney and Linn van der Zanden Scottish

Itembanking Infrastructure: A Proposal for a Decoupled Architecture Brendan Tierney and Linn van der Zanden Scottish Qualifications Authority TENCompetence, Sofia. Overview. Introduction Autonomous development Diagram Elements which make up the architecture

fabiano
Download Presentation

Itembanking Infrastructure: A Proposal for a Decoupled Architecture Brendan Tierney and Linn van der Zanden Scottish

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Itembanking Infrastructure: A Proposal for a Decoupled Architecture Brendan Tierney and Linn van der Zanden Scottish Qualifications Authority TENCompetence, Sofia

  2. Overview • Introduction • Autonomous development • Diagram • Elements which make up the architecture • Future areas of exploration

  3. Introduction and Definition • Itembank is considered to be made up of a repository and database • Itembanking system is considered everything up to the point of delivery, and everything from the output of data from the delivery system

  4. Decoupled Architecture: Benefits • Easily adapted to accommodate change in model or workflow • Pieces can be upgraded in line with specifications • Small chunks can be built and used immediately • Sophistication of the system/ community will place additional demands

  5. Decoupled Architecture: Implications • Standards compliance • Additional functionality to support existing processes may not be required at a later stage • Robust testing required: early detection of errors difficult in pieces where there is little user interaction

  6. What does Itembanking entail? • Storage of items • Generation of items • Delivery, Marking and Result Processing • Test Construction • Roles and Workflows

  7. Storage of Items The Itembank: • Repository: storage of QTI files, resources, manifest files • Database: storage of LOM and QTI metadata, search and retrieval functionality • Unpackaging Functionality

  8. Generation of Items • QTI Authoring Tool: outputs QTIv2.0 items • Specialist Authoring Software: i.e. for graphics or other markup languages • Metadata Tagger: attributes data to items according to IEEE LOM standard and extracts QTI metadata • Application Profile Development Software: interface for development of profiles which prefills metadata • Content Packager: packages elements of QTI items according to IMS specification

  9. The Itembank and Generation of Items

  10. Test Construction • Glossary Development Software: produces glossary which defines statistics for test construction • Test Construction Software: takes in application profile (metadata) and glossary (statistics) to produce algorithm • Item Analysis Software: runs required analysis from algorithm, identifying items from pool that match the conditions

  11. Test Construction

  12. Delivery, Marking and Result Processing • Delivery Software: imports QTIv2.1 package from itembank, and sends responses to Marking Processing Software • Marking Processing Software: has several elements for different item types i.e. human based, computer based or both • Result Processing Service: aggregates items and implements pass mark or grade boundaries • Master Results Databank: stores candidate interactions with item IDs which are fed out from the Delivery Software

  13. Delivery, Marking and Result Processing

  14. Future areas of Exploration • First attempt at scoping the potential for decoupled architecture • Requirements must be scoped for each element • Roles of users need further defined • Workflow processes need defined • Seeking partners (UK and EU)

  15. Contact Linn van der Zanden Learning Technologist Linn.vanderZanden@sqa.org.uk Brendan Tierney Project Manager Brendan.Tierney@sqa.org.uk

More Related