General Techniques - Making the functionality of content predictable.

Submitter's Name: Clayton Lewis
Submitter's Email: clayton.lewis@colorado.edu

Technique ID: UNKNOWN
Short Name: Making the functionality of content predictable.
Technique Category: General Techniques
Guideline Reference: consistent-behavior
Success Criterion Reference: UNKNOWN

Applicability:
Use in all cases

UA Issues:
none

Description:
The objective of this technique is to make the functionality of content predictable. The method is to use familiar, commonly encountered presentations of functionality, and avoid novel, rarely seen methods.


No example 1 header was submitted!
No example 1 description was submitted!
No example 2 header was submitted!
No example 2 description was submitted!
No resource 1 title submitted!
No resource 1 URI submitted!
No resource 2 title submitted!
No resource 2 URI submitted!
No related techniques were submitted!
No test procedure was submitted!
No expected result was submitted!
No test file 1 was submitted!
No test file 1 pass/fail was submitted!
No test file 2 was submitted!
No test file 2 pass/fail was submitted!
No additional notes were submitted!


------------------------------------------------

<technique id="UNKNOWN">
<short-name>Making the functionality of content predictable.</short-name>
<applies-to>
<guideline idref="consistent-behavior" />
<success-criterion idref="UNKNOWN" />
</applies-to>

<applicability>
Use in all cases
</applicability>
<ua_issues>
none
</ua_issues>
<description>
The objective of this technique is to make the functionality of content predictable. The method is to use familiar, commonly encountered presentations of functionality, and avoid novel, rarely seen methods.
</description>

<examples>
<ex_head_1>

</ex_head_1>
<ex_desc_1>

</ex_desc_1>
<ex_head_2>

</ex_head_2>
<ex_desc_2>

</ex_desc_2>
</examples>

<resources>
<resources_title1>

</resources_title1>
<resource_uri1>

</resource_uri1>
<resources_title2>

</resources_title2>
<resource_uri2>

</resource_uri2>
</resources>

<related_techniques>
</related_techniques>

<tests>
<procedure>

</procedure>
<expected_result>

</expected_result>
<test_file_1>

</test_file_1>
<pass_fail_1>

</pass_fail_1>
<test_file_2>

</test_file_2>
<pass_fail_2>

</pass_fail_2>
</tests>

</technique>

Additional Notes:

Received on Saturday, 17 March 2007 16:07:24 UTC