Itembanking Architecture

1
Itembanking Architecture

• CETIS Metadata/Assessment SIG
• University of Strathclyde,
• Glasgow

2
Introduction and Definition

• This presentation looks at the essential features
  for a sustainable itembanking system and suggests
  an architecture based on these principles.
• It suggests five key approaches that should be
  used to future proof any development in this area
  and suggests that it would be beneficial if a
  common architecture blueprint could be agreed
  between the key stakeholders

3
Desirable Architecture features

• Services Orientated Architecture
• Standards Based Approach
• Integration of Workflow management
• Flexible Role Profiling
• Open Source

4
Services Orientated Architecture

• Services can be substituted
• Additional services can be developed
• Allows a mixed model of FOSS, user and
  commercially developed services
• Can facilitate a piecemeal approach

5
Overview of Infrastructure
Test construction software
6
Standards Based Approach

• Using IMS Specifications where-ever possible
• Developing application profiles to narrow
  specifications and deal with areas of ambiguity
• Publishing vocabularies and working with others
  to converge or map with others.

7
Examples of Application Profiling

• LTS metadata vocabularies
• SQA Metadata application profile
• COLEG application profile
• LIFE applications profile and vocabularies

8
Integration of Workflow management

• Using a superimposed workflow management
  system/language
• Identifying the workflow processes to be
  integrated into the system
• Identifying overall workflow for established
  procedures and processes

9
Identification of workflows
10
Flexible Role Profiling

• Access should be controlled by role based user
  groups
• Multiple membership should be enabled
• Permissions allocated by role profile rather than
  identifier.

11
Examples of SQA Roles

• Item Writer
• Scrutineer
• Validator
• Test constructor
• Itembank Manager.

12
Open Source Licencing

• Allows further development
• Encourages development documentation
• Encourages convergence
• Value for public money

13
Where now?

• Services are already available need to be built
  on within an agreed blueprint
• Work is required to converge and map application
  profiles and develop other standards
• Workflow management needs defined and broken into
  smallest components
• Roles need identified and defined
• Agreement reached on the principle of FOSS, and a
  commitment by the principle partners

14
Producing a blueprint?

• The architecture outlined at the beginning is a
  first attempt to map this area, but
• Not detailed enough
• Not comprehensive enough
• Not based on services
• Hoping to work with others to develop a framework
  for this area that all can agree to in order to
  maximise the benefit for the whole sector.

15
Contact Details

• Mhairi McAlpine
• Project ManagerComputer Assisted Assessment
  TeamOptima58 Robertson StreetG2 8QD0845 213
  5399mhairi.mcalpine_at_sqa.org.uk