DOCSLIB.ORG

Isys Information Architects Inc

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Isys Information Architects Inc. Home Design Announcements Hall of Shame Isys Information Architects Inc. specializes in the design and development of New Entries robust, highly usable information systems. Isys focuses on ease of use, recognizing Controls that software should assist the user in the performance of some task rather than Stupidity becoming a task in itself. Isys was founded by Brian Hayes, a former professor of Visual Color Industrial Engineering, and system design consultant whose clients have included Terminology AT&T, General Electric, General Motors, Lucent Technologies, NASA, Siemens, Errors the U.S. Air Force, and the U.S. Army. Tabs Metaphors We are a full-service Our software development Globalization provider of user interface department specializes in the In-Depth design and usability design and development of engineering services. Our careful robust, highly usable information Books systems for the Windows operating Links attention to the user interface can system. We provide custom Index reduce system development time, Feedback increase user satisfaction, and reduce programming, database, and training costs. application development services. Hall of Fame Contact Us The Interface Hall of Shame The Interface Hall of is an irreverent look at Fame is a collection of ineffective interface design. images that demonstrate The site includes a collection of interface design solutions that are images from commercial, corporate, both creative and effective. and shareware applications that illustrate how software should not be designed. Isys Information Architects Inc. 5401 McNairy Drive, Suite 100 Greensboro, NC 27455 [email protected] © 1996-1999 Isys Information Architects Inc. All rights reserved. Reproduction in whole or in part in any form or medium without express written permission is prohibited. http://www.iarchitect.com/index.htm [14-02-2001 5:43:57 PM] Isys Interface Design and Usability Engineering Home Design Announcements Hall of Shame New Entries Controls Interface Design and Usability Stupidity Visual Engineering Color Terminology Overview Errors The look and feel of the application can be the single most important determinant of Tabs its value to the user. Isys Information Architects specializes in the design of highly Metaphors Globalization usable interfaces that are easily learned, minimize user frustration and maximize In-Depth user productivity. Books We begin with the system requirements and a few basic rules: Links Index ● Software must assist the user perform a task, not become a task in itself Feedback ● Software must not make the user feel stupid Hall of Fame ● Software must not make the computer appear to be stupid Contact Us Our overiding goal is to delight the user, which we accomplish by anticipating needs and exceeding expectations. Benefits Due to our careful attention to the user interface, Isys Information Architects can reduce system development time, increase end-user productivity, and reduce training costs. Background Isys Information Architects designers have provided design consultations, design seminars, and usability engineering services to a wide variety of national and multi-national companies. Isys Information Architects president, Brian C. Hayes, has taught undergraduate and graduate courses in human factors engineering and user interface design, and has conducted extensive research into GUI design and adaptive assistance software. List of Publications Our staff has provided design services in the following types of applications: http://www.iarchitect.com/mdesign.htm (1 of 2) [14-02-2001 5:44:12 PM] Isys Interface Design and Usability Engineering ● CMMS Applications ● Human Resource Management ● Computer Assisted Design ● Industrial Automation ● Computer-Assisted Instruction ● International Applications ● Customer Support ● Military Tactical Systems ● Database Reporting Systems ● Order-entry Retail Systems ● Facilities Layout and Design ● Telephony Systems ● Financial Applications Services Isys Information Architects serves as a facilitator between the users and developers of the application. We can help you attain the highest user satisfaction with your products by providing: ● User interface design specifications for new or legacy applications ● Evaluation of existing or proposed interface designs ● Analysis of existing task procedures and workflow ● Assistance with eliciting requirements from intended users ● Prioritization of user requirements ● Rapid and iterative prototyping of user requirements ● Usability evaluations and laboratory testing ● Tools and techniques for assessing usability ● Seminars in user interface design and usability engineering Isys Information Architects is a full-service provider of user interface design and usability engineering services. We will tailor our services to meet your specific needs. Contact us for further information, or to arrange a consultation to discuss your needs. Home - Design - Develop - Shame - Fame © 1996-1999 Isys Information Architects Inc. All rights reserved. Reproduction in whole or in part in any form or medium without express written permission is prohibited. [email protected] http://www.iarchitect.com/mdesign.htm (2 of 2) [14-02-2001 5:44:12 PM] Interface Hall of Shame - Announcements Interface Hall of Shame - Announcements - February 3, 2000 CALL FOR PARTICIPATION Second International Workshop on Internationalisation of Products and Systems (IWIPS2000). 13-15 July 2000, Baltimore, Maryland, USA. A previously announced deadline for submission of papers to IWIPS2000 has been extended to March 1, 2000. The revised call for papers is available at http://www.acm.org/~perlman/IWIPS2000.html. For details of last year's IWIPS workshop, visit http://webctr.net/IWIPS99/. January 17, 2000 Isys Information Architects has expanded its staff. Thomas Harrison Hayes, shown here being welcomed by Isys President Brian Hayes, was brought on board January 13, 2000, with the expectation that he will eventually assume an executive position within the company. During the next few months, the entire staff will be devoted to Thomas' transition to the company, which will likely contribute to delays in site updates and the staff's ability to respond to email in a timely manner. Additional images can be seen at Thomas' homepage, but be forewarned: I'm a new dad with a new digital camera and a cable modem. November 27, 1999 http://www.iarchitect.com/announce.htm (1 of 2) [14-02-2001 5:47:45 PM] Interface Hall of Shame - Announcements Bad GUI in the News J. Peter Mugaas send in a link to a press release describing a recent lawsuit filed against America Online on behalf of the National Federation for the Blind. A copy of the complaint is available at http://www.nfb.org/aolcompl.htm. The lawsuit alleges that AOL specifically designed its service and proprietary browser to be incompatible with screen access programs used by persons with visual impairments. The following features of the user interface were cited in the complaint as barriers to persons with visual impairments: the use of unlabeled graphics in place of text, the lack of keyboard access to controls and functionality, and the use of custom controls painted on the screen instead of the use of standard operating system controls. The suit alleges that as a result, the information on the screen cannot be converted by screen access programs such as screen readers and refreshable Braille displays. Hopefully, the implications of the lawsuit will be recognizable to those developers who emphasize "pretty" over good design. Home - Design - Shame - Fame © 2000 Isys Information Architects Inc. All rights reserved. Reproduction in whole or in part in any form or medium without express written permission is prohibited. [email protected] http://www.iarchitect.com/announce.htm (2 of 2) [14-02-2001 5:47:45 PM] Interface Hall of Shame Interface Hall of Shame The Interface Hall of Shame is an irreverent collection of common interface design mistakes. Our hope is that by highlighting these problems, we can help developers avoid making similar mistakes. We are constantly searching for examples of design practices that are worthy of extinction, and those worthy of emulation (see the Interface Hall of Fame). Submit your own nominations for potential entries into either hall to [email protected], and we'll try to add it to the collection. Our review of the new GUI in New Entries Apple's QuickTime 4.0 Player. 4-June-2000 Users of all operating systems should be concerned. Selecting the wrong control for a Nobody likes a stupid computer. task or changing the way controls However, many applications interrupt operate can often result in an the user to ask stupid questions, inefficient and frustrating provide meaningless information, or require the application. user to make what should be an obvious selection. Improper design of the visual elements The improper use color in an in an application can often result in application can seriously impede the applications that are difficult to read and usability of the application. difficult to use. The terminology used in many Error messages are the antithesis of applications often leads the user to proper application design. They are feel that the interface has been written often ambiguous, rude, and all too in a foreign language. We provide a number of often, incorrect, blaming the user for failures of examples of these 'programmerisms'. the programmer. Tabbed Dialogs can be a Metaphors can greatly enhance the wonderful solution for complex
Recommended publications
  • Cognitive and Usability Engineering Methods for the Evaluation of Clinical Information Systems

    Cognitive and Usability Engineering Methods for the Evaluation of Clinical Information Systems

    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Elsevier - Publisher Connector Journal of Biomedical Informatics 37 (2004) 56–76 www.elsevier.com/locate/yjbin Methodological Review Cognitive and usability engineering methods for the evaluation of clinical information systems Andre W. Kushniruka,* and Vimla L. Patelb a Information Technology Division, Department of Mathematics and Statistics, York University, Toronto, Canada b Laboratory of Decision Making and Cognition, Department of Biomedical Informatics, Columbia University, New York, NY Received 29 September 2003 Abstract Increasingly healthcare policy and decision makers are demanding evidence to justify investments in health information systems. This demand requires an adequate evaluation of these systems. A wide variety of approaches and methodologies have been applied in assessing the impact of information systems in health care, ranging from controlled clinical trials to use of questionnaires and interviews with users. In this paper we describe methodological approaches which we have applied and refined for the past 10 years for the evaluation of health information systems. The approaches are strongly rooted in theories and methods from cognitive science and the emerging field of usability engineering. The focus is on assessing human computer interaction and in particular, the usability of computer systems in both laboratory and naturalistic settings. The methods described can be a part of the formative evaluation of systems during their iterative development, and can also complement more traditional assessment methods used in summative system evaluation of completed systems. The paper provides a review of the general area of systems evaluation with the motivation and rationale for methodological approaches underlying usability engineering and cognitive task analysis as applied to health in- formation systems.
  • Qt/Embedded Whitepaper Trolltech Abstract This Whitepaper Describes the Qt/Embedded C++ Toolkit for GUI and Application Developm

    Qt/Embedded Whitepaper Trolltech Abstract This Whitepaper Describes the Qt/Embedded C++ Toolkit for GUI and Application Developm

    Qt/Embedded Whitepaper Trolltech www.trolltech.com Abstract This whitepaper describes the Qt/Embedded C++ toolkit for GUI and application development on embedded devices. It runs on any device supported by Linux and a C++ compiler. Qt/Embedded provides the entire standard Qt API and can compile out unused features to minimize its memory footprint. Qt/Embedded provides its own windowing system which is far more compact than Xlib and the X Window System that it replaces. Qt/Embedded applications can be developed on familiar desktop systems, e.g. Windows and Unix, and with standard tools. It is provided with all the Qt tools including Qt Designer for visual form design, and with tools specifically tailored to the embedded environment. The Sharp Zaurus PDA using Qt/Embedded ii Qt/Embedded Whitepaper Trolltech www.trolltech.com Contents 1. Introduction . 3 2. System Requirements . 4 3. Architecture . 5 3.1. Windowing System . 6 3.2. Fonts . 6 3.3. Input Devices . 7 3.4. Input Methods . 7 3.5. Screen Acceleration . 8 4. Development Environment . 8 4.1. Qt's Supporting Tools . 8 5. Signals and Slots . 9 5.1. A Signals and Slots Example . 10 5.2. Meta Object Compiler . 11 6. Widgets . 12 6.1. A `Hello' Example . 12 6.2. Common Widgets . 13 6.3. Canvas . 14 6.4. Custom Widgets . 15 6.5. Main Windows . 18 6.6. Menus . 18 6.7. Toolbars . 19 6.8. Balloon Help . 19 6.9. Actions . 20 7. Dialogs . 20 7.1. Layouts . 20 7.2. Qt Designer . 23 7.3. Built-in Dialogs .
  • Maestro 10.2 User Manual

    Maestro 10.2 User Manual

    Maestro User Manual Maestro 10.2 User Manual Schrödinger Press Maestro User Manual Copyright © 2015 Schrödinger, LLC. All rights reserved. While care has been taken in the preparation of this publication, Schrödinger assumes no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. Canvas, CombiGlide, ConfGen, Epik, Glide, Impact, Jaguar, Liaison, LigPrep, Maestro, Phase, Prime, PrimeX, QikProp, QikFit, QikSim, QSite, SiteMap, Strike, and WaterMap are trademarks of Schrödinger, LLC. Schrödinger, BioLuminate, and MacroModel are registered trademarks of Schrödinger, LLC. MCPRO is a trademark of William L. Jorgensen. DESMOND is a trademark of D. E. Shaw Research, LLC. Desmond is used with the permission of D. E. Shaw Research. All rights reserved. This publication may contain the trademarks of other companies. Schrödinger software includes software and libraries provided by third parties. For details of the copyrights, and terms and conditions associated with such included third party software, use your browser to open third_party_legal.html, which is in the docs folder of your Schrödinger software installation. This publication may refer to other third party software not included in or with Schrödinger software ("such other third party software"), and provide links to third party Web sites ("linked sites"). References to such other third party software or linked sites do not constitute an endorsement by Schrödinger, LLC or its affiliates. Use of such other third party software and linked sites may be subject to third party license agreements and fees. Schrödinger, LLC and its affiliates have no responsibility or liability, directly or indirectly, for such other third party software and linked sites, or for damage resulting from the use thereof.
  • Usability Basics for Software Developers Usability Engineering

    Usability Basics for Software Developers Usability Engineering

    focususability engineering Usability Basics for Software Developers Xavier Ferré and Natalia Juristo, Universidad Politécnica de Madrid Helmut Windl, Siemens AG, Germany Larry Constantine, Constantine & Lockwood n recent years, software system usability has made some interesting ad- vances, with more and more organizations starting to take usability seri- ously.1 Unfortunately, the average developer has not adopted these new I concepts, so the usability level of software products has not improved. Contrary to what some might think, us- Usability engineering defines the target us- This tutorial ability is not just the appearance of the user ability level in advance and ensures that the examines the interface (UI). Usability relates to how the software developed reaches that level. The system interacts with the user, and it includes term was coined to reflect the engineering ap- relationship five basic attributes: learnability, efficiency, proach some usability specialists take.3 It is between usability user retention over time, error rate, and sat- “a process through which usability character- and the user isfaction. Here, we present the general us- istics are specified, quantitatively and early in interface and ability process for building a system with the the development process, and measured desired level of usability. This process, which throughout the process.”4 Usability is an is- discusses how most usability practitioners apply with slight sue we can approach from multiple view- the usability variation, is structured around a design- points, which is why many different disci- process follows a evaluate-redesign cycle. Practitioners initiate plines, such as psychology, computer science, design-evaluate- the process by analyzing the targeted users and sociology, are trying to tackle it.
  • Learning to Code

    Learning to Code

    PART ILEARNING TO CODE How Important is Programming? “To understand computers is to know about programming. The world is divided… into people who have written a program and people who have not.” Ted Nelson, Computer Lib/Dream Machines (1974) How important is it for you to learn to program a computer? Since the introduction of the first digital electronic computers in the 1940s, people have answered this question in surprisingly different ways. During the first wave of commercial computing—in the 1950s and 1960s, when 1large and expensive mainframe computers filled entire rooms—the standard advice was that only a limited number of specialists would be needed to program com- puters using simple input devices like switches, punched cards, and paper tape. Even during the so-called “golden age” of corporate computing in America—the mid- to late 1960s—it was still unclear how many programming technicians would be needed to support the rapid computerization of the nation’s business, military, and commercial operations. For a while, some experts thought that well-designed computer systems might eventually program themselves, requiring only a handful of attentive managers to keep an eye on the machines. By the late 1970s and early 1980s, however, the rapid emergence of personal computers (PCs), and continuing shortages of computer professionals, shifted popular thinking on the issue. When consumers began to adopt low-priced PCs like the Apple II (1977), the IBM PC (1981), and the Commodore 64 (1982) by the millions, it seemed obvious that ground-breaking changes were afoot. The “PC Revolution” opened up new frontiers, employed tens of thousands of people, and (according to some enthusiasts) demanded new approaches to computer literacy.
  • Introducing Usability Engineering and Universal Design in the Computer Science Curriculum

    Introducing Usability Engineering and Universal Design in the Computer Science Curriculum

    Introducing Usability Engineering and Universal Design in the Computer Science Curriculum Authors: Kirsten Ribu, Oslo University College, Postboks 4, St. Olavs plass, 0130 Oslo, [email protected] Nes, Avenir, [email protected] Abstract ⎯ Software and information systems are usually developed for a stereotypical user: Young, white, male and non- disabled. In order to understand and include a variety of user groups, universal design and usability engineering must become part of the software engineering curriculum. Learning to develop systems for diverse user groups means that students must acquire knowledge of the relations between humans and technological solutions, as well as the requirements of disabled users. In order to communicate the importance and meaning of accessibility and usability, classroom exercises like using a computer with one hand, surfing the Internet wearing sunglasses or glasses smeared with oil or grease, and distorted computer screens can illustrate the challenges of designing software solutions for all users. We describe how students can be made aware of the social importance of software engineering, and conscious of professional and democratic responsibilities. The paper outlines suggestive curriculum, defining the major disabled user groups and their accessibility and usability requirements, and describes how to approach teaching universal design and usability. At Oslo University College, a new bachelor program called ‘Applied Computer Technology’ was initiated in 2005. The main focus of this program is the practical use of information systems in specific contexts, and the principles and ideas outlined in this paper will be incorporated into the third year course 'Modern Methods for Systems Development'. The students will work on real projects, developing solutions for real users.
  • Jaguar Quick Start Guide

    Jaguar Quick Start Guide

    Jaguar Quick Start Guide Jaguar 7.6 Quick Start Guide Schrödinger Press Jaguar Quick Start Guide Copyright © 2009 Schrödinger, LLC. All rights reserved. While care has been taken in the preparation of this publication, Schrödinger assumes no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. Canvas, CombiGlide, ConfGen, Epik, Glide, Impact, Jaguar, Liaison, LigPrep, Maestro, Phase, Prime, PrimeX, QikProp, QikFit, QikSim, QSite, SiteMap, Strike, and WaterMap are trademarks of Schrödinger, LLC. Schrödinger and MacroModel are registered trademarks of Schrödinger, LLC. MCPRO is a trademark of William L. Jorgensen. Desmond is a trademark of D. E. Shaw Research. Desmond is used with the permission of D. E. Shaw Research. All rights reserved. This publication may contain the trademarks of other companies. Schrödinger software includes software and libraries provided by third parties. For details of the copyrights, and terms and conditions associated with such included third party software, see the Legal Notices for Third-Party Software in your product installation at $SCHRODINGER/docs/html/third_party_legal.html (Linux OS) or %SCHRODINGER%\docs\html\third_party_legal.html (Windows OS). This publication may refer to other third party software not included in or with Schrödinger software ("such other third party software"), and provide links to third party Web sites ("linked sites"). References to such other third party software or linked sites do not constitute an endorsement by Schrödinger, LLC. Use of such other third party software and linked sites may be subject to third party license agreements and fees. Schrödinger, LLC and its affiliates have no responsibility or liability, directly or indirectly, for such other third party software and linked sites, or for damage resulting from the use thereof.
  • Oracle Clinical Getting Started Guide

    Oracle Clinical Getting Started Guide

    Oracle® Clinical Getting Started Release 4.6.2 E18819-01 April 2011 Oracle Clinical Getting Started, Release 4.6.2 E18819-01 Copyright © 2003, 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
  • Appleshare 3-0 Admin

    Appleshare 3-0 Admin

    APPLESHARE SERVER 3.0 ADMINISTRATOR'S QUICKSTART Before You Start This QuickStart is designed to help you get AppleShare Server 3.0 file and print servers ready and running in the shortest possible time. The QuickStart is divided into three sections: - Getting Started - Setting Up File Service - Setting Up Print Service You may not need to read all three sections -- only those that apply to your specific needs. For instance, if you know you will be setting up only a print server, you can skip to the section "Setting Up Print Service" after reading "Getting Started." Getting help This QuickStart assumes you're already familiar with basic Macintosh concepts and tech-niques. However, if you need additional information about AppleShare Server 3.0, you have two other sources of information: Balloon Help, which is built into the AppleShare Server 3.0 software, and the AppleShare Server 3.0 Administrator's Guide. Using Balloon Help If you don't understand the instructions in this guide -- or if you see a window, button, menu, or command you want to know more about -- use Balloon Help: 1. Choose Show Balloons from the Help menu. 2. Position the pointer over the item you want to know more about. A balloon appears with an explanation of that item. You can turn off Balloon Help at any time by choosing Hide Balloons from the Help menu. Using the AppleShare Server 3.0 Administrator's Guide If you still need more information after consulting Balloon Help, see the AppleShare Server 3.0 Administrator's Guide. It's easy to locate the information you need: Each section of this QuickStart corresponds to a section of the AppleShare Server 3.0 Administrator's Guide, where all procedures are explained in detail.
  • Newton 2.0 User Interface Guidelines

    Newton 2.0 User Interface Guidelines

    Newton 2.0 User Interface Guidelines Addison-Wesley Publishing Company Reading, Massachusetts Menlo Park, California New York Don Mills, Ontario Wokingham, England Amsterdam Bonn Sydney Singapore Tokyo Madrid San Juan Paris Seoul Milan Mexico City Taipei Apple Computer, Inc. Balloon Help, Espy, Geneva, the MERCHANTABILITY, OR FITNESS © 1996, 1994 Apple Computer, Inc. light bulb logo, MessagePad, FOR A PARTICULAR PURPOSE. AS A All rights reserved. NewtonScript, Newton Toolkit, New RESULT, THIS MANUAL IS SOLD “AS IS,” AND YOU, THE PURCHASER, No part of this publication may be York, QuickDraw, and System 7 are ARE ASSUMING THE ENTIRE RISK reproduced, stored in a retrieval trademarks of Apple Computer, Inc. AS TO ITS QUALITY AND system, or transmitted, in any form Adobe Illustrator and PostScript are ACCURACY. or by any means, mechanical, trademarks of Adobe Systems electronic, photocopying, recording, Incorporated, which may be IN NO EVENT WILL APPLE BE or otherwise, without prior written registered in certain jurisdictions. LIABLE FOR DIRECT, INDIRECT, permission of Apple Computer, Inc., FrameMaker is a registered SPECIAL, INCIDENTAL, OR except to make a backup copy of trademark of Frame Technology CONSEQUENTIAL DAMAGES any documentation provided on Corporation. RESULTING FROM ANY DEFECT OR CD-ROM. Printed in the United Helvetica and Palatino are INACCURACY IN THIS MANUAL, States of America. registered trademarks of Linotype even if advised of the possibility of such No licenses, express or implied, are Company. damages. granted with respect to any of the ITC Zapf Dingbats is a registered THE WARRANTY AND REMEDIES technology described in this book. trademark of International Typeface SET FORTH ABOVE ARE EXCLUSIVE Apple retains all intellectual Corporation.
  • What Is the Contribution of Personal Information Management Systems (PIMS) to the Working Model and Personal Work System of Knowledge Workers?

    What Is the Contribution of Personal Information Management Systems (PIMS) to the Working Model and Personal Work System of Knowledge Workers?

    Open Research Online The Open University’s repository of research publications and other research outputs What is the contribution of personal information management systems (PIMS) to the Working Model and personal work system of knowledge workers? Thesis How to cite: Gregory, Mark Roger (2017). What is the contribution of personal information management systems (PIMS) to the Working Model and personal work system of knowledge workers? PhD thesis The Open University. For guidance on citations see FAQs. c 2016 The Author Version: Version of Record Copyright and Moral Rights for the articles on this site are retained by the individual authors and/or other copyright owners. For more information on Open Research Online’s data policy on reuse of materials please consult the policies page. oro.open.ac.uk What is the contribution of personal information management systems (PIMS) to the Working Model and personal work system of knowledge workers? Mark Gregory, B.Sc. (Hons), M.Sc. Thesis submitted in partial fulfilment of the requirements for the degree of Ph.D. in Information Systems December 2016 The Open University Rennes School of Business Affiliated Research Centre ARC Supervisors: Prof. David Weir (Visiting Professor at York St John University) Dr. Renaud Macgilchrist (Rennes School of Business) Examiners: Prof. Trevor Wood-Harper (Manchester Business School) Dr. Tom Mcnamara (Rennes School of Business) 1 / 343 Abstract The thesis reports research into a phenomenon which it calls the personal working model of an individual knowledge worker. The principal conjecture addressed in this thesis is that each of us has a personal working model which is supported by a personal work system enabled by a personal information management system.
  • The Role of Usability in Software Validation - Case: Medical Device Manufacturing

    The Role of Usability in Software Validation - Case: Medical Device Manufacturing

    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Aaltodoc Publication Archive Aalto University School of Science Degree Programme in Computer Science and Engineering Emmi Kaivosoja The Role of Usability in Software Validation - Case: Medical Device Manufacturing Master’s Thesis Espoo, October 1, 2015 Supervisor: Professor Marko Nieminen, Dr.Sc. (Tech) Thesis advisor: Ninna Koivunen, M.Sc. Aalto University, P.O. BOX 11000, 00076 AALTO www.aalto.fi Abstract of master's thesis Author Emmi Kaivosoja Title of thesis The Role of Usability in Software Validation – Case: Medical Device Manufacturing Degree programme Degree Programme in Computer Science and Engineering Thesis supervisor Prof. Marko Nieminen, Dr.Sc. (Tech) Code of professorship T-121 Department Department of Computer Science Thesis advisor(s) Ninna Koivunen, M.Sc. Date 1.10.2015 Number of pages 9+77+2 Language English Abstract This master’s thesis follows a software project in a medical device company. The software is a manufacturing execution system (MES) which guides the production of medical devices and collects traceability data, including the device history files. Because the software is used in the manufacturing of medical devices and in the implementation of the company quality system, the software needs to be validated for its intended use. The validation process must comply with the guidance and regulations of the Food and Drug Administration. The software system is implemented by a software supplier but the customer organization is responsible for the validation process. In addition to fulfilling the regulatory requirements, the software is expected to increase productivity.