Integrating Usability, Semiotic, and Software Engineering into a Method for Evaluating User Interfaces

2011 ◽  
Author(s):  
Kenia Sousa
Keyword(s):  
Software Engineering ◽  
User Interfaces

Programmatic modeling for biological systems

2021 ◽  
Author(s):  
Alexander L.R. Lubbock ◽  
Carlos F. Lopez
Keyword(s):  
Software Engineering ◽  
Best Practices ◽  
Computational Modeling ◽  
User Interfaces ◽  
Model Development ◽  
List Type ◽  
Cellular Processes ◽  
Domain Specific ◽  
Community Benefits ◽  
Engineering Best Practices

AbstractComputational modeling has become an established technique to encode mathematical representations of cellular processes and gain mechanistic insights that drive testable predictions. These models are often constructed using graphical user interfaces or domain-specific languages, with SBML used for interchange. Models are typically simulated, calibrated, and analyzed either within a single application, or using import and export from various tools. Here, we describe a programmatic modeling paradigm, in which modeling is augmented with best practices from software engineering. We focus on Python - a popular, user-friendly programming language with a large scientific package ecosystem. Models themselves can be encoded as programs, adding benefits such as modularity, testing, and automated documentation generators while still being exportable to SBML. Automated version control and testing ensures models and their modules have expected properties and behavior. Programmatic modeling is a key technology to enable collaborative model development and enhance dissemination, transparency, and reproducibility.HighlightsProgrammatic modeling combines computational modeling with software engineering best practices.An executable model enables users to leverage all available resources from the language.Community benefits include improved collaboration, reusability, and reproducibility.Python has multiple modeling frameworks with a broad, active scientific ecosystem.

scholarly journals Ten years of software sustainability at the Infrared Processing and Analysis Center

2011 ◽  
Vol 369 (1949) ◽  
pp. 3384-3397 ◽  
Author(s):  
G. Bruce Berriman ◽  
John Good ◽  
Ewa Deelman ◽  
Anastasia Alexov
Keyword(s):  
Software Engineering ◽  
Best Practices ◽  
Software Architecture ◽  
User Interfaces ◽  
Image Mosaic ◽  
Analysis Center ◽  
Software Services ◽  
Careful Assessment ◽  
Over Time

