نتایج جستجو برای: software fmea requirement analysis

تعداد نتایج: 3234165  

Journal: :Complex Systems Informatics and Modeling Quarterly 2016

2015
Nadia Belu Laurentiu M. Ionescu

In this paper we propose a computer-aided solution with Genetic Algorithms in order to reduce the drafting of reports: FMEA analysis and Control Plan required in the manufacture of the product launch and improved knowledge development teams for future projects. The solution allows to the design team to introduce data entry required to FMEA. The actual analysis is performed using Genetic Algorit...

2014
Tor Stålhane Vikash Katta Thor Myklebust

Any change that will influence the system’s safety requirements after we have finished the safety analysis and safety planning for development of safety-critical software will require a change impact analysis. One of the reasons for using Scrum is its declarations to “embrace change”. Using agile development we may add new requirements, change existing requirements and make current requirements...

2002
Fumihiko Kimura Tomoyuki Hata Noritomo Kobayashi

For proper management of life cycle of machines and manufacturing facilities, it is important to perform appropriate maintenance operations, and to keep machine status for better reuse and recycling opportunity. For this purpose, a virtual maintenance system is very effective, where facility life cycle model is constructed in computer, and reliability and availability of machines are predicted ...

2011
Ilya Lopatkin Alexei Iliasov Alexander Romanovsky Yuliya Prokhorova Elena Troubitsyna I. Lopatkin

Failure Modes and Effect analysis (FMEA) is a widely used technique for inductive safety analysis. FMEA provides engineers with valuable information about failure modes of system components as well as procedures for error detection and recovery. In this paper we propose an approach that facilitates representation of FMEA results in formal Event-B specifications of control systems. We define a n...

2008
Katalin M. Hangos Erzsébet Németh Rozália Lakner

An ontology for representing operating, safety and control procedures is proposed in this paper that supports diagnosis based on following these procedures and combining observed malfunctions with Failure Mode and Effects Analysis (FMEA) information. The procedure ontology is defined within interconnected components of the process plant, diagnostic analysis (where the FMEA is described) and pro...

Journal: :Health information management : journal of the Health Information Management Association of Australia 2004
Khin Than Win Hai Phung Lis Young Mai Tran Carole Alcock Ken Hillman

This article discusses the risk assessment of a health information system. A case study was conducted at the South Western Sydney Area Health Service to examine the potential risks of the Maternal and Infant Network (MINET) health information system using Failure Mode Effect Analysis (FMEA). FMEA was conducted by utilising safety attributes identified by the authors. Potential failure modes of ...

2016
Andre Rusli Osamu Shigo

Requirement elicitation is a very critical step in software development. In order to develop adequate software which answers to user’s needs, it is essential to understand the real-world environment, the users themselves, goals, constraints, and risks and its possible solutions. Unable to describe correct requirements can lead to a massive software development failure. This paper aims to propos...

Journal: :Transfusion 2013
Yao Lu Fang Teng Jie Zhou Aiqing Wen Yutian Bi

BACKGROUND The aim of blood transfusion risk management is to improve the quality of blood products and to assure patient safety. We utilize failure mode and effect analysis (FMEA), a tool employed for evaluating risks and identifying preventive measures to reduce the risks in blood transfusion. STUDY DESIGN AND METHODS The failure modes and effects occurring throughout the whole process of b...

2005
Torgrim Lauritsen Tor Stålhane

Even if the application developers produce software in accordance with the customer requirements, they cannot guarantee that the software will behave in a safe way during the lifetime of the software. We define a system as safe if the risks related to its use are judged to be acceptable [1]. Safety must not be confused with security which broadly is defined as keeping the system unavailable for...

نمودار تعداد نتایج جستجو در هر سال

با کلیک روی نمودار نتایج را به سال انتشار فیلتر کنید