Kentaro Go
John M. Carroll
Skip Abstract Section
Abstract
Six blind men encounter an elephant. Each of them touches a different part of the elephant and expresses what the elephant is. Although they are touching the same elephant, each man's description is completely different from that of the others. We have been using this story as a metaphor for understanding different views of scenario-based system design.
- Carey, T., McKerlie, D., Bubie, W., & Wilson, J. (1991). Communicating human factors expertise through design rationales and scenarios. In D. Diaper & N. Hammond (Eds.), People and Computers VI: Proceedings of the HCI `91 Conference, August 20-23, Edinburgh, UK (pp. 117-130). Cambridge, UK: Cambridge University Press.Google Scholar
- Carroll, J. M. (Ed.). (1995). Scenario-based design: Envisioning work and technology in system development. New York: John Wiley & Sons. Google ScholarDigital Library
- Carroll, J. M. (1997). Human-computer interaction: Psychology as a science of design. International Journal of Human-Computer Studies, 46, 501-522. Google ScholarDigital Library
- Carroll, J. M. (2000). Making use: Scenario-based design of human-computer interactions. Cambridge, MA: MIT Press. Google ScholarDigital Library
- Clarke, L. (1991). The use of scenarios by user interface designers. In D. Diaper and N. Hammond (Eds.), People and Computers VI: Proceedings of the HCI `91 Conference, August 20-23, Edinburgh, UK (pp. 103-115). Cambridge, UK: Cambridge University Press.Google Scholar
- Dubberly, H. & Mitch, D. (1987). The Knowledge Navigator. Apple Computer, videotape. Appears in B. A. Myers ed. HCI'92 Special Video Program.Google Scholar
- diSessa, A. (1985). A principled design for an integrated computational environment. Human-Computer Interaction 1(1), 1-47.Google ScholarDigital Library
- Gould J. D., Boies, S. J., Levy, S., Richards, J. T., & Schoonard, J. (1997). The 1984 Olympic message system: A test of behavioral principle of system design. Communications of the ACM 30(9), 758-769. Google ScholarDigital Library
- Hooper, J. W. & Hsia, P. (1982). Scenario-based prototyping for requirements identification. Software Engineering Notes 7(5), 88-93. Google ScholarDigital Library
- Hsia, P., Samuel, J., Gao, J., Kung, D., Toyoshima, Y., & Chen, C. (1994). Formal approach to scenario analysis. IEEE Software 11(3), 33-41. Google ScholarDigital Library
- Hughes, J. A., Randall, D., & Shapiro, D. (1992). Faltering from ethnography to design. In Proceedings of CSCW'92 Conference, Oct. 31-Nov. 4, Toronto, Canada (pp. 115-122). New York: ACM. Google ScholarDigital Library
- Jacobson, I. (1995). The use-case construct in object-oriented software engineering. In J. M. Carroll (Ed.), Scenario-based design: Envisioning work and technology in system development, 309-336. New York: John Wiley & Sons. Google ScholarDigital Library
- Jacobson, I., Christersson, M., Jonsson, P., & Overgaard, G. (1992). Object-Oriented Software Engineering: A use-case driven approach. Reading, MA: Addison-Wesley. Google Scholar
- Kahn, H. (1962). Thinking about the unthinkable. New York: Horizon Press.Google Scholar
- Koskimies, K. Systa, T., Tuomi, J., & Mannisto, T. (1998). Automated support for modeling OO software. IEEE Software 15(1), 87-94. Google ScholarDigital Library
- Mountford, S. J. (1991). A day in the life of .. (Panel). In Proceedings of CHI'91, April 27-May 2, New Orleans, LA. (pp. 385-388). New York: ACM. Google ScholarDigital Library
- Potts, C., Takahashi, K., & Anton, A. I. (1994). Inquiry-based requirements analysis. IEEE Software 11(2), 21-32. Google ScholarDigital Library
- Rolland, C., Achour, C. B., Cauvet, C., Ralyte, J., Sutcliffe, A., Maiden, N. A. M., Jarke, M., Haumer, P., Pohl, K., Dubois, E., & Heymans, P. (1996). A proposal for a scenario classification framework. Requirements Engineering 3(1), 23-47. Google ScholarDigital Library
- Rosson, M. B. & Carroll, J. M. (2001). Usability engineering: scenario-based development of human computer interaction. Redwood City, CA: Morgan Kaufmann. Google ScholarDigital Library
- Wack, P. (1985). Scenarios: Uncharted waters ahead. Harvard Business Review 63(5), 72-89.Google Scholar
- Weidenhaupt, K., Pohl, K., Jarke, M., & Haumer, P. (1998). Scenarios in system development: Current practice. IEEE Software 15(2), 34-45. Google ScholarDigital Library
- Wirfs-Brock, R., Wilkerson, B., & Wiener, L. (1990). Designing object-oriented software. Englewood Cliffs, NJ: Prentice Hall. Google ScholarDigital Library
- Young, R. M. & Barnard, P. J. (1991). Signature tasks and paradigm tasks: new wrinkles on the scenarios methodology. In D. Diaper and N. Hammond (Eds.), People and Computers VI: Proceedings of the HCI `91 Conference, August 20-23, Edinburgh, UK (pp. 91-101). Cambridge, UK: Cambridge University Press.Google Scholar
Index Terms
- The blind men and the elephant: views of scenario-based system design
Recommendations
Elephant Flow Detection Mechanism in SDN-Based Data Center Networks
Aiming at the problem of network congestion and unbalanced load caused by a large amount of data capacity carried in elephant flow in the data center network, an elephant flow detection method based on SDN is proposed. This method adopts the autodetect ...
Poster: A Low-cost Elephant Localization System
EWSN ’17: Proceedings of the 2017 International Conference on Embedded Wireless Systems and NetworksThe human-elephant conflict is affecting the day-to-day life of villagers and farmers of rural Sri Lanka. To protect humans from elephants, reliable mechanisms to identify the presence of wild elephants around human habitats are necessary. In this work, ...
Resource-Efficient Detection of Elephant Rumbles
SenSys '17: Proceedings of the 15th ACM Conference on Embedded Network Sensor SystemsThe human-elephant conflict is causing significant damages to the life of human and elephants in Sri Lanka. Minimizing encounters between humans and elephants is hence crucial in alleviating the human-elephant conflict. We have earlier introduced Eloc, ...
Comments