CSCI 672 – HUMAN COMPUTER INTERACTIONS

INSTRUCTOR : Dr.Bill Manaris

PROJECT : #2 WIMP User Interface – PHASE 4

DUE : 2001-04-24 (noon)

DEVELOPPERS:

Yang Henry
Paul Markiewicz   
Johan Chauvet

Certificate of Authenticity:

We verify that this deliverable is almost our own work.
For the #2, We used the "Introduction to Visual Basic 5.0 Programming Reference Notes". (http://www.dcs.napier.ac.uk/hci/VB50/HTML/menus.html)


  1. HIERARCHICAL TASK ANALYSIS + FEEDBACK (Phase 1 and 3)
  2. IDENTIFICATION AND ANALYZES OF THE UI METAPHORS (Phase 2)
  3. DESCRIPTION OF THE DESIGN RATIONALE (Phase 2)
  4. INTERACTION DIAGRAM OF WIMP (Phase 3)
  5. FINAL INTERACTION DIAGRAM OF WIMP (Phase 4)
  6. FINAL DESCRIPTION OF THE DESIGN RATIONALE (Phase 4)
  7. APPENDIX A: Evaluation comments received from Phase 1 (only 1 team)
  8. APPENDIX B: Evaluation comments received from Phase 2 (only 1 team)
  9. APPENDIX C: Evaluation comments received from Phase 3
  10. The Application The Application
  11. Project 2 - PHASE 2: project2-2.zip (3.5ko)
  12. Project 2 - PHASE 4: project2-4.zip (23.4ko)


**************************************************************************

1. IDENTIFICATION AND ANALYZES OF THE UI METAPHORS


Pull down menus are used extensively in Windows applications :

-*- The menu names are visible textual items on the menu bar, so the user can see the main functions of the software at all times.

-*- Menu titles, or menu items (such as Open on the File menu) is unambiguous. The user knows instantly what will happen once he will click over the option.

-*- The menu bar takes up very little space on the screen.

-*- The menu options are also available by means of access keys (holding down the Ctrl key then typing underlined letters of the menu title and menu item required, so Ctrl+X for ‘Cut’ on the ‘Edit’ menu).

-*- Functions are grouped together to form a set of menu items that are related, this helps users to know where to look for facilities.

The main advantage and why we have chosen a Pull down menu based is that an effort has been made to standardise the naming and ordering of menu items across applications (especially Microsoft), so that packages are easier to learn and use.

We used the "Introduction to Visual Basic 5.0 Programming Reference Notes". (http://www.dcs.napier.ac.uk/hci/VB50/HTML/menus.html)

MENU



**************************************************************************

2. DESCRIPTION OF THE DESIGN RATIONALE


General view

File menu
New :
To run the application with an empty log file.

Open :
To open an existing log file.

Save :
To save the existing log file.

Exit :
To stop the application and to exit the application (need to save before if necessary).

Edit menu
Cut :
To move Selection into Paste Buffer.

Copy :
To copy Selection into Paste Buffer.

Paste :
To paste Selection from Paste Buffer.

Interact
Clear :
To clear pre-existing event.

Start collection :
To start the collection.

Terminate collection :
To end the collection.

MENU



**************************************************************************

3. APPENDIX A : Evaluation comments received from Phase 1

 

DEVELOPPERS: 

Barbara Ball

Dmytro Kantala



"Task 0: should be more abstract, user-centered"
ANSWER: it has been changed to "Construct Keyboard and Mouse Event Log".

item#2) "Plan 0: Doesn't Task 2 have to come befor Task 3?"
ANSWER: Yes, BUT... That IS what "2-3" means... repeat as a set 2 then 3...

item#3) "Task 2.2: How can you Browse a new file?"
ANSWER: Good question. The "browse" part is how the directory portion of
the file is specified, Also, we might want to CLOBBER another file that
isn't a logFile, ... mostly the fat that we are do not key-in the directory
information.

item#4) "Task 3.1: Shouldn't this be under 3.5 (Edit the Event Log File)?".
ANSWER: I suppose it could be, but it doesn't have to be.

item#5) "Plan 3: Shouldn't you have to do 3.2 before 3.3? - this is probably
what you meant, we just weren't sure"
ANSWER: Yup, they got it now; that is what the notation (3.2 - 3.3) means.

item#6) "Plan 3.5: Shouldn't you have to do 3.5.4 before 3.5.5 or 3.5.6?"
ANSWER: There expectations common. It wouldn't have to be though. I think
its perfectly valid that it 3.5.5 would simply clear the Paste Buffer and
that 3.5.6 would also just clear the buffer.

item#7) "Task 3.5.1: Shouldn't this be done before 3.5.2 as well as 3.5.3
and possibly 3.5.4?"
ANSWER: That would be up to the user; it is plauseable to happen to be "at
the right spot" and go directly to the insert text, delete text phase.
Consider the opposite: I start editing, I happen to be at the right spot,
would I HAVE to move somewhere then move back? (nope). Task 3.5.4, as a
task WOULD include the mouse down, move, etc. By doing those events it
does not "preclude" the notion that 3.5.1 is being performed also (or even
that the insertion pointer movement is part of this action).

MENU

**************************************************************************

3. APPENDIX B : Evaluation comments received from Phase 2

 

DEVELOPPERS: 

Chris Cordes

David Mendelsohn



1) Change the Box Title from “Project 2” to something indicative of the application’s functionality.
2) There is nothing in the menu structure or on the screen that indicates functionality (i.e. the “Interact” menu does not afford the users what the tasks are supposed to be performed).
3) Hiding the Rich Text Box follows suit with the comments in #2.
4) The use of standardized Windows menus is a good idea and helps with usability.

Overall Comments: If the paradigm is to resemble a notepad, then the program should open with a “blank sheet”. Also, in our experience, users are more open to programs with shortcut/toolbars/buttons when operating software, because they don’t like to remember lists of commands.

We do generally agree with the overall layout of the application.

MENU

**************************************************************************

3. APPENDIX C : Evaluation comments received from Phase 3

Also included in the part #1(HIERARCHICAL TASK ANALYSIS + FEEDBACK) with another team's evaluation.

 

Modifications according to the evaluation by Dr. Manaris: 

Item#1: What about "New"?
Answer: A "New" menu is added as an option when user starts.

Item#2: What about "Print"?
Answer: A "Print" menu could be added as an option when file is open.

Item#3: What if file is not saved (when user wants to exit)?
Answer: When a file is not saved, the "Exit" menu is disabled.

Item#4: What if user exits from one of these states?
Answer: The "Exit" option is disabled for the File Selection and Log Collection State. It goes to the Warning State from File Interaction State when a log file is not saved.

Item#5: Missing part of the interaction.
Answer: A "Warning State" is added to transit from the File Interaction State.

Item#6: Where is the Certificate of Authenticity?
Answer: It's added at this time.

MENU

**************************************************************************

 

THE APPLICATION


Here are links to the source code files: "Presentation.bas", "Translation.bas", and "Application.bas" (each as TXT files).

"EventLogger.exe" (the EXECUTABLE itself).

"Project2-4.zip" (the "zipped-up" VB project files).



MENU