User Involvement in System Development - Case Study Example

USER INVOLVEMENT IN SYSTEM DEVELOPMENT 1. Reading (Full citation required including author, title, date, publication details, etc.) Article 1: Zhou, Tao. 2011. "Understanding Online Community User Participation: A Social Influence Perspective." Internet Research 21 (1): 67 - 81. Article 2: Issa, T, and Andrew Turk. 2008. User Participation in Website Development WWW/Internet 2008, Friburg, Germany Article 3: Ekelin, Annelie, and Sara Eriksen. 2011. "Does User Participation Matter in the Design and Development of E-Participation Tool? Experiences from a Proof-of-Concept Project " In Ongoing Research and Projects of IFIP EGOV and ePart 2011, Linz 1- 8 Article 4: Shelly, Gary B., and Harry J. Rosenblatt. 2012. Systems Analysis and Design: Course Technology, Cengage Learning. Article 5: Costabile, Maria Francesca, Yvonne Dittrich, Gerhard Fischer, and Antonio Piccinno. 2011. "End-User Development." Third International Symposium, IS-EUD 2011 Torre Canne (BR). Article 6: Gammack, John, Valerie Hobbs, and Diarmuid Pigott. 2006. "The Book of Informatics." Melbourne: Thomson. What is the theme/subject of the articles? Theme/Subject Article 1 Article 2 Article 3 Article 4 Article 5 Article 6 HCI Usability Methodology Aesthetics Personality Interface Design E-Business Culture User Participation Online Community Article one: Understanding Online Community User Participation: A Social Influence Perspective Article two: User Participation in Website Development Article three: Does User Participation Matter in the Design and Development of E-Participation Tools? Experiences from a Proof-Of-Concept Project Article Four: Systems Analysis and Design Article Five: End-User Development Article Six: The book of informatics 2. Argument or Finding Tao Zhou. (2010) emphasizes that the mode of interaction between online communities is a collaborative one. Online users’ motivation alongside their social and other processes determine their level of participation. Tao draws the social influence theory and points to its effects that include internalization, identification, and compliance. He stresses that user behavior is greatly dependent on group norm and social identity. Issa et al. (2008) elaborates the extent for usability in all commercial systems. As new users are anticipated from repeatedly, it is vital that all HCI be familiar to all user for ease of usability. Issa et al. (2008) introduces a new usability methodology. The methodology focuses on the marketing of web designers and advocates for designs that reduce user frustration and increase end user experience. In addition, Issa stresses on the need to employ HCI and usability to ensure customer satisfaction. Ekelin et al. (2011) majors on user involvement in design phase. He highlights on participatory design, user centered design and user driven innovational approaches. He elaborates the Augment proof-of-concept and how user involvement in designing can vary even in a given project. Ekelin et al. (2011) cautions that if these variations are not noted, the entire project is at risk of failure. Shelly & Harry, Rosenblatt. (2012) Note that the system analysis and the system design phase are the most crucial phases in the SDLC. Ideally, it is at this point that all the functionalities and deliverables are determined. The system objectives and the overall goals of the project are noted. They further explain how the analysis phase offers the first chance for user involvement in system development. Costabile, Dittrich, Fischer & Piccinno. (2011) major on the development contribution of the user. Despite the user being involved in the system analysis and design phases, the user is also involved in the development phases. Primarily, system prototypes are mostly adapted to give the user an initial feel of how the product will be. Gammack, Hobbs & Pigott. (2006) detail on the initial stages of development, the analysis phase and the last phases of development that involve unit testing. Ideally, the inputs of the analysis phase are vital. As noted above, the initial user involvement is most effective in the analysis phase. Here after, it is vital to involve user in the initial testing, mostly the unit testing before the modules are merged to form the final system. 3. Evidence Tao Zhou. (2010) talks of group norms and how they, the group norms share common interactive goals. He states that group norm relevance in online activates and interactions. It is believed that humans’ or rather online users tend to form active participation should they discover that they have similar values and achievements with their fellow users. Tao points the effect of group norm on social identity. The intention of users had a direct impact on their online activities and tasks. This translates to the change of actual user behavior depending on their online participation intentions. These intentions are also affected by the subjective norms and the social identities of the online users. Issa et al. (2008) expounds on the use of various tools to establish consistency in the designing of e-business web application usability. Groups of website usability experts alongside a group study were studied as they embarked on the stated HCI and usability tools. In the methodology, Issa tackles the question (why are things the way they are?). It is believed that most user find websites and web application rather challenging to use. In other words, most websites have poor usability design. After adequate research, a methodology was structured for development of web application from a market perspective. Use of online questionnaire was the second approach employed in Issa research. The questions drafted in the questionnaire were drafted from the conducted interviews from the initial research method. The online questionnaire was employed to grasp understanding of both benefits and practicality of the proposed design methodology. Shelly & Harry, Rosenblatt. (2012) clearly stated that all system methodologies emphasize on accurate system analysis then design. The deliverable of the system analysis phase, offer the initial input of the system design. They point out that at system analysis in the phase in which user involvement in introduces into the development cycle. The user clearly points out all the desired functionalities of the proposed system. In addition, they, the users have a chance to express their desires on how the final system should achieve its expected functionalities. As Costabile, Dittrich, Fischer & Piccinno. (2011) notes, the design phases are very crucial to the end system. Ideally, it is very close to the actual development of the system. Some SDLC employ prototypes in the final staged of design and the initial stages of codding. User involvement in these phases can be deemed as end user development. Prototypes give the end user an initial look and feel of the final product. Ideally, the user can comment and or provide more input on their initial perception of the HCI and the usability of the final system from the prototypes. Gammack, Hobbs & Pigott. (2006) emphasizes on flow of communication in all the development phases. Most importantly, the systems analysis the design, the development and the deployment phases of a system. User involvement in any system development is in terms of information. Ideally, this information should be analyzed, understood, and finally, disseminated adequately. Its adaptation and implementation into the system development phases should be in a manner that will not negatively affect the development of the system. Finally, yet importantly, Ekelin et al. (2011) explains the use of participatory design approach and why it should be employed in projects. This approach offers some similar strategies like the Scandinavia system development approach. The Scandinavia approach advocates for mutual learning. Therefore, all members and end users to offer a better understanding should conduct the designing phase and the collaborative. The approach of design ethnography is also employed in Ekelin research methodology. This approach advocates for exploration of technology productions. It states the ideal importance of mapping the working relations of any technology to be employed in the project. 4. Observations All the articles agree that the end user is vital in the design process. Ideally, HCI and usability go hand in hand. All developers and e-business should always employ the HCI and usability concepts in mind. The best way to achieve usability is to ensure of end user involvement in the development and designing phase of any application. Considering that they will be the users, it is paramount that they be part of the designing team to express their design expectation of any application clearly. The articles agree that e-business is the future of technology and with the enormous use of hand held devise if not smart phones is the next big thing. HCI and Usability researchers should expound on their smart phone and cellular technology. In my own words, I believe the mobile technology is huge. Adequate and progressive research should be done to keep up with this technology if business organizations are to capitalize in this line of business. 5. Conclusion As noted, HCI and Usability are paramount in any design work. The level to which a website is perceived as user friendly is solely dependent on its usability. It is vital for the end user be incorporated into the designing team. This offers a channel for the design experts to have the end user perception in mind as they design the system. Familiarity is among the contributing factors to usability, which in turn contributes to the overall success of any software product. The user involvement in the designing phase of a website will greatly ease usability once the product is launched. The end user will be familiar with what he sees and as the HCI of the product hence improving the overall usability. This is opposed to letting technical experts deal with the design. From their expertise, they might include HCI technology new to most users. However, irrespective of the technical advantages of the new HCI technology incorporated, if the end users cannot work with it then the usability of the product is rendered poor. However, the extent to which the user is involved in the development phase of software products should be limited. Excess involvement of end user can lead to scope creep. Scope creep is the changing of software requirements during its development. Scope creep caused projects to be delayed due to constant re designing to meet the changing functional requirements. Ultimately, this affects the entire project as a whole and the final product, should the project proceed to the end.  Read More