degree to which a product or system enables the user to learn how to use it with effectiveness, efficiency in emergency situations. Operability degree to which a. The quality model is the cornerstone of a product quality evaluation system. The quality model determines which quality characteristics will be taken into account . product quality requirements based on the fuzzy logic and likert scale for DSS which aims to quantify the quality requirements. ISO / IEC ―Systems .
|Language:||English, Spanish, Portuguese|
|Genre:||Fiction & Literature|
|Distribution:||Free* [*Sign up for free]|
ISO/IEC was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering. PDF | The Malaysian Government initiated the Digital Malaysia (DM) program to advance the country towards a developed digital economy by. ISO /IEC (). Systems and software engineering -- Systems and software Quality Requirements and Evaluation (SQuaRE).
This characteristic is composed of the following subcharacteristics: Functional completeness. Degree to which the set of functions covers all the specified tasks and user objectives. Functional correctness. Degree to which a product or system provides the correct results with the needed degree of precision. Functional appropriateness.
Degree to which the functions facilitate the accomplishment of specified tasks and objectives. Time behaviour. In this paper, this standard was used to assess the quality in use of e-Ebola Awareness System, an online health awareness portal.
The results provide some insights into the quality into the use of the online portal and also pointing to some issues that impact negatively on the quality in use of the portal, demanding attention and improvement.
All rights reserved 1. The focus of this study is on quality in use. The quality-in-use of E-Ebola There is an increase in the usage of online or Web Awareness System an online e-health awareness systems for important tasks . Studies have also shown that the Web is use standard .
These studies reveal that there is a rise in with the goal of describing and evaluating software surfing of the Web based portals for health related quality. There are two ISO models and standards for information. Increasing number of users access free software quality: These models describe software quality in Because of this surge in the use of health-related use in general .
However, there is a dearth of online systems and portals, there is the need to literature on the use of these standards in the ascertain the quality of these Web portals. Their quality evaluation of software quality in the e-health is a precursor to their continual success, usage and awareness domain.
This paper seeks to leverage on usefulness and their ability to attract new users and this gap to evaluate the quality in use of e-Ebola maintain existing ones . The e- quality in different perspectives, namely: The components are: The model sections: It further defines the results of analysis and section 5 is for discussion and satisfaction in use as likeability, pleasure, comfort, and final conclusion. This definition of usability, although in use derived from ISO  constitute the most popular, has some demerits.
It does not satisfaction in use. The model also incorporates safety consider some aspects of software quality in use, such in use and flexibility in use into the quality in use model.
Also, the model defines Flexibility in use is the characteristics of context satisfaction in terms of only comfort and acceptability comprehensiveness of the model .
The usability in use component is further broken for the quality of software products . It consists of the into three sub-components: In this study, usability, efficiency, maintainability, and portability. However, this model has been Malaysia. The test was conducted on Laptops. Also, to were unverified and perhaps unverifiable . These capture efficiency of use metric, from the same critiques lead to its revision in and The the revision, Al-Kilidar et al.
A single question questionnaire was used to get the task ease metric. The questionnaire is a 7- 2.
It sees usability as indicate task ease while lower scores indicate task a constituent of quality in use and as a software difficulty.
The System Usability Scale SUS was used as quality attribute composed of three elements as in the a proxy to measure satisfaction in use. The task scenarios include: Open three news contents on Ebola in new tab and write out the name of the news media; task 2: Find three tweets on Ebola and write down the name of the source of the tweets; task 3: Search for information on Ebola symptom and Ebola prevention and write out one symptom and prevention each; task 4: View the content on Ebola causes and Ebola treatment in any language of your choice other than English.
More so, flexibility in use, which covers operability and context, completeness and comprehensiveness was captured via observation while safety in use, which protects users from adverse consequences of use was also obtained by observation.
All users failed the task, suggesting that there is an issue with the functionality associated with the task, as users cannot access it. Figure 2 Task error rate The task error rate Figure 2 result shows that there is no significant different in task error rates. However, there are some observed differences.
It is noteworthy to observe that though task 4 has the least error rate, all user nonetheless failed it.
From figure 3 above, task 1 had the highest task time, this is followed by task 2, then task 3. Task 4 had the least time. Since task 4 had particular issues, users seem to abandon it, this is the reason for the lesser task time for the task. On the average, users spent about one and the half minutes on the tasks with all tasks below 2 minutes on the average. Task 1 is significantly different from task 2 but all other tasks are non- significantly different from each other.
The task with Figure 5 System satisfaction the highest ease is task 1, followed by task 2. The task ease of task 4 appears to be exaggerated as the task was failed by all users or perhaps, the users felt it was Figure 5 above shows the result for system easy even though they all failed it.