DOCSLIB.ORG

Relevant Norms and Standards

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Relevant Norms and Standards Appendix A Relevant norms and standards A.1 A Short Overview of the Most Relevant Process Standards There is a huge number of different process standards, and Fig. A.1 contains an overview of the most relevant such standards as covered in this book, showing the topics covered. A more extensive list of the relevant standards will be provided in the following section below. ISO/IEC 15504, ISO 19011 ISO/IEC 330xx Auditing man- agement systems Process Process assessment ISO/IEC 20000-1 ISO 9001 ISO/IEC 15504-6 ISO/IEC 15504-5 Service management QM system re- System life cycle PAM Software life cycle PAM Assessments, audits Criteria system requirements quirements ISO/IEC/IEEE 15288 ISO/IEC/IEEE 12207 ITIL System life cy- Software life cy- IT Infrastruc- cle processes cle processes ture Library COBIT Life cycle processes SWEBoK Software engineering Funda- Body of Knowledge mentals ISO/IEC/IEEE 24765 ISO 9000 Systems and SW Engineering Vocabulary QM fundamentals (SEVOCAB) and vocabulary Vocabulary Systems Software Organzational IT Quality Management Engineering Engineering Fig. A.1 Overview of the most important standards for software processes © Springer Nature Switzerland AG 2018 327 R. Kneuper, Software Processes and Life Cycle Models, https://doi.org/10.1007/978-3-319-98845-0 328 A Relevant norms and standards A.2 ISO and IEC Standards The International Organization for Standardization (ISO) is the main international standard-setting organisation, working with representatives from many national standard-setting organisations. Standards referring to electrical, electronic and re- lated technologies, including software, are often published jointly with its sister organisation, the International Electrotechnical Commission (IEC), but IEC also publishes a number of standards on their own. Recently, ISO and IEC started to publish relevant standards jointly with the US- American Institute of Electrical and Electronics Engineers (IEEE). IEEE also pub- lished a number of relevant standards on their own, see Sect. A.3. The following table lists the main standards that are relevant in the context of software processes. The editions are the latest editions of these standards at the time of writing. The list is ordered by the numbers of the standards, independent of the exact organisation(s) that published it. Many of the norms and standards in this list were also re-published by other national and international organisations, sometimes after translation into another language. For example, the norm ISO 9001 listed below was also published as a European norm EN ISO 9001, and as a German national norm DIN EN ISO 9001 (and similarly in many other countries as well). “TR” in the identification of a standard shows that this document is published by ISO as a technical report as opposed to an international standard. Similarly, “TS” identifies a technical standard issued by ISO. The year at the end of the ID of any of these standards, after the colon, defines the year when this standard was released. In general, ISO and IEC standards must be bought and tend to be fairly expensive. However, some of the following standards are available for free download from the ISO web page at [5]. These standards are marked (*) in the list below. ISO 9000:2015 Quality management systems—Fundamentals and vocabu- lary ISO 9001:2015 Quality management systems—Requirements ISO 9004:2009 Managing for the sustained success of an organization—A quality management approach ISO/IEC 9126:2001 Software engineering—Product quality—Part 1: Quality model (replaced by ISO/IEC 25010, see below) ISO/IEC/IEEE 12207:2017 Systems and software engineering—Software life cy- cle processes ISO/IEC 13719-1:1998 Information technology—Portable Common Tool Envi- ronment (PCTE)—Part 1: Abstract specification ISO 13849-1:2015 Safety of machinery—Safety-related parts of control sys- tems—Part 1: General principles for design ISO 13849-2:2012 Safety of machinery—Safety-related parts of control sys- tems—Part 2: Validation ISO/IEC/IEEE 15288:2015 Systems and software engineering—System life cy- cle processes A.2 ISO and IEC Standards 329 ISO/IEC 15408-1:2009 Information technology—Security techniques—Evalua- tion criteria for IT security—Part 1: Introduction and gen- eral model (*) ISO/IEC 15408-3:2008 Information technology—Security techniques—Evalua- tion criteria for IT security—Part 3: Security assurance components (*) ISO/IEC 15504-1:2011 Information technology—Process assessment—Part 1: Concepts and vocabulary (replaced by ISO/IEC 33001, see below) ISO/IEC 15504-2:2011 Information technology—Process assessment—Part 2: Performing an assessment (replaced by ISO/IEC 33002, see below) ISO/IEC 15504-5:2012 Information technology—Process assessment—Part 5: An exemplar software life cycle process assessment model ISO/IEC 15504-6:2013 Information technology—Process assessment—Part 6: An exemplar system life cycle process assessment model ISO/IEC TS 15504-8:2012 Information technology—Process assessment—Part 8: An exemplar process assessment model for IT service man- agement ISO/IEC 15939:2017 Systems and software engineering—Measurement process ISO/TS 16949:2009 Quality management systems—Particular requirements for the application of ISO 9001:2008 for automotive produc- tion and relevant service part organizations. (Withdrawn and replaced by IATF 16949:20161) ISO 19011:2011 Guidelines for auditing management systems ISO/IEC 19508:2014 Information technology—Object Management Group Meta Object Facility (MOF) Core (*) ISO/IEC TR 19759:2015 Software Engineering—Guide to the software engineer- ing body of knowledge (SWEBOK R ) (*) ISO/IEC 20000-1:2011 Information technology—Service management—Part 1: Service management system requirements ISO/IEC 20000-2:2012 Information technology—Service management—Part 2: Guidance on the application of service management sys- tems ISO/IEC TR 20000-4:2010 Information technology—Service management— Part 4: Process reference model ISO/IEC TR 20000-10:2015 Information technology—Service management— Part 10: Concepts and terminology (*) ISO 21505:2017 Project, programme and portfolio management—Guidance on governance ISO/TS 22163:2017 Railway applications—Quality management systems—Par- ticular requirements for the application of ISO 9001:2015 in the rail sector 1 IATF=International Automotive Task Force is a group of major automotive manufacturers. 330 A Relevant norms and standards ISO/IEC 24744:2014 Software Engineering—Metamodel for Development Meth- odologies ISO/IEC TR 24748:2016 Systems and software engineering—Life cycle manage- ment—Part 1: Guidelines for life cycle management ISO/IEC/IEEE 24765:2017 Systems and software engineering—Vocabulary (*)2 ISO/IEC TR 24774:2010 Systems and software engineering—Life cycle manage- ment—Guidelines for process description (*) ISO/IEC 25000:2014 Systems and software engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—Guide to SQuaRE ISO/IEC 25010:2011 Systems and software engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—System and software quality models ISO 26262-6:2011 Road vehicles—Functional safety—Part 6: Product devel- opment at the software level ISO/IEC 27000:2014 Information technology—Security techniques—Information security management systems—Overview and vocabulary (*) ISO/IEC 27001:2015 Information technology—Security techniques—Information security management systems—Requirements ISO/IEC 27002:2013 Information technology—Security techniques—Code of prac- tice for information security controls ISO/IEC 27005:2011 Information technology—Security techniques—Information security risk management ISO/IEC 29100:2011 Information technology—Security techniques—Privacy frame- work (*) ISO/IEC TR 29110-1:2016 Systems and software engineering—Lifecycle pro- files for Very Small Entities (VSEs)—Part 1: Overview (*) ISO/IEC TR 29110-3:2015 Systems and software engineering—Lifecycle pro- files for Very Small Entities (VSEs)—Part 3–1: Assessment guide (*) ISO/IEC/IEEE 29119-1:2013 Software Testing—Concepts & definitions ISO/IEC/IEEE 29119-2:2013 Software Testing—Test processes ISO/IEC/IEEE 29119-3:2013 Software Testing—Test documentation ISO 31000:2009 Risk management—Principles and guidelines ISO/IEC 33001:2015 Information technology—Process assessment—Concepts and terminology ISO/IEC 33002:2015 Information technology—Process assessment—Requirements for performing process assessment ISO/IEC 33003:2015 Information technology—Process assessment—Requirements for process measurement frameworks 2 The definitions from ISO/IEC/IEEE 24765, also known as the Software and Systems Engi- neering Vocabulary SEVOCAB, are available online at https://pascal.computer.org/ sev_display/index.action (last access 2017-12-09) where they are continuously updated. A.3 Other Relevant Standard Documents 331 ISO/IEC 33004:2015 Information technology—Process assessment—Require- ments for process reference, process assessment and ma- turity models ISO/IEC TR 33014:2013 Information technology—Process assessment—Guide for process improvement ISO/IEC 33020:2015 Information technology—Process assessment—Process mea- surement framework for assessment of process capability ISO/IEC 38500:2015 Information technology—Governance of IT for the organi- zation IEC 61508-2:2010 Functional safety of electrical/electronic/programmable elec- tronic safety-related systems—Part 2: Requirements for electrical/electronic/programmable electronic safety-related systems IEC 61508-3:2010 Functional safety of electrical/electronic/programmable
Load more

