Ocotillo Presentation #44

Secure Application Testing Environment (SATE)

presenter: Grant Gagnon
email: grant.gagnon@sccmail.maricopa.edu
department: CITS
affiliation: Scottsdale Community College

Co-presenters:
Darren Stauth
Matt Diglio

time and place: Morning (10:15 - 11:45 AM) and Afternoon (1:00 - 2:30 PM) Open Demo Computing Commons P6.65

description:
Secure Application Testing Environment at Scottsdale Community College


Submitted by:

Grant Gagnon: Computing and Instructional Technology Services, Manager

Innovation Team:

Darren Stauth: System Analyst
Matt Diglio: System Administrator
Grant Gagnon: Project Manager
Jerry Booher: CIS Faculty
Pat Serrano: CIS Department Chair

Executive Summary:

This collaborative effort between SCC CITS staff and CIS faculty created a secure computerized testing environment. The end product delivers a test to a specific student, and location, at a predetermined time while providing the application functionality necessary to complete the exam without compromising the security of the test.

Background:

In the fall term of 2004, CITS staff were approached to discuss possible methods of securing tests for BPC110 courses. Issues were raised that network based tests that allowed student access, may be accessed prior to test times or in a normal class environment they could be emailed, copied out to server locations or otherwise compromised during testing because of the number of tools available on classroom computer systems. Faculty expressed dissatisfaction with previously used commercial products and simulators. Testing of Microsoft Office Productivity Suite products was to start in one week and a reasonable solution was needed quickly.

It became clear that the tools necessary to support the requests of the faculty were available or could be developed from existing tools already used in the instructional environment. Based on a brief needs assessment, the following criteria were developed:

• Tests would only be available to students in the course section that the test was to be given.
• Students would not need to navigate additional logins to a utility and could access the test through their personal computer account.
• The test would only be available at the time and location of the class meeting.
• Tests must be easily submitted.
• Students must not be allowed to modify the test after submission.
• Students would not be able to view other submitted tests.
• Students would not be able to use any other applications, Windows explorer, browsers or other tools during testing.
• Students would be able to work in the actual application with out limitations from a simulation.
• The test environment would be administered in house.
• Instructors would have complete control over the creation of the test file. Options would include; Printing (Yes/No), Timed Test (Yes/No at any interval), Run once (Yes/No) and the solution would work with any Microsoft Office Application.

Description:

The result of meeting all the criteria is a single Desktop Icon that is delivered to the student upon login. The Icon is only presented to the student if they are in the course section detailed by the Instructor, they are at the location for the test and it is the correct time for the test.

The student initiates the test by simply double clicking the Desktop Icon. After selection of the Icon the student is presented with the test file in the appropriate application. At this time the student is locked into the application as a shell and has no other resources available to them. After completing the test, the student only needs to close the application. File naming and saving is all done transparent to the student. The workstation is automatically restarted and the student can continue normal workstation use.

After the tests are taken, the Instructor has full access to the completed student tests. The tests are named with the student’s login account. The test can be reviewed by the instructor and graded.

Innovation Criteria:

Quality
The use of the testing function has brought many exemplary comments from our Faculty and Students. The in class effort administrating the test is minimal. Students are able to concentrate on the test rather than putting effort into learning a testing environment. By using the installed application, the student is presented with the same application configuration they use normally in class. Review of the submitted test is done electronically, with no need for test printing and collection during class. Returning of scored tests can be done through faculty class folders on the network. The Instructor has full control over the content and appearance of the test.

Efficiency
The use of the testing function has been very efficient for Instructors and Students. No class time or resource is needed to learn the testing environment. Students are not burdened with additional logins to testing systems. The locally administrated application has removed the dependency on internet based commercial products or the added resources needed to install commercial products and continued updating of those products. Instructors do not need to learn a commercial product to administer and grade tests.

Cost Effectiveness
The delivered product will save the college money by reducing the need to purchase commercial testing products.

Replication
Because the testing environment was created from resources already deployed to support Instructional Computing campus wide, the system can be replicated to other instructional disciplines and testing environments on campus. The testing environment would also support replication to other institutions since many pieces of the application are already in use at a number of MCCCD locations.

Creativity
The tools used to create the testing environment were all in place on the campus. While this was an exceptional start for the project; creativity in looking at the environment for an “outside the box” application was needed. The systems and utilities used are normally focused on the administration of student accounts and desktop management. Creativity was necessary to view these systems and utilities as resources for developing a testing environment.

Timeliness
Using only a week to create a solution was extraordinary. The effort and completion exceeded any expectation set by the initial team. The key in being able to deliver the solution quickly was the ability to use the current computing environment with out adding additional resources. Administrative tasks, application delivery and defined desktop management had been a long standing area of expertise for the System experts on the team. Being given a well set list of criteria by the end of the first meeting, set a project tone and allowed the technical staff to focus on the resulting project.

Learning
Although this project has not yet been shared district wide, it has been made available beyond the CIS department at SCC.

Collaboration
This project is an excellent example of collaboration among college IT staff and faculty. The faculty presented a well defined problem and established a clear set of criteria for a solution. The IT staff then developed a unique re-purposing of existing tools to create a solution that would meet faculty specifications.

More details and presentation materials are available in the Maricopa Learning eXchange package for this session.
http://www.mcli.dist.maricopa.edu/mlx/slip.php?item=1567