Scrutinizing the world around you, work in teams of two to identify interesting examples of forcing functions. Use images to document two examples in each of the first two categories, and one example in the last category:
Appropriate and Satisfactory |
User Acceptance |
Image of Example |
|
Examples 1 & 2 |
(YES) | (Good) | |
Examples 3 &4 |
(Inappropriately heavy handed (strict); not very satisfactory) |
(Poor) | |
Example 5 |
(Absent or too relaxed (weak) and not very satisfactory) | (Poor) |
Chosen examples may
be very simple (mechanical) mechanisms, or more sophisticated combinations
of technologies that inhibit a user from providing certain
undesirably actions or input parameters by making it difficult to respone in that manner.
In each case state the presumed purpose of your example, and discuss how
effectively the forcing function achieves it. For two of your examples that are
not entirely satisfactory, describe the shortcomings and how you would
modify the forcing function to improve its performance, possibly overcoming the
described deficiency.
By the project due date, turn in one .pdf file
to cs5540 assign4. Be sure to put the names and logins of
both team members on the cover page of the presentation
< sample cover page >. Indicate the
team member's name who provided each set of examples, and the improvements.
The team should come up with 5 examples and, after discussing them, each team member should provide individual separated comments on those 5 items. That is, after discussing ideas within the team, each team member should have an individual response section giving 5 examples plus 2 improvement discussions.
Only hand-in a pdf verson, once under either team member's name.
Please apply the below template to generate the filename and
faithfully conform to the following handin convention:
>handin |
cs5540 |
assign4 |
ForcingFns.Lastname1.Lastname2.pdf |
