Home > Articles > Programming

Designing the Obvious, Part 4: Use Cases, Screenflows, and Wireframes

  • Print
  • + Share This
Okay, you know who wants the application and what they want it to do. Ready to start coding, right? Perhaps, but Robert Hoekman, Jr. has some suggestions about how to find problems in the design before it gets too expensive to fix.
Like this article? We recommend

Part 3 of this series talked about why and how to perform research on the people who will use your web products, in order to understand how they use the interfaces you produce. Once the preliminary research is done, it’s time for the really fun part. (Of course, user research can also be a lot of fun if you’re one of those rare geeks who enjoys talking to other people.) It’s time to come up with some designs. Part of this phase involves some writing, though, so don’t get your pencil out just yet.

Writing Use Cases

You may have heard the term use case thrown around in your office; if you’re a programmer, you probably even understand what it means. If you’re on the design side of things, you may be more familiar with the term scenario, used to refer to a description of an actual usage scenario for a piece of an application. Both use case and scenario really mean the same thing. Use cases can vary in detail from a vague description of a task to a step-by-step explanation of every last detail of the behavior of your new scratch-and-sniff greeting card tool. Whatever the case, it’s important to know why writing down these blurbs is so valuable.

This may sound a bit sick, but writing use cases is one of my favorite things to do. In somewhere between 5 and 30 minutes, typically, I can list the exact process for how an interaction will work once it’s built. This exercise invariably surfaces potential problems and really brings to light the assumptions I was making about a task prior to writing it out.

Just yesterday, in fact, I wrote a use case for a task that enables users to submit personal recommendations for products. To do this, I wrote out several steps that looked like this:

Submit a Recommendation

  1. User clicks "Write a recommendation" and a short form displays beneath the button.
  2. User completes the form.
  3. User clicks OK to submit the recommendation, and the form disappears.

Then I thought to myself, "That doesn’t sound right. If the form just disappears as soon as you click OK, that could look kind of awkward, and the user would have no idea whether the recommendation was submitted successfully." So I revised step 3, opting to keep the form visible after clicking OK, and displaying a message above the form to tell the user that the submission was successful.

At that point, I realized that there would have to be a way to "close" the form once it the user was done with it. So now the use case has a fourth step, in which the user clicks a Close button. But where does the Close button go? Should I make a new button and display it as part of the form? Nah—I’d rather make the "Write a recommendation" button a toggle. The "Write a recommendation" button can’t be used once the form is displayed, however, because it has nothing to display, so instead of disabling it and displaying another button for Close, why not reuse "Write a recommendation" in a new context? Once you click that button, its label and function could change to a Close button.

Fitts’ Law tells me that this is a good thing to do, because the easiest thing to click on your whole computer screen is the pixel where your mouse pointer currently rests. If I combine the two buttons, I’ve enabled the user to open and close the form without moving the mouse (should the user decide not to complete the form, that is).

Great, now I have a four-step use case that says the user will click the button, complete the form, click OK to submit the form, and click Close to make the form go away (optional). But what happens if the user doesn’t want to complete the form? Do I need a Cancel button? Not really, because the Close button would handle that functionality. So now I have a single button that has three purposes without any additional clutter, the form appears right in the page instead of sending the user to another page in a roundtrip process, and the whole interaction is "as simple as possible, but not simpler" (from a quote attributed to Albert Einstein).

Perfect. That’s my use case.

Wait.

The developer will want to know what happens if the user decides not to complete the form. To handle this issue, I added a quick exception to the use case. The final version looked like this:

Submit a Recommendation

  1. User clicks "Write a recommendation," and a short form displays beneath the button. The button toggles to say Close instead of "Write a recommendation."
  2. User completes the form.
  3. User clicks OK to submit the recommendation, and a success message appears above the form.
  4. User clicks Close to close the form.

Exceptions

3a User clicks Close, without completing the form.

The designation 3a indicates that the exception applies to step 3 in the use case. It means that if the user decides not to complete/submit the form, another workflow would take place, which is detailed in step 1 of exception 3a. Simple as that.

Use cases can get rather lengthy, of course, when detailing complicated interactions or a large set of interactions, but each use case will end up similar to this example.

Typical use cases don’t go into the details of which buttons appear where or anything that specific, but I find it incredibly useful to add these details—usually resulting in a perfectly acceptable spec, discussed later in this article—because the details give graphic designers and developers a more exact idea of how the interaction should look and work.

Adding details also forces me to think out whether the interaction is technically possible, and how simple or complex it will really be when it’s up and running. In this use case, it enabled me to find a way to consolidate three possible buttons into a single button with three purposes. (In the real version, I included information on the form itself, such as how the fields were labeled, how big they were, and all that jazz, but such details weren’t important for this example.)

My initial use case was making a big assumption about the interaction: that I could just display a simple form that drops into place, and call it a day. The developer who eventually built the thing would have made other assumptions, such as the assumption that the form should have two buttons: one that opens the form and one that submits the data. Ty from the web team would have built exactly what I said to build, as he understood it, and the interaction would have been all wrong.

Once Ty was done, I would have written a review of the interaction, explaining to Ty that it was all wrong, and Ty would have had to rework his code (rather substantially) to make the interaction right. And I might have left out another detail in the review. This process could have gone on for days, adding to Ty’s already frustrating existence as a programmer, increasing my stress level, and wasting many hours of expensive and valuable programming time.

By writing an effective use case at the start, I’ve avoided most of the pitfalls, and I did it in twenty minutes. The rather obvious secret is this: It’s far easier to change a sentence in a Word document than it is to rewrite code that performs a specific operation in an interactive system.

Get the picture? Write use cases before you write code. It’s the Law.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020