|
The Management Center
gives you complete control over the structure and flow of each class offered.
It lets you configure system behavior, course content, class scheduling,
student signup and use of optional features such as the Message Board and the
Instructor module.
All setup, definition and course management functions may be
accomplished through the administrator buttons.
Concept: “Course”
vs. “Class”
A Course is a collection of
definitions and material, such as content sections, a course guide, tests, and
optionally, assignments. A course is not scheduled and has no instructor(s) or
students.
When a course is scheduled (placed in
the Course Catalog) it becomes a Class. A Class may be thought of as an
instance of a Course. One Course may be offered several times, and therefore
several classes may be built on the same Course.
A Class has Start and End dates and
may have an Instructor. Students may enroll in a Class once it is placed in the
catalog. From then on, all Student activity is associated with that Class.
Courses and Classes are both defined
from the Management Center
menu. You create a Course under the Course Builder option, and you
create a Class under the Scheduling Wizard option.
|
Training
One commenter suggested that the proposed guidance circular requires that all of the agencies in a region agree before a project can be implemented, thus conferring ''veto'' power over the project. The agency does not intend for the policy to halt ITS deployment in areas where agencies cannot agree on project designs. As part of the regional ITS Architecture development, the agencies can agree to disagree, however, the regional ITS architecture should include a representation of the standalone ITS deployments.
One commenter suggests that the proposal infers that existing agreements between agencies will now need to be amended or redone, which would result in a halt in operations of successful ITS projects and prevent the completion of other ITS projects. In response to the comment, the agency has clarified the regional ITS architecture requirements to specify that existing agreements that address the regional ITS architecture requirements are sufficient and that new agreements are not necessarily required.
One commenter noted that a definition of ITS was not included in the policy. The commenter suggested that the definition provided in TEA-21 section 5206(e) should be included in the policy. The agency agrees and has added the definition of ITS to the list of definitions. However, the legislative definition of ITS is broad and other commenters have suggested that if the policy is written to include every new piece of electronics or hardware, then the policy would be too limiting. As a result, the policy is intended to apply only to projects meeting the definition of an ''ITS project'' listed in the ''Definitions'' section of the policy.
|