<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>https://wiki.kram.nz/index.php?action=history&amp;feed=atom&amp;title=SE401%3A33%3ACognitive_Dimensions</id>
	<title>SE401:33:Cognitive Dimensions - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.kram.nz/index.php?action=history&amp;feed=atom&amp;title=SE401%3A33%3ACognitive_Dimensions"/>
	<link rel="alternate" type="text/html" href="https://wiki.kram.nz/index.php?title=SE401:33:Cognitive_Dimensions&amp;action=history"/>
	<updated>2026-04-30T01:25:50Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.3</generator>
	<entry>
		<id>https://wiki.kram.nz/index.php?title=SE401:33:Cognitive_Dimensions&amp;diff=82&amp;oldid=prev</id>
		<title>Mark: New page: ==&lt;font color=#00267c&gt;Cognitive Dimensions Framework&lt;/font&gt;== Analysis of our application using the cognitive dimension framework   :&#039;&#039; The dimensions can be used to evaluate the usability...</title>
		<link rel="alternate" type="text/html" href="https://wiki.kram.nz/index.php?title=SE401:33:Cognitive_Dimensions&amp;diff=82&amp;oldid=prev"/>
		<updated>2008-02-15T20:06:56Z</updated>

		<summary type="html">&lt;p&gt;New page: ==&amp;lt;font color=#00267c&amp;gt;Cognitive Dimensions Framework&amp;lt;/font&amp;gt;== Analysis of our application using the cognitive dimension framework   :&amp;#039;&amp;#039; The dimensions can be used to evaluate the usability...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;==&amp;lt;font color=#00267c&amp;gt;Cognitive Dimensions Framework&amp;lt;/font&amp;gt;==&lt;br /&gt;
