The General tab is the place for entering the tripartite "Objective Statement" and other properties.
Objective Topic
Use the Topic field to enter a brief, one-line description of the objective, using a phrase that is less "behavioral" or formal than the actual objective statement.
There are benefits from thoughtfully completing this field:
•You can generate a list of objectives by their "topics" rather than by their longer, formal behavior statements. This makes certain searches, queries or sorts easier to use at a glance.
•VISION can create several types of documents from the same set of objectives. If you want to create a reference document, VISION would use the topic field, rather than the formal behavior statement, as the heading of each segment.
Note: The Topic line is limited to 100 characters.
Tip: For additional edit features, click the right mouse button while in the field. To enlarge (or zoom) the window, click the Z button.
Condition
Enter the objective’s conditions here. Note that the conditions for the objective are not automatically derived from the conditions of its corresponding Task Analysis component. In other words, the Task Analysis component’s conditions are not carried over to the objective when the objective is created from that analysis component. The reasoning for this is that you may have different conditions for actual task performance in the field than you do for training its associated objective.
See also the following Advisor topic: Identifying conditions of performance
Behavior
Enter or edit the objective behavior statement here. To do this, simply start typing in the text area. The behavior statement of the Objective is the text displayed in the objectives hierarchy.
If the Objective was derived from a Task Analysis, the behavior statement (action verb) is carried over from the corresponding Task Analysis component. But that doesn't mean that any change to the behavior statement will affect the corresponding Task Analysis statement from which the objective was originally created (or vice-versa). The objective and the analysis component from which it was derived might initially share the same text, but they are independent objects in the VISION database.
See also the following Advisor topic: Writing the behavior (action) statement
Standard
Enter the objective’s standard(s) here. Note that the standards for the objective are not automatically derived from the standards of its corresponding Task Analysis component. In other words, the Task Analysis component’s standards are not carried over to the objective when the objective is created from that analysis component. The reasoning for this is that you may have different standards for actual task performance in the field than you do for training its associated objective.
See also the following Advisor topic: Establishing Standards of Performance
Status
Is this objective ready for presentation to the learner? Is it still in development? Is it currently unused? Select the status that best represents its standing.
VISION reports, as well as the VISION Learning Station (if applicable), may use the status to decide whether to present an objective. For example, a particular report might be programmed to present an objective only if its status is "Approved".
Note: Changes to the list of available statuses affect the current project only.
"Approved" Objectives
The objective's status must be "Approved" before it can be seen by learners in a lesson. If you are not sure what to do to put an objective into Approved status, review the items on the Objective Status Checklist.
Objective Status Checklist
•Objectives are "Approved" on the General page, on the Status menu.
•Tasks that are "Directly Linked" to an Objective must be Completed before an Objective can be Approved.
•Subordinate objectives do not need to be approved in order for their parent to be approved.
•Linked questions don't need to be Active unless you plan to use them in a course or test.
See Also
Developing Formal Objective Statements
See also the following Advisor topics:
