Spelling suggestions: "subject:"confusability"" "subject:"focusability""
111 |
Grail²Saxeggen, Tomas January 2007 (has links)
<p>Detta arbete är det första steget i en lång process vars slutgiltiga mål är att utveckla en metod för automatisk övergång från en icke-generisk objektorienterad applikation till en generisk.</p><p>Helst borde stöd för en sådan transformation implementeras i en utvecklingsmiljö, IDE. En analogi skulle kunna dras till faktorisering av klasser, en operation som stöds av de flesta utvecklingsmiljöer idag. Som ett första steg i en pågående process är detta arbete tänkt att fungera som ett icke-trivialt exempel för framtida analys. Exemplet består av ett icke-generisk och ett generisk grafpaket som är skrivet i Java 1.4.2 respektive Java 5.0. Uppsatsen beskriver övergången från den icke-generiska till den generiska lösningen på systematiskt sätt som går att upprepa. Tanken är att detta arbete även skall kunna appliceras på andra språk och applikationer i framtiden.</p> / <p>This work is the first step in a long process, which final goal is to develop a method that automatically allows you to go from a non-generic object-oriented program to a generic one. Preferably, support for such a conversion should be implemented in an Integrated Development Environment (IDE). An analogy could be drawn to the factorisation of classes, an operation supported by the most common IDEs today. As a first step in an ongoing process, this work is meant to be a non-trivial example for future analysis. The example project constitutes of a non-generic and a generic graph package, which is written in Java 1.4.2 and Java 5.0 respectively. The thesis describes the transition from the non-generic to the generic solution in a systematic and repeatable way. The idea is that this work could be applied to other languages and applications in the future, as well.</p>
|
112 |
Als Web und GUI verschmolzen - Betrachtungen zu Design und UsabilityPetersen, Karsten 19 May 2001 (has links)
Gemeinsamer Workshop von Universitaetsrechenzentrum und Professur "Rechnernetze und verteilte Systeme" der Fakultaet fuer Informatik der TU Chemnitz.
Workshop-Thema: Mobilitaet
Dieser Vortrag begruendet die Notwendigkeit beim
Gestalten von Webseiten auf Gesichtspunkte der
Benutzbarkeit einzugehen und zeigt Wege wie dies
beruecksichtigt werden kann.
|
113 |
Usability and productivity for silicon debug software: a case studySingh, Punit 24 February 2012 (has links)
Semiconductor manufacturing is complex. Companies strive to lead in the markets by delivering timely chips which are bug (a.k.a defect) free and have very low power consumption. The new research drives new features in chips. The case study research reported here is about the usability and productivity of the silicon debug software tools. Silicon debug software tools are a set of software used to find bugs before delivering chips to the customer. The study has an objective to improve usability and productivity of the tools, by introducing metrics. The results of the measurements drive a concrete plan of action. The GQM (Goal, Questions, Metrics) methodology was used to define and gather data for the measurements. The project was developed in two parts or phases. We took the measurements using the method over the two phases of the tool development. The findings from phase one improved the tool usability in the second phase. The lesson learnt is that tool usability is a complex measurement. Improving usability means that the user will use less of the tool help button; the user will have less downtime and will not input incorrect data. Even though for this study the focus was on three important tools, the same usability metrics can be applied to the remaining five tools. For defining productivity metrics, we also used the GQM methodology. A productivity measurement using historic data was done to establish a baseline. The baseline measurements identified some existing bottlenecks in the overall silicon debug process. We link productivity to time it takes for a debug tool user to complete the assigned task(s). The total time taken for using all the tools does not give us any actionable items for improving productivity. We will need to measure the time it takes for use of each tool in the debug process to give us actionable items. This is identified as future work. To improve usability we recommend making tools that are more robust to error handling and having good help features. To improve productivity we recommend getting data on where the user is spending most of the debug time. Then, we can focus on improving that time-consuming part of debug to make the users more productive. / text
|
114 |
Αξιολόγηση ευχρηστίας εκπαιδευτικού λογισμικού & ευχρηστίας ιστότοπου εκπαιδευτικού ιδρύματος βασισμένη σε μεθόδους παρατήρησης χρηστών σε εργαστηριακό περιβάλλονΠαπαλουκάς, Σπυρίδων 23 October 2007 (has links)
Πραγματοποιήθηκε έρευνα σχετικά με την αξιολόγηση της ευχρηστίας εκπαιδευτικού λογισμικού, καθώς και της ευχρηστίας ιστότοπου εκπαιδευτικού ιδρύματος βασισμένη σε μεθόδους παρατήρησης χρηστών. Σε πρώτη φάση έγινε η εγκατάσταση του εργαστηρίου αξιολόγηση ποιότητας. σε δεύτερη φάση έγιναν εργαστηριακά πειράματα με αντικείμενο την αξιολόγηση της ευχρηστίας του ανανεωμένου ιστότοπου του ΕΑΠ και της ευχρηστίας λογισμικού φυσικής που χρησιμοποιείται για εκπαίδευση από απόσταση. / A research referring to usability of educational software and web site o HOU based on users observation methods was contacted. First face laboratory installation-s/w installation and second face the experiment performance.
|
115 |
ViDLog: Understanding Website Usability through Log File ReanimationMenezes, Chris 05 September 2012 (has links)
Webserver logfiles are an inexpensive, automatically captured text-based recording of user interactions with a website. In this thesis, a tool, ViDLog, was created to take logfiles and reanimate a user session with the purpose of gaining usability insights.
To evaluate the effectiveness and value of reanimating user sessions, 10 usability professionals viewed logfile-recorded website usage using ViDLog and were then asked to infer users’ goals, strategies, successes or failures, and proficiencies; and afterwards, rate, ViDLog across multiple dimensions.
ViDLog’s logfile reanimation proved successful for gaining usability insights; usability professionals were able to infer users’ goals, strategies, successes or failures, and proficiencies. Participants were able to do this without ViDLog training, without familiarity of the website being evaluated (Orlando), and without domain knowledge of the subject depicted in the user sessions (women’s literature). However, they were only able to infer users’ overarching goal, not specific goal criteria; and were only able to determine relative proficiencies after viewing both user sessions. They also expended a good deal of mental effort when comprehending ambiguous user sessions, and found inefficiencies in ViDLog’s user interface. / Dr. Susan Brown for The Orlando Project
|
116 |
The Effects of Distraction on Usability Testing Results in a Laboratory EnvironmentThrift, Brady 03 October 2012 (has links)
Hand held device users encounter various forms of distraction in their daily lives. Distractions may prevent them from correctly using the hand held device. Usability evaluations are meant to identify issues prior to end-users experiencing them. However the laboratory environment, which usability evaluations are conducted, may not reflect the real-world conditions that devices are used.
The experiment involved each participant performing tasks in both a quiet and a noisy environment. The noisy environment emulated part of a real-world experience by adding social noise in the background during the participant's tasks. The goal was to compare how much insight each participant was able to achieve from the data in each of the environments.
It was found that task performance accuracy was higher in a quiet environment as opposed to the noisy environment. The mental demands and frustration of participants were found to be higher during the noisy environment evaluation.
|
117 |
Mitigating the Risks of Smartphone Data Sharing: Identifying Opportunities and Evaluating NoticeBalebako, Rebecca 01 September 2014 (has links)
As smartphones become more ubiquitous, increasing amounts of information about smartphone users are created, collected, and shared. This information may pose privacy and security risks to the smartphone user. The risks may vary from government surveillance to theft of financial information. Previous work in the area of smartphone privacy and security has both identified specific security flaws and examined users’ expectations and behaviors. However, there has not been a broad examination of the smartphone ecosystem to determine the risks to users from smartphone data sharing and the possible mitigations. Two of the five studies in this work examine the smartphone data sharing ecosystem to identify risks and mitigations. The first study uses multi-stakeholder expert interviews to identify risks to users and the mitigations. A second study examines app developers in order to quantify the risky behaviors and identify opportunities to improve security and privacy. In the remaining three of five studies discussed in this work, we examine one specific risk mitigation that has been popular with policy-makers: privacy notices for consumers. If done well, privacy notices should inform smartphone users about the risks and allow them to make informed decisions about data collection. Unfortunately, previous research has found that existing privacy notices do not help smartphone users, as they are neither noticed nor understood. Through user studies, we evaluate options to improve notices. We identify opportunities to capture the attention of users and improve understanding by examining the timing and content of notices. Overall, this work attempts to inform public policy around smartphone privacy and security. We find novel opportunities to mitigate risks by understanding app developers’ work and behaviors. Also, recognizing the current focus on privacy notices, we attempt to frame the debate by examining how users’ attention to and comprehension of notices can be improved through content and timing.
|
118 |
Improving understanding of website privacy policies2004 August 1900 (has links)
Machine-readable privacy policies have been developed to help reduce user effort in understanding how websites will use personally identifiable information (PII). The goal of these policies is to enable the user to make informed decisions about the disclosure of personal information in web-based transactions. However, these privacy policies are complex, requiring that a user agent evaluate conformance between the user’s privacy preferences and the site’s privacy policy, and indicate this conformance information to the user. The problem addressed in this thesis is that even with machine-readable policies and current user agents, it is still difficult for users to determine the cause and origin of a conflict between privacy preferences and privacy policies. The problem arises partly because current standards operate at the page level: they do not allow a fine-grained treatment of conformance down to the level of a specific field in a web form. In this thesis the Platform for Privacy Preferences (P3P) is extended to enable field-level comparisons, field-specific conformance displays, and faster access to additional field-specific conformance information. An evaluation of a prototype agent based on these extensions showed that they allow users to more easily understand how the website privacy policy relates to the user’s privacy preferences, and where conformance conflicts occur.
|
119 |
Visualisation of requirements and their relations in embedded systemsLööf, Robert, Pussinen, Kenny January 2014 (has links)
In the automotive industry, the complexity of electronic components is increasing rapidly. Modern functional safety standards rely on strict requirements engineering techniques in order to ensure the safety of a given system. Current requirements management tools on the market either suffer in their ability to handle such constraints or are not susceptible to industrial applicability. To solve this problem, two main questions have been focused in this master thesis. How to visualise the requirements and their relationship to architecture and how to provide a solution that reflects on how work is conducted today at Scania. A prototype with focus on visualisation of requirements and their relationship to architectures has been developed. To provide an intuitive solution that reflects on how work is conducted, an evaluation of the prototype has been conducted. The prototype was evaluated by engineers at Scania that works with requirements in their daily work. The conclusion of the evaluation suggests that visualisation of requirements and their relation to architecture could be beneficial for requirement engineering. To keep the solution intuitive it is important to focus on filtering methods for the visualisation in future development.
|
120 |
Usability of Paper-based Industrial Operating ProceduresIannuzzi, Mario 25 June 2014 (has links)
Procedures are standardized lists of instructions that designate the safe and accepted way of accomplishing a task. This study intended to develop and compare the usability of paper-based industrial operating procedures. Two procedures at a plant were redesigned with evidence-based guidelines and human factors input. 16 operators of varying experience were asked to read through and assess the new and old procedures. The new procedures were rated significantly or moderately better than their predecessors for efficiency, effectiveness, and subjective satisfaction. On average, inexperienced operators reported fewer inaccuracies, more confusion, and higher workload ratings than their experienced counterparts, regardless of procedure type or area. For satisfaction, experienced and inexperienced operators reported similar ratings across both procedure types and areas. Future studies should attempt to discern which particular change in the procedures contributed the most to increased usability, and whether operator experience significantly correlates with usability ratings.
|
Page generated in 0.0569 seconds