Analysis of our application using the cognitive dimension framework&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:&amp;#039;&amp;#039; The dimensions can be used to evaluate the usability of an existing interface, or as heuristics to guide the design of a new one.&amp;#039;&amp;#039;&lt;br /&gt;
:&amp;#039;&amp;#039;They provide a common vocabulary for discussing many factors in interface design.&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Abstraction gradient===&lt;br /&gt;
:&amp;#039;&amp;#039;What are the minimum and maximum levels of abstraction exposed by the notation? Can details be encapsulated?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*Mashup elements are a low level abstraction&lt;br /&gt;
::- they cannot be further broken up logically&lt;br /&gt;
:*WYSIWYG editor allows for low level abstractions&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Closeness of mapping===&lt;br /&gt;
:&amp;#039;&amp;#039;How closely does the notation correspond to the problem world?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*WYSIWYG editor view simulates exactly what the mashup will look like&lt;br /&gt;
::- This is a high closeness of mapping&lt;br /&gt;
::- Form editing uses common Internet terms and should be known by novice users&lt;br /&gt;
:*Application looks like other Windows applications &lt;br /&gt;
::- Provides familiarity for users&lt;br /&gt;
::- Same icons as programs like MS Word&lt;br /&gt;
::- Mashup element icons use official icons for quick recognition&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Consistency===&lt;br /&gt;
:&amp;#039;&amp;#039;After part of the notation has been learned, how much of the rest can be successfully guessed?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*Mashup elements all follow the same input structure&lt;br /&gt;
::- Once form input notation is learned, most can be guessed&lt;br /&gt;
::- FormattingData is a little more complicated and may be harder to guess&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Diffuseness===&lt;br /&gt;
:&amp;#039;&amp;#039;How many symbols or how much space does the notation require to produce a certain result or express a meaning?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*One symbol (placeholder image) is needed to represent each mashup element&lt;br /&gt;
::- The sidebar provides another view (textural)&lt;br /&gt;
::- Both views are kept consistent&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Error-proneness===&lt;br /&gt;
:&amp;#039;&amp;#039;Does the notation induce mistakes in the user?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*The user can edit the source code if they wish &lt;br /&gt;
::- Affects consistency&lt;br /&gt;
::- May break mashup&lt;br /&gt;
:*Certain combinations of mashup element and basic html functions (align etc) can create problems&lt;br /&gt;
::- Problem with code base not our part of the tool (FUTURE WORK)&lt;br /&gt;
:*Form creation/editing for mashup elements and form error checking eliminates most of the possible user errors&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Hard mental operations===&lt;br /&gt;
:&amp;#039;&amp;#039;How much hard mental processing lies at the notational level, rather than at the semantic level?&amp;#039;&amp;#039;&lt;br /&gt;
:&amp;#039;&amp;#039;Are there places where the user needs to resort to fingers or penciled annotation to keep track of what is happening?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*There are no hard mental operations&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Hidden dependencies===&lt;br /&gt;
:&amp;#039;&amp;#039;Are dependencies between entities in the notation visible or hidden? Is every dependency indicated in both directions? &amp;#039;&amp;#039;&lt;br /&gt;
:&amp;#039;&amp;#039;Does a change in one area of the notation lead to unexpected side-effects?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*Editing an RSS feed will only update the RSS feed object&lt;br /&gt;
::- Any &amp;lt;strike&amp;gt;Google/Yahoo Maps&amp;lt;/strike&amp;gt; or FormattedData using the RSS Feed will not update&lt;br /&gt;
:*RSS Feeds are not shown in the WYSIWYG editor view&lt;br /&gt;
::- User can accidentally delete the hidden tags for the RSS code (Not a big deal because code is only for show)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Premature commitment===&lt;br /&gt;
:&amp;#039;&amp;#039;Are there strong constraints on the order with which tasks must be accomplished?&amp;#039;&amp;#039;&lt;br /&gt;
:&amp;#039;&amp;#039;Are there decisions that must be made before all the necessary information is available? Can those decisions be reversed or corrected later?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*RSS feeds must be loaded before creating an object which will use it&lt;br /&gt;
::- Google/Yahoo maps can be made with no RSS and changed later&lt;br /&gt;
::- FormattedData needs an existing RSS feed&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Progressive evaluation===&lt;br /&gt;
:&amp;#039;&amp;#039;How easy is it to evaluate and obtain feedback on an incomplete solution?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*HTML preview allows the user to see a rough estimate of the incomplete page &lt;br /&gt;
::- However to actually test the page the user will need to upload the document to their site&lt;br /&gt;
::- Google Maps/Yahoo Maps/YouTube only provide placeholders not actual result&lt;br /&gt;
::- RSS Feed data can be viewed in the source code for more advanced users&lt;br /&gt;
&lt;br /&gt;
:*No dynamic viewing of document is available in our application&lt;br /&gt;
::- JavaScript is not supported&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Role-expressiveness===&lt;br /&gt;
:&amp;#039;&amp;#039;How obvious is the role of each component of the notation in the solution as a whole?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*RSS Feeds purpose may be not obvious&lt;br /&gt;
::- The user may not know why you would want this &lt;br /&gt;
::- The user may not know what a feed is&lt;br /&gt;
::- The user may not know how to make one or obtain one from an external source&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Secondary notation===&lt;br /&gt;
:&amp;#039;&amp;#039;Can the notation carry extra information by means not related to syntax, such as layout, colour, or other cues?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*No secondary notation allowed&lt;br /&gt;
::- HTML comments are not yet supported&lt;br /&gt;
::- More advanced users can manually add comments in the source code view&lt;br /&gt;
::- Layout/Colour are HTML syntax&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Viscosity===&lt;br /&gt;
:&amp;#039;&amp;#039;Are there inherent barriers to change in the notation?&amp;#039;&amp;#039;&lt;br /&gt;
:&amp;#039;&amp;#039;How much effort is required to make a change?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*Mashup elements are easy to edit&lt;br /&gt;
::- Dialog boxes provided for editing&lt;br /&gt;
&lt;br /&gt;
:*HTML preview allows the user to add new content at any position and delete any content&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Visibility===&lt;br /&gt;
:&amp;#039;&amp;#039;How readily can required parts of the notation be identified, accessed and made visible?&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
:*Google/Yahoo Maps do not show location markers for rss addresses&lt;br /&gt;
::- User must upload document and try manually to see result&lt;br /&gt;
::- More advanced users can view the address data embeded in the JavaScript using the source code view &lt;br /&gt;
&lt;br /&gt;
:*YouTube videos cannot be previewed&lt;br /&gt;
&lt;br /&gt;
:*RSS feed data cannot be viewed&lt;br /&gt;
::- Data is visible in source code view when combined with a Map - more advanced users only&lt;br /&gt;
&lt;br /&gt;
:*Formatting RSS data does not show the resulting data&lt;br /&gt;
::- &amp;lt;font color=red&amp;gt;Results are temporarily printed to the console&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*Sidebar allows the user to quickly view mashup elements in use in the current document &lt;br /&gt;
::- User can quickly access the edit/delete options for any mashup element using this sidebar&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[SE401:33:Mashup_Creation_Tool|◄ Back]]&lt;/div&gt;</summary>
		<author><name>Mark</name></author>
	</entry>
</feed>