This paper presents a case study of an approach to sustainable software architecture that has been successfully applied over a period of 10 years to astronomy software services at the NASA Infrared Processing and Analysis Center (IPAC), Caltech ( http://www.ipac.caltech.edu ). The approach was developed in response to the need to build and maintain the NASA Infrared Science Archive ( http://irsa.ipac.caltech.edu ), NASA's archive node for infrared astronomy datasets. When the archive opened for business in 1999 serving only two datasets, it was understood that the holdings would grow rapidly in size and diversity, and consequently in the number of queries and volume of data download. It was also understood that platforms and browsers would be modernized, that user interfaces would need to be replaced and that new functionality outside of the scope of the original specifications would be needed. The changes in scientific functionality over time are largely driven by the archive user community, whose interests are represented by a formal user panel. The approach has been extended to support four more major astronomy archives, which today host data from more than 40 missions and projects, to support a complete modernization of a powerful and unique legacy astronomy application for co-adding survey data, and to support deployment of M ontage , a powerful image mosaic engine for astronomy. The approach involves using a component-based architecture, designed from the outset to support sustainability, extensibility and portability. Although successful, the approach demands careful assessment of new and emerging technologies before adopting them, and attention to a disciplined approach to software engineering and maintenance. The paper concludes with a list of best practices for software sustainability that are based on 10 years of experience at IPAC.

Integrating Usability, Semiotic, and Software Engineering into a Method for Evaluating User Interfaces

2009 ◽  
pp. 448-464
Author(s):  
Kenia Sousa ◽  
Albert Schilling ◽  
Elizabeth Furtado
Keyword(s):  
User Interface ◽  
Software Engineering ◽  
Human Computer Interaction ◽  
User Interfaces ◽  
Usability Engineering ◽  
Ui Design ◽  
Usability Tests ◽  
Computer Interaction ◽  
Area Of Study

We present artifacts and techniques used for user interface (UI) design and evaluation, performed by professionals from the human-computer interaction (HCI) area of study, covering usability engineering and semiotic engineering, which can assist software engineering (SE) to perform usability tests starting earlier in the process. Tests of various interaction alternatives, produced from these artifacts, are useful to verify if these alternatives are in accordance with users’ preferences and constraints, and usability patterns, and can enhance the probability of achieving a more usable and reliable product.

Software Engineering for User Interfaces

1985 ◽  
Vol SE-11 (3) ◽  
pp. 252-258 ◽  
Author(s):  
S.W. Draper ◽  
D.A. Norman
Keyword(s):  
Software Engineering ◽  
User Interfaces

Teaching User Interface Development to Software Engineers

1988 ◽  
Vol 32 (5) ◽  
pp. 391-394 ◽  
Author(s):  
Gary Perlman
Keyword(s):  
User Interface ◽  
Software Engineering ◽  
Human Factors ◽  
User Interfaces ◽  
Task Analysis ◽  
Positive Impact ◽  
Empirical Evaluation ◽  
Applied Psychology ◽  
Graduate Curriculum ◽  
Software Engineers

Most software engineers have weak backgrounds in areas where human factors engineers are strong: task analysis, applied psychology, and empirical evaluation. Software engineers can become better builders of user interfaces if they are instructed in these techniques, and that is the main goal of the Software Engineering Institute's graduate curriculum module on user interface development. Parts of the module provide instruction about when, where, and how consultants such as human factors engineers can contribute to the design and evaluation of user interfaces. It is critical that human factors engineers understand how they can contribute during development, so that they can have the greatest positive impact.

scholarly journals Ontology Fixing by Using Software Engineering Technology

2020 ◽  
Vol 10 (18) ◽  
pp. 6328
Author(s):  
Gabriela R. Roldan-Molina ◽  
Jose R. Mendez ◽  
Iryna Yevseyeva ◽  
Vitor Basto-Fernandes
Keyword(s):  
Software Engineering ◽  
User Interfaces ◽  
Design Patterns ◽  
Application Programming Interface ◽  
Scientific Software ◽  
Engineering Technology ◽  
Ontology Evaluation ◽  
Ontology Quality ◽  
Quality Assessments

This paper presents OntologyFixer, a web-based tool that supports a methodology to build, assess, and improve the quality of ontology web language (OWL) ontologies. Using our software, knowledge engineers are able to fix low-quality OWL ontologies (such as those created from natural language documents using ontology learning processes). The fixing process is guided by a set of metrics and fixing mechanisms provided by the tool, and executed primarily through automated changes (inspired by quick fix actions used in the software engineering domain). To evaluate the quality, the tool supports numerical and graphical quality assessments, focusing on ontology content and structure attributes. This tool follows principles, and provides features, typical of scientific software, including user parameter requests, logging, multithreading execution, and experiment repeatability, among others. OntologyFixer architecture takes advantage of model view controller (MVC), strategy, template, and factory design patterns; and decouples graphical user interfaces (GUI) from ontology quality metrics, ontology fixing, and REST (REpresentational State Transfer) API (Application Programming Interface) components (used for pitfall identification, and ontology evaluation). We also separate part of the OntologyFixer functionality into a new package called OntoMetrics, which focuses on the identification of symptoms and the evaluation of the quality of ontologies. Finally, OntologyFixer provides mechanisms to easily develop and integrate new quick fix methods.

Integrating Usability, Semiotic, and Software Engineering into a Method for Evaluating User Interfaces

2009 ◽  
pp. 2307-2324
Author(s):  
Kenia Sousa ◽  
Albert Schilling ◽  
Elizabeth Furtado
Keyword(s):  
User Interface ◽  
Software Engineering ◽  
Human Computer Interaction ◽  
User Interfaces ◽  
Usability Engineering ◽  
Ui Design ◽  
Usability Tests ◽  
Computer Interaction ◽  
Area Of Study

We present artifacts and techniques used for user interface (UI) design and evaluation, performed by professionals from the human-computer interaction (HCI) area of study, covering usability engineering and semiotic engineering, which can assist software engineering (SE) to perform usability tests starting earlier in the process. Tests of various interaction alternatives, produced from these artifacts, are useful to verify if these alternatives are in accordance with users’ preferences and constraints, and usability patterns, and can enhance the probability of achieving a more usable and reliable product.

Multimodal Software Engineering

2011 ◽  
pp. 508-529
Author(s):  
Andreas Hartl
Keyword(s):  
User Interface ◽  
Software Engineering ◽  
Ubiquitous Computing ◽  
User Interfaces ◽  
Graphical User Interfaces ◽  
Application Development ◽  
Web Based ◽  
Adaptive Applications ◽  
Model Based ◽  
Interface Definition

Ubiquitous computing with its multitude of devices certainly makes it necessary to supplant the desktop metaphor of graphical user interfaces by other kinds of user interfaces. Applications must adapt themselves to many modalities: they must support a wide variety of devices and interaction languages. Software engineering methods and tools also need to embrace this change so that developers can build usable adaptive applications more easily. This chapter will present three different software engineering approaches that address this challenge: extensions to Web-based approaches, abstract user interface definitions that add a level of abstraction to the user interface definition, and model-based approaches that extend model-based application development to integrate user interface issues as well.

Integrating Usability, Semiotic, and Software Engineering into a Method for Evaluating User Interfaces

2007 ◽  
pp. 55-81
Author(s):  
Kenia Sousa ◽  
Albert Schilling ◽  
Elizabeth Furtado
Keyword(s):  
User Interface ◽  
Software Engineering ◽  
Human Computer Interaction ◽  
User Interfaces ◽  
Usability Engineering ◽  
Ui Design ◽  
Usability Tests ◽  
Computer Interaction ◽  
Area Of Study

We present artifacts and techniques used for user interface (UI) design and evaluation, performed by professionals from the human-computer interaction (HCI) area of study, covering usability engineering and semiotic engineering, which can assist software engineering (SE) to perform usability tests starting earlier in the process. Tests of various interaction alternatives, produced from these artifacts, are useful to verify if these alternatives are in accordance with users’ preferences and constraints, and usability patterns, and can enhance the probability of achieving a more usable and reliable product.

Sign in / Sign up

Export Citation Format

Share Document