Operating Human Computer Interaction Approach in Design Phases of Software Developing Process Waralak Vongdoiwang Siricharoen
Operating Human Computer Interaction Approach in Design Phases of Software Developing Process 1
*1,
Waralak Vongdoiwang Siricharoen Universiy of the Thai Chamber of Commerce,
[email protected]
Abstract "I needed to know: Is there any way that I can travel around Bangkok using sky train or subway? How long does it take? and how much does it cost?" asked someone, who want to travel around Bangkok.” This is like talking or communicating with oneself by asking the questions. This research can answer these questions, Interactive maps add more dimensions of information; they become a more and more helpful tool and resource. Interactive design is the significant part of new media which has been proposed to the world for the past decades, and it is a very efficient technique. This research clarifies the idea of how we can facilitate presenting and communicating the essential information using new media which here is Internet. The interactive map of the underground train and sky train navigation routes map in Bangkok was developed as the case study using user-centered design methodology. The key is to take the interactive manner of information in term of communication issue as users’ requirements of prototype. The paper mentions the role of interactive manner in new media communication theory, human computer interaction (or more specific on user-system interaction), and user-centered design. The affects of the Internet as the information superhighway or as someone called global network on how it can help communicating the content within web site in more efficient way. Interactive map will help providing the information better and bringing navigation data to life. In this paper will show how we can create the system with the new media for the real users by their own requirements.
Keywords: Communication, Human Computer Interaction (HCI), User- Centered Design (UCD), User-System Interaction, Interactive Manner
1. Introduction “Human-computer interaction is a discipline concerned with the design, evaluation and implementation of interactive computing systems for human use and with the study of major phenomena surrounding them”. According to ACM SIGCHI Curricula for human-computer interaction, its definition has two basic parts; the machine or computer part and the human part. It brings the focus on application design and engineering, psychology, sociology, anthropology, industrial design, robotics, mechanics, and physiology. To further explain this human-computer interaction other aspects and concerns can be examined [1]. Very simply states that HCI “is the study of interaction people (user) and computer. It is an interdisciplinary subject, relating computer science with many other fields of study and research.” [2]. Interaction design is a newly coined discipline, and it focuses on constructing the ways people interact with objects and systems, and the product of interaction design is almost entirely the quality of the user’s experience [3] in [4] This would infer as one or more people using one or more computer as computational machine. User-system interaction studies a human and a machine in communication; this would focus on both human and machine side. On the human side we consider design disciplines (graphical and industrial), social science cognitive psychology, and also human performance toward the machine whiles they are using them. On the machine side is more about operating system, system architecture, software engineering, programming matter, and system developing disciplines, and computer graphics. The history of USI, three different approaches for relating functionality to a proper form can be distinguished: 1. Mechanical style (1900s-1960s), Mechanical style (Figure. 1): the relationship of human and machine back then was fixed, so there are large interface spaces to be filled, the specific type of interface objects are button, knob, switch, push, pull, etc. are provided. 2. Electronic style (1960s- 2000s), Electronic style (Figure. 2) is discussed in this work; this type of interaction style is embedded in the computer, TV, mobile devices. This hardware of all mentioned
Journal of Convergence Information Technology(JCIT) Volume7, Number11, June 2012 doi:10.4156/jcit.vol7.issue11.53
422
Operating Human Computer Interaction Approach in Design Phases of Software Developing Process Waralak Vongdoiwang Siricharoen
devices has so called channel function through that the user can access to needed functionality in form of sensitive appearance of the channel content. 3. Mechatronic style (2000s) the latest style is Mechatronic (Figure. 3) because in the near future the design space for the function-form mapping will be opened towards 'active elements' as a new approach for design user-system interaction. This would integrate the benefit from old mechanical style with the powerful new expression space of active elements. The most highly developed and investigated version is in robotics; but this new style is powerful enough to go significantly beyond human like robot design [5].
Figure.1 Mechanical style1
Figure. 2 Electronic style2 Figure. 3 Mechatronic Style3
2. Software Developing Approach When people read what are on the computer screen as the user interface. What the messages on screens are from other people. When human add or enter data to through any kinds of interface such as click, type etc. the messages are not only delivered for computer system itself, but it will be later shown to others. An explicit communicative interpretation of user interface is presented by Andersen [6] and [7]. A differentiation into three types of communicative situations is made: (1) user-system interaction, (2) user-user interaction and (3) designer-to-user communication. Founded in the information systems actability perspective, Sjöström & Goldkuhl [8] build on this differentiation of communicative situations and make a further elaboration. The communication via an user interface is expanded into four types: (1) designer-to-user communication of action possibilities, (2) business communication from others to user, (3) business communication to others from user and (4) user navigation of system. A communicative and socio-pragmatic model of user interface is presented. In [7] paper emphasizes the communication in an user-interface from its designers to its users. They describe the user interface of a computer system in the following way: “They are one-shot messages from sent from designers to users about the range of messages users can exchange with the system to achieve certain effects”. This can be compared to the concept of action repertoire (or action potential) within the Information System actability theory (e.g. [9], [8]). The action repertoire of the information System is the possible actions which the system affords to its users. This action potential is a result of the designers’ work. In their discussion, [7] focus on the communication among designer and user. The communication can be efficient when the user understands how they can work with the system without confusion. Therefore, the design phase is the critical part of how we can get the good system in term of usability successes. Information systems are developed to improve the communication among people or of people in organizations or through information technology [10]. Waterfall model or paradigm is the traditional methods that usually develop customized software. The waterfall model of software development is the one example of Software Development Life Cycle (SDLC). It is called waterfall because of the phases of each developing process falls down and the deliverables of the earlier phases will be the input for the next process (figure 4). This visual aspect is what effects people’s perceptions of what it does and hence how it is carried out. The earliest paper which describes the waterfall is “Managing the Development of Large Software Systems” by Dr. Winston W. Royce published in 1970[11].
1
http://www.historicalstockphotos.com/images/xsmall/2537_mechanical_operator_working_on_boiler_parts.jpg http://zone.ni.com/cms/images/devzone/tut/electronics%20education%20platform.PNG 3 http://preview.filesonic.com/img/1316261.jpg 2
423
Operating Human Computer Interaction Approach in Design Phases of Software Developing Process Waralak Vongdoiwang Siricharoen
Figure 4. Waterfall Model4 These methods are normally used in large-scale projects, which have comprehensible objectives and are limited in duration. System development is detached, in the sense that new versions of the information system, mostly with expanded functionality, are produced and released at intervals (Figure 5). At a certain moment in time, which is often determined by arbitrary project deadlines, instead of by true quality [12], a blueprint of the (new version of the) information system is produced, which is implemented after approval by the users. After the release of the new version, the implemented or installed version is fixed and the functionality offered often quickly become out of date (obsolete), due to fast changing in the user requirement. When the changing requirement and the installed functionality become larger, the developing process has to start from the beginning again. An in-depth analysis of the many problems encountered in this kind of large project-based software development is given in [13]. In traditional information system development methods, computer experts normally analyze the organization and specify the requirements. In such user-assisted development methods, users play a rather passive role, which is often limited to being interviewed by the analysts and designers. In these users driven development methods, the users themselves discuss what activities they should achieve, and determine which information tools to use to achieve their goals. Another characteristic is that there is not a single, bird’s eye view on the universe of discourse, which the external analysts tend to produce. Because the problem can occurs when the experts want the best system they can have in limited time and budget. In user-driven specification, there are rather multiple ants’ eyes views, each user generally being knowledgeable about and interested in, redefining only the small part of the total workflows the user is involved in. Thus, the integration of these multiple requirements, including handling the predictable conflicts, deserves special attention. The engineer’s functions are meaningful to engineers, but these functions are not the only truth, and not necessarily shared by non-engineers [14]. The nature of a linear development, the process must first be completed before the next process start. On the contrary; the system has employed an user-centered design technique, the process from start to finish, there is the interaction among designers and user at any time throughout the project cycle. In this work, the developers (software engineers) [23] apply the evolutionary information system developing techniques; with the user centered design concept which is similar to user-driven developing methods. The developers consider the user as the first priority and get them involved with all the developing process, adding the sense of product owner. This would be easy in term of product deliverable. Because the users themselves think that they participated in every steps of software developing. The results will be satisfied by users and developers.
4
http://www.coleyconsulting.co.uk/images/waterfall-model.gif
424
Operating Human Computer Interaction Approach in Design Phases of Software Developing Process Waralak Vongdoiwang Siricharoen
Figure 5. Discrete versus Evolutionary Information System Development Although acknowledging the central position of users in the analysis and design process, usercentered specification approaches still presume that external analysts and designers play initiating, coordinating or integrating roles. However, users, rather than just consulted in the design process, should be true partners in this process [15]; [16]; [17] in [12], [24].
Figure 6. Differences between designer’s mental model and user’s mental model
3. How the experiment was conducted? The questionnaires from the two groups of users are collected and analyze many times in order to get the real user requirement. The experimental system is navigation map of major transportation system of Bangkok (MRT underground train and BTS sky train). The experiment applied the user’s requirement as the first design and then produced the final prototyping of the interactive map. Usercentered system design is essentially an interactive and iterative process. The man stages are: [18]: 1. Task Analysis 2. Requirement Specification 3. Prototyping 4. Evaluation
425
Operating Human Computer Interaction Approach in Design Phases of Software Developing Process Waralak Vongdoiwang Siricharoen
The designer cannot passively go through several stages in linear manner, doing each stage once before signing it off and moving on like waterfall model. In UCSD, by contrast, the designer and the design process must both work interactively. The emphasis is more on research, design and evaluation as an interactive cycle. Initial good ideas are revised in the light of experience and evaluation. Thus designers cannot become stuck with their initial ideas and assumption, but must respond to data about what works and what does not. An essential difference should be made between requirement and specification. Requirements are function or system characteristics that the users believe they need, communicated as clearly as possible to the system developers. Specification are attempts by the latter to represent the requirements completely and consistently in terms of system definitions [12]. Thus, specification both originate from and extend requirements in terms of the proposed solution system [19]. The prototype usually contains functionality that the system should have, however, this functionality is not yet fully specified and implemented. The system analyst refines specifications which form the basis for a new prototype. This process can be repeated until the user is satisfied. As a system development approach comes under many different names, such as rapid application development or rapid prototyping [20]. The result of the research is the accomplishment of prototype which contains the requirements for both designer and users as following table 1. Table 1: The user’s requirement show in the developed system Requirement
Screen
1.Route distinction by using different color of each route Option1: Select at any area on the map. When the users select each route, each route will active from the background and the background will be in inactive state. Or the users can click at the individual buttons which will pop the route up separately. 2. Route distinction by using different color of each route Option2: Select from main menu
3. Route distinction by using different color of each route Option3 : Select at origin station and destination on the map
426
Operating Human Computer Interaction Approach in Design Phases of Software Developing Process Waralak Vongdoiwang Siricharoen
Requirement (Cont.)
Screen(Cont.)
4. Station names: The users need to see the clear station name: showing station name from origin to destinations route selection
5.Price and travel times presentation
6.Connection (Interchange) station information Option1: Select an area on the map
7.Connection (Interchange) station information Option2: Map
8.Printable 9. Download: With the download button, the users can download the whole route map
427
Operating Human Computer Interaction Approach in Design Phases of Software Developing Process Waralak Vongdoiwang Siricharoen
and print it out as well. The whole map can be saved and downloaded to pdf file.
Requirement (Cont.)
Screen(Cont.)
10.Zoom in- Zoom out: Bold font, the Zoom-in and Zoom-out buttons are to zoom in and out the route selection as user’s need.
428
Operating Human Computer Interaction Approach in Design Phases of Software Developing Process Waralak Vongdoiwang Siricharoen
11.English-Thai language : There are both Thai and English language in interactive map.
4. Conclusion and discussion If the design is not user-centered, it could lead bad designs. When users’ expectations are not met, the user may get frustrated. The major disadvantage to user centered design is that is can be expensive. It takes time to gather data from and about users especially if you seek to understand the environment in which they will be using the products. The process requires resources, both financial and human. User-centered design teams generally benefit from including persons from different area of interest, particularly psychologists, sociologists and anthropologists whose job it is to understand user’ needs and communicate them to the technical developers in the team. The downside of this approach is that member of the team have to learn to communicate effectively and to respect each other’s contributions and expertise. This can be time consuming and hence adds costs to the process. Management may question whether this added value is worth the cost, particularly if delivery dates are threatened [21], [22]. Advantages is mentioned of UCD are: Products are more efficient, effective, and safe; Assists in managing users’ expectations and levels of satisfaction with the product; Users develop a sense of ownership for the product; Products require less redesign and integrate into the environment more quickly; and The collaborative process generated more creative design solutions to problems. It also helps designers manage user’s expectations about a new product. This leads to a sense of ownership for the final product that often results in higher customer satisfaction and smoother integration of the product into the environment [22]. User-centered design come to a good user interface design at the end, it is essential to lay the foundation in the beginning. This foundation is an understanding of what end users really need and want “the user requirement”. As already stated in the name of the process, "User-Centered" Design, the end-user should be involved in every step of software development processes and increase the ownership of the product. This investment of involving end users and customers early in the development process ensures that software products are produced that are demanded and accepted by users at the end. Clearly after the last evaluation from the users, they say that the research work is very save time and money for the residents and tourists in order to prepare the trips. The result is UCD is the methodology which let the user gets involve with the developing processes since the beginning of the project; there are advantage and disadvantage here. From the case study in brief; the advantages are: increasing the acceptance of the product because of participatory and ownership in products, getting the real requirement from the users, and usable products. The disadvantages are: time consuming and costly because of iterative design, change of requirements, and argument among developers and users. User-centered design (UCD) is a general term for a philosophy and methods which focus on designing for and involving users in the design of computerized systems. The ways in which users participate can vary. At one end of the spectrum involvement may be relatively light; they may be consulted about their needs, observed and participate in usability testing. At the other end of the
429
Operating Human Computer Interaction Approach in Design Phases of Software Developing Process Waralak Vongdoiwang Siricharoen
spectrum involvement can be intensive with users participating throughout the design process as partners in the design. System design is based on principles with an user-centered design methodology. Not just only the user interface and display of images on the screen and color of a button that we have to focus on. However, it is to obtain the user requirement embeds in the interface integrated in the system is the most important thing. Because when we apply a good plan at the beginning, the plan is to understand the needs of real users. As defined we use "User-centered design”, so users should be required to be involved with all stages of software development in order to increase the ownership of software. Since the development process to ensure, that the system is produced and correct in keeping with generally accepted. The major advantage of the user centered design approach is that deeper understanding factors that affect the use of computer technology emerges from the involvement of the users at every stage of the design and evaluation of the product. The involvement of users assures that the product will be suitable for its intended purpose in the environment in which it will be used. This approach leads to the development of products that are more effective, efficient.
5. Acknowledgement The author would like to thank University of the Thai Chamber of Commerce (UTCC) for funding this research.
6. References [1] M. M. Gabouri, “Human-Computer Interaction,” California State University Northridge, p.5,2010,http://www.bruce-shapiro.net/math382/Projects/content/Mardi.pdf [2] Hewett, Baecker, Card, Carey, Gasen, Mantei, Perlman, Strong and Verplank, “ACM SIGCHI Curricula for Human-Computer Interaction,” 1996. http://old.sigchi.org/cdg/cdg2.html [3] Gillian Crampton Smith and Philip Tabor, “The role of the artist designer”, in: T. Winorad (Ed.), Bringing Design to Software,ACM Press, 1996. [4] Enrico Coiera, “Interaction design theory”, International Journal of Medical Informatics Vol.69, pp.205-222, 2003, www.elsevier.com/locate/ijmedinf [5] Matthias Rauterberg, “User-System Interaction (USI) Overview and Introduction”, 2001. http://www.idemployee.id.tue.nl/g.w.m.rauterberg/publications/USIprogram.pdf [6] Peter Bøgh Andersen ,”A theory of computer semiotics. Semiotic approaches to construction and assessment of computer systems”, Cambridge University Press. (1997) [7] Clarisse Sieckenius de Souza, Simone Dini z Junqueira Barbosa, Raquel Oliveira Prates, “Semiotic Engineering Approach to User Interface Design”, Knowledge-Based Systems, Vol. 14, No. 8, pp. 461–465, 2001 [8] Jonas Sjöström and Göran Goldkuhl, “Information systems as instruments for communication – refining the actability concept”, the 5th International Workshop on Organisational Semiotics Proceedings, Delft, 2002 In Goldkuhl, G. et al. [9] Göran Goldkuhl, Stefan Cronholm, Jonas Sjöström, “User Interfaces as Organisational Action Media”, http://www.orgsem.org/papers/06.pdf [10] Barbara McNurlin, Ralph Sprague, “Information Systems Management in Practice”, Prentice-Hall International, Inc., 2nd edition. 1989 [11] Coley Consulting, “Waterfall Model”, 2010, http://www.coleyconsulting.co.uk/waterfall-model.htm [12] Aldo de Moor, “EMPOWERING COMMUNITIES”, A Method for the Legitimate User-Driven Specification of Network Information Systems. 1999. http://www.communitysense.nl/phd/thes_aldo.pdf [13] Fred Brooks, “The Mythical Man-Month: Essays on Software Engineering”. Addison Wesley, anniversary edition.,1995 [14] Klaus Krippendorff , “The Semantic Turn: A New Foundation for Design”, chapter two: Basic concepts of human-centered design, Taylor & Francis Group, LLC, CRC Press, pp. 39–75, 2006. [15] R. Hirschheim, “User participation in practice: Experiences with participative systems design”. In Knight, K., editor, Participation in Systems Development. Kogan Page, 1989 [16] Morten Kyng, “Designing for cooperation: Cooperating in design”. Communications of the ACM, Vol.34, No.12, pp.65–73, 1991
430
Operating Human Computer Interaction Approach in Design Phases of Software Developing Process Waralak Vongdoiwang Siricharoen
[17] Irene S.Y. Koh, Michael S.H. Heng, “Users and designers as partners - design method and tools for user participation and designer accountability within the design process”. Information Systems Journal, 6:283–300. 1996 [18] Serengul Smith-Atakan, “Human-Computer Interaction”, Thomson Learning, London, England. Chapter 1, 2, 2006 [19] Robert Jackson, David Embley, “Using joint application design to develop readable formal specifications”, Information and Software Technology, Vol.38, no.10, pp.615-631, 1996 [20] John Reilly,” Rapid Prototyping: Moving to Business-Centric Development”, International Thomson Computer Press, 1996. [21] Alan Dix, Janet Finlay, Gregory Abowd and Russell Beale, “HUMANCOMPUTER INTERACTION”, PRENTICE HALL. 2004 [22] Jenny Preece, Yvonne Rogers, Helen Sharp, “Interaction Design: Beyond Human-Computer Interaction”, New York, NY: John Wiley & Sons, 2002 [23] Waralak Vongdoiwang Siricharoen, "Using Integrated Ontologies for Determining Objects towards Software Engineering Approach", AISS, Vol. 2, No. 4, pp. 61 ~ 70, 2010 [24] Hsin-His Lai, Szu-Lan Yang, "An Ergonomics-oriented Product Development and Evaluation Process: A Case Study of Children's Pointing Device", JCIT: Journal of Convergence Information Technology, Vol. 7, No. 6, pp. 323 ~ 331, 2012
431
