Dukane Corporation SRSAC1 사용자 설명서
Before the start of the assessment, the Login Session will initiated, and each Remote
will prompt the users to enter their Student ID (and if applicable, their PIN)
will prompt the users to enter their Student ID (and if applicable, their PIN)
and / or
Other considerations (?):
• Ability of students able to “login” (age appropriate)?
• Student number viability (non S.S., usable, integration from grade book etc)?
• Maintenance of student PIN #’s (Reset, change etc)?
• Any other methods of identifying user via short key code combinations?
• Any other methods of identifying user via short key code combinations?
3.2. Assigned
Hand-Out
Requires:
• List of remotes that will be used
• Student roster mapped with logical Remote ID’s
• Student roster mapped with logical Remote ID’s
• Diligent re-use of the same Remote by each and every individual in the
class.
In this mode, a given room will maintain a unique list of Remotes to be used within
that room alone. ConVA Presentation Manager will be (initially) required to build
and maintain the collection of remotes that will be used, with the remote unique ID’s
stored in the ARP table. This could be done through a couple of options, such as
“Open Enrollment”, or “Prompted Response”:
that room alone. ConVA Presentation Manager will be (initially) required to build
and maintain the collection of remotes that will be used, with the remote unique ID’s
stored in the ARP table. This could be done through a couple of options, such as
“Open Enrollment”, or “Prompted Response”:
Open enrollment could automatically accept any remote request, and assign a
logical remote id based on a running sequential list. Normal maintenance could
then handle removal / additions after the fact.
logical remote id based on a running sequential list. Normal maintenance could
then handle removal / additions after the fact.
Prompted response could alert the instructor that a remote wishes to connect, and
given a screen to accept or deny the request.
given a screen to accept or deny the request.
A student roster must be available that will maintain the assigned logical Remote ID
to Student mapping.
to Student mapping.
Other considerations (?):
• Repeatability of student / remote combination.
• Maintenance of lost/replacement remotes.
• Maintenance of incoming / outgoing students.
• Maintenance of incoming / outgoing students.
Page 8 of 13