Summary: Putting It All Together - Foundations for Designing User-Centered Systems - page 399

A short, easy to read technical report is available online that lays out a tax-
onomy of system development risks and a method to perform a risk analysis:

Carr, M., Konda, S., Monarch, I., Ulrich, C., & Walker, C. (1993). Taxonomy-Based Risk
Identification (Tech. Report No. CMU/SEI-93-TR-6, ADA266992). Pittsburgh, PA:

Software Engineering Institute, Carnegie-Mellon University.

14.7 Exercises

14.1 Consider a smartphone, either a specific one or a composite one, or a simple
cell phone. Note all the limitations that will preclude users from performing
well with it. Organize these by the ABCS framework.
14.2 Choose an existing interface. Note the tasks that users will want to use it for.
Note the types of users and their characteristics. Run two small studies
examining how well your theory of use fits the data. These studies could be
to find out what tasks users really do, how well they do it (time and errors,
and strategies), or characteristics of the users.
14.3 Choose an interface or system to create, such as a new application for a
smartphone, such as a game, or book reader. Note what risks there are in
developing such a system, with particular attention paid to the technical risks
and those related to the user. Prioritize them. If you had 100 h, how would
you allocate that time to reduce these risks?
14.4 Go back and read the Appendix on the Kegworth air accident again. Read the
supplementary material referenced (e.g., the AAIB report) or other reports
you can find. Identify four more factors (events, processes, or mistakes) that
can be considered as causes of the accident. Describe how these things could
have been avoided or ameliorated. Address the question of whether it was
'pilot error' that caused that plane to crash.

References

Anderson, J. R. (2007). How can the human mind exist in the physical universe? New York, NY:
Oxford University Press.
Barnard P. J. (1987). Cognitive resources and the learning of human-computer dialogues. In
J. M. Carroll (Ed.), Interfacing thought: Cognitive aspects of human-computer interaction
(pp. 112-158). Cambridge, MA: MIT Press.
Baxter, G., Besnard, D., & Riley, D. (2007). Cognitive mismatches in the cockpit: Will they ever
be a thing of the past? Applied Ergonomics, 38, 417-423.
Boehm, B. (2008). Making a difference in the software century. IEEE Computer,41(3), 32-38.
Boehm, B., & Hansen, W. (2001). The spiral model as a tool for evolutionary acquisition.
Crosstalk: The Journal of Defense Software Engineering, 14(5), 4-11.
Boehm, B., & Lane, J. (2006). 21st century processes for acquiring 21st century systems of
systems. Crosstalk, 19(5), 4-9.