The Experts below are selected from a list of 135 Experts worldwide ranked by ideXlab platform
Joyce Yee - One of the best experts on this subject based on the ideXlab platform.
-
the role of the Interaction Designer in an agile software development process
Human Factors in Computing Systems, 2006Co-Authors: Matthew Lievesley, Joyce YeeAbstract:In this paper we describe observations of a contrast in thinking styles between a user-interface design team and a software engineering team developing a new software product. Presented in case study form, it is a first hand account by the Interaction Designers of work-in-progress. It concludes by identifying some key roles for the Interaction Designer working in an agile software development environment .
-
CHI Extended Abstracts - The role of the Interaction Designer in an agile software development process
CHI '06 extended abstracts on Human factors in computing systems - CHI EA '06, 2006Co-Authors: Matthew Lievesley, Joyce YeeAbstract:In this paper we describe observations of a contrast in thinking styles between a user-interface design team and a software engineering team developing a new software product. Presented in case study form, it is a first hand account by the Interaction Designers of work-in-progress. It concludes by identifying some key roles for the Interaction Designer working in an agile software development environment .
Ann Lantz - One of the best experts on this subject based on the ideXlab platform.
-
The Practice of Interaction Design
2010Co-Authors: Ann LantzAbstract:The aim with this paper is to look into the role of Interaction design and we investigate how Interaction Designers experience their work role, and, activities they perform. Semi-structured interviews were conducted with Interaction Designers. They do not have an overall view of the design process and are hired as internal consultants. The role of the Interaction Designer is included in the formal reports on how to conduct a development project. Often the Interaction Designer is used to work with a limited piece of the design process and the methods at hand. It is important to separate the role of the Interaction Designer from an old development tradition and move it to a more design-oriented way of thinking about Interaction design and the work of Interaction Designers.
-
HCIS - The Practice of Interaction Design
IFIP Advances in Information and Communication Technology, 2010Co-Authors: Ann LantzAbstract:The aim with this paper is to look into the role of Interaction design and we investigate how Interaction Designers experience their work role, and, activities they perform. Semi-structured interviews were conducted with Interaction Designers. They do not have an overall view of the design process and are hired as internal consultants. The role of the Interaction Designer is included in the formal reports on how to conduct a development project. Often the Interaction Designer is used to work with a limited piece of the design process and the methods at hand. It is important to separate the role of the Interaction Designer from an old development tradition and move it to a more design-oriented way of thinking about Interaction design and the work of Interaction Designers.
-
Interaction design in procurement: the view of procurers and Interaction Designers
CoDesign, 2010Co-Authors: Ann Lantz, Stefan HolmlidAbstract:Among those involved in human–computer Interaction (HCI) and user-centred design (UCD) the idea of co-design mainly applies to the software developer organisation and the users. In mainstream HCI research and in the literature only a few attend to the co-creation that occurs between IT acquirers and either users or software developers. Interaction design is central when it comes to designing a system that shows a high degree of use quality; often the Interaction Designer is working at the IT department and thus is ‘owned’ by the developers.This paper describes a case study of how procurers and Interaction Designers view the procurement process, the intention being to inform and improve the way that co-design is performed among procurers and developers. The study is conducted in an organisation that chose to include the Interaction design competence as part of the software acquisition organisation; we look at how different actors in the organisation view Interaction design and how Interaction design contributes to the software acquisition process.The Interaction Designers wish to work with more experienced procurers who know what they want. The procurers, on the other hand, want more control over the initial process, but are worried about how to present their requirements to the IT developers.
Matthew Lievesley - One of the best experts on this subject based on the ideXlab platform.
-
the role of the Interaction Designer in an agile software development process
Human Factors in Computing Systems, 2006Co-Authors: Matthew Lievesley, Joyce YeeAbstract:In this paper we describe observations of a contrast in thinking styles between a user-interface design team and a software engineering team developing a new software product. Presented in case study form, it is a first hand account by the Interaction Designers of work-in-progress. It concludes by identifying some key roles for the Interaction Designer working in an agile software development environment .
-
CHI Extended Abstracts - The role of the Interaction Designer in an agile software development process
CHI '06 extended abstracts on Human factors in computing systems - CHI EA '06, 2006Co-Authors: Matthew Lievesley, Joyce YeeAbstract:In this paper we describe observations of a contrast in thinking styles between a user-interface design team and a software engineering team developing a new software product. Presented in case study form, it is a first hand account by the Interaction Designers of work-in-progress. It concludes by identifying some key roles for the Interaction Designer working in an agile software development environment .
Panayotis E. Pintelas - One of the best experts on this subject based on the ideXlab platform.
-
Design of Interactivity in Virtual Reality Applications with Emphasis on Educational Software Using Formal Interaction Specification
Education and Information Technologies, 2000Co-Authors: Costas N. Diplas, Panayotis E. PintelasAbstract:Virtual Reality (VR) technology has already entered into the area of the educational software and delivers systems where the trainees can use interactive virtual microworlds and benefit by transfer of experience, interacting directly with the learning domain. This paper describes the Virtual Multi Flow Graph (Virtual-MFG) graphical formal model and the Interaction Specification Workspace (ISW) software architecture for the Interaction specification and design of VR applications with emphasis on educational software. The Interaction Designer specifies the Interaction issues of the final system formally, using the tools of ISW. The virtual microworld's objects database is updated with these Interaction specifications which include both the virtual objects' dynamic properties and their tutoring capabilities. The model is validated by applying it on an existing VR educational software (EIKON). The Virtual-MFG graphs specifying a learning scenario of EIKON along with the application of ISW on EIKON are also presented.
Brad A Myers - One of the best experts on this subject based on the ideXlab platform.
-
the state of the art in end user software engineering
ACM Computing Surveys, 2011Co-Authors: Andrew J Ko, Robin Abraham, Laura Beckwith, Alan F Blackwell, Margaret Burnett, Martin Erwig, Christopher Scaffidi, Joseph Lawrance, Henry Lieberman, Brad A MyersAbstract:Most programs today are written not by professional software developers, but by people with expertise in other domains working towards goals for which they need computational support. For example, a teacher might write a grading spreadsheet to save time grading, or an Interaction Designer might use an interface builder to test some user interface design ideas. Although these end-user programmers may not have the same goals as professional developers, they do face many of the same software engineering challenges, including understanding their requirements, as well as making decisions about design, reuse, integration, testing, and debugging. This article summarizes and classifies research on these activities, defining the area of End-User Software Engineering (EUSE) and related terminology. The article then discusses empirical research about end-user software engineering activities and the technologies designed to support them. The article also addresses several crosscutting issues in the design of EUSE tools, including the roles of risk, reward, and domain complexity, and self-efficacy in the design of EUSE tools and the potential of educating users about software engineering principles.