View this PageEdit this Page (locked)Attachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Rock Marinov

Coweb Assignment #1

Problem 1: CRC Cards for Online Ticketing System.

Scenarios
1. Bob goes to the online ticketing website. He selects a ticket by searching for a specific show. He checks out, fills in his personal information, and the tickets are sent in the mail.

2. Bob accesses the online ticketing website, and selects several tickets by searching for a specific show. He gets several tickets that are close to one another, and then checks out and fills in personal information. The tickets are in the mail.

3. An owner logs into the ticketing system. He decides to collect the money from a venue. He enteres the bank account where he wants the money deposited. The money is automatically transferred to the owners account.

4. An owner logs into the ticketing system. He decides to add a new show to the ticketing system. He fills in important information for the show, including place, price of tickets, date, and people involved in the show. The instance of the show is then released to the public site for users to search and book tickets.

Uploaded Image: ticketingSiteCard.gif
Uploaded Image: orderCard.gif
Uploaded Image: transactionCard.gif
Uploaded Image: userCard.gif
Uploaded Image: ticketCard.gif


Coweb Assignment #3

Usability (2 Points)
You've learned about three usability evaluation techniques in this class: heuristic evaluation, cognitive walkthrough, and observing users. Compare and contrast two of these. What are the strengths of each approach? What are the weaknesses? When are they appropriate to use? Why would you choose one over the other?

Both the heuristic evaluation and cognitive walkthrough have their own advantages and disadvantages. The heuristic evaluation uses the experience and previous knowledge of experts to review and evaluate a program, thus providing a solid backing for any bugs that are found in the software. Any reviewer can site specific rules or regulations when determining if a program is sufficiently usable or not using the H.E. approach. H.E. is also reasonably fast to conduct when considering the different methods for evaluating a program for usability. The downside to H.E. is that Nielson’s methods have been questioned, and there are alternative and conflicting rules that exist, which may cause issues upon review. The Cognitive Walkthrough approach puts the designer in the user’s shoes, and thus allows the designer or reviewer to evaluate the software or program from a user’s perspective. The Cognitive Walkthrough also stresses the sequence of tasks that are necessary to perform a function. A couple of disadvantages of C.W. are that it may not isolate all usability problems of the program, and it may be somewhat tedious to review using this technique. Either one is appropriate to use on a program, depending on the reviewer’s preferences and setup of the program. H.E. could possibly be used above C.W. in order to give a more complete picture of usability issues.

Language Features (2 Points)
Squeak is perhaps the least well documented programming language you will ever use; however, Smalltalk and the Morphic GUI compensate for this by being pokable (easy to explore). There are many language features and tools for exploring Squeak. For four of these, name them, describe how you use them, and explain why they are useful.

System Browser
Method Finder
Implementers Of…
Senders Of…

1)System Browser – The browser contains every class that could be used in the project, free for a programmer to search through and explore. Each class is placed in a category, to make for a easier searching.
2)Method Finder – The method finder is an option in the menu that allows users to find an implementation of a certain method if they know the name of the method. This could be useful in determining return types and parameters.
3)Implementors Of…. – This option allows programmers to find the classes that implement specified methods. This functionality helps when a programmer wishes to debug code and determine where an error is occurring.
4)Senders Of… – This option is similar to implementers of, except that it finds the classes that call a specified method. It is also useful in debugging code in a program.

Links to this Page