Recommended publications
  • System Manual Pdm360smart Monitor CR1070 CR1071 Codesys® V2.3 Target V05 English
    System Manual PDM360smart monitor CR1070 CR1071 CoDeSys® V2.3 Target V05 English 7390674_01_UK 2012-05-16 2012-05-16 7390674_01_UK ifm System Manual ecomatmobile PDM360smart (CR1070, CR1071) Target V05 2012-05-16 Contents Contents 1 About this manual 7 1.1 What do the symbols and formats mean? ......................................................................7 1.2 How is this manual structured?.......................................................................................8 2 Safety instructions 9 2.1 Important!........................................................................................................................9 2.2 What previous knowledge is required?.........................................................................10 3 System description 11 3.1 Information concerning the device................................................................................11 3.2 Information concerning the software.............................................................................11 3.3 PLC configuration .........................................................................................................12 4 Configurations 13 4.1 Set device parameters (setup)......................................................................................13 4.1.1 Start set-up ..............................................................................................................14 4.1.2 Show the current device settings.............................................................................15 4.1.3 Change
    [Show full text]
  • Medical Devices
    FRAUNHOFER INSTITUTE FOR EXPERIMENTAL SOFTWARE ENGINEERING IESE MEDICAL DEVICES Contact Fraunhofer Institute for Experimental Software Engineering IESE Ralf Kalmar Software is a part of our lives. Embedded into everyday equipment, into living and working en- [email protected] vironments or modern means of transportation, countless processors and controllers make our Phone: +49 631 6800-1603 lives simpler, safer, and more pleasant. We help organizations to develop software systems that www.iese.fraunhofer.de are dependable in every aspect, and empirically validate the necessary processes, methods, and techniques, emphasizing engineering-style principles such as measurability and transparency. Fraunhofer Institute for The Fraunhofer Institute for Experimental Software Engineering IESE in Kaiserslautern has been Experimental Software one of the world’s leading research institutes in the area of software and systems engineering Engineering IESE for more than 20 years. Its researchers have contributed their expertise in the areas of Process- es, Architecture, Security, Safety, Requirements Engineering, and User Experience in more than Fraunhofer-Platz 1 1,200 projects. 67663 Kaiserslautern Germany Under the leadership of Prof. Peter Liggesmeyer, Fraunhofer IESE is working on innovative topics related to digital ecosystems, such as Industrie 4.0, Big Data, and Cyber-Security. As a technology and innovation partner for the digital transformation in the areas of Autonomous & Cyber-Physical Systems and Digital Services, the institute’s research focuses on the interaction between embedded systems and information systems in digital ecosystems. Fraunhofer IESE is one of 72 institutes and research units of the Fraunhofer-Gesellschaft. To- gether they have a major impact on shaping applied research in Europe and contribute to Ger- many’s competitiveness in international markets.
    [Show full text]
  • ECSO State of the Art Syllabus V1 ABOUT ECSO
    STATE OF THE ART SYLLABUS Overview of existing Cybersecurity standards and certification schemes WG1 I Standardisation, certification, labelling and supply chain management JUNE 2017 ECSO State of the Art Syllabus v1 ABOUT ECSO The European Cyber Security Organisation (ECSO) ASBL is a fully self-financed non-for-profit organisation under the Belgian law, established in June 2016. ECSO represents the contractual counterpart to the European Commission for the implementation of the Cyber Security contractual Public-Private Partnership (cPPP). ECSO members include a wide variety of stakeholders across EU Member States, EEA / EFTA Countries and H2020 associated countries, such as large companies, SMEs and Start-ups, research centres, universities, end-users, operators, clusters and association as well as European Member State’s local, regional and national administrations. More information about ECSO and its work can be found at www.ecs-org.eu. Contact For queries in relation to this document, please use [email protected]. For media enquiries about this document, please use [email protected]. Disclaimer The document was intended for reference purposes by ECSO WG1 and was allowed to be distributed outside ECSO. Despite the authors’ best efforts, no guarantee is given that the information in this document is complete and accurate. Readers of this document are encouraged to send any missing information or corrections to the ECSO WG1, please use [email protected]. This document integrates the contributions received from ECSO members until April 2017. Cybersecurity is a very dynamic field. As a result, standards and schemes for assessing Cybersecurity are being developed and updated frequently.
    [Show full text]
  • Building Functional Safety Into Industrial Robotics
    BUILDING FUNCTIONAL SAFETY INTO INDUSTRIAL ROBOTICS Rian Whitton Principal Analyst EXECUTIVE SUMMARY TABLE OF CONTENTS Functional safety is critical to many modern robotic applications and will become more so. In the near future, many robots will run in areas where they interact directly Executive Summary ................................1 and indirectly with workers, and the tasks they perform will disproportionately relate The Market for Industrial Robotics ...........2 The Potential of the Robotics Industry .....................2 to production logistics and moving goods for the general public. If a robot malfunctions, New Robots, New Demands ...................................4 there is a risk to the surrounding workers, to product safety, and to public safety. This Functional Safety Is Crucial for the Industry to Meet risk amplifies as robots are increasingly required to handle multiple tasks and navigate Its Potential ............................................................5 Regulations .............................................................6 crowded environments. So, mitigating safety risks under these conditions will become Embedded Systems for Robotics ..............7 a fundamental requirement that cannot be addressed without considering security as RTOS and the Benefits of Microkernel an integral part of robot design. Architecture ............................................................8 Hypervisors-as-a-Solution .......................................9 This is where functional safety of the underlying software and
    [Show full text]
  • Catalog of GA Control Systems
    GA automation technology product catalog Contact information GEBHARDT Automation GmbH Thüngenfeld 3 D- 58256 Ennepetal Germany Tel.: +49 2333 7908 - 0 available during working hours, Mo to Fr, from 800 to 1700 (5 pm) central european time (CET, GMT+1). FAX: +49 2333 7908 - 24 Web: www.gebhardt-automation.de Support [email protected] Information [email protected] Date: 10/2012 GA catalog_Rev 02.01_2012-10-09 en.doc page 2 of 40 Contents GA BlueLine Systems ............................................................................................................4 Redundancy, fault tolerance and voting...............................................................................................5 Machinery Monitoring Systems............................................................................................................6 Monitoring Capabilities.........................................................................................................................7 GA TMR/10-S.......................................................................................................................................8 GA TMR SMART-S ..............................................................................................................................9 GA DUPLEX/7-S ................................................................................................................................10 GA DUPLEX SMART-S .....................................................................................................................11
    [Show full text]
  • Evaluation of Open Source Operating Systems for Safety-Critical Applications Master’S Thesis in Embedded Electronic System Design
    Evaluation of open source operating systems for safety-critical applications Master’s thesis in Embedded Electronic System Design Petter Sainio Berntsson Department of Computer Science and Engineering CHALMERS UNIVERSITY OF TECHNOLOGY UNIVERSITY OF GOTHENBURG Gothenburg, Sweden 2017 MASTER’S THESIS 2017 Evaluation of open source operating systems for Safety-critical applications Petter Sainio Berntsson Department of Computer Science and Engineering Chalmers University of Technology University of Gothenburg Gothenburg, Sweden 2017 Evaluation of open source operating systems for safety-critical applications Petter Sainio Berntsson © Petter Sainio Berntsson, 2017 Examiner: Per Larsson-Edefors Chalmers University of Technology Department of Computer Science and Engineering Academic supervisor: Jan Jonsson Chalmers University of Technology Department of Computer Science and Engineering Industrial supervisors: Lars Strandén RISE Research Institutes of Sweden Dependable Systems Fredrik Warg RISE Research Institutes of Sweden Dependable Systems Master’s Thesis 2017 Department of Computer Science and Engineering Chalmers University of Technology University of Gothenburg SE-412 96 Gothenburg Telephone +46(0) 31 772 1000 Abstract Today many embedded applications will have to handle multitasking with real-time time constraints and the solution for handling multitasking is to use a real-time operating system for scheduling and managing the real-time tasks. There are many different open source real-time operating systems available and the use of open source software for safety-critical applications is considered highly interesting by industries such as medical, aerospace and automotive as it enables a shorter time to market and lower development costs. If one would like to use open source software in a safety-critical context one would have to provide evidence that the software being used fulfills the requirement put forth by the industry specific standard for functional safety, such as the ISO 26262 standard for the automotive industry.
    [Show full text]
  • SAFE TORQUE OFF a Guide to the Application of the Control Techniques Safe Torque Off Safety Function and Its Compliance with IEC 61800-5-2 SAFE TORQUE OFF
    SAFE TORQUE OFF A guide to the application of the Control Techniques Safe Torque Off safety function and its compliance with IEC 61800-5-2 SAFE TORQUE OFF 1. Purpose of this guide This application guide gives general explanations, advice and guidance for the use of the Safe Torque Off (STO) feature which is provided in many of Control Techniques’ variable speed drive products. It supplements the specific product information given in the product Technical Guides. In the event of any discrepancy the product Technical Guide takes precedence. Most of the information is general in nature and applies to all models. Some model- specific information is given in Annex 1. Important warnings The design of safety-related systems requires specialist knowledge. To ensure that a complete control system is safe it is necessary for the whole system to be designed according to recognised safety principles. The use of individual sub-systems such as drives with Safe Torque Off functions, which are intended for safety- related applications, does not in itself ensure that the complete system is safe. The information given in this publication gives guidance on the application of Control Techniques Safe Torque Off, and also some general background material on the design of safety-related systems for machinery control. This publication is not intended to form a complete guide to the subject. Some more detailed references are given at the end of the guide. The information provided is believed to be correct and to reflect accepted practice at the time of writing. It is the responsibility of the designer of the end product or application to ensure that it is safe and in compliance with the relevant regulations.
    [Show full text]
  • Thesis and Dissertation Template
    DEVELOPMENT OF A QUALITY MANAGEMENT ASSESSMENT TOOL TO EVALUATE SOFTWARE USING SOFTWARE QUALITY MANAGEMENT BEST PRACTICES Item Type Other Authors Erukulapati, Kishore Publisher Cunningham Memorial library, Terre Haute,Indiana State University Download date 23/09/2021 23:31:43 Link to Item http://hdl.handle.net/10484/12347 DEVELOPMENT OF A QUALITY MANAGEMENT ASSESSMENT TOOL TO EVALUATE SOFTWARE USING SOFTWARE QUALITY MANAGEMENT BEST PRACTICES _______________________ A Dissertation Presented to The College of Graduate and Professional Studies College of Technology Indiana State University Terre Haute, Indiana ______________________ In Partial Fulfillment of the Requirements for the Degree Doctor of Philosophy _______________________ by Kishore Erukulapati December 2017 © Kishore Erukulapati 2017 Keywords: Software Quality, Technology Management, Software Quality Management, Bibliometric techniques, Best Practices VITA Kishore Erukulapati EDUCATION Ph.D. Indiana State University (ISU), Terre Haute, IN. Technology Management, 2017. M.S. California State University (CSU), Dominguez Hills, CA. Quality Assurance, 2011. B.Tech. National Institute of Technology (NIT), Calicut, Kerala, India. Computer Science and Engineering, 1996. INDUSTRIAL EXPERIENCE 2011-Present Hawaii Medical Service Association. Position: Senior IT Consultant. 2008-2010 Telvent. Position: Operations Manager. 2008-2008 ACG Tech Systems. Position: Test Manager. 2000-2008 IBM Global Services. Position: Project Manager. 1996-2000 Tata Consultancy Services. Position: System Analyst. PUBLICATIONS/PRESENTATIONS Erukulapati, K., & Sinn, J. W. (2017). Better Intelligence. Quality Progress, 50 (9), 34-40. Erukulapati, K. (2016). What Can Software Quality Engineering Contribute to Cybersecurity?. Software Quality Professional, 19(1). Erukulapati, K. (2015, Dec 2). Information Technology in Healthcare: Current Status and Future Perspectives. Presented at IEEE Hawaii Chapter - Computer Society Meeting, Honolulu, Hawaii.
    [Show full text]
  • Components DISTRIBUTOR
    The REGION’S LARGEST Essential Components DISTRIBUTOR www.cbtcompany.com Why essential components? Get the right components, at the right price, right when you need them. CBT offers you quality Allen-Bradley® essential components with 110 years of time-tested quality and durability. This catalog is your initial guide to selecting the best components to meet your specific appli- cation requirements. With Allen-Bradley®’s product portfolio, you will find the highest quality components at a fair price, an intuitive product selection, and fast delivery. Additionally, you will receive components that perform to your specifications, accompanied by the professional knowledge and support of CBT’s industry special- ists, you will receive components that perform to your specifications and make up the complete system you need. Smart devices include: Variable Frequency Servo Motor Condition Drives Drives Starters Monitoring Smart devices make data-driven productivity improvements using smart devices At its most basic level, The Connected Enterprise is about enabling the equipment, machinery, and devices in a manufacturing plant to provide real-time information that can help optimize plant operations. Rockwell Automation smart devices help you: • Increase productivity • Produce higher-quality products at lower costs • Support regulatory compliance • Identify and address worker-safety issues • Optimize supply chains Smart devices are the foundation of integrated control and information, providing seamless connectivity and the raw data for your Connected
    [Show full text]
  • Standards Publications
    IRISH STANDARDS PUBLISHED BASED ON CEN/CENELEC STANDARDS 1. I.S. 178:1973 Date published 28 SEPTEMBER 2005 Extruded Rigid PVC Corrugated Sheeting 2. I.S. EN 60835-1-2:1993 Date published 1 JUNE 2005 Methods of measurement for equipment used in digital microwave radio transmission systems -- Part 1: Measurements common to terrestrial radio-relay systems and satellite earth stations -- Section 2: Basic characteristics (IEC 60835-1-2:1992 (EQV)) 3. I.S. EN 160000:1993/A1:1996 Date published 1 JUNE 2005 Generic Specification: Modular electronic units 4. I.S. EN 61595-1:1999 Date published 1 JUNE 2005 Multichannel digital audio tape recorder (DATR), reel-to-reel system, for professional use -- Part 1: Format A (IEC 61595-1:1997 (EQV)) 5. I.S. EN 1990:2002+NA:2010 Date published 24 MARCH 2005 Eurocode - Basis of structural design (including Irish National Annex) 6. I.S. EN ISO 14122-4:2004 Date published 23 FEBRUARY 2005 Safety of machinery - Permanent means of access to machinery - Part 4: Fixed ladders (ISO 14122-4:2004) 7. I.S. EN 13877-1:2004 Date published 23 SEPTEMBER 2005 Concrete pavements - Part 1: Materials 8. I.S. EN 13877-2:2004 Date published 23 SEPTEMBER 2005 Concrete pavements - Part 2: Functional requirements for concrete pavements 9. I.S. EN 12843:2004 Date published 4 MARCH 2005 Precast concrete products - Masts and poles 10. I.S. EN 13225:2005 Date published 4 MARCH 2005 Precast concrete products - Linear structural elements 11. I.S. EN 13693:2004 Date published 4 MARCH 2005 Precast concrete products - Special roof elements 12.
    [Show full text]
  • Quality Factors for Mobile Medical Apps
    _________________________________________________________________________________________________________________Proceedings of the Central European Conference on Information and Intelligent Systems 229 Quality Factors for Mobile Medical Apps Nadica Hrgarek Lechner Vjeran Strahonja MED-EL Elektromedizinische Geräte GmbH Faculty of Organization and Informatics Fürstenweg 77, 6020 Innsbruck, Austria Pavlinska 2, 42000 Varaždin, Croatia [email protected] [email protected] Abstract. The increased use of mobile phones, less in healthcare. According to a report from the smartphones, tablets, and connected wearable devices business consulting firm Grand Review Research, Inc. has fostered the development of mobile medical (2016), the global connected health and wellness applications (apps) in the last few years. Mobile devices market is expected to reach USD 612.0 billion medical apps are developed to extend or replace some by 2024. existing applications that run on a desktop or laptop The results of the sixth annual study on mobile computer, or on a remote server. health app publishing done by research2guidance If mobile apps are used, for example, to diagnose, (2016) are based on 2,600 plus respondents who mitigate, treat, cure, or prevent human diseases, participated in the online survey. As displayed in Fig. patient safety is at potential risk if the apps do not 1, remote monitoring, diagnostic, and medical function as intended. Therefore, such apps need to be condition management apps are the top three mHealth cleared, approved, or otherwise regulated in order to app types offering the highest market potential in the protect public health. next five years. In 2016, 32% of total respondents There are many papers that have been published predicted remote monitoring apps as the app category about the quality attributes of mobile apps.
    [Show full text]
  • Safety Guide for the Americas
    Safety Guide for the Americas Six steps to a safe machine Contents Six steps to a safe machine Six steps to a safe machine Contents Six steps to a safe machine Laws, directives, standards, liability g §-1 • Regulatory requirements g §-1 • European directives g §-4 • Obligations of the machine manufacturer g §-5 • Standards g §-9 § • International/European standards g §-11 • Nationally recognized testing labs g §-14 • Test bodies, insurance providers, and authorities g §-15 Risk assessment g 1-1 • The risk assessment process g 1-1 • Functions of the machine g 1-3 • Identification of tasks and hazards g 1-4 1 • Risk estimation and risk evaluation g 1-5 • Documentation g 1-6 Safe design g 2-3 • Mechanical design g 2-3 • Operating and maintenance concept g 2-4 • Electrical installation g 2-5 • Enclosure ratings g 2-8 • Lock-out/tag-out g 2-10 2 • Stop functions g 2-11 g • Electromagnetic compatibility (EMC) 2-12 2-1 • Fluid technology g 2-14 g g • Use in potentially explosive atmospheres 2-15 c Design of the safety function g 3-1 Technical protective measures • Development of the safety concept g 3-13 g • Selection of the protective devices g 3-18 a Definition of the safety functions 3-2 g b Determination of the required g 3-9 • Positioning and dimensioning of 3-44 safety level protective devices • Integration of protective devices into g 3-65 3 the control system Implementation of the safety functions • Product overview for safeguarding g 3-76 d Verification of the safety function g 3-79 e Validation of all safety functions g 3-95 Risk reduction
    [Show full text]