CSCI 499 Unit #3

Unit 3 Examples

Error handling examples

• Nice format Disk Error has especially helpful suggestions
• #3 is funny Always use caution with humor, but I enjoyed this one
• Nice css Keeps error close to issue

Many of the Subaru rewrites were good. Here's one that seemed to hit a good balance of persuasion (necessary for sales) and concise wording: Subaru rewrite.

Purpose

• Understand why peripheral vision limitations should be considered in application layouts
• Practice minimizing the language used in your program (because users don't like to read!)

Chapter 5 - Reading Assignment and Exercise

Read:

• Mind in Mind Chapter 5
• https://conversionxl.com/blog/error-messages/

Create a Chapter Summary for this material.

Exercise

Assume you are writing a cloud-based app to allow users to store, share and search documents. Possible error situations include:

• The username is not valid
• A file is formatted incorrectly
• Another user has locked a file
• The disk the user wants to write to is full

Your task: Design error messages/dialogs for each of these that are helpful and avoid "geek speak." Make assumptions as needed (e.g., about what file types are allowed, how the system operates, etc.). The goal is to be as clear, concise, and helpful as possible.

Specific requirements (see figure 1):

• Include all four messages in one html file
• Prior to each message, state the situation (i.e., copy the situation from the list above)
• The messages can be displayed automatically when the page loads, as in figure 1. OR you can have buttons to press (one per situation) that display a pop-up error. Bottom line: it should be quick for me to run your file and see the messages

Hint: Our focus is primarily on wording, so I used a simple alert box as described by w3schools: here. Feel free to use other techniques as you see fit (but not just a JS alert).

Chapter 6 - Reading Assignment and Exercise

Read:

• Mind in Mind Chapter 6
• https://www.davidsanson.com/handouts/omit_needless_words.html
• https://writingcenterunderground.wordpress.com/2015/11/18/tighten-up-omit-needless-words-phrases-from-your-writing/
• https://blog.codinghorror.com/happy-talk-must-die/

Exercise/Chapter Questions

For this exercise you will create one document that contains three separate critiques.

#1 Review: https://support.apple.com/repair. Can you identify any happy talk? Are there sentences that are similar to happy talk, but may serve a purpose?

#2 Review: https://booksy.com/en-us/s/nail-salon. Critique these. What do you like? Are there any suggestions you’d make for changes?

#3 Review this website, starting from Subaru Dealership Near Denver, CO: https://www.autonationsubaruwest.com/.

• In your document, list any issues that relate to problems described in the text or other sources.
• Now create a web page with revised wording for just the paragraphs from Subaru Dealership Near Denver, CO through (including) 2019 Subaru Lease Specials and Finance Options. We are focused on wording here, so no css or images are needed. As you make this more concise, be sure you don't remove important information.

NOTE: if there's another site you'd prefer to critique and revise, that's fine. Just include a link to the original site so I can see what changes you've made.

Submit

Zip your html and css from chapter 5, the pdf from chapter 6, and the html from chapter 6 into one zip file named [YourLastName]Unit3.zip.

Evaluation

The error messages will be evaluated based on whether I can imagine being in that situation and appreciating your error message because it's clear how to proceed. The chapter 6 critiques will be evaluated based on being thoughtful (#1 and #2) or clearly more concise (#3) they are.

Separate grades will be given for each chapter.