CS295J/Research proposal (draft 2) - Revision history

Adam Darlow: /* Preliminary Results */

2009-08-21T19:39:48Z

Preliminary Results

@@ Line 125: / Line 125: @@
 ====IV.  '''Discussion'''====
 These results qunatiatively support our hypothesis that there is no clearly dominant set of metawork strategies employed by information workers.  This highly fragemented landscape is surprising, even though most information workers work in a similar environment - at a desk, on the phone, in meetings - and with the same types of tools - computers, pens, paper, etc.  We believe that this suggests that there are complex tradeoffs between these methods and that no single method is sufficient.  We therefore believe that users will be better supported with a new set of software-based metawork tools.
 = [Criticisms] =

David Laidlaw: /* Specific Aims and Contributions (to be separated later) */

2009-04-28T19:30:50Z

Specific Aims and Contributions (to be separated later)

Show changes

Ian Spector: /* Integration into the Design Process */

2009-04-28T17:18:48Z

Integration into the Design Process

← Older revision		Revision as of 17:18, 28 April 2009
Line 522:		Line 522:

	This can be broken down further into just information architecture design followed by physical design and testing.		This can be broken down further into just information architecture design followed by physical design and testing.

			As far as this proposal is concerned in the context of interface design, the goal of our proposal is to improve what is involved with later end of the middle two portions: logical and physical design. Prior to feeding an interface to the system we are proposing, designers should have already created a baseline model for review that should exhibit the majority, if not all, of the functionality listed in the interface requirements. Once this initial interface has been created, our system will aid in rapidly iterating through the physical design process. The ultimate end products are then subject to human usability testing.

	= Preliminary Results =		= Preliminary Results =

Ian Spector: /* Integration into the Design Process */

2009-04-28T16:59:38Z

Integration into the Design Process

← Older revision		Revision as of 16:59, 28 April 2009
Line 506:		Line 506:
	* Owner: [[User:Ian Spector \| Ian Spector]]		* Owner: [[User:Ian Spector \| Ian Spector]]

	''This section outlines the process of designing an ~~HCI~~ interface and at what stages our proposal fits in and how.''		''This section outlines the process of designing an interface and at what stages our proposal fits in and how.''

	The interface design process is critical to the creation of a quality end product. The process of creating an interface can also be used as a model for analyzing a finished one.		The interface design process is critical to the creation of a quality end product. The process of creating an interface can also be used as a model for analyzing a finished one.

	There are a number of different philosophies on how to best design software and in turn, interface. Currently, agile development using an incremental process such as Scrum has become a well known procedure.		There are a number of different philosophies on how to best design software and in turn, interface. Currently, agile development using an incremental process such as [http://en.wikipedia.org/wiki/SCRUM Scrum] has become a well known and generally practiced procedure.

	The steps to create interfaces varies significantly from text to text, although the [http://http://cfg.cit.cornell.edu/design/process.html Common Front Group at Cornell] has succinctly been able to reduce this variety into six simple steps:		The steps to create interfaces varies significantly from text to text, although the [http://http://cfg.cit.cornell.edu/design/process.html Common Front Group at Cornell] has succinctly been able to reduce this variety into six simple steps:

Ian Spector: /* Integration into the Design Process */

2009-04-28T16:58:30Z

Integration into the Design Process

← Older revision		Revision as of 16:58, 28 April 2009
Line 507:		Line 507:

	''This section outlines the process of designing an HCI interface and at what stages our proposal fits in and how.''		''This section outlines the process of designing an HCI interface and at what stages our proposal fits in and how.''

			The interface design process is critical to the creation of a quality end product. The process of creating an interface can also be used as a model for analyzing a finished one.

			There are a number of different philosophies on how to best design software and in turn, interface. Currently, agile development using an incremental process such as Scrum has become a well known procedure.

			The steps to create interfaces varies significantly from text to text, although the [http://http://cfg.cit.cornell.edu/design/process.html Common Front Group at Cornell] has succinctly been able to reduce this variety into six simple steps:

			*Requirement Sketching
			*Conceptual Design
			*Logical Design
			*Physical Design
			*Construction
			*Usability Testing

			This can be broken down further into just information architecture design followed by physical design and testing.

	= Preliminary Results =		= Preliminary Results =

Ian Spector: /* Background / Related Work */

2009-04-28T16:58:11Z

Background / Related Work

@@ Line 85: / Line 85: @@
 **Disadvantages
 ***Lack of formalism hinders translation of theory into scripting language
 = Specific Aims and Contributions (to be separated later) =

Ian Spector: /* Sample Modules */

2009-04-28T16:55:58Z

Sample Modules

@@ Line 498: / Line 498: @@
 '''Outputs'''
 * Learning curve
 == Integration into the Design Process ==

Ian Spector: /* Background / Related Work */

2009-04-28T16:34:17Z

Background / Related Work

@@ Line 85: / Line 85: @@
 **Disadvantages
 ***Lack of formalism hinders translation of theory into scripting language
 = Specific Aims and Contributions (to be separated later) =

Eric Sodomka: /* Contributions */

2009-04-28T16:06:49Z

Contributions

← Older revision		Revision as of 16:06, 28 April 2009
Line 218:		Line 218:
	==== Contributions ====		==== Contributions ====

	* '''Create a framework that provides better interface evaluations than currently existing techniques, and a module weighting system that provides better evaluations than any of its ~~individual~~ modules.'''		* '''Create a framework that provides better interface evaluations than currently existing techniques, and a module weighting system that provides better evaluations than any of its modules taken in isolation.'''

	* Demonstrate by running user studies and comparing this performance to expected performance, as given by the following interface evaluation methods:		* Demonstrate by running user studies and comparing this performance to expected performance, as given by the following interface evaluation methods:

Eric Sodomka: /* Contributions */

2009-04-28T16:06:29Z

Contributions

← Older revision		Revision as of 16:06, 28 April 2009
Line 218:		Line 218:
	==== Contributions ====		==== Contributions ====

	* '''Create a framework that provides better interface evaluations than any of its individual modules.'''		* '''Create a framework that provides better interface evaluations than currently existing techniques, and a module weighting system that provides better evaluations than any of its individual modules.'''

	* Demonstrate by running user studies and comparing this performance to expected performance, as given by the following interface evaluation methods:		* Demonstrate by running user studies and comparing this performance to expected performance, as given by the following interface evaluation methods: