1. Content Management System 213 Project 4-26-01 Peter Roessler, Dhea Maloney, Chris Marin, Chan Jean Lee

2. Content Management System Overview System for managing text files (documents) style sheet files graphic files System can manage the above files for three different types of web sites Basic Site – called the HTML site Wireless Site- called the WAP site Animated Site – called the Flash site You can combine style sheet, graphics, and document files and then templates are used to create web pages from these files. Users are assigned rights in the system so they have access to different parts of the system

3. Overview of Heuristic results Lack of metadata associated with documents Author, date last modified, etc. Potential to have files accidentally overwritten Lack of ability to search Lack of Feedback Users can’t see previews of their work in the system Lack of escapes other then option to log out. Lack of guidance through the work flow in the system Poor error messages

4. Changes based on Heuristic Put a short description of the system on the login page and put instructions on every page Provide more guidance in the system Put in a preview section so users can see how changes will look Provides feedback Provide last author, last update, and category information for documents Carry metadata with object Tell users which documents are linked to a style sheet Provides feedback Tell users which documents are linked to a graphic Provides feedback

5. Continued Changes Based on Heuristic Added cancel button and go back buttons Provides escapes within the system Other smaller changes Editors console to verification console Fixed the inconsistent buttons/links Removed the numbering in places where there weren’t steps Removed parts of Ezedit to simplify

6. Things we didn’t have time to fix Add help and documentation-include flow chart Add search/browse Fix error messages Fix issue of overwrite Deal with issue of Verifiers having to go to the Verification console to make their own documents go live Add a list of documents that will be affected by a style sheet or graphic deletion before the user presses the delete button Additional unwanted features in Ezedit

7. Measures for Pilot Usability Test Navigation Added go back and cancel buttons Instructions clear. Added instructions to each page Terminology clear We used terms in our instructions Flow of action on the screen follows the users conceptual model and work flow. Appropriate Feedback Added preview option to document section

8. Overview of Results of Usability Test Navigation needs improvement Button names need to be more descriptive Need titles for each page Go Back/Cancel buttons were useful Instructions aren’t clear We learned about several places that need work Did find that the instructions helped Terminology We learned that some of the terms in the instructions aren’t clear Changing the term background to graphics worked well

9. Continue Overview of Usability Results Work Flow Separating style sheet and graphic selection from text entry was a problem Notification to verifier that something is waiting Last authors name in verification console Feedback Preview with documents was great Missing preview for style sheet changes Missing preview for graphics

10. Changes Based on Usability Test Navigation Changed names on buttons to be more descriptive Added titles to each page Feedback Preview buttons for style sheets and graphics Work Flow Added information about who authored a document in verification console Style sheet selection and graphic selection on same page as document entry Tell users an e-mail sent to boss about document Terminology/Instructions Fixed instructions

11. Continued Changes Based on Usability Changes left over from the Heuristics See list of linked documents to graphics and style sheets before deletion Added an accelerator button for editors so they can verify without going to verification console Provided Search Provided Help and Documentation Provided Better Error Messages Provided Flow Chart Dealt with Overwrite Problem Removed Ezedit

12. Demo

13. What needs to be finished for third prototype Many of the changes in our demo aren’t actually implemented. Search Overwrite protection Plan to try to make system as interactive as possible Go through our system with a fine tooth comb to make sure our changes are consistent and instructions match well Bugs to fix from usability test Discuss the issue of document naming standards

14. Our Formal Usability Test Overview CMS contains a large quantity of documents. We want to provide users with a fast and easy way to find a document. This experiment is designed to determine the easiest and fastest way to find a certain document in the CMS among three alternatives. Hypotheses Showing list of documents of a chosen category in one page will reduce number of click and search time. Showing list of documents that were recently modified or added in one page will reduce number of click and search time.

15. Way of Displaying Doc list 1. Separated in two pages (Current way of finding a document)

16. Documents list in this category Way of Displaying Doc list 2. Together in one page (Category Selection + Doc Selection)

17. Recent modified Doc list Press/Press7 AboutUs/Picnic Press/Press100 Press/Press139 Way of Displaying Doc list 3. Recent list (Along with Document Category Selection)

18. Variables Dependent Variables Number of clicks Search time Independent Variables #One between subjects factor Ways of displaying document list a. Separate: Display the list of document of the selected category in the next page of category selection page, when a user select a category and submit (current way). b. Together: Display the list of document of the selected category in the same page next to the category list, when a user select a category and submit. c. Recent list: Display 10 documents modified or added most recently the same page with category selection box. # Two within-subjects factor The author of the document the user searches a. Himself/Herself b. Other person The last day a document is modified or added by the same user a. A document that was modified 1 week ago. b. A document that was modified 2 weeks ago. c. A document that was modified 3 weeks ago.

19. Blocking and Repetition SeparateTogetherRecent 1weeks2weeks3weeks 2weeks3weeks1weeks 3weeks1weeks2weeks 12people In each 12 block, the order of the document’s author (Himself vs. Other) will differ for each participant. HimselfOther Himself

20. The End Questions Comments