Interaction Design - Essay Example

Interaction Design TechPro Business Website Report _______ Submitted _____ Table of Contents Executive Summery Efficient system design and user interaction always guarantee the success of the system that is going to be developed. This research is about the effective system design and development regarding the effective applications development for the Technical Production Trading Saudi Arabia. The management of Technical Production Trading (TechPro) Saudi Arabia has decided to implement a web based business for the effective business marketing and access to global business market. In this scenario, this report presents a detailed analysis of new application interaction design development for the TechPro business. 1. Introduction The purpose of human computer interaction is to analyze the interaction between user and computer. In this paradigm we analyze how we can develop system that is able to offer better features and facilities regarding the usage of system. In addition, this subject investigates the user psychology, behaviours and develops the system that capable to meet the user expectations regarding system working. Human-computer interaction (HCI) research deals with the design of interfaces that facilitate simple and efficient use of computer systems (Marchionini & Sibert, 1991; Myers et al., 1996; DePaula, 2003). Dix, Finlay, Abowd, & Beale (2003) define effective interaction design as the analysis and study of communication among users or people with computers. The fundamental objective of effective human computer interaction design is to build systems that are much more user friendly as well as responsive to user’s requirements thus that people could be able to get their outcomes faster, through smaller mistakes and better satisfaction (Dix et al., 1998; Tate, 2001; Field, 2005). The management of the TechPro has decided to implement a new web based system to effectively handle and manage its business activities. In addition, by implementing this system TechPro is aimed to gain competitive edge and get access to global business market. This report will present a detailed analysis of the three development methods that are often used to produce software that are interaction designed focussed are the star model, the dynamic systems development method (DSDM) and the user-centred lifecycle design model. In addition, this report will assess and ensure an effective web design that is needed for creating websites and meeting the standards of web accessibility. This research will also offer some of main relevant legal, social or ethical issues that may arise during the development of software. Here I will critically evaluate how we undertook the development process and reflect the final design. 2. Development methods According to Tidwell (2006), the interaction design is the way of developing and shaping the interactive systems by giving particular importance to their usage qualities. Additionally, the interaction design is the design of system appearance, properties and behaviour of a future information system from the planned users viewpoint". However, the traditional design provides tangible shape, dimension, pattern, colour as well as character to information, products, spaces, communications as well as services. Thus, design is gradually more regarding human interaction with spaces, objects and people. Interaction Design is regarding drawing out the significant potential of novel technology, whether in the activities of intelligent artefacts, or the virtual world of digital environments. In addition, the paradigm of the interaction design has grown-up from the traditional design fields (particularly graphic and product design) as well as socially oriented computer studies (particularly HCI (human computer interaction), participatory design and computer supported cooperative work), through contributions from art, architecture, sociology as well as media studies. However, the outcome is a combination of unique techniques, and a project-based technique to develop environments, objects and systems. Moreover, it looks for to set up a dialogue among people, products and physical, cultural as well as historical contexts (Tidwell, 2006; Field, 2005; Pantic et al., 2005). Figure 1- Interaction Design entails numerous disciplines Source: [http://www.peterboersma.com/blog/uploaded_images/Dan_Saffer_T-Model_for_IxD-740311.jpg] 2.1. Star Model In developing the system for TechPro business I have used the star model. In this model we have to follow the following development stages (Schadewitz et al., 2006): Task analysis/functional analysis Requirements/specification Conceptual design/formal design representation Prototyping Implementation Figure 2- Star Model Below I will discuss the development life cycle for the TechPro website: 2.1.1 Task analysis/functional analysis In this phase of the website development we will take the requirements from the customers (TechPro staff and management). Additionally, we will discuss with them regarding his requirements. In addition, we analyze the main areas that will be addressed by the website. In this phase of the web site development we apply some requirements gathering tools (interview, analysis, survey, etc.) to gather the system requirements (Schadewitz et al., 2006). 2.1.2 Requirements/specification In this phase we establish the preliminary specifications that are drawn up by covering up every element of the system development requirement. In this phase we will assess the main web site modules, general layout, site navigation as well as dynamic parts of the website (Schadewitz et al., 2006). 2.1.3 Conceptual design/formal design representation This phase is the most significant phase of any web system development. Here we will design the website user interface and also the overall system’s operational design on which further development will be carried out. This phase of the website system development will incorporate the use of splice tools for designing and developing the system (Schadewitz et al., 2006). 2.1.4 Prototyping This phase is essential primarily for the websites systems. At this stage, we have to develop the prototype of the system to asses its main requirements and functionality (Schadewitz et al., 2006). 2.1.5 Implementation This phase is similar to traditional system development. Here we have to code and implement the website system and make it functional. This phase is the most significant part of the website system development. Here we will develop the system against the pre-developed system design (Schadewitz et al., 2006). 3. Ensuring an Effective web design This section presents some of the main aspects to ensure an effective web design. Here I will critically evaluate and present some of main steps that I have taken to develop a web design. However, for an effective web based interaction design we need to overcome a number of from users’ point of view that may be a group user, individual user, and an association or spatially or temporally separated peoples. The analysis and investigation of the web based interaction design features spotlight its concentration to the "user" being the fundamental part and interaction and systems to be intended and developed that assure the user objectives in a well-organized and profitable way (Dix et al., 1998; Tate, 2001). To develop a web based system for the TechPro business, I have researched the web and it is analyzed that effective web design is possible through some effective designing rules and guidelines. To design the TechPro business web based system I have utilized the Shneiderman’s 8 Golden Rules. (These rules are available at (University of Washington, 2008) and also discussed by the (Dix et al., 1998; Field, 2005). Below I have dicussed the Shneiderman’s 8 Golden Rules that I have implemented to the TechPro business web based system interaction design: 1. Strive for consistency In TechPro business web based system I have implemented the design that presents and incorporates the features of consistency through the system development. In this regard the system user will get the relief and ease regarding the system data and operations. Here below I have presented the main web based system theme that is followed all through the web based system. 2. Enable frequent users to use shortcuts Here I have also decided to offer the user the facility of shortcuts to handle the system. Here in TechPro business web based system I have offered the user small commands and clicks for retrieval of data and information from the main system as shown in image below: 3. Offer informative feedback In the TechPro business web based system the information feedback functionality is also incorporated. Here in case of TechPro business web based system I have offered the contact us facility as shown in image below: 4. Design dialogs to yield closure During the system usage we need to offer the user a dialogue based approach that presents the closure in case of system operations. In this scenario our website uses the simple interaction language that is easy to understand and simple to navigate. 5. Offer error prevention and simple error handling Here in the TechPro business web based system development I have tried to develop the system in a more convenient way from the user’s point of view that offer less system errors and error free working. In case of any error the system user feels distraction, so I have tried to make the web based system more error free. 6. Permit easy reversal of actions For the TechPro business web based system development I have made all the operations easy so a naive user can use the system effectively 7. Support internal locus of control In the scenario of the TechPro business web based system I have established an internal locus of control to all pages from where a user can move all around the web based system. 8. Reduce short-term memory load In this case I have tried to make the system operations easy and short in this way the business web site user can have reduced short term memory load. 3.1. Incorporating Accessibility, Usability and Portability in Web Design In this section I will outline how I have incorporated various features such as accessibility, usability and portability in web design. Here I have also used the W3C web content accessibility guideline 1.0 regarding TechPro business web based system development: Usability: For the usability of the website we require techniques and measures that necessitate vigilant consideration for designing websites. In this scenario I have tried to make use of the usability guidelines regarding the TechPro business web based system development. In this scenario I have tried to add visibility, clarity, quality and effectiveness to present the web based system contents (W3C, 1999). Website Portability: TechPro business web based system has developed under the stranded HTML language that offers the website portability. This web based system offers similar functionality in different web browsers (W3C, 1999). Accessibility: In case of web accessibility scenario the TechPro business web based system offers effective accessibility features in case of running on different operating systems and operational environment. In addition, the web based system is more effectively accessibile and easy to retrieve from the web based platform (W3C, 1999). 4. Meeting the Web Accessibility Standards According to Henry (2005), the web accessibility indicates how people will interact with web. Additionally web accessibility means that how people are able to understand, perceive, navigate and interact with the web. In addition, the web accessibility as well benefits others, including older people having changing capabilities due to age. Kyrnin (1999) has outlined that web accessibility indicates the application of making websites working for people of the entire disabilities and abilities. In addition, when the websites are properly developed, designed and edited, every user is able to have identical access to information as well as functionality. For instance, when a website is coded through semantically momentous HTML, by means of textual equivalents offered for images as well as by links named significantly this aids some people with some disabilities users by means of text-to-speech software as well as text-to-Braille hardware (Kyrnin, 2010; Henry, 2005; Sloan et al., 2006). In case of TechPro business web based system development, we have taken some important decisions regarding system development to conform the accessibility standards. In this scenario for meeting the accessibility standards I have used the web content accessibility guidelines 1.0 or WCAG 1.0 as main system development guidelines. Here in TechPro web based system I have used the WCAG 1.0 guidelines to ensure the ultimate accessibility of the web based system. These guidelines were first time released as a W3C suggestion in year 1999. WCAG 1.0 gives details how to develop website information content to present to the public. Although WCAG 1.0 is embedded mainly for web based content developers (W3C, 1999). In the section below I will explain the main checkpoints from the WCAG 1.0 Guideline that I have used and implemented in developing the TechPro web based system: 4.1. Structure vs. Presentation Web Content Accessibility Guidelines 1.0 has suggested that we have to make sure that all data and information that is coloured we are going to present on the web must be available into without colour. Additionally, this check point is really significant for the colour blind people. Now they will also have the opportunity to take information in a better way. For this we have to establish a version of our information that incorporates such a type of feature (W3C, 1999). In scenario of TechPro website I have used simple colours and writing style that is easily readable and understandable to any type of web user. In addition, the text colour and its font are so simple that any person can easily assess the basic information. 4.2. Text equivalents The basic theme of this feature is the availability of the text data and information into equivalent non-text element. In other words, all non-text data and information content have a text equal of the function or information, so that the non-text data or information content would be conveyed (W3C, 1999). In case of TechPro web based system I have adopted this point for the effective availability of all type of information to the user. In this scenario I have offered visual and text based help for the web site information and business contents. The proposed website image for TechPro is shown below that demonstrates the use of both image and text based help to website visitor: 4.3. Multimedia equivalents In this scenario we are asked to provide the multimedia (non-text like images, sound, video) equivalents to the original data and information contents (W3C, 1999). Here in TechPro web we have to provide these alternatives for the people who want to take quick insight or do not able read well or not at all. The same way of business information presentation is shown in the image shown above. 4.4. Content negotiation According to this feature of web content accessibility guidelines we have to offer the information in a way that the users can obtain documents according to their preferences like according to their language, content type, etc (W3C, 1999). The web pages of TechPro web based system are developed through the standard HTML language that can offer standard computability in all type of web browsers. In addition, its contents are based on English language that is readable and accessible in most part of word. Therefore we have targeted the international business market through use of English language. 4.5. Writing style The clear and easy writing style helps make the information contents of a website clearer and easier to understand and read for everyone, particularly for the people who have some problems. Here in case of TechPro web system we have used the accurate headings style and link descriptions in this way the viewer will have more effective way to obtain the information from the website. In addition, we also connected every paragraph to one major idea so that the person that has some low logical level would also be able to perceive the basic theme in an efficient way. The clear writing and presentation style is one of the best ways to handle our website contents and delivery style. This has also offered a great deal help present the basic ideas separately and distinctively (W3C, 1999). 5. Information architecture In this part of report for the TechPro web based system development I will outline some aspects regarding, how information is structured in the web based system and information architecture of our web site. In addition, I will present and outline some web site content usability factors to present the basic idea of the web based system information architecture. For the usability of the information architecture for TechPro website we require techniques, and measures that necessitate vigilant deliberation when designing websites. The main significant point of these are things in the website information architecture usability that are about determining a right and comprehensive position of client needs, making sure that the website fulfills user’s requirements, putting usability objectives, and offering practical content. Moreover, to achieve the most excellent result, designers should believe a complete variety of user-interface matters, and effort to generate a website that allows the most excellent possible human performance (Nielsen, 2000) & (Glen, 2010). 5.1. Use Case Diagram The use case of the “view and analyse project information” is really essential use case that engages lot of different processing. Like in this use case we have to retrieve the whole project information and view the whole events running there (David & Guy, 2003; Sommerville, 2004). Below I have outlined the basic information architecture of the TechPro website with the use case diagram: Figure 4 Main Use case diagrams 5.2. Sequence Diagram The sequence diagrams demonstrate the overall system execution and working behaviour. The sequence diagrams are the overall view of the system working cycle. These diagrams present the user interface with the system and the possible outcome or response of the system against any external input. In addition, the sequence diagram also outlines the possible negative outcome of the system activity (David & Guy, 2003; Pressman, 2001). Below I have outlined some of main aspects of system working through sequence diagram: Figure 5 Sequence diagrams 5.3. State transition Diagrams Figure 6- State transition Diagrams 5.4. SSADM diagram This section discusses the development of the SSADM diagram regarding this system development. I will also elaborate the main development scenarios of this system. The main aim of this diagram is to present the basic structure of the system: (David & Guy, 2003; Sommerville, 2004) Figure 8- SSADM diagram 6. Legal, social or ethical issues This section presents relevant legal, social or ethical issues that can arise while the development of this web based system: 6.1. Legal Issues One of the main legal issues can arise while developing the TechPro business website is the name of the website system. In this scenario we are conscious regarding the name of business website because it can be occupied by some other business. While naming this website domain I have got that this name is available through the .net domain of the web based business. 6.2. Social Issues To tackle social issues regarding this web based system we need to look at the people. In other words, we need to asses users’ point of views, how they want to see this web site, how they perceive our information. In this regard I have tackled following aspects of the system: 6.2.1 Page Layout TechPro website is aimed at attracting the website visitors and providing a very attractive user interface and working environment. For implementing an attractive user interface we have paid attention to the better page layout. In addition, the page layout is directly linked with content, such as how the TechPro website content is presented on the web page. At the same time researches have exposed that people are prepared to scroll to examine in the course of web pages, if they dont discover appropriate web content rapidly, they will probable to run off. So I have established the aim to keep our TechPro website pages simple and clean (Tidwell, 2006). 6.2.2 Download Speed One of the main element in any website is downloading the website (means its retrieval to user browser). Since, if our website did not support the appropriate downloading speed and mechanism for better downloading, then user will feel distraction and would not use the services of our website. If the downloading strategy is simple, better and easy then user will never feel distracting from our website. In addition, the web usability investigations carry on to demonstrate that the pace webpage page downloads is extremely significant. After 10 sec, website visitors can lose interest in our website, no matter how much they were paying attention in the area (Tidwell, 2006). In this scenario TechPro web based platform is developed through simple HTML language that appears to user web browser in 3-5 second with normal speed that is very good response time. 6.2.3 Colours Online website must be built on a more attractive colour theory. Additionally, the colours of the website are the main tools for taking the site visitor/customer attraction. In addition, the colours are able to influence the usability of our website. The web-browsers have regular colours standard that are employed for navigational link. Thus, when we make use of the additional colours, we can place the risk of puzzling our site visitor/customers (Tidwell, 2006). However, to implement the web based business platform for the TechPro I have obtained a standard colour template of web pages from businex 2009. 6.3. Ethical Issues During the development of the web based platform for the TechPro business I have attempted to pay more attention towards resolving the ethical issues. In this scenario the main ethical issue can arise is about exposing the business secrete information through the web. In this web based system I have not exposed any special or secrete business information on the web pages of TechPro. 7. Development Process The basic motive of this project is to enhance the traditional working style of the TechPro Company. The old system was traditional paper based working system. Thus, in that system the information searching, retrieval and editing were very complex. As a project manager of this project and I am responsible to plan and manage the project of the online TechPro Company system. The main objective of this project is to generate profit for this innovation, and gain a competitive edge by throwing this state of the art technology in the customary way of doing such type of business. This project is going to facilitate the people in their daily online products search form the TechPro. This project will add value to the pre-established products stores. 7.1. Work Breakdown Schedule (WBS) A large project can be organized by dividing it into small individual components in hierarchical structure that is acknowledged as work breakdown structure (Internet Center for Management and Business Administratio, Inc., 2007; Gray & Larson, 2006). In this section I will present the Work Breakdown Schedule (WBS) for all the activities that we are going to implement for the construction of this project. Figure 10- WBS 7.2. Requirements This section will provide a deep insight into the system requirements. Here it will emphasize that we can address each aspect of system non-functional requirements area: 7.2.1 Hardware requirements: Pentium 4 [workstation for development] Internet connectivity 7.2.2 Software requirements: Windows XP Front Page for the interface HTML for coding MS Office for Documentation UML tool for CASE development 7.3. Aspects that worked well In the overall development of the web based system I have found that there are three given aspects that have worked well all through the development of the web based system; Business management response regarding requirements collection System designing process System development consultation (greater help from teacher, friends and web development professional ) 7.4. Aspects that worked not well Here I will outline three main aspects that have not worked well regarding the overall working and handling of the online system development for the TechPro business. System testing was really hard Fixing some of the usability problems has also taken a huge time One main aspect is making this live. We have found a lot of problems regarding this system web based deployment. 8. Conclusion In this report I have presented a detailed analysis of the web based application designing, development and implementation for the TechPro business. In this research based report I have outlined some of the main aspects of the web based system development, life cycle and effective user interface. The main topics covered in this report were Web based system development lifecycle, navigation, accessibility, interaction design, development model and evaluation. I hope this report will offer a deep insight into the overall operational structure and working of the web based system for TechPro. 9. Bibliography David, A. & Guy, F., 2003. Information systems development. 3rd ed. New York: McGraw-Hill education. DePaula, R., 2003. A new era in human computer interaction: the challenges of technology as a social proxy. In CLIHC; Vol. 46, Proceedings of the Latin American conference on Human-computer interaction. Rio de Janeiro, Brazil, 2003. ACM New York, USA. Dix, A., Finlay, J., Abowd, G. & Beale, R., 1998. Human-Computer Interaction. Hillsdale: Prentice Hall. Field, M., 2005. Issues of Human Computer Interaction. Hershey, PA: Idea Group. Glen, 2010. Web Information Architecture Deliverables and Diagrams. [Online] Available at: http://www.fatpurple.com/2010/03/01/web-information-architecture-deliverables-and-diagrams/ [Accessed 26 April 2010]. Gray, C. & Larson, E., 2006. Project Management, The Managerial Process. 3rd ed. New York: McGraw-Hill. Henry, S.L., 2005. Introduction to Web Accessibility. [Online] Available at: http://www.w3.org/WAI/intro/accessibility [Accessed 25 April 2010]. Internet Center for Management and Business Administratio, Inc., 2007. Work BreakDown Structure. [Online] Available at: http://www.netmba.com/operations/project/wbs/ [Accessed 27 April 2010]. Kyrnin, J., 2010. What do the Accessibility Guidelines Mean to Me? Writing Accessible Web Pages is Easier Than You Think. [Online] Available at: http://webdesign.about.com/od/accessibility/a/accessibility_g.htm [Accessed 26 April 2010]. Marchionini, G. & Sibert, J., 1991. An agenda for human-computer interaction: science and engineering serving human needs. SIGCHI Bulletin, 23(4), pp.17-32. Myers, B. et al., 1996. Strategic directions in human-computer interaction. Computing Surveys (CSUR), 28(4), pp.794-809. Nielsen, J., 2000. Designing Multimedia web Usability: The Practice of Simplicity. Indianapolis, IN: New Riders Publishing. Pantic, M., Sebe, N., Cohn, J.F. & Huang, T., 2005. Affective multimodal human-computer interaction. In International Multimedia Conference, Proceedings of the 13th annual ACM international conference on Multimedia. Hilton, Singapore, 2005. ACM New York, USA. Pressman, R.S., 2001. Software Engineering: A Practicioners Approach, 5th Edition. London: McGraw Hill. Schadewitz, N., Jorge, P.., Moncur, W. & Roberts, J., 2006. The STAR Interaction Design Summer Schools Framework. In Proceedings of WONDERGROUND, International Deign Research Conference. Lisbon, Portugal, 2006. Sloan, D. et al., 2006. Contextual web accessibility - maximizing the benefit of accessibility guidelines. In ACM International Conference Proceeding Series; Vol. 134, Proceedings of the 2006 international cross-disciplinary workshop on Web accessibility (W4A): Building the mobile web: rediscovering accessibility? Edinburgh, U.K., 2006. ACM New York, USA. Sommerville, I., 2004. Software Engineering. 7th ed. New York: Pearson Education (Addison Wesley). Tate, M., 2001. Human Computer Interaction: Issues and Challenges. Hershey, PA: Idea Group. Tidwell, J., 2006. Designing Interfaces: Patterns for Effective Interaction Design. New York: OReilly. University of Washington, 2008. Shneiderman’s 8 Golden Rules. [Online] Available at: http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html [Accessed 27 April 2010]. W3C, 1999. Web Content Accessibility Guidelines 1.0. [Online] Available at: http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/ [Accessed 27 April 2010]. Read More