An amalgamated model of software usability

Author(s):  
R. Holcomb ◽  
A.L. Tharp
Keyword(s):  
Author(s):  
Florian Scheiber ◽  
Dominika Wruk ◽  
Achim Oberg ◽  
Johannes Britsch ◽  
Michael Woywode ◽  
...  

Author(s):  
Manuel Alejandro Barajas Bustillos ◽  
Aide Aracely Maldonado-Macías ◽  
Juan Luis Hernández Arellano ◽  
Liliana Avelar Sosa ◽  
Rosa María Reyes Martínez

Usability is the characteristic of a software product of being effective and efficient and producing satisfaction for users and traditionally is assessed through questionnaires but most of them are only available in English. A software usability assessment questionnaire (SUAQ) is proposed in two languages: Spanish and English. The methodology comprises four stages: 1) questionnaire development, 2) administration, 3) statistical validation, and 4) sample size determination. Twenty items were evaluated in terms of clarity, consistency, and relevancy. Then, the SUAQ was administered to 95 respondents. Overall, reliability values were acceptable in Spanish and English version, respectively. The factor analysis was feasible since the KMO index, and the Bartlett sphericity test was statistically significant. Both versions of SUAQ were tested to determine their validity. The findings show that the proposed methodology is an effective usability assessment instrument and thus an effective software improvement tool from a bilingual approach.


2008 ◽  
pp. 1734-1741
Author(s):  
Patricia A. Chalmers

Two decades ago, the U.S. Air Force asked human factors experts to compile a set of guidelines for command and control software because of software usability problems. Many other government agencies and businesses followed. Now hundreds of guidelines exist. Despite all the guidelines, however, most Web sites still do not use them. One of the biggest resulting usability problems is that users cannot find the information they need. In 2001, Sanjay Koyani and James Mathews (2001), researchers for medical Web information, found, “Recent statistics show that over 60% of Web users can’t find the information they’re looking for, even though they’re viewing a site where the information exists”. In 2003, Jakob Nielsen (2003), an internationally known usability expert, reported, “On average across many test tasks, users fail 35% of the time when using Web sites.” Now in 2005, Muneo Kitajima, senior researcher with the National Institute of Advanced Industrial Science and Technology, speaks of the difficulties still present in locating desired information, necessitating tremendous amounts of time attempting to access data (Kitajima, Kariya, Takagi, & Zhang, to appear). This comes at great costs to academia, government, and business, due to erroneous data, lost sales, and decreased credibility of the site in the opinion of users. Since emotions play a great role in lost sales and lost credibility, the goal of this study was to explore the question, “Does the use of usability guidelines affect Web site user emotions?” The experimenter tasked participants to find information on one of two sites. The information existed on both sites; however, one site scored low on usability, and one scored high. After finding nine pieces of information, participants reported their frequency of excitement, satisfaction, fatigue, boredom, confusion, disorientation, anxiety, and frustration. Results favored the site scoring high on usability.


2016 ◽  
Vol 9 (1) ◽  
pp. 101
Author(s):  
Nedhal A. Al-Saiyd

<p><span style="font-size: 10.5pt; font-family: 'Times New Roman','serif'; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 宋体; mso-font-kerning: 1.0pt; mso-ansi-language: EN-US; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;" lang="EN-US">Software is changed continuously in order to respond to different users and business needs. Requirements are changed dynamically to improve software usability and increase its value, but requirement volatility sometimes cause failures for many projects because of inadequate understanding of the changing causes and the consequences of these changes. This research highlights the importance of managing requirement changes, classify them, and control the impact risks of requirement volatility on software project. The proposed model is designed based on software requirements risks factors and how to reduce their impacts. Generally, requirements changing is considered as a difficult, costly and time-consumed task, and consequently it is too important to study the inter-relationships between the changes and their impacts on the other phases of software system. The good understanding of the changing causes and their consequences can improve and support requirements management process and also lead successfully to the predicted goals of changes. The high quality of the requirements influences the success of a software project during software development and maintenance processes.</span></p>


Sign in / Sign up

Export Citation Format

Share Document