To use the Hub Testing Integration System (HITS), you'll need the following:
You'll also need a basic knowledge of SIF REST:
You need to know how to work with a use case in HITS and access the HITS API
If you get stuck: drop us a line at
Allow jurisdictions (and potentially individual schools) to retrieve information about the NAPLAN test constructs for the current cycle, and about the performance of their students in the current cycle, in order to determine the level of education attainment of their students and to generate expected reporting to schools.
A Jurisdiction client connects to HITS, as a proxy for the National Assessment Platform, collecting the relevant information about student assessments and performance under NAPLAN, and gathering it back to jurisdiction applications for further processing.
Diagrams the interactions between SIF objects for this use case.
Information about the students taking part in the NAPLAN assessment has already been provided to the National Assessment Platform. The workflow for this is captured in the NAPLAN Registration use case. The workflow for this use case assumes that the information is already available, either because a client has carried out the NAPLAN Registration workflow, or because the client will accept StudentPersonal records prepopulated on the HITS server.
The students have already undertaken all the NAPLAN assessment for this year, and the responses they have provided have been captured in the National Assessment Platform.
The assessment results have already been processed post-assessment, and all required information is available for jurisdictions from the National Assessment Platform. This includes scaling of scored results, and deriving the national and jurisdiction averages for each test.
The source of truth about the jurisdiction schools involved in NAPLAN assessment is not the National Assessment Platform, but the Australian Schools List. The assessment results data includes ACARA Ids for schools, which reference the records held in the Australian Schools List.
Jurisdictions need to access information about the NAPLAN test structure as well as the test results: the former helps contextualise and interpret the latter. Information about the NAPLAN test structure is available under SIF modelling in two separate models: a single codeframe object per test, which contains all testlets, test items, rubrics and stimuli accessible through the test; and separate test, testlet and test item objects, which are referenced individually from the student test results object. The use case assumes that the code frame object will be consumed prior to testing, and the individual testlet and test item objects will be consumed alongside the test results.
Jurisdictions can cope with very large volumes of XML records being retrieved. To that end, they will need to be familiar with how the SIF standard does flow control through paging of results. (See "Paged Query" discussion in http://www.a4l.org/general/custom.asp?page=Infrastructure3_1, Base Architecture 3.1 PDF.)
Jurisdiction has access to HITS
HITS has been provisioned with School Data. Note that HITS can act as a proxy for the Australian Schools List; but jurisdictions should be planning on integrating with the Australian Schools List directly
HITS has been provisioned with Student Data, whether by the Jurisdiction client (through the NAP Registration Use case), or as pregenerated data within HITS
SchoolInfo (the Platform API releases data for multiple schools from a single endpoint. StudentPersonal records contain the ACARAId of the school they are registered against; so there is no need to consume or model a StudentSchoolEnrollment record.)
Consume (Codeframe + Results)
Note that this is not the usual workflow under HITS of Produce–Consume or Consume–Produce. This is a Consume-only workflow: the Produce component of the workflow is already captured under the NAP Registration use case.
Any processing of the NAPLAN results is out of scope of this use case, since it depends on jurisdiction-speific setup. Note that NSIP offers some support to jurisdictions for processing NAP results, throughh its NIAS toolkit.
Client-facing (pull); HITS represents the National Assessment Platform and is the data source for results information.
The following is a list of calls that need to be made to consume the required information:
http://.../SchoolInfos(from the Australian Schools List)
http://.../StudentPersonals(HITS should determine the URLs eg
http://hits.nsip.edu.au/StudentPersonals- access this information from your Dashboard.)
As there is no Produce component to the workflow, there is also no Assurance component. Any processing of NAPLAN results will be specific to the jurisdiction’s database setup, and will need to be undertaken within the jurisdiction: it is out of scope of this use case.
Jurisdictions need assurance that they can retrieve from the National Assessment Platform the large bulk of records associated with NAPLAN results.
The following conditions also must be met:
The Platform is likely to support service paths breaking results down by school, and possibly by year level. As the Platform is updated to realise those service paths, HITS will be updated as well.
None. This use case represent retrieving bulk data; querying individual records from the data scope is not currently in scope.