C. Abras, D. Maloney-Krichmar, J. Preece (2004). User-Centered Design. Encyclopedia of Human-Computer Interaction. Thousand Oaks: Sage Publications. (http://www.e-learning.co.il/home/pdf/4.pdf
This article looks at the concept of User Centered Design. They offer four main components to keeping this design in mind: Make it easy to determine what actions are possible at any moment.
• Make things visible, including the conceptual model of the system, the
alternative actions, and the results of actions.
• Make it easy to evaluate the current state of the system.
• Follow natural mappings between intentions and the required actions; between
actions and the resulting effect; and between the information that is visible
and the interpretation of the system state
Users not only need to be able to review designs, but also to involve users in the creation of the design itself. The entire reason for programming any system is so that someone will be able to use it. Otherwise, the system becomes quickly obsolete in favor of a new more user-friendly system. Usability needs to be constantly tested for the system to keep functioning towards the needs of the users.
After reading this article, I just keep thinking about the aspect of customer service that is often neglected in technology. Yes, a design for a system can be groundbreaking and innovative, but it also needs to be optimized for the user. Many systems are developed to match technology rather than the user. It is inevitable that these systems will fail because the users will change over to other, more usable systems.
Zhang et al. (2005). Integrating Human-Computer Interaction Development into the Systems Development Life Cycle: A methodology. Communications of the Association for Information Systems, Vol. 15. pp. 512-543 Full-text available at http://melody.syr.edu/pzhang/publications/CAIS_05_Zhang_etal_HCI_SDLC.pdf
This article talks about how SDLC models are more geared towards organizational needs rather than human needs. While this model benefits general organization, it does not benefit the user: the human. The human interaction aspect needs to be better integrated into the information system in order for the system to be useful. The four phases of development are: planning and selection, systems analysis, systems design, and systems implementation and operation. Yet, the human aspect does not come into this design until systems design rather than from the start. Also, the process needs to consider how it will benefit organizational and human needs right from the very start.
After reading this article, I think back to the previous article in how the user is considered very late within the development process of informational systems. The purpose of information systems are to serve the user, so it makes little sense to me that users would be considered so late in the process. Programs should be built around the user in order to benefit the user.
My question for this week is: How can the user petition for more thought into their needs when buying or requesting information systems? How do they have their voice heard if designers do not look for their opinions and needs assessments?
