Scripting Certification

From Second Life Wiki
Revision as of 13:24, 26 April 2007 by Strife Onizuka (talk | contribs)
Jump to navigation Jump to search

The holder of a SL Certification has demostrated compency in basic SL User Interface, SL Permissions

This certification exams consisted objective type questions such as true/false or multiple choice questions and simulated labs for examining a candidate's expertise. For this reason, it is essential that those aspiring for SL Scripting certification have sufficient hands-on experience. The majority of questions will require the writing of scripts.

Certifications

Core Scripting

Topics:

Intermediate Specialties

Media Management

Topics:

  • Land based Audio & Video

Asset Management

Topics:

Avatar Permissions

Topics:

  • Animation
  • Camera
  • Controls
  • Money

Basic Animation

Topics:

  • Object animation
  • Texture animation
  • Particle systems

Attachments

Topics:

  • HUD
  • Body

Movement

Topics:

  • Objects
  • Linked Prims

Detection & Sensing

Topics:

Dataserver

Topics:

Physics & Collisions

Topics:

Data Management

Topics:

  • String Parsing
  • Manipulating Large Datasets

Script Communications

Description: Interacting with other scripts Topics:

External Communications

Description: Interacting with external data stores & web content
Topics:

Advanced Specialties

Applied Animation

Topics:

  • Object animation
  • Texture animation
  • Particle systems

Agent Interaction/UI

Requires: Data Management
Topics:

  • Chat Interfaces
  • Touch based UI
  • Dialog UI
  • Notecard Config

Vehicles

Topics:

Database Creation

Requires: Data Management
Topics:

Test Scoring

Proposal A

This complex scoring system allows for sections to be tailored so that less important sections have less impact on the score without upsetting the balance of points.

  • Each section is scored seperately.
  • Each question will be worth some number of points.
  • Each section would have a set number of points that could count towards the total.
    • A hypothetical section may contain 20 points worth of questions only 15 would be counted.
    • This would allow for the user to get a certain number of questions wrong in a section without it effecting the score.
  • The section scores would be totaled and then a pass/fail would be determined based on some set number of points that could be missed.
    • The total section usable points may add up to something like 200 but the user would only need something like 190 to